yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] aicjofs:
OK, "System Storage" is what is known as the system partition. It's mounted as /system. Its 504MB, and while it is possible to increase that size it's something that isn't in the cards for you right now. The system partition is where the "ROM" is stored. ROM is also known as Read Only Memory. It's contents(any files) should only really be changed 3 or 4 times on a device over the course of it's life by a normal user. On the Nabi it's files are being changed when you hear about the 1.937, 2.0.5, 2.1.27 update, etc, etc. Nothing gets written here by any Google, Amazon, Fuhu or any other downloaded apps. While we have been discussing moving some thing to squeeze ever last kb out it for the most part it is read only.

Then there is "Internal Storage", it is known as the data partition. It's mounted as /data. Its ~4.5GB, and while it is possible to increase that size it's something that isn't in the cards for you right now either. The data partition on this device serves 2 purposes. 1) Store user apps, 2) Function as the "Internal SD Card". For the most part any app you install ends up /data/app, and those apps use /data/data to store the apps "stuff". There is also a folder in data called /data/media. This is your internal SD card. Your pictures, media, downloads end up here. Its what you see when you connect your tablet to a computer. Some apps also save things here. All your pain(and everyone's too) comes from this data partition.

It needs mention that there is also a partition called addon. It's ~1.5GB. It stores all the Nabi specific apps. When you start the Nabi out of the box, or after a factory reset in copies all these apk's(apps) to the /data/app folder. Although Fuhu did change this a bit in the last update, it's more or less what happens. So you have the exact same apk files(app) in 2 different locations. Yes this is a waste of space, but the only way to factory reset and still have Nabi apps. An arguably more efficient way for a tablet that only comes with 8GB of flash total would be to download all the Fuhu specific apps out of box, or after a factory reset but that has it's own issues. In effect there is 1.5GB that could only be used one time during the devices life(again that's changed a tidbit since the latest update but not much)

You need an app like Storage Analyzer. It will scan your /data partition and point you to the biggest data hogs which you can then delete. Of course you can't install it yet. See if there is something obvious on the internal SD that you can delete to free space. You need to get to 500 free.

Each vendor does there own. Fuhu's is terrible. They even waste space on the cache partition, nobody's cache is ever going to get that big. While we can bash them all we want it really was the decision to hit a price target under Nexus 7 to break in the market and the resulted in only 8GB of flash on the device. The rest lies at google's feet(and some could even argue Apple) and the elimination of the external SD card for app usage without hacking.
[Miscellaneous Android Development] pvman:
Wow!! 500 MB, huh? That is quite a bit of overhead for an app that may be less than 1 MB. Wow!!

Okay, so to do this and NOT lose any data, it seems I need to first use ADB to copy my data to my PC. App data is stored on /data/sdcard, right? If I am reading the posts correctly, Fuhu elected to mount the actual SD Card at /data/sdcard2. Please correct me if I am wrong.

I've already moved all photos/videos to the SD Card.

Once done, I can then restart and delete some apps, and then update the system.

From there I can then:

1.) Backup the data one more time (to be safe).

2.) Replace the recovery with TWRP (using ADB).

3.) Root upon restart.

4.) Do a NAND backup.

5.) Install Link2SD (or something similar).

6.) Move/link my apps to the SD Card.

7.) Reinstall the app(s) I deleted to free up the 500 MB.

8.) Copy the data back with ADB (since Link2SD is installed, do I copy it back to /data/sdcard? Link2SD mounts the physical card at /data/sdcard, right)?.

9.) If I then choose to unroot, do so by replacing TWRP with the stock recovery.

Did I miss anything?

Thanks again to you, katinatez, and all the other posters who have contributed advice to this thread. Its really been an education on Fuhu, Google, TWRP, and other related subjects.
[Miscellaneous Android Development] aicjofs:
No I was just saying freeing 500MB will give you plenty of room to do this change you want and make sure you don't get the insufficient space error, or other issues. Forget I mentioned it. Storage Analyser is only ~3MB, and doesn't need any more space to do it's thing.

No

The actual SD card,(external) is mounted at /storage/sdcard1 not at data/sdcard1

