New custom firmware for MK802IV

[jpci]

Hello,

Surfing on the web I found this new custom firmware. It's based on official rom from 2012-05-23

http://www.arctablet.com/blog/forum/rockchip-rk3188-android-mini-pc/rikomagic-rkm-mk802iv-android-4-2-2-custom-root-firmware-version-20130523/

Custom firmware features:

• root with latest SuperSU version 1.30 (free version)
• removed most Chinese and unnecessary applications
• Google Play Store fixes so more application are visible/compatible
• updated busybox v1.21.0.git (2012-11-29)
• Unix like init.d boot scripts support, more details on init.d scripts here
• changed permissions on external sdcard to allow write access

I can't try until tomorrow, if anybody try before, please comment.
Regards,

[Nugmast3r]

I would hardly call this custom firmware. Has all the same issues as the stock JB rom. The only difference between the two is superuser comes preinstalled. I'd wait until Neo, Bob, or one of the other developers here comes out with a real usable ROM.

[jpci]

Hello,
Yes, I also do not know where is the limit to determine if a rom is a custom rom or just a crude copy of the original with slight alterations. And so, without trying.
I'm with you on that, Finless and NeoMode have done very interesting things and solved many of the problems that manufacturers of mini-pc's have not been able or unwilling to solve for us.
Like you, I hope that they will soon get a good and reliable firmware.
But from there to undervalue the work of others, not me, sorry.
Regards,

[Finless]

Neomode and I talked today about the 3188 issues common to all these ROMs. He has this stick and we will work together to make a better ROM.

Nothing against Arctablet but most their ROMs add no value other than root or things they find here or on XDA on how to make things better. They are not developing (like taking apart framework, editing .smali code, etc), they are just rooting. All fine and good and no offense to them, but we are fixing things and not just rooting.

Just need the time....


Bob

[aloksinha2001]

Neomode and I talked today about the 3188 issues common to all these ROMs. He has this stick and we will work together to make a better ROM.

Nothing against Arctablet but most their ROMs add no value other than root or things they find here or on XDA on how to make things better. They are not developing (like taking apart framework, editing .smali code, etc), they are just rooting. All fine and good and no offense to them, but we are fixing things and not just rooting.

Just need the time....


Bob

I have been struggling with the 802IV

Here is my problem.
1. I am able to extract the image files.
2. sysimg is being modified and works with these modifications - no problems there.
3. boot.img - we were able to open it up, only using split_bootimg.pl
Mounted the RAM disk.
Were able to make CHANGES in the RAM disk
4. Packed it up with mkbootfs, mkbootimg package, created a new boot.img. Confirmed that my changes are here.
5. Created the complete package again... using afptool followed by img_maker_rk3188 - (when I re-open this package, I can see my new bootimg inside) - so far so good.
6. Flashed the new ROM, using rkbatch flash tool. System booted. All things working OK !!
7. BUT...
None of the changes made in the boot.img file have taken effect... its as if, there is another boot.img file, somewhere that seems to have overwritten my changes.. (For test purposes, I had made changes to init.rc, init.usb.rc and I had created an empty file in the root of the boot.img) - All changes made in the system.img file appears nicely...

Diagnostic
1. I used adb shell, rkflash to flash the newly made boot.img... it flashed ok... Rebooted.. and AGAIN the changes were lost... it would seem that there is another boot.img somewhere which kind of overwrites the boot image file. ??
2. I used 1.37 flash tool, from finless 1.5a tronsmart... copied my parameter file from this ROM, and flashed ONLY the boot.img, again, flash went off well (with some tinkering on parameter file), system came up, and once again had no changes that I had made...
3. used adb, to extract the update, and kernel file from live device... - the update DID NOT have the system.img file.. only 290MB as compared to 490MB of total kernel. However, could not work on the boot.img file much. It does NOT have ANDROID header, it does NOT appear to be cramfs, and split_bootimage did not work on it ...

Where is this new (different boot.img stuff coming from).. When I do a double check on the boot.img within the kernel image, I can see the changes inside the boot.img ??

Any ideas ?

Alok

[jpci]

Hello, Finless.

Neomode and I talked today about the 3188 issues common to all these ROMs. He has this stick and we will work together to make a better ROM.

No doubt it.
I hope you have enough time and opportunity, and soon we see another of your accustomed good jobs.
regards

[randymorristx]

Just a quick note to Bob and Neo. Thank you for delving into this device. Until I saw that you two were working on it, the future was looking bleak, lol. Looking forward to your usual stellar, stable work.