Repartition Nabi2 to remove / reallocate "addon" partition? - Fuhu Nabi 2

All,
I've done quite a bit of searching and can't seem to find a good tutorial or method for re-partitioning the NABI2-NV7A to remove the "addon" partition and reallocate its space elsewhere. I would ideally like to put the extra space in the system and data partitions. Has anyone successfully done this? Is it a bad / more risky than normal for XDA users are used to?
I currently have the 3.0.13 KK debloated ROM from n3wt and the latest TWRP 2.8.5.0v2 from aicjofs installed, as well as Links2SD setup with a second ext4 partition on my SD card. I have formatted the addon partition per terminal command instructions for the Nabi2 found elsewhere. Links2SD is not always reliable as it often causes the system to hang when moving data to the second partition. I have seen the post from ashahin1 that sets up this similar second partition without the need for Links2SD - is this more reliable?
Any advice or direction someone can send me in would be very helpful. Thanks!

---

Gabes Dad said:
All,
I've done quite a bit of searching and can't seem to find a good tutorial or method for re-partitioning the NABI2-NV7A to remove the "addon" partition and reallocate its space elsewhere. I would ideally like to put the extra space in the system and data partitions. Has anyone successfully done this? Is it a bad / more risky than normal for XDA users are used to?
Click to expand...
Click to collapse
The only way is by nvflash, and I am a little fuzzy on the whole thing since it was so many years back. The only solution that was "tested" was using some of the cache partition and putting it in the system partition. I created that solution and somewhere between 5-10 users used it and it worked. I also documented increasing data partition and found that while the tablet ran mounting /data/media/ was having issues. I wouldn't say it was any more risky or bad but it is definitely a very high user understanding to implement it. I have a tool posted somewhere here that does some of it by script but what you want would need to be developed for the data and addon partition(which could then be scripted). Short version. Taking from cache and adding to system worked no issue, increasing data(and I forget from where i took it) had some bugs that I think could be worked through but I stopped at that time.
I'll try and find a link to my notes but in general the issue is that the repartitioning through nvflash is not 100% perfect. There are 3 partition tables, one nvflash uses and a GPT style linux kernel uses(and it's backup). If I remember correctly when formating in nvflash it updates both partition tables but won't boot unless you restore the old nvflash PT(leaving the new modded GPT). It's also best not to remove a partition but shrink it down. In example below I wouldn't get rid of addon but make it 2097152 from 1572864000 then use the left over space to put on data.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You really can't go wrong as long as you grab the first 3 partitions before you start editing. The script I have out there makes a file "bricksafe.img" of those partitions.
Code:
nvflash --bl bootloader.bin --rawdeviceread 0 3072 nabibricksafe.img
Really as long as you have that it is impossible to brick a Nabi2(hardware failure not withstanding). Another common issue is the Nabi2 original came in 2 versions, 18 partitions, and 19 partitions. It's important to figure out which you have before starting. I could go on and on about this but it's been a month since your post so you may not care any more, or you may read what I have said so far and not want to try it so I will save my breath unless you want to try it.
This is where I start talking about nvflash stuff
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
there is a few more after this but more or less the end of my using it
http://forum.xda-developers.com/showpost.php?p=49435879&postcount=2182
I currently have the 3.0.13 KK debloated ROM from n3wt and the latest TWRP 2.8.5.0v2 from aicjofs installed, as well as Links2SD setup with a second ext4 partition on my SD card. I have formatted the addon partition per terminal command instructions for the Nabi2 found elsewhere. Links2SD is not always reliable as it often causes the system to hang when moving data to the second partition. I have seen the post from ashahin1 that sets up this similar second partition without the need for Links2SD - is this more reliable?
Any advice or direction someone can send me in would be very helpful. Thanks!
Click to expand...
Click to collapse
I have honestly never been very interested in making external SD work as increased storage(nor do I own a Nabi2 anymore) but I told people for a long time that ramdisk was the way to go, so ashahin's method is one I would prefer although again I have never tried it.

---

aicjofs, thanks for all the great info! I'll do my homework and give it a try. My son recently got a gen 5 7" kindle fire. It's nice and I'm trying to resist the urge to do any mortifying to it. So that means I can play around with his old Nabi2 without upsetting him. I have some experience using nvflash to in brick my wife's old Asus Transformer TF100.
I'll let you know how it turns out.