The fake SD card(internal) is mounted at /sdcard and is really /data/media

The app is at /data/apps

The apps data is at /data/data

Some apps put other stuff at /data/media.

I don't use Link2SD so I can't comment on how it symlinks . But that's what you have right now.

1.) Backup the data one more time (to be safe). If you are just talking about only /data/media(internalSD) yes. I would think it's easier to connect the tablet to PC then ADB, make sure you can see hidden files in explorer and drag everything from SD to the PC. Remember apps stuff/game saves aren't in there, but would be included in the NAND backup below, alot of people use Titanium back type app because the data is easier to work with then the NAND backup.

2.) Replace the recovery with TWRP (using ADB). A script may use ADB but it has to be via fastboot by you or the script.

3.) Root upon restart. Root will happen automatically when you exit TWRP unless you tell it not to.

4.) Do a NAND backup. YES. Make sure to check "data", this and step 1 will at least get you back to where you are now if things go wrong

5.) Install Link2SD (or something similar).

6.) Move/link my apps to the SD Card.

7.) Reinstall the app(s) I deleted to free up the 500 MB. Don't worry about this

8.) Copy the data back with ADB (since Link2SD is installed, do I copy it back to /data/sdcard? Link2SD mounts the physical card at /data/sdcard, right)?. I don't know anything about link2sd

9.) If I then choose to unroot, do so by replacing TWRP with the stock recovery. No that won't "unroot" have to use the SUperSU app to remove the binaries.
[Miscellaneous Android Development] pvman:
Wow! Okay, I guess I was way off. My original post to this thread was to get a complete ,comprehensive process to rooting the Nabi 2 and then solving my space problem with Link2SD.

I'm starting to realize there is something else going wrong here. My space problem may be symptoms of another issue. If I'm interpreting you correctly, since I have a couple of hundred MB free in "Internal Storage", I should be able to load a 1, 10, or 20 MB app, Yet I keep getting Insufficient Space errors.

