Share this post

Link to post

Share on other sites

More likely setting up a vendor folder & getting all hardware to work in a clean aosp rom?

^this is much more important than a recovery image for now. These Rockchip based tablets are handled differently from most other Android devices so you'll find that making a recovery image will actually be a lot more work.

0

Share this post

Link to post

Share on other sites

^this is much more important than a recovery image for now. These Rockchip based tablets are handled differently from most other Android devices so you'll find that making a recovery image will actually be a lot more work.

Share this post

Link to post

Share on other sites

RKAndroidTool works perfectly on the device. There's also the AFPTool (by Wendal) which packs all the images to an update.img, that can be flashed using the official tools. (if you want, I'll upload those later).

I've tried setting up an android vendor, but without the kernel (which they are obligated to give us by GPL), it's rather useless.

After 3 mails, they still haven't sent me the source.

0

Share this post

Link to post

Share on other sites

RKAndroidTool works perfectly on the device. There's also the AFPTool (by Wendal) which packs all the images to an update.img, that can be flashed using the official tools. (if you want, I'll upload those later).

I've tried setting up an android vendor, but without the kernel (which they are obligated to give us by GPL), it's rather useless.

Share this post

Link to post

Share on other sites

Yes, but without kernel source, there are some things you can't. e.g. the cpu is UV'd, change some drivers, add better bluetooth functionality.

Making a ROM for the current one, is really useless. We could base it on the RockChip SDK2 firmware though, since that kernel sort of 'rocks', except the touchscreen driver is inverted there (or somewhere in framework.jar, not sure yet)

If anyone's interested working on it today, irc.freenode.net #andypad

1

Share this post

Link to post

Share on other sites

I'm doing some dev work for RK2808/RK2818 tablets from last year. I wrote some program, e.g. generate CRC for kernel/boot/recovery.img, dump ROM images on live tablet via broken MTD driver(it was terrible on 2808/2818), unpack update.img(like as AFPTool.exe from rockchip, but it can work other than Windows), and read/write flash ROM from PC via USB(like as RKAndroidTool, but w/o Windows).

I also made/making CyanogenMod7 for RK2818. very recently I got Yuandao(Window) N50, which have RK2918, and I want to make CM7 for it too.

Share this post

Link to post

Share on other sites

I have only Yuandao(Window) N50DT. I think it will work on other tablets, but it may need some modification for them. this is first one, don't expect so many. I need your info to support more tablets.

please download boot.img(ramdisk) and system.img(in zip). you need at least 144MiB system partition. you can flash these images with RKAndroidTool or rkflash/rkflashtool, or you can use these images to make custom upate.img based on your stock update.img. (replace only boot.img and system.img. do not use update.img for other tablets, otherwise your tablet will be bricked)

if you are using SDK2.0 based ROM, your stock boot.img may include kernel and you may not have separated kernel.img. then, you need to split boot.img into kernel and ramdisk, and you need to make kernel.img from it.

$ unpackbootimg -i boot.img
$ rkcrc -k boot.img-zImage kernel.img

don't forget to add/flash kernel.img into your update.img/ROM. flashed kernel.img will be used if boot.img/recovery.img is pre-SDK2.0 format, i.e. it has only ramdisk and no kernel.

new format used in SDK2.0 based ROM is almost same as common format for android. in general, mkbootimg can generate it. but Rockchip changed something. I can't regenerate same SHA1 hash value in header of boot.img(offset 0x240 bytes). it may use another value to generate hash, or it may not be SHA1.

anyway, we can split kernel and ramdisk from SDK2.0 boot.img, we can make pre-SDK2.0 kernel.img and boot.img(ramdisk) from it, so it should not be a problem.

--

if you want to build CM7 yourself, please use following repo as a base.

this is my free time project. I can do something only if I have enough time, and generally I have no time at all. if you want something, you can use my files freely. I may not be able to answer your question/request so many.

Share this post

Link to post

Share on other sites

about wlan, Realtek chip is used on N50DT. it may be different on your tablet. there are firmwares for Atheros, Broadcom, Marvell chip in /system/etc/firmware/ in stock ROM. you may need to copy them into /system/etc/firmware/ in CM7 image.

about accelerometer, buttons, touchscreen, and any other input devices, it may be different on your tablet. you may need to modify init.rc and/or some files in system.img.

about bluetooth and GPS, there is no on-board chip on N50DT. I'll add support for USB dongles. if you have on-board chip, you may need to modify init.rc.

about HDMI, there is no HDMI port no N50DT. I'm not sure how to use it.

if you want to make old format kernel.img/boot.img from SDK2 boot.img(kernel+ramdisk), please use "unpackbootimg -i" and "rkcrc -k" commands.

you can use old format kernel.img/boot.img with SDK2 bootloader/kernel.

if you want to make ext3 system.img, please make empty ext3 image, mount it, then extract cramfs/yaffs2/something system.img on it. you need to preserve permission, owner, group info.

you can use ext3 system.img on pre-SDK2 ROM with necessary modification to init.rc.

* misc.img

it just contain command for recovery. normally it's "wipe all" command. if you flashed it into misc partition, next boot will go into recovery, and "wipe all" will start automatically.

(it's not "must" thing for wipe. there is another way to wipe)

* very first logo on boot.

I think first logo is in kernel. it's same as tux(penguin) logo on Linux.

(I'm not sure on RK2918. but it's true on RK28x8)

* MTD partition layout

there are 2 info, one for kernel, one for flash tool. both need to be synced.

for kernel, there is CMDLINE: ... mtdparts=... in parameter file. you can change it with text editor.

for flash tool, there is offset/size info in header of update.img. it should be generated by AFPTool.exe with definitions in HWDEF file. there is no HWDEF for RK2918 ROM, but this way works for RK2818 ROM.

or, my rkafpack tool can set these values without HWDEF file. I confirmed it works for RK2918 ROM.

or, RKAndroidTool.exe can be used.

anyway, when you try complete new ROM (e.g. my CM7) first time, you should not change anything. please confirm procedure with working image at first, then verify what works, or not works. then you'll know what need to be modified/added for your tablet.