yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] katinatez:
Wow lot of questions, but I will answer.

1. To root you have 2 options

1:install TWRP recovery and on exit of TWRP it will ask if you want to root and it will do it automaticly download chainfire supersuroot.zip

2:you could download the chainfire supersu.zip and place in ext card and flash in TWRP which is found here

SuperSU/

2.Link2SD requires that you prepare the sd card first, for example in another device I rooted I use Link2SD. I partion the sdcard 12 Gb with ext2 and 20 Gb with fat32. Its really not 12GB & 20GB its more like 9GB & 20 GB. The program is free and its here

easeus_partition_master_home

3. Unrooting , yes you can. You have to download a fresh firmware from the Nabi wiki found here and extract the zip firmware and place files in the TWRP backup directory & restore from within TRWP. Just do a quick search in the thread and you will get a few results.

wiki/Fuhu_nabi_2

4. Stock or TWRP recovery, stock recovery that comes with nabi only allows to flash official nabi updates, factory reset, clear cache thats it. TWRP allows you to do backups of entire operating system or partitions, restore backups, the list go on & on. look at the key features here.

twrp2

5.fastboot/ bootloader is a fastboot command for fastboot.exe and you will also need to know about adb commands. but first you need to install fastboot & adb into your computer and that depends on which OS you are running, but a quick hint everything runs easier on linux. You are going to use fastboot to install TWRP recovery unless you use the automated Nabilab program to do that.

After you succeed in rooting YOU MUST DO BACKUP not yelling just trying to emphasize how important it is to have a backup to restore if you caught in a bootloop.

Good Luck
[Miscellaneous Android Development] pvman:
Less confused about rooting/not-rooting

Thank you so much for your answers. I think I pretty much understand. :good:

I do have some follow up questions for the quoted answers above:

1. Is the 20 GB partition in your example required to be FAT32, or will other file systems work? Why not extx? Since my Nabi is running Android 4.1 (Jellybean), which Linux file systems will it recognize?

2. So, if I understand your "unrooting" answer, once TWRP loads the "fresh" firmware, when the Nabi 2 restarts, it overwrites TWRP with the Fuhu default recovery, correct? Or is TWRP always going to be there?

3. Currently, on my PC (laptop) I'm running Vista Home Premium x64. Will that suffice? If I use something like NabiLabs to install TWRP, do I need ADB (not that I'm afraid to learn it or anything)? I guess I could fire up a VM player or something. I have a few old Ubuntu live CD's lying around somewhere, also.

Backup: I can do that with TWRP, correct? Or were you suggesting something more robust, like Titanium Backup?

Lastly, after the Dec. 19, 2013 update from Fuhu, how relevant is the process in the following thread? Can some steps now be eliminated (e.g., the PdaNet drivers)?: http://xdaforums.com/showpost.php?p=38661095&postcount=1

Again, thank you for sharing. I'm getting educated!

---------- Post added at 11:01 AM ---------- Previous post was at 10:13 AM ----------

I just took a look at the TWRP web site. I'm beginning to understand why everyone keeps recommending it. I beginning to understand this paradigm a lot better. TWRP seems VERY nice. I might consider running it on my Nexus 4 (currently stock, unrooted/unmodded, KitKat). I've put the N4 into recovery mode once before, just messing around, but didn't really do anything. Never did it with the Nabi 2.

So, in either case (Nexus, Nabi), does TWRP cause OTA updates to break? Rooted or not?
[Miscellaneous Android Development] n3wt:
Interesting discovery: Even though mostly hidden in landscape view there is just enough of settings showing to be touchable. You can't see the text at all but you can see the line beneath Notifications and there's a little bit of space under the line...if you tap that space settings will open from landscape.
[Miscellaneous Android Development] katinatez:
1. In my example I used ext2 file typeto move apps into ext2 partition and chose fat32 file because both linux and windows OS can recognize that files and I could drag and drop to both OS.