It might be time to simply do a system reset, re-establish the Google account, reinstalll the apps and restore data from a backup made with a simple Windows Explorer copy (I can't install anything like Helium).

Although rooting may be in my future, sounds like it should not be my first prioritiy.

Okay, I got it:

/data/apps

/data/data

/sdcard -> /data/media
[Miscellaneous Android Development] aicjofs:
You would think your 200MB of space would be enough to install a small app, but the device won't let you install unless you have so much space. Nothing wrong with yours, it's just below the limit of free space. I forget what that limit is... 300MB maybe? Someone else might know.

Remember the windows explorer copy won't have all of your game or app saves, so that would be lost. In fact right now you should have what you can see in windows explorer down to almost nothing.
[Miscellaneous Android Development] pvman:
Well I was thinking of doing the Win Explorer thing and then running something like:

[B]adb backup -apk -noshared -all -nosystem -f nabi_[I]date[/I]_backup.ab[/B]

or -noapk, I haven't decided yet.

Wouldn't that backup the apps and app data?

I should be able to do this prior to replacing the recovery kernel, correct?

Could I not restore that after a reset, root, and fresh install of everything?
[Miscellaneous Android Development] pvman:
Install over old NabiLab?

So, do I just unzip the NabiLabLite with JB recovery.zip file and copy the folders into my C:\Users\username\appdata\Local\apps\2.0 structure somehow? How do I install this over my currently installed NabiLabs? I have version NabiLab v1.2.0.0 fromt he nabitabs web site.
[Miscellaneous Android Development] katinatez:
Unzip to C:\ then connect nabi and run program, the only difference between this one and original nabi lab, is that the install recovery option is loaded with JB recovery and installs it.
[Miscellaneous Android Development] pvman:
Thank you!!! That did it. I've finally finished the process. It took a few days, but it's done and is working very well.

I was able to install TWRP, root, install Link2SD, reclaim some Internal Storage, load a lot of new apps and in the process, I did NOT lose any data or progress.

The steps were:

Make and adb backup to backup any app data and settings I can get at without "root".

Use NabiLabLite, as it has the TWRP and SuperSU for JellyBean. After, use TWRP to do a NAND backup, just in case. I didn't need it, but you never know . . . ! If you brick the Nabi, at least you can get it back to where you started.

Repartition the microSD card (EaseUS did not work for me as it could not see the built-in card reader on my laptop. I ended up using a Linux Live CD (Ubuntu) and GParted)

Delete enough apps/data to free up enough room (at least 500 MB free of Internal Memory) to install Link2SD.

Read http://www.link2sd.info, esp. the FAQ. Install Link2SD and do some linkin'! I chose to only link the apps I've installed, not the things that came with the Nabi, although they can be linked as well. That was just a personal decision. I may change my mind on that later. Set up Link2SD to automatically link any new apps to be installed.

Perform an adb restore. Reboot and let LinkSD do its magic. If you deleted apps to install Link2SD, now that they have been restored, link those as well.

The Internal Memory should have much more free space now.

Install any new apps.

I'm happy and my kid is happy to both have his Nabi back and to have some new things on it.

Thanks to aicjofs for NabiLabs, and all the advice.

Thanks to katinatez for NabiLabsLite and the detailed explanations.

And finally, that's to all that contributed to this thread, no matter how small you posts or how much they seemed to digress. They all helped me learn a lot about Android and the Android Universe.

I know this journey is just beginning.
[Miscellaneous Android Development] DarkAngel:
Has anyone thought about trying to have a go at making a Custom Rom for this? I don't see why it wouldn't be too hard seeing that we only have to deal with the WiFi and G-sensor if anything were to not function correctly. I remember a while ago someone posting over a ROM they ported from a Nexus 7 or something similar I believe. They could not get the screen to function but when plugged in they could see it just fine. A completely different OS would be kind of cool actually.

Just wondering if anyone was interested.......

Now this doesn't mean they would be compatible with each other but would come close for a possible Port or even a build. The ones bolded in Red I found here in XDA. Others in the same family may have the same processor as well like the Asus Transformer (TF300T).
[Miscellaneous Android Development] katinatez:
Actually I was thinking of building Philz Advance CWM recovery for nabi, once I iron out the bugs on one plus one phone.
[Miscellaneous Android Development] DarkAngel:
LOL I was thinking the same thing just to see if I could make it........

Been learning a lot over the months and wanted to try and just experiment.

By chance does anyone have the stock recovery image for JB 4.1? I swear..... I can't recall if someone gave it to me or not but I can not find it anywhere in my hard drive......
[Miscellaneous Android Development] knoxploration:
I don't have the knowledge to make one, but I'd be happy to help test. Is love to see a completely stock AOSP room on the Nabi2...
[Miscellaneous Android Development] aicjofs:
Have you guys been following this starting on post 45 http://xdaforums.com/showthread.php?t=2207499&page=5

We had a few PM messages first before I asked him to put in the thread so any discoveries could be shared with others, but that is a good chunk of the info about trying custom for the NabiXD.

The kernel is going to be the biggest issue if going for a KK ROM. JB might be more possible with a prebuilt kernel but I think it's still going to be a task. Funny I mentioned someone claiming the Nexus build in that thread with sharpe351 too, I'm glad you remember that too I swore I remember reading it.

Side note: the crazy folks at fuhu updated that dreamtab HD8 to KK a couple days ago

I'm pretty sure I do, but for some reason can't ssh in to my home computer today. Why you want it? To get the zimage out? Or just take a peek at ramdisk?
[Miscellaneous Android Development] DarkAngel:
Still remember about post 1590 or so Liquid Smooth 4.2.1 Grouper is what I last remember was used.. Everything worked except the screen. KK would be a major leap for the XD and the Nabi2 but yes it would be a task. On the recovery I just want a back up really. I swore up and down I had it and never even backed it up before I flashed TWRP. Made the Same mistake with both my daughters tablets as well. I'm in no rush.
[Miscellaneous Android Development] aicjofs:
Yep that was it. As I told sharpe351(XD) the choice is trying to make the stock kernel work with Jellybean 4.2(not thinking 4.3 is good for this initially) or the kernel has to have changes for KitKat. While all the emails made a difference and I ended up talking on the phone with them the source is still useless so option 2 isn't really an option with the talent we have at our disposal until we can convince Fuhu that they are still in violation of GPL. So on option 1 I would avoid CM and try a more pure AOSP jellybean. To try and recreate where deskjet was I would think grouper is a good bet, break out Nabi zImage use the ROM ramdisk merge it and take the /system/lib/modules and firmwares from Nabi and put it all together with correct permissions. Proof of concept only.

I'll find a recovery.img. I "fastboot boot" and imaged everything from 1.9.37 to 2.3 so i just have to go through it all. Problem is "it all" is an insane amount. I have Nabi2 US, Disney and UK, NabiXD, NabiJR, Dreamtab, nvflash images. I try to keep things organized but it's not in my nature, half the reason of the Nabilabs and posts, etc is to get it out my hands and to the Internet before I completely forget what things are. Lol.

EDIT: I didn't open this but should be it.
[Miscellaneous Android Development] katinatez:
Any one know the pixel dimensions for Nabi, its 800x ?,

Never mind found it 1024x600
[Miscellaneous Android Development] katinatez:
[MENTION=4939189]aicjofs[/MENTION] hello can you update your github android_device_fuhu_mt799 with 2.3.11 kernel or can some one grab the boot.img, tired going to bed.
[Miscellaneous Android Development] DarkAngel:
The boot.img is in one of the OTA's. I would post it up but I am not home right now. If you open to view one of the two OTA.zip you will see it. It's about 5 MB.

TY aicjofs. Trying to understand the structure of this thing was something else. I am so used to my phones and using certain commands ( one being parted ) on my Galaxy devises via ADB that when I use them on the Nabi2 I can only get so far getting somewhat of the information I am looking for.
[Miscellaneous Android Development] katinatez:
[MENTION=325306]DarkAngel[/MENTION]I found the boot.img will work on Philz recovery on my weekend.
[Miscellaneous Android Development] aicjofs:
You just want the kernel(zimage) or are you wanting what I'm using as a device tree(I hesitate to call it a device tree because it's pretty much only for recovery, but the nabi2 is the most complete one)? I never pushed it because I switched to OmniROM as base instead of CM, thus I had to change the makefiles. It's also different between cm10 and cm11, for example you have to set device resolution in a different spot. If you look at my t8400n(Dreamtab) device tree it's the newer style. just change all things t8400n to mt799(file names included)
[Miscellaneous Android Development] katinatez:
Dont need the kernel, pulled the boot.img from the first 2.3.11 update.Yes already forked your device tree, I am aware of setting resolution ( in Philz recovery its set in another place).

