[Miscellaneous Android Development] aicjofs:
Updated to Kitkat on the Nabi_2S. I'll put my notes here.

Software version is now 2.0.141107. I'd imagine to get the OTA link for next update would be http://updates.fuhu.com/updates/android/SNB02-NV7A/US/xxx/2.00.141107/FIH-PUBLIC/updates.json? or maybe http://updates.fuhu.com/updates/android/SNB02-NV7A/US/xxx/2.0.141107/FIH-PUBLIC/updates.json?

Here is the backup of the Kitkat ROM with addon(called preload in recovery now), boot and recovery.

https://drive.google.com/file/d/0B08qqrSbn4djRl9PaF9PSzktSGc/view?usp=sharing

The kernel flag for showing config.gz in /proc wasn't set when they built the kernel so I didn't grab that.

I didn't look close but it looked like the Wifi was different Broadcom chip.

The kernel cmdline for original Nabi on 2.4

tegraid=30.1.3.0.0 mem=1022M@2048M androidboot.hw_ver=15 commchip_id=1 androidboot.cpuid=xxxxxxxxxxxxxxxx androidboot.commchip_id=1 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=4919296@0xacc23000 core_edp_mv=0 power_supply=Adapter audio_codec=rt5640 board_info=f41:0:1:0:0 tegraboot=sdmmc gpt gpt_sector=15532031 android.kerneltype=normal

The kernel cmdline for Nabi2S on 2.0

tegraid=30.1.3.0.0 mem=1022M@2048M commchip_id=0 androidboot.countrycode=US androidboot.serialno=xxxxxxxxxxxxxxxxxxxx androidboot.tegra.cpuuid=xxxxxxxxxxxxxxxx androidboot.commchip_id=0 video=tegrafb no_console_suspend=1 console=null,115200n8 debug_uartport=lsport,3 usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabc01000 core_edp_mv=0 displayboard=0x8037:0xc500:0x41:0x80:0x00 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=30539775 modem_id=0 androidboot.hw_ramcode=03 androidboot.board_strap=5 androidboot.board_deviceid=0 androidboot.bootloader=20140612.18:10 androidboot.hw_dram=1024 androidboot.panel_id=0 android.kerneltype=normal

EMMC STRUCTURE (2GB for /cache? really?)

179 0 15269888 mmcblk0

179 1 8192 mmcblk0p1

179 2 8192 mmcblk0p2

179 3 2048 mmcblk0p3

179 4 2048 mmcblk0p4

179 5 2097152 mmcblk0p5

179 6 1572864 mmcblk0p6

179 7 2097152 mmcblk0p7

179 8 2048 mmcblk0p8

179 9 32768 mmcblk0p9

179 10 2048 mmcblk0p10

179 11 9435136 mmcblk0p11

179 32 4096 mmcblk0boot1

179 16 4096 mmcblk0boot0

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 495852 128 495724 0% /dev

tmpfs 495852 16 495836 0% /tmp

/dev/block/mmcblk0p7 2064208 33572 2030636 2% /cache

/dev/block/mmcblk0p11 9287000 1781200 7505800 19% /data

/dev/block/mmcblk0p11 9287000 1781200 7505800 19% /sdcard

/dev/block/mmcblk0p6 1548144 1001400 546744 65% /system

/dev/block/mmcblk0p5 2064208 749636 1314572 36% /preload

TWRP

Here is my device source

https://github.com/aicjofs/android_device_fuhu_nabi2S

Like the Dreamtabs Fuhu has left only 8MB for the recovery partition while ballooning the size of the kernel. I had to shoehorn the recovery on to the Dreamtab by reducing image quality and sticking with TWRP 2.7.1. I did the same here except didn't have to mess with the images, there is probably 160kb left so maybe we can get a later TWRP without much effort. Just not that interested in doing it.

They also have decided to call the addon partition addon in Android but preload in recovery. I have TWRP call it preload so that it will be in sync with how Fuhu does OTA's. I also had to make a change to the ro.product.board and device so the TWRP I put up a few post back is replaced with the one I'll attach here.

TWRP should allow you to root the device.

-unlock bootloader (fastboot -i 0x0489 oem unlock)

-boot TWRP to memory (fastboot -i 0x0489 boot recovery.img)

-install Super SU.zip http://download.chainfire.eu/supersu

Quick video for advanced beginners http://youtu.be/UY9_M_-AvMU

Other thoughts

With the last update they are getting most of their current devices on the same launcher, it at least looks congruent among devices. The Nabi port(for charging and syncing) is now the same on all current devices. No mini HDMI although perhaps there is a cable that can pass HDMI. At $180 for the 2S when the Dreamtab has been going on sale at $129 every week I can't see why you would buy this.

I was hoping we could use some of this to get Kitkat on the Nabi2 Original it a somewhat simple fashion. I don't think that's going to be the case.

Using 2S Kitkat kernel on Original via TWRP. Gray screen. Device comes up, can interact via ADB.

Using 2S Jellybean Kernel on Original via TWRP. Gray screen. Device comes up, can interact via ADB.

Using bootloader.bin from 2S on Original via nflash(i.e. nvflash --bl nabi2Sbootloader.bin blah blah). Gray screen. nvflash performs the commands given.

I'm not sure its looking in the wrong memory address for the frame buffer, or if it can't drive the original panel.