RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hipboi has quit [Ping timeout: 246 seconds]
ganbold_ has quit [Ping timeout: 240 seconds]
hipboi has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
npcomp has quit [Ping timeout: 245 seconds]
npcomp has joined #linux-rockchip
npcomp has quit [Client Quit]
npcomp has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
hipboi has quit [Ping timeout: 244 seconds]
RayFlower has joined #linux-rockchip
hipboi has joined #linux-rockchip
npcomp has quit [Quit: leaving]
npcomp has joined #linux-rockchip
npcomp has joined #linux-rockchip
npcomp has quit [Client Quit]
npcomp has joined #linux-rockchip
npcomp has quit [Client Quit]
npcomp has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
Astralix has joined #linux-rockchip
Astralix1 has quit [Ping timeout: 250 seconds]
hipboi has quit [Ping timeout: 246 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
hipboi has joined #linux-rockchip
naobsd has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
naobsd has quit [Ping timeout: 246 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
nighty^ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
benja` is now known as benja
benja is now known as benja`
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
wildea01 has joined #linux-rockchip
dlezcano has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cristian_c has joined #linux-rockchip
<cristian_c>
Hi
<cristian_c>
I don't know how to get a root shell for a mk809iii
<cristian_c>
Any ideas?
<cristian_c>
a working root shell
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd>
su
<cristian_c>
naobsd, su is not found
<cristian_c>
if I install shells
<cristian_c>
also if device is rooted
<cristian_c>
I've tried also to install su
<naobsd>
rockchip device is not protected at all, you can do anything install/replace/etc
<cristian_c>
naobsd, I can't launch root commands , for example 'reboot'
<cristian_c>
I get 'not allowed'
<naobsd>
cristian_c: just modify firmware
<naobsd>
I think you already learn about tools
<naobsd>
why people want to get root is because firmware is protected on major devices such as xperia, galaxy, etc
<naobsd>
but we can do more than root on rockchip
<cristian_c>
I can't mount /system in recovery and I can't boot from the device
<cristian_c>
*reboot from the device, but only by adb
<naobsd>
I can't understand why you can't because you don't explain more than "I can't".
<cristian_c>
ok
<naobsd>
I don't know what software is running on your device
<cristian_c>
naobsd, about the reboot problem
<cristian_c>
I've tried this command in a shell but i get 'not allowed'
<naobsd>
because you're not root
<cristian_c>
sushell insteead tells the device is not rooted, but it lies
<cristian_c>
naobsd, no, I've rooted the device
<cristian_c>
droid inspector also says it's rooted
<cristian_c>
and if I type id from adb shell
<cristian_c>
I get 0 and 0
<naobsd>
I guess you're using Android 4.4
<cristian_c>
no, 4.2.2
<naobsd>
I don't know how did you get root
<naobsd>
I have no interest about any rooting app and related app
<cristian_c>
naobsd, I can link
<naobsd>
no thank you
<cristian_c>
ok
<naobsd>
you can put shell binary with setuid root into firmware
<cristian_c>
ok
<naobsd>
I forgot detail but modifying /default.prop just work on some rockchip
<cristian_c>
ok
<naobsd>
ah, recently factory modify stock rom terribly
<naobsd>
on my RK3288 box, su command is replaced :( it needs superuser app(or something like that) interaction
<naobsd>
default "su" or "adb root" by rockchip worked on many rom, but recently factory modify rom badly :(
hramrach_ has quit [Remote host closed the connection]
hramrach_ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd>
btw, I don't so much about "rooting" on rockchip because it's totally unnecessary
<naobsd>
ro.secure in /default.prop can be modified easily
<naobsd>
put setuid root binary into somewhere is easy too
<naobsd>
since Android 1.5/RK2808A device.
<cristian_c>
ok
<cristian_c>
ro.secure=0
<naobsd>
ro.debuggable=1 may be needed, I forgot detail :(
<naobsd>
and it may not work on newer Android. I also forgot it's 4.2 or 4.4 :(
<naobsd>
adb root is dropped when non-"eng" flavor build in recent Android
<cristian_c>
ok
<cristian_c>
ro.debuggable=1
<cristian_c>
value is already 1
<naobsd>
last time I tried, I thinkg I just put setuid root shell binary into boot.img like as /xxx
<cristian_c>
ok
<cristian_c>
naobsd, I can use root command from adb, but not from device
<cristian_c>
*commands
<naobsd>
"adb root" is just an adb argument, not command binary
<naobsd>
same as "adb shell", no command named "shell"
<naobsd>
command -> binary
<cristian_c>
ok
<cristian_c>
I can use root commands from adb shell
<cristian_c>
connected via adb
<naobsd>
what's "root command"? "shell with root right"?
<cristian_c>
yes, I can use many commands they need root permissions
<cristian_c>
but only via adb
<naobsd>
what's "not from device"? terminal app?
<naobsd>
well
<naobsd>
you could solve your problem? not yet?
<cristian_c>
yes, I can't use these commands into android shell app
<naobsd>
reasonable, shell invoked from adb and app are different
<naobsd>
and your problem is using root command from android terminal app?
<cristian_c>
naobsd, you have told me that I can modifying the formware putting setuid root shell binary into boot.img
<cristian_c>
naobsd, yes
<cristian_c>
so not using the connection with computeer
<cristian_c>
*computer
<naobsd>
then, many things discussed on here were worthless.. :(
<cristian_c>
?
<naobsd>
please explain what do you _really_ want clearly :(
<cristian_c>
I think I can use dd command to extract boot .img
<cristian_c>
*boot.img
<naobsd>
try setuid root shell from terminal app
<naobsd>
well
<naobsd>
I think you tried rkflashtool
<cristian_c>
naobsd, I want to type am command in cwm recovery via adb, but am is not present in recovery, so I was told to mount /system in recovery, but mount command returns error
<naobsd>
you may use dd
<naobsd>
well
<naobsd>
what error?
<naobsd>
well
<cristian_c>
invalid argument
<naobsd>
I have no idea what you typed
<naobsd>
anyway
<naobsd>
you can use rkflashtool
<cristian_c>
~ # mount -o remount,rw /dev/block/mtd/by-name/system /system
<cristian_c>
mount: mounting /dev/block/mtd/by-name/system on /system failed: Invalid argument
<cristian_c>
naobsd, ok
<naobsd>
-t ext4
<cristian_c>
I've tried t option too
<naobsd>
mount /system should be easy too
<naobsd>
well
<naobsd>
why remount?
<naobsd>
I think cwm don't mount it read-only
<naobsd>
and cwm don't mount /system automatically
<naobsd>
you just did copy&paste thing?
<cristian_c>
/system is existing in recovery /
<cristian_c>
naobsd, no
<cristian_c>
but /system/bin is empty
<naobsd>
empty /system directory is required, avaiable
dlezcano has quit [Remote host closed the connection]
<naobsd>
what I asked is system partition is really mounted on /system
<naobsd>
btw, it can be mounted by cwm menu too
<cristian_c>
Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE
<cristian_c>
with t flag
<cristian_c>
naobsd, I don't see the menu entries
<cristian_c>
naobsd, I've to change resolution
<cristian_c>
using am command
<naobsd>
no
<naobsd>
cwm is not android
<naobsd>
no am command
<naobsd>
any android way cannot be used
<naobsd>
please answer why you specified remount and/or system partition is really mounted
<cristian_c>
I think system is not mounted, also if it's present in /
<cristian_c>
when I'm in recovery mode
<cristian_c>
naobsd, I was suggested to use remount option
<naobsd>
then, no -o remount,rw please
<naobsd>
by who?
<cristian_c>
naobsd, I've tried also without o flag
<cristian_c>
naobsd, an user has suggested me to mount system to use additional commands
<cristian_c>
that are not present in recovery mode
<naobsd>
what additional command do you need??
<cristian_c>
naobsd, but not in this channel
<cristian_c>
fdisk, for example
<cristian_c>
and others
<cristian_c>
naobsd, without option flags, always I get usage command help
<cristian_c>
~ # mount -o -t ext4 /dev/block/mtd/by-name/system /system
<cristian_c>
sorry
<cristian_c>
I'm very stupid
<cristian_c>
~ # mount -t ext4 /dev/block/mtd/by-name/system /system
<cristian_c>
mount: mounting /dev/block/mtd/by-name/system on /system failed: No such file or directory
<naobsd>
is /dev/block/mtd/by-name/system exist?
<naobsd>
I cannot remember I added that code into cwm
<naobsd>
mount -a may work
<cristian_c>
oh, in cwm mount and /proc/partitions don't show the system partition
<cristian_c>
but only in android
<naobsd>
well...
<naobsd>
cat /proc/mtd
<cristian_c>
mount: mounting /dev/block/mtd/by-name/system on /system failed: No such file or directory
<naobsd>
you can see partitions
<cristian_c>
mount -a
<cristian_c>
no partitions in /proc/mtd in recovery mode
<cristian_c>
dev: size erasesize name
<cristian_c>
~ #
<naobsd>
I see
<cristian_c>
this is a strange result for me
<naobsd>
kernel module is not loaded properly
<naobsd>
of course, it's strange
<naobsd>
but please don't assume everything (include typed command) fine, "it doesn't work" is too short to explain problem :(
<cristian_c>
you are right about this
<naobsd>
I think
<naobsd>
put setuid root binary into firmware, and flash it, it shortest way...
<cristian_c>
rkflashtool
<naobsd>
(btw, nand/mtd should work fine if recovery image is created properly)
<naobsd>
sorry, I don't have any time now
<cristian_c>
naobsd, than k you, I'll use dd to extract boot.img
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
bengal has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
benja` is now known as benja
benja is now known as benja`
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cristian_c has quit [Quit: Sto andando via]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
dlezcano has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
BorgCuba has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
naobsd has joined #linux-rockchip
libv_ has joined #linux-rockchip
userx__ has quit [Quit: Page closed]
libv has quit [Ping timeout: 250 seconds]
<BorgCuba>
naobsd, I was able to upload and execute some test code using uboot
<naobsd>
BorgCuba: good
<BorgCuba>
but when I try to run a zImage I do get "Compressed data violation" "-- System halted" for now
<naobsd>
who print that message? u-boot? kernel?
<BorgCuba>
the kernel
<naobsd>
ah, zImage uncompress
<BorgCuba>
yes
<naobsd>
then, Image?
<BorgCuba>
I try
<naobsd>
btw, what you sent is zImage, not kernel.img (KRNL header etc)?
<naobsd>
hmm
<BorgCuba>
okay, for a plain "Image" it stays silent
<naobsd>
which u-boot are you using?
<naobsd>
oops
<BorgCuba>
this "neo tech" git version
<naobsd>
I'm not sure how much memory is mapped by u-boot
<naobsd>
can you try small code such as barebox?
<naobsd>
instead of kernel
<BorgCuba>
but I must say that I am doing no preparations like setting up an ATAG list, the code only jumps to the specified memory address
<naobsd>
ah
<BorgCuba>
I tried a super small file and that works
<BorgCuba>
like 32bytes
<naobsd>
I think u-boot does something for ATAG etc
<BorgCuba>
which repeatedly sends '.' via uart
<naobsd>
haha
<naobsd>
kernel could say "Compressed data violation"
<naobsd>
good signal :)
<BorgCuba>
but downloaded the uploaded code and did a diff and the data seems to be okay
<naobsd>
you modified u-boot to do just "go (address)" ?
<naobsd>
then memory map should be fine...
<naobsd>
probably things like "bootm" need to be done for Linux kernel
<BorgCuba>
well, I had a look at the rockchip code so I call "MMUDeinit();" and "__asm__(" msrcpsr,#0xd3");" before jumping to the code
<BorgCuba>
btw, I found out that if you upload code to "0x60000000" the argument to execute is "0x0"
<naobsd>
I see
<naobsd>
0x60000000 is start address of physical ram
<naobsd>
(for RK3188 and older)
<BorgCuba>
yes
<naobsd>
u-boot-rockchip on linux-rockchip github
<naobsd>
it loads parameter too
<naobsd>
it does some more setup before jump to kernel
<BorgCuba>
the usual way uses the code in armlinux sub directory
<naobsd>
how about mainline kernel?
<BorgCuba>
if you specify "#define LINUX_BOOT"
<naobsd>
yes
<BorgCuba>
but I am using "void UsbBootLinux(uint32 KernelAddr,uint32 Parameter)" from MainLoop.c
<BorgCuba>
let me try something
<naobsd>
probably that's what I'm thinking...but it does nothing other than mmudeinit?
<naobsd>
thank you for your work :)
<naobsd>
btw
<naobsd>
your small code can run with RK loader?
<naobsd>
RK loader exec function is alive?
<BorgCuba>
I havent tried it
<naobsd>
anyway
<naobsd>
good news :)
<naobsd>
BorgCuba: which address you loaded zImage?
libv_ is now known as libv
<BorgCuba>
I tried 0x60000000 and 0x60400000
<naobsd>
0x60408000
<BorgCuba>
okay, let me try
<naobsd>
if u-boot uses that area, we need some code to copy from another upload address to 0x60408000 before jump
<naobsd>
or change start address for kernel ;)
<BorgCuba>
okay, this does not work (no message)
<naobsd>
oops :(
<BorgCuba>
and dumping the uploaded memory it differs from what was uploaded
<BorgCuba>
so you say the kernel needs to be uploaded to address 0x60408000?
<naobsd>
well
<naobsd>
load address and start address may be different
<naobsd>
when you get compress error, which address you used?
<BorgCuba>
0x60000000
<BorgCuba>
and I also tried 0x60008000
<BorgCuba>
when I uploaded it to 6040.8000 there was no message
<BorgCuba>
and the uploaded data differed from zImage
<naobsd>
well
<naobsd>
there are load address, entry address for Image, and entry address for zImage
<naobsd>
(probably)
<BorgCuba>
looking at the u-boot map file: the code is between __image_copy_start = 6000.0000 and 6002.9f4 = __image_copy_end
<BorgCuba>
but I guess it gets relocated to somewhere else
<naobsd>
I'm confusing a little ;)
<naobsd>
let try 0x60408000 with Image
<naobsd>
I'm away for a while
<naobsd>
see you later
naobsd has quit [Quit: Page closed]
<BorgCuba>
I guess that wont work either, because when I write data to that address it get corrupted
naobsd has joined #linux-rockchip
<naobsd>
preparing dev env @home...
dlezcano_ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
dlezcano_ has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
naobsd has quit [Ping timeout: 246 seconds]
naobsd has joined #linux-rockchip
<BorgCuba>
okay, seems to work with "KRNL" image
<BorgCuba>
well, I used an older kernel image for rk3066, so the "Compressed data violation" seems to be a kernel issue
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
ssvb has quit [Remote host closed the connection]
ssvb has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
GriefNorth has joined #linux-rockchip
RayFlower has joined #linux-rockchip
GriefNorth has quit [Client Quit]
GriefNorth has joined #linux-rockchip
benja` is now known as benja
<BorgCuba>
naobsd, for testing purposes I changed the kernel address to 0x60008000 and now I can see that it boots partially
<BorgCuba>
currently I am uploading a "KRNL" image and I pass the machine id 0xbfa manually
<BorgCuba>
what else is needed to for booting the kernel properly?
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
<cristian_c>
File boot.img not a plain boot image, seeking for embedded image ... not found.
<c0d3z3r0>
oh hm
<c0d3z3r0>
i don't know maybe it's corrupt
<cristian_c>
lol
<cristian_c>
c0d3z3r0, how can I solve?
<c0d3z3r0>
what do you want to extract? initrd?
<cristian_c>
c0d3z3r0, no
<cristian_c>
c0d3z3r0, I was told that I can solve the partition mount problem
<cristian_c>
putting setuid root shell binary into boot.img
<c0d3z3r0>
I don't know anything about android … only using linux I'm sorry
<cristian_c>
ok
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
dlezcano has quit [Ping timeout: 272 seconds]
bengal has quit [Quit: Leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
froek has joined #linux-rockchip
<froek>
i'd like to get started building my own rom + android.. lots of links out there but is there a defacto guide to follow?
hramrach_ has quit [Remote host closed the connection]
<karlp>
this channel is _mostly_ focussed on regular linux,
<karlp>
android tends to be splattered across forums
hramrach_ has joined #linux-rockchip
<froek>
karlp hrm.
<froek>
so lets avoid the android part for a minute. So - with this site, I could build kernel+linux onto my Neo x7
<amstan>
karlp: i hate that.... and it seems like a lot of people from forums like that do not know what they're doing
<froek>
i'm just looking for a definitive guide for *something* that I can burn a new OS onto a rockchip device. Like, how did linuxium, or picuntu, or any of those other distributions get their env to build an image so that you can use rkloader/etc to flash the device/
dlezcano has quit [Ping timeout: 272 seconds]
<karlp>
picuntu at least is just an android kernel and a different Root File System
ssvb has quit [Ping timeout: 272 seconds]
<karlp>
I don't know about linuxium, but last I looked, it was documented ina string of forum posts and some binaries so I just ignored it.
<karlp>
neo x7 should be relatively easy to get going, as it's very similar to radxa rock,
<froek>
I've flashed picuntu before to my device, but I have yet to find something that tells me how picuntu build it's image :)
<karlp>
I'm working on neo x5 mini,
ssvb has joined #linux-rockchip
<froek>
cool
<karlp>
the general idea is "find a working kernel tree + workign config"
<froek>
so does that make sense? eg: I would like to build my own "froekuntu"
<froek>
karlp right
<karlp>
and then sign/pack the image, and use rockchip's upgrade_tool to flash it, and then just reboot.
<karlp>
the reason there's a depth of options and conflicts is that you can use initramfs or not,
<karlp>
you can put a kernel+initramfs in the kernel partition, or you can put just a kernel in one, and fs in boot, or x or y or z
<karlp>
I agree it's a poorly documented mess of assumed information
<karlp>
finding the right useful forum thread is tedious
<froek>
hehe. that's for sure.
<froek>
kernel+initramfs is fine by me.. either way at this point it doesn't matter to me
<karlp>
please, feel very free to edit/add/create pages on linux-rockchip.info
<froek>
karlp thank you very much. First link looks promising.
<karlp>
even if it's just pulling tested notes on how to do things from other forum pages.
<froek>
yeah, eventually I want to customize the linux base system itself.. change packages, etc.. maybe even change some kernel options.
<froek>
i'm more than happy to submit to linux-rockchip.info on my findings.
<naobsd>
cristian_c: btw, talk about getting root on android, customize android, etc are little of-topic here, sorry
<naobsd>
cristian_c: things like how to flash on rockchip are ok of course
<cristian_c>
naobsd, I must flash
<cristian_c>
but I can't do it
<cristian_c>
naobsd, I've tried the rktools
<cristian_c>
naobsd, i get 'invalid signature'
<froek>
karlp now for this is this just the kernel? It mentions picuntu kernel source code. However, not the OS itself, is that a valid assumption?
<karlp>
well, the "OS" is just the root file system, plus any tailoring done, that's rarely provided as anything other than just "here's my aw3s0me binaryz"
<naobsd>
Linux is name of kernel
<froek>
hrrm. so it really is pretty basic then.. kernel+initramfs and maybe some ls/cp/ld etc commands provided by the kernel?
<cristian_c>
and I tried to look for the manufacturer official site
<karlp>
no, no commands in the kernel,
<karlp>
kernel just tries to run /sbin/init
<naobsd>
distribution is distribution
<cristian_c>
but I've found nothing
<naobsd>
I recommend to use major distribution
<karlp>
first steps are getting a kernel that executes and seems to probe your hardware, then crashes when it can't find a root file system
<naobsd>
especially if you want to learn about basic things
<karlp>
when you get that far you can play with what to put on that root file system.
<froek>
i see.
<karlp>
you often put the RFS on an sd card, and flash somethign "minimal" either a plain kernel with built in modules, or a kernel+initramfs+modules that will get you to being about to mount the RFS
<froek>
right
<cristian_c>
naobsd, I've found nothing in goole about rkunpack error
<karlp>
so your choices are sort of: do you have actual vendor source for your kernel,
<cristian_c>
*google
<froek>
gotcha
<karlp>
and if so, do you want to use that old (often hacked up) version
<karlp>
or are you trying to see about runnign mainline linux,
<karlp>
regardless, the RFS is _largely_ independent,
<froek>
don't care about mainline linux actually
<naobsd>
cristian_c: sorry, too less information about your problem...
<karlp>
the hardest thing is findin a suitable "android" kernel source tree that matches your hardware.
<cristian_c>
naobsd, I've to open the image with the rktools
<froek>
karlp I plan on getting minimal enough 'OS' on there, and then only adding what I need in order to run my binary app that is currently running in any "linux" right now.
<karlp>
froek: so, in your case, you can quite likely just ignore kernel rebuilding
<froek>
obviously I have to sort out the .so dependencies and get them in the system
<naobsd>
root file system is independent, agreed :)
<froek>
karlp I suppose I could - I just want to ensure control over the entire process.
<karlp>
just take a dump of the kernel/boot and erase the RFS on nand
<karlp>
put your own RFS on sd card,
<naobsd>
installing distribution is preparing root file system. it can be done on any device/any kernel
<froek>
well - I have reasons why I don't want to use the sd card.. I have done the method you have just described, but I'd like to embed everything into the NAND and leave the SD card for mass storage later.
<karlp>
(as long as you know how to tell the existing kernel which RFS to mount from where)
<naobsd>
any kernel = prepared for your device, of course
<karlp>
froek: there's some notes in the wiki about using NAND, but note bene, the NAND driver for rockchip is rather proprietary
<froek>
i'll have a look now karlp
<naobsd>
cristian_c: hexdump -C your_file | head -1
nighty^ has quit [Quit: Disappears in a puff of smoke]
<naobsd>
cristian_c: "my" rkunpack should work. maybe rkunsign(?) distributed with "another" rkunpack will work too
<froek>
karlp now my only question is.. this all possible to flash everything once and have the kernel+initramfs+rfs on NAND in one shot of the rkbatchtool flash?
<karlp>
not sure, but why would you need to?
<karlp>
(also, there's an official rockchip tool for linux that works really well for general flashing stuff, it's just not as good for dumping arbitrary sections
<froek>
well, idealy I'd build an image, and flash on a few different devices. I just don't want to be loading sd cards on say 10 devices. Be nice if I could line en up and flash them in one go
<karlp>
do you mean the windows rkbatchtool program?
<naobsd>
many people want single image and 1step install method, it makes thing magical :(
<froek>
karlp yes - although it doesn't have to be windows. I'm just using that as an example
<karlp>
upgrade_tool di -k kernel.img && upgrade_tool di -blah wop.img & aasdfasdf works pretty well.
<karlp>
I've no experience with the windows tool sorry
<froek>
no worries - I would stick with linux anyways.
<karlp>
if you research android, you can probably take all your pieces and construct some sort of "update.zip" bundle that does "the right thing"
<naobsd>
same time people say open all steps to build it
<karlp>
so you would stick an sd card into each one in turn, and let them rebuild,
<karlp>
but I haven't tried that, and don't have any information about it personally,
<karlp>
it's a standard android thing though
<froek>
yah, I think you're right. I've started to build android from source on another box and that process is fairly straightforward.
<karlp>
but you need to get all the pieces right first anyway
<cristian_c>
naobsd, I've found the sourceforge version
<naobsd>
cristian_c: I think you could unpack recovery.img
<naobsd>
cristian_c: did you try same procedure?
<froek>
karlp yup. I'll start with kernel+initramfs and then add the +rfs part. From there I can start to build my own 'os' or slap in android if i really wanted to.
<naobsd>
I prepared miniroot for someone who want to learn about things at boot
<naobsd>
but people want complete desktop
<cristian_c>
naobsd, previously, I could unpack recovery.imh
<cristian_c>
*img
<cristian_c>
but I can't do the same with boot.img
<naobsd>
cristian_c: you have working rkunpack, you know procedure
<cristian_c>
so, I don't understand the error
<cristian_c>
maybe it's not the same thing, maybe
<naobsd>
cristian_c: are you really using my rkunpack, right?
<naobsd>
cristian_c: that header says it's rkcrc-ed gzip file
<cristian_c>
I've tried with rkcrc, but the output file is named boot-crc.img
<naobsd>
rkcrc _adds_ header
<naobsd>
rkunpack _removes_ header
<cristian_c>
to distinguish from the input file (boot.img)
<naobsd>
(actually header and trailer)
<cristian_c>
i've tried ./rkunpack boot.img
<cristian_c>
naobsd, ok, I've checked
<cristian_c>
<naobsd> cristian_c: are you really using my rkunpack, right?
<cristian_c>
I've tried neo-technologies repo , dumped with git
<cristian_c>
not yours
<naobsd>
I explained they are different
<naobsd>
this time and past
<cristian_c>
previously, I had downloaded your rkunpack, but not by git
<cristian_c>
so, by my error, I've tried with rkunpack in the rkflashtool directory, thinking it was tha same I've tried to unpack recovery.img
<naobsd>
then? worked?
<naobsd>
I also said rkunsign will work
<naobsd>
in neo-'s rkflashtool git
<naobsd>
but rkunsign doesn't warn about unusual input
<cristian_c>
naobsd, you was right
<cristian_c>
it's my fault
<cristian_c>
your rkunpack works and unpacks the boot.imh
<naobsd>
github is good for linux, u-boot, and other regular things
<naobsd>
is there any other thing which should go this mirror?
<karlp>
froek: that marvin thing is, in my mind, a hacky solution to the fact that the stock factory android kernels are full of hacky workarounds for cpu speed and resolution and hardware support,
<karlp>
mainline fixes all of that with proper device trees and standard mechanisms
<karlp>
some of the android trees out there completely fail if you try and enable two different power supply chip drivers, even if your board only has one of them and so on.
cristian_c has quit [Quit: Sto andando via]
RayFlower has quit [Read error: Connection reset by peer]