Will take a look at the t8400n, tonight.
[Miscellaneous Android Development] Eric Karz:
I tinkerd with philz recovery (tinker mode lol) I could get it to work but I never got every thing to back up .
[Miscellaneous Android Development] katinatez:
The recovery.fstab is twrp style, did you change it to cwm style, also the you have to remove the twrp flags also.

I tried to build philz recovery but would hang on one of the make files. Have been working on websites and fixed the screenshots on philz bacon (one plus one)recovery.

Can you share your files, or let me see what you have for recovery.fstab?
[Miscellaneous Android Development] Eric Karz:
mind you that I have no real clue to what I am doing but let me upload it.

Note this is not 100% working - this only posted as science and Please do not use if u do not know what you are doing .

https://www.dropbox.com/s/z98kg6f3134fwg0/philzRecovery_test_nabi2.rar is the one I did back in march

and this one has the split image

https://www.dropbox.com/s/w6ucpfwa7zj6qm2/pilzbyname.rar
[Miscellaneous Android Development] Eric Karz:
told ya it was a tinker - that's good you are doing it the proper way . maybe when the seasons change I will get back in to it.
[Miscellaneous Android Development] amebiasis:
Custom rom?

Sorry if been answered been reading through pages but my heads spinning and I havent seen a definite answer anywhere. But can we install a custom rom Id love just to throw CM on it and call it good, older version is fine with me. Ive had nothing but issues on my sons tablet, currently the camera wont work gallery force closes when I open it, and if i open it in skype i just get green or purple lines. I even bought a new camera and replaced it so I know its software, and have reinstalled both gallery and camera apks, formated the tablet, factory reset, etc etc etc. So over this OS. Thanks guys!
[Miscellaneous Android Development] n3wt:
sounds like a bad camera.
[Miscellaneous Android Development] amebiasis:
That's what I thought but I put a brand new one in and same exact results. It keeps closing and saying unfortunately gallery closed and the screen is showing the stripes still I've installed I swear 100 different cameras from aosp to one's on the market it worked fine until I updated it months ago just got around to working on it
[Miscellaneous Android Development] th3taman:
Hoping someone can help me out. My son's Nabi somehow no longer has a System on it? It won't go past the boot screen and when I log into TWRP and try to do a backup it shows 0MB for System. I'm not really sure what happened honestly. So basically I want to get a ROM back on there so he can start using it again. It doesn't have to be stock, but that will work too. Any suggestions on ROM (JB preferable) that I might be able to flash?