2. I believe the Stock Version 2.1.27 (417 MB) will overwrite the TWRP because there is a file inside called recovery, if you remove that file called recovery from the unzipped Stock Version 2.1.27 (417 MB) it will leave TWRP. Or you could also just use fastboot commands to install original recovery also found in the Wiki Nabi. I also recommend restoring to Stock Version 2.1.27 (417 MB) because its the last firmware that is in 1 piece as oppose to 2.3.11 that has to have two separate updates. also be aware that the TWRP to flash depends on the firmware you are on.

3.You dont need adb if you are going to use NAbilab all that is in the program. If you are going to run Linux in VM try BBQLinux found here http://sourceforge.net/projects/bbqlinux/files/x86_64/you could either run live cd or install in VM. I would use the 3-16-14 iso that installs good but cant update. I recommend this distro because it was created from the ground up by a senior dev in XDA named codeworx. It has fastboot & adb among many other thing out the box!

Yes I meant a TWRP backup of entire OS of Nabi. Titanium Backup only backs ups apps but has many other useful features.

Yes you need the PDA drivers to run Nabilab.

Once you go root you never go back, Good Luck
[Miscellaneous Android Development] Waleslie:
Removal of Addon Partition

It looks like this message board has died down quite a bit...

I am about to reinstall my son's Nabi from scratch because his wifi is having problems. So I'm wondering: Has anyone has successfully eliminated the Addon partition to gain more space in the main data partition?
[Miscellaneous Android Development] katinatez:
I have; using minimalnabi.zip found in wiki. I did not eliminate the partition but removed the apps found in the partition.
[Miscellaneous Android Development] Waleslie:
I'm aware of "minimalnabi.zip", which I might do, but I was more interested in reclaiming the addon partition and expanding the main data partition...

---------- Post added at 05:01 PM ---------- Previous post was at 04:54 PM ----------

I'm not sure what's going on with one of our Nabis. Everything has been running smoothly on both of or Nabi 2 tablets ever since the big official JB ota. Recently, one of the tablets seems to have significantly diminished wifi. The "good" tablet can see wifi signal throughout our house. The problem tablet now only picks up the wifi signal if it is within about 10 feet of the router. It seems to be all or nothing. Across a certain distance threshhold, it has strong signal. Go a bit further then it shows the network is out of range. I just tried a factory reset, but that didn't change anything.
[Miscellaneous Android Development] Waleslie:
Wi-Fi problems / Revert to older version

Factory reset didn't fix the wi-fi, so I am hoping that reverting the tablet to an older version (1.9.37) and allowing it to OTA update will solve the problem.

I seem to be running into problems reverting though. I loaded up TWRP and restored a stock 1.9.37 backup. However on reboot, it just sits at the Nabi logo. Is there something in the latest JB rom that would stop me from downgrading in this fashion?
[Miscellaneous Android Development] aicjofs:
You have Jellybean bootloader, 1.9.37 is ICS based boot.img. It will do exactly what you describe, Nabi logo and nothing else. Have to put back on the ICS bootloader, if you want to downgrade(not sure it will fix you issue though). No easy way was ever made to downgrade bootloader, except using nvflash which I outlined here. http://xdaforums.com/showpost.php?p=48683262&postcount=124

The easier way would be to make a blob from the bootloader and make a flashable zip that copies the blob to the staging partition, just we never made it.
[Miscellaneous Android Development] DarkAngel:
At one point back then on ICS, one of my daughters tablets lost wifi completely. What I did was completely reset the tablet and that brought it back. If that doesn't work you could always make a complete back up of one of the working Nabi2 and load it onto the "not so working" tablet and see if it does the trick. If not, and I don't want to say this, then it may be a hardware issue being the wifi.