Also I have TWRP 2.6.0 on there I think. I think that is ICS based TWRP. Should I be updating to JB TWRP and I thought I saw one a couple pages back, will that work?

Appreciate any help. My son is dying without his Nabi. Sadly seems to be addicted to tech like his dad.:p
[Miscellaneous Android Development] DarkAngel:
You all get the new update v2.4.6?

States as Google Security Fixes. I uploaded it for you all if you need or want it. Pulled it from my Nabi2. Have not installed it yet. Want to check it out first.

Download : v2.4.6 OTA ( 165 MB )
[Miscellaneous Android Development] aicjofs:
Yep. Seems a rather simple update when peeking inside. Does another bootloader update though. TWRP still works fine.

Here is the full stock Nabi 2.4.6 image. system, boot, addon, recovery

246stock.zip

Here is a flashable bootloader update

JB246bootloader

With those 2 files it should allow any Nabi in any condition to return to stock 2.4.6. Like the previous procedure extract the images to your TWRP backup folder and restore all, then before reboot "install" the JB246bootloader.zip. Basically this http://xdaforums.com/showpost.php?p=51037177&postcount=21 but with 246stock.zip in place of 2311stock and 2311addon zips, and the 246 bootloader zip instead of the old JBbootloader zip

Then here are some TWRP flashable OTA's, we are all kind of all over the map so making an update for everyone isn't so easy.

First TWRP flashable zip is for anyone that has rooted, has done a lock screen mod, used the 4 way reboot menu, or edited the build.prop. It will undo those changes and then do OTA

2311to246.zip

The second I have no idea if will even work. It's for anyone that applied the minimal Nabi zip awhile back. I can't test it but it ignores all those files. DONT use this one unless you know you flashed the minimal Nabi and even then it may not work.

2311to246minimal.zip

Finally I new TWRP

Nabi Specific: Add 2.4.6 kernel

TWRP Changes

Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.

Various bugfixes to backup and restore

Improvements to USB storage handling

Added a class to search for files to make finding the correct brightness file automatic in most cases

Various other bugfixes and tweaks

NABI2JBTWRP271.zip (fastboot)

twrp-recovery-JBNV7AUS-271.zip (flashable)

Latest device tree for building recovery with Omni 4.4.4 as base with 2.4.6 kernel

https://github.com/aicjofs/android_device_fuhu_mt799_omni

There ya go just enough to cause a lot of chaos. It's been too quite around here anyway... :p
[Miscellaneous Android Development] DarkAngel:
LOL TY! Always on top of it. I had dissected the OTA as well and noticed the bootloader as well.

If I am not mistaken these security updates were made out to all providers. I noticed all three of my phones bootlooped after a restart when they were done updating from Google just yesterday! The Wife's phone did it just last week. Easiest way out was to hard reset her phone, all was well afterwards. The dang Android Bug got to my phones as well unfortunately.

Well just an update..... testing on ALL my Galaxy Phones, what was causing the phone to bootloop after it updated is the Xposed Framework App or a Module from it. Can't theme my phones the easy way for now...... :(
[Miscellaneous Android Development] th3taman:
aicjofs thanks a million! Your latest files were a savior. They helped me restore my son's soft-bricked Nabi 2.

Do you know if there is a way to get rid of things like Wings that take up so much Internal Storage space? If not, you've still been a savior as I'm in must better place than before.