Last resort ( if no warranties are still valid ) is buying a used one with a cracked screen on ebay for cheap and swapping out boards. I have taken apart my Nabi2 three times already. No problems at all though as I just did it to paint the outer case a different color. Mine is now completely Matte Black from the buttons to the Kinabis holder.
[Miscellaneous Android Development] Waleslie:
katinez -

I finally gave up and replaced the Nabi that was having wifi connection problems. Since I'm starting from scratch, I was going to apply a version of your MinimalNabi...

Since my kids don't use Nabi Mode at all, I was going to remove a bit more of the Nabi apps (all the ones you excluded, listed above). Since one of your steps was to go into Nabi mode and download the updates, can I remove Nabi mode?

I'm looking to end up with something close to a Nexus 7.

Also, the script lists several other seemingly non-Nabi apps that are deleted:

delete("/system/app/Browser.apk");

delete("/system/app/Books.apk");

delete("/system/app/Email.apk");

delete("/system/app/Exchange2.apk");

delete("/system/app/GenieWidget.apk");

delete("/system/app/Hangouts.apk");

delete("/system/app/HTMLViewer.apk");

delete("/system/app/Music.apk");

delete("/system/app/GMS_Maps.apk");

delete("/system/app/LiveWallpapersPicker.apk");

delete("/system/app/Magazines.apk");

delete("/system/app/SoundRecorder.apk");

delete("/system/app/MusicFX.apk");

delete("/system/app/PlusOne.apk");

delete("/system/app/VideoEditorGoogle.apk");

delete("/system/app/Street.apk");

delete("/system/app/Videos.apk");

Some of these seem obvious, others not so much. For example "Browser.apk" is this the stock Android browser?

Would you be able to spell out what's what here?

Also, these particular apps are in the system area, right? So deleting them doesn't gain any space for installing additional apps, does it?
[Miscellaneous Android Development] katinatez:
Yes, its the stock browser.

Yes all apps listed are in the system partition. It gains you space in the system partition. You can use Titanium Backup to make any apk into a system apk, thus reclaiming some of the system partition.
[Miscellaneous Android Development] Waleslie:
That's true. TB can make that space usable. Good point. That being said, aren't there some APKs related to phones that could be removed or are they too integral to Android?

Also, you didn't comment on my question about removing the rest of the Nabi apps, in particular Nabi Mode.
[Miscellaneous Android Development] Waleslie:
Two more questions...

1) Is there a way to view the contents of the addon partition from within ES File Exporer? I've navigated all around but don't seem to find it. Is that partition not mounted under typical operation?

2) Has any more progress been made on reallocating the space of the Addon partition to general use?
[Miscellaneous Android Development] aicjofs:
1. it's mounted as addon_res

2. the same "principle" that those external sd app linkers to /data would work in theory with addon. 2nd of course is partition editing, once JB came to the Nabi I stopped playing with nvflash since that was the main reason, that method is certainly the cleanest(just shrink addon and give all the space to data) I just never could get the internal SD(/data/media) to mount properly afterwards, granted I only spent a day doing it. Seems like most are content with linking to an external SD, give you up to 64GB of extra space, so I haven't seen many people pursuing the addon route.
[Miscellaneous Android Development] katinatez:
I did not comment on that because I can't remember at the moment. At least the specific apk names. Its all documented in this thread though. Just search for my comments in this thread.

My suggestion is follow the directory path in the Minimalnabi.zip to find the few remaining apks.

Full backup including addon partition first; then flash zip then find the remainder apks & delete to your liking.
[Miscellaneous Android Development] Waleslie:
Do I just need to modify update the "updater-script" text file and replace it in the zip or do I need to do something with update-binary too? (and if so, what?)
[Miscellaneous Android Development] katinatez:
Yes, you can use 7-zip to extract updater script modify to your liking then place updater script back in same location with 7-zip. And follow the directory of apk's listed in the updater script. Dont touch the update binary.
[Miscellaneous Android Development] Bait-Fish:
My kid's Nabi 2 typically won't wake the screen the next day after charging all night.

This is early, but three nights I have turned off its wifi at the end of the night and I haven't experienced a lock-up doing this yet. Anybody else with the same issue have any feedback?

Edit 6/14: I'm still experiencing no overnight lockups requiring a hard shutdown. Fingers crossed!

Update 6/19: I have experienced no lock-up overnight since turning wifi off for the night. Seems promising to me.
[Miscellaneous Android Development] rokenford:
I may need to do this, as i'm in the same situation you were. did you ever get it resolved completely, and how did you short the recovery solder joints? i've never had to bring something back this far from the dead.
[Miscellaneous Android Development] aicjofs:
Sounds like it was fixed. Nabi is insanely hard to permanently brick unless it's a hardware issue. http://xdaforums.com/showpost.php?p=49796661&postcount=2201

How did you get to the point your at?
[Miscellaneous Android Development] rokenford:
was trying to upgrade from a rooted 1.9.37, probably didnt read enough before getting flashappy.

flashed the JB bootloader, then JB TWRP 2.6something, then tried to flash the JB stock rom. didnt notice the flash had failed before hitting reboot button. stuck on nabi logo, no bootloader. windows doesnt detect that anything is plugged in. gonna try Linux later today. if that doesnt work, i'll have to try and get more details about the teardown and shorting the recovery solder joints.
[Miscellaneous Android Development] rokenford:
So linux (Ubuntu 14.04) also doesnt detect that the device is plugged in. i've read most of this thread, and i'm not sure where to go from here. i cant seem to find any more details about where the recovery solder joints are located, or how to short them. any help would be appreciated.
[Miscellaneous Android Development] Waleslie:
I modified updater-script in Wordpad, reinserted it using 7zip, then I get the following error in TWRP when I try to install the zip:

E:Error executing updater binary in zip '/external_sdcard/MinimalNabiWipe.zip'

Error flashing zip '/external_sdcard/MinimalNabiWipe.zip'

Not sure what I've done wrong...

I've uploaded my updater-script file (added ".txt" to make it uploadable)
[Miscellaneous Android Development] katinatez:
Start over and use notepad ++ , its free just Google it.
[Miscellaneous Android Development] aicjofs:
Did you see this? http://xdaforums.com/showpost.php?p=46694284&postcount=1701
[Miscellaneous Android Development] rokenford:
argh. i missed it. thanks. will try it and report back tonight.
[Miscellaneous Android Development] rokenford:
with difficulty i can get it to boot into APX mode, but the last step in the instructions seems to be eluding me. i'll have the first two commands be apparently successful , but then when i send the final command

nvflash --resume --go

and hold down the volume+ button, it just takes me back to where i've been, at just the nabi logo.

maybe its a matter of timing. i'll keep trying. its tricky to get it to boot to APX mode.
[Miscellaneous Android Development] aicjofs:
You were following these instructions right? http://xdaforums.com/showpost.php?p=48683262&postcount=124

That only puts the bootloader, this put the JB recovery and boot.img. Bootloader hangs if it doesn't detect one of the two. This won't hurt at this point.

http://xdaforums.com/showpost.php?p=49796661&postcount=2201
[Miscellaneous Android Development] rokenford:
Aha, looks like I need to relearn critical reading.

It worked great. Thanks so much. Now to flash a rom and see if I can get it to boot.
[Miscellaneous Android Development] rokenford:
backup to external sd (for creation of serial#folder) says successful, but when i pull the card to check it, its empty.

manually created folder based on onscreen text from backup attempt. This worked. nabi is back from the dead!

thanks so much to all who contributed. now to reassemble and get it back in the hands of the owners.
[Miscellaneous Android Development] aicjofs:
Not Nabi2 related but...

Anyone see the Nabi Dreamtab HD8 at Target or Walmart? I decided to pick one up and see what it was all about. I don't think they hit the price point with this one. Screen looks nice and sound with speakers on front are better. Feels snappy enough with the Tegra 4 and their new UI is kinda cool. Comes with a stylus which I haven't played with that is suppose to be some hybrid between an active and passive stylus, that may be interesting. Just curious if anyone else messed around with one.

Modding side

No Source yet(and even then it's been pretty terrible from them)

Unlocked bootloader. Make life so much easier. Weird that they only messed with bootloader with Nabi Jr B.

Already 1 OTA

It's rootable, and should be forever with they way they do things.

I have a recovery built but in Fuhu fashion that recovery partition is a tiny 8MB, and the recovery image is 8.5MB. I think I can get it to 8MB on the nose with some PNG, and JPG optimizations.
[Miscellaneous Android Development] n3wt:
I had not seen this one before. Looks neat.
[Miscellaneous Android Development] pvman:
repartition "System Storage"

Thanks!! I was going to do it today, so I re-read everything. That only generated more questions. The one at the forefront of my mind right now is: So, the "System Storage" partition seems to be the culprit with not allowing new apps to install. That said, is there a way to increase the size of that partition prior to reloading the OS? If so, what is a good size to start with?

I still plan on going with the Link2SD to install my apps to the SD card instad of the "Internal Storage" partition, but I assume that if the "System Storage" partition refills, I'll be back in the same situation.

I was hoping to keep all the Nabi software and bloat, but if the "System Storage" partition cannot be expanded, then I'll have to go the route of removing things.

What has gotten me confused is that we have not loaded much extra than came with the tablet (a few extra Angry Birds and some Sonic apps), so I assume this problem would occur if I was loading up stuff from the Nabi Store. Or does Nabi apps somehow use less "System Storage"? (okay that was like 3 or 4 questions :D )
[Miscellaneous Android Development] katinatez:
All your apps install to data partition which fills up quickly. I removed all nabi apps and nabi store because I have two kids with each having their own nabi, I set my Google account to purchase one app and I download it to both tablets.

With Nabi store app purchases stay with one child and only nabi tablets. If and when my children outgrow nabi I have the option of downloading all apps from play store again if I get them Nexus 7 tablets. This is why I wrote the script to remove Nabi bloat.

System partition gets apk deleted but I use up the system partition by installing apps in there as well, so as not to waste any space.

I also have both tablets with 64GB cards, but first you have to format to NTFS then format to fat32 for the Nabi to recognize. Then make a partition for ext3 for you Link2SD.

Voila plenty of storage for all your kids apps. Hope all my examples answered your questions.
[Miscellaneous Android Development] pvman:
I'm not sure my questions were answered. Let me paint a picture: So on the Nabi 2, Google Play indicated several apps that needed updating, mostly Google stuff. One or 2 updated. Nothing else would load. The errors indicated "Insufficient Space". So, I commenced to deleting apps and data. I cleared a couple of hundred megabytes. Attempted the update again. Still could not load updates.

I ran nabiMD and I noticed a memory area called "System Storage". 504 MB partition with about 1.x MB free. No matter what I delete, it doesn't change. There was another partition called "Internal Storage", it had just over 200 MB free. But, I can't install any new apps that are only KB in size or install any updates to existing apps, regardless to how small the update may be.

I beleve I've seen other forum posters describe the same situation.

Thus I concluded that either something in the "System Storage" area is corrupt and Android isn't managing it properly, OR it is working as designed and is recording some type of system data permanently as one adds apps and is not removed when the app is removed.

Either way, no matter the source of the apps or where they are stored, I'm assuming some sort of configuration data gets put int the "System Storage" partition and it would fill up no matter where it is stored in "Internal Storage" or SDcard or whether the app comes from Fuhu, Amazon, or Google. Please correct me if I got that all wrong.

Is there a standard memory configuration for JB, or does each vendor (Fuhu, Samsung, HTC, etc.) create their own memory partition configurations with custom sizes? If so, did Fuhu just design that badly?