yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] aicjofs:
Nope. :( I have been spending most of my free time working with the Dreamtab Intel version.

We may have to have someone pop on here trying to root one and failing that hasn't upgraded yet and capture the OTA. The hard part is that the Nabi forces the upgrade on its initial boot so most people allow it to happen. You have to not setup wifi in the beginning, then use the swipe down from the clock to get in to settings and get adb, because I dont remember the ota being visble with MTP. Even the original software version number would be useful for the brute force method.
[Miscellaneous Android Development] DarkAngel:
@aicjofs

I noticed this model number on the internet for the Nabi2-S for a possible naming convention .... I just am not able to check or do anything at this time.

SN02-NV07A-WH

Walmart listed it as:

Operating System Version: Android 4.2 Jelly Bean

Model No.: SN02-NV07A-WH
[Miscellaneous Android Development] katinatez:
What's up? Dropping this off here. Tested and confirmed working both twrp 2.8.4.0 & updated minimalnabi.zip running on v2.4 nabi 2 US

Enjoy :D
[Miscellaneous Android Development] jaxbierley:
Any news with the 2S?
[Miscellaneous Android Development] aicjofs:
A little bit.

We were never guessing the update path.

http://updates.fuhu.com/updates/android/SNB02-NV7A/US/xxx/1.12.140612/FIH-PUBLIC/updates.json?

Minor Rev 140612? Haha. Ok my brute force script was not quite that brute!

Here is the update zip from Jellybean

http://cdn.firmware.fuhu.com/snb02-nv7a/N2S-JB422_01_12_140612_298_TO_KK442_02_00_141107_273_WW.zip

The 2S seems based on nvidia cardhu where the original Nabi2 is a Kai product. The screen resolution also seems to be 1280x800. The system partition is 1.5GB, with 1GB for the ROM. I didn't put a ton of effort in to it but besides the obvious issue with partition size, I'm not sure we can do much to bring Kitkat to the old Nabi. Booting either the 2S boot.img or the 2S bootloader yields a blank screen. This blank screen isn't a lockup, the kernel or bootloader come up and you can interact with the tablet by commandline, just no graphics.

If someone wants to mess around with it I can help out. I have the jellybean stock images for the 2S at this point, probably grab kitkat later. The bootloader blob, boot and recovery image are in the root of the update zip if someone wants to dissect them a bit. I'll attach the bootloader removed from the blob for usage with nvflash.

I built a quick TWRP for the 2S, I haven't done much testing with it. There are some odd properties with the touchscreen, so I don't know if it will work with all 2S tablets. You can likely root with the TWRP, although I haven't tested.
[Miscellaneous Android Development] katinatez:
I see you edited your message, noticed the kernel is larger in ota.zip so a new twrp would be needed moving ahead. Did you flash the update? What version # is it and can you briefly explain noticeable updates. What odd touchscreen properties? Are you refereeing to when inside of recovery?

Thanks
[Miscellaneous Android Development] aicjofs:
Yeah I edited, was going to go to bed and then couldn't sleep because I had some ideas. I think the TWRP I built with will work(well boot anyway) for both(Jellybean and kitkat), just a guess but I think it will.

I didn't flash the update, I got ahead of myself on the Intel Dreamtab so I figured I would think on it for a day and make sure I'm not missing anything I want to grab/try in case there is no going back. The 2S doesn't have nflash so things are a bit more risky(Fuhu has been using updated bootloaders on recent tablets where you need the SBK anyway) I will update the version number and things I see when I do.

Odd touchscreen, in that it's like the NabiJr B and Dreamtabs where it's portrait, and the bigger one, is the touchscreen is flipped. Had to compile TWRP with some touchscreen flip flags, not huge, just different then every other Nabi. Any other questions just ask, might make me think of something I haven't thought of.
[Miscellaneous Android Development] jaxbierley:
Looks like I'll be rooting this tonight. Thank you.
[Miscellaneous Android Development] saw429:
http://www.androidpolice.com/2015/0...let-gets-an-overdue-update-to-android-kitkat/
[Miscellaneous Android Development] aicjofs:
Nice find, looks like it's true:

http://updates.fuhu.com/updates/android/NABI2-NV7A/US/xxx/2.4.6/updates.json?

and the OTA

http://cdn.firmware.fuhu.com/nabi2-nv7a/nabi2-ota-update-2.4.6.us-to-3.0.13.us.zip

EDIT:

Bootloader is updated but not locked

nvflash still accessible

JB TWRP 2.8.4 boots and backups http://xdaforums.com/showpost.php?p=58453164&postcount=2502

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

3013stock.zip

Here is a flashable bootloader update

KK3013bootloader

With those 2 files it should allow any Nabi in any condition to return to stock 3.0.13. Like the previous procedure extract the images to your TWRP backup folder and restore all, then before reboot "install" the KK3013bootloader.zip. Basically this http://xdaforums.com/showpost.php?p=51037177&postcount=21 but with 3013stock.zip in place of 2311stock and 2311addon zips, and the 3013 bootloader zip instead of the old JBbootloader zip
[Miscellaneous Android Development] ncfoster:
Edit: Updated both of the kids' original Nabi2 tablets to 3.0

Very intrigued by the possibility of removing the extra bloat / apks. Coming to the conclusion that I probably don't even need root to do this (though I'm open to doing so). Is there a version of TWRP that is proper/recommended for Nabi2 with 3.0 installed?
[Miscellaneous Android Development] DarkAngel:
Post # 2502 or look right above your post.

Man! Away for a bit modding and getting to know Lollipop on my Note 3 and then Nabi drops the KK bomb for the Nabi2. Sweet! Time to update and start modding away.....oh dang need to update both my girls Nabi's again.......
[Miscellaneous Android Development] ncfoster:
I guess that I was just not sure whether either of those would necessarily be compatible with the latest drop. Is that confirmed?
[Miscellaneous Android Development] aicjofs:
Yes. 2.8.4 works and confirmed with 3.0.13.

It might have problems installing future nabi OTA's directly through TWRP, we will cross that bridge when it arrives.
[Miscellaneous Android Development] brownel02:
I have not updated the kids nabi2’s since my original rooting about 2 years ago (they would not let daddy play!). But now that they are getting a little older and want different games they have given me the green light to wipe away. I have read a bunch of this post but still am looking for a bit of guidance. Looking to upgrade the tabs to the latest stable version and remove as much bloat as possible. Tablet specs are as follows:

TWRP: v2.6.1.0 (Nabi 2.1.27)

Model number: NABI2-NV7A

Version: 4.0.4

Kernel: 3.1.10-00275-g3a4f8c1

MID@keenhi-desktop # 28

SMP PREEMPT Fri Oct 26 21:05:35 HKT 2012

Build Number: IMM76L

Product Version: 1.9.37-release-keys

Can I go straight from where I am now or do I need to perform an intermediate update? Any help is appreciated. Thanks
[Miscellaneous Android Development] aicjofs:
There are a few ways to go about it. Part of me thinks it might be easier to restore stock 1.9.37 with ICS TWRP. Then do all the updates through OTA. This might be able to be sped up by downloading the OTA's from the post a few posts back, but it doesn't save huge amounts of time.

You could jump directly to 3.0.13 by installing the latest kitkat bootloader zip, then installing TWRP 2.8.4 then restoring the full 3.0.13 backup(system, addon, boot). That may be complicated as well.
[Miscellaneous Android Development] mjw2k11:
I'm having problems installing the new update, starting on TWRP 2.7.1 then installing new bootloader 3, and then TWRP 2.8.4 then on reboot to recovery im having touchscreen issues and unable to swipe to restore 3.0.13stock

any ideas? i have just restored back to 2.4.8stock and will try OTA update but not much hope, TWRP recovery keeps stopping OTA Installation with "Unable to mount partitions"
[Miscellaneous Android Development] aicjofs:
2 ideas. The 2.8.4 TWRP may not have all the touchscreen input blacklists it needs.

1) Stick with TWRP 2.7.1 and try to restore 3.0.13 with that.

2) If you are on 2.4.6 stock. Pull the recovery.emmc.win out of the 2.4.6stock zip and put it in fastboot folder. Reboot to bootloader.

fastboot flash recovery recovery.emmc.win

that should put the stock recovery back on. Then try to take OTA.
[Miscellaneous Android Development] mjw2k11:
ok thanks for that, tried with 2.7.1 but still touchscreen issues, flashed 2.7.0 and it then worked I was able to restore 3.0.13stock and then flashed KKBL and then 2.8.4, all working now, thanks :good:
[Miscellaneous Android Development] aicjofs:
This is from last couple of days. It seems there might be some touchscreen issues with TWRP 2.8.4 on certain Nabi2's.

Strange though, [MENTION=3814731]katinatez[/MENTION] has TW_INPUT_BLACKLIST := "accelerometer\x0dmard06\x0lis3dh_acc\x0lis3de_acc" which usually fixes the issue on all the different Nabi2 hardware we have come across. However when I was helping someone build TWRP for the Nabi BigTab 20 we ran in to the same problem. I had to show him where to hard code it in to event.c to solve the touchscreen issue, as TW_INPUT_BLACKLIST wasn't doing the blacklist.

I think it was my mistake after looking this morning.

https://github.com/omnirom/android_bootable_recovery/commit/5742a40b87dfdc26df3bd9fe94197ae414ece546

We should change the line to this: with \x0a, not \x0 like I had it. oops my bad, sorry guys.

TW_INPUT_BLACKLIST := "accelerometer\x0admard06\x0alis3dh_acc\x0alis3de_acc"

Looking at the post above this probably effects some Nabis going back to 2.7.1 so 2.7.0 is the last fully working touchscreen since that was the last one I hardcoded. Surprised this is the first we have heard of it.
[Miscellaneous Android Development] ncfoster:
Sounds like I might wait until the latest TWRP builds get ironed out.

One more question. Just to be clear, flashing a custom recovery on a Nabi2 does not require wiping the device, right? I understand that I should backup what I can, but I'd rather avoid having to restore everything.
[Miscellaneous Android Development] aicjofs:
The 2.8.4 recovery works, but certain Nabi's will have touchscreen issues. That's the only problem. No it doesn't require wiping.

[MENTION=5248350]mjw2k11[/MENTION] can you try this TWRP and see if the touch screen works? The zip is a flashable version.

When adding the latest kernel we are over the recovery partition size of 8MB. For this version to fit I have removed Super user install ability, I don't know how to really go forward. Tethered boot(always fastboot boot xxxx) I don't like. As they add more features to TWRP the problem only grows worse. We could stay with the 2.4.6 kernel, but I don't think we will be able to flash official OTA's if the kernel doesnt have SElinux support. As it is I don't miss the ability to install SuperSU. It's easy enough to grab the latest zip and flash.
[Miscellaneous Android Development] katinatez:
There are other ways to make smaller recovery image. Let me give it a try. Did you push any new commits into your repo for touchscreen issues? I have yet to update my nabis because I just set them up perfectly for my kids. Also now with kitkat and selinux available Philz recovery can be compiled also, I gave up a while back because Philz recovery did not support jellybean with touchscreen it was all hardware buttons for jellybean.
[Miscellaneous Android Development] aicjofs:
Yeah I'm thinking of dropping exfat instead of super user. I might do that on the Dreamtab too. All the Fuhu devices put NTFS support and no EXFAT, so unless your thing is swapping cards in and out you won't be using an exfat card in the Nabi anyway.

I didn't push it because I'm not sure what my final solution would be. The only change is to this line. Just copy the below and replace the old blacklist

TW_INPUT_BLACKLIST := "accelerometer\x0admard06\x0alis3dh_acc\x0alis3de_ acc"

Also for now

TW_EXCLUDE_SUPERSU := true

but I think I might undo the super user and do away with exfat

TW_NO_EXFAT_FUSE := true

TW_NO_EXFAT := true
[Miscellaneous Android Development] katinatez:
Done compiling 8.6 mb with SuperSU left in. I think the way to go is eliminate exfat. I personally format my 64 GB exfat card to fat32 the biggest file I have is 1.5 GB of cartoons so I'm fine with removing exfat. Starting new build

Added this for aroma file manager

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
[Miscellaneous Android Development] aicjofs:
Yeah I added the pixel format to mine too.

The latest kernel adds 200kb probably for SE linux stuff and just pushes it too high. Sigh how many times have we said "wish we had the source...." haha

Weird "mount.exfat" stays behind in sbin but "exfat-fuse" and "libexfat.so" is gone.
[Miscellaneous Android Development] katinatez:
Still to large 8.6mb now I'm removing SuperSU but going to bed will let you know how this ends tomorrow.
[Miscellaneous Android Development] mjw2k11:
Thanks for this, I can confirm touchscreen issues now resolved thanks for your help
[Miscellaneous Android Development] katinatez:
Ok I got recovery.img to 8.4 mb with updated kernel by removing SuperSU & exfat. I guess I can update one of my nabi's and test. [MENTION=4939189]aicjofs[/MENTION] are those updates a few post above flashable? I will try to update tonight and test new recovery.
[Miscellaneous Android Development] brownel02:
aic and kat,

Thank you both for working on this. I will take the slower approach and revert back to stock then upgrade slow and steady. I am really excited to get a bit more space on these devices as you have been working on. THanks again.
[Miscellaneous Android Development] thajacka:
can someone tell me why we have to update twrp to flash 3.0 and new bootloader? my nabi is on 2.6.3 and im on nabi v 2.3.11? why cant i just restore with this version and flash the bootloader and keep thisv version or twrp?
[Miscellaneous Android Development] aicjofs:
You might be able to. No one has tested with TWRP 2.6.3, I don' think you need any SE linux contexts to "restore" so it could work. Try it out and let us know. What won't work is "installing" the 3.0 OTA.
[Miscellaneous Android Development] Eric Karz:
what version are we up to? I tried updating to get current... I failed on asserts (deleted and tinkered to much lol) is there a TWRP back up of what ever is current(as of 2-20-2015).so it shows the set up screen on boot up?
[Miscellaneous Android Development] aicjofs:
Look who is back!! About to send a search party for you.

http://xdaforums.com/showpost.php?p=58786524&postcount=2510

Have to clear data if you want setup screen
[Miscellaneous Android Development] Eric Karz:
Dear nabi master ...thank you so much was pretty easy to do it that way .

you da man :good:
[Miscellaneous Android Development] n3wt:
So, I'm liking the KK update now that I've removed all the bloat...I was wondering if you guys would be interested in a stripped-down version? and if so, what launcher do most people favor (as the stock one seems to have no way to disable the nabi blue morpho whatever)? any other must have apps that we can agree on?

[MENTION=4939189]aicjofs[/MENTION] is there any way to make use of the addon partition without actually re-partitioning?
[Miscellaneous Android Development] datboy143:
I'm trying to root my sons nabi jr. I cant find the instructions for the model that he has. Its the 4 gig snbjr-mt5c. Its running 4.4.2 kitkat. I tried the instructions for the other models but its a no go.
[Miscellaneous Android Development] n3wt:
I'd try Kingo Root...it worked for me on the KK update on the Nabi 2.
[Miscellaneous Android Development] datboy143:
Never heard of it. Il do some research and give it a try. Thanks.
[Miscellaneous Android Development] n3wt:
Yeah, I didn't think it was gonna work for me but after a while of it loopimg thru it's thing my tablet froze and then when I rebooted it was rooted.
[Miscellaneous Android Development] datboy143:
Thanks bro it worked i got root lol. Now il try to add twrp any suggestions?
[Miscellaneous Android Development] n3wt:
Not sure on that one as I doubt there's one updated for KK but whatever the latest is for nabi jr would be your best bet...just have to try it and see if it works.
[Miscellaneous Android Development] dcooterfrog:
it worked for me as well. it took a while. looked like a loop. it kept trying 3 steps. eventually the machine froze I rebooted and i had root.

i installed busy box and updated the su binary

I had a pure stock nabi i needed to do a factory reset to get kitkit to pupdate.
[Miscellaneous Android Development] aicjofs:
I've thought about that so many times I can't even count. Without re-partitioning it's just such an odd size at 1.5GB that it's too big not to use and too small to be useful. There are tons of ways to use symlinks but we discussed it somewhere in this mess of a thread that stuff like backups don't follow the symlinks. Any apps that could read the root file system and up could use it for something maybe. Like say xbmc(kodi) maybe you could put 1.5GB of media... I don't know, something like that. Re-partitioning is really the ideal way.

It really depends on if it is a new Nabi device.

On a side note. I have been kind of working on and off on a new NabiLab2015 with support for all Nabi devices it's still very rough, alpha at best. But the pure Nabi2 stuff works ok.

I always think I will have time to do some work on it and I never do, been working like once a month on it forever, and by the time I get back to it something else has changed about the Nabi devices. Has some different detection, some nvflash, bootloader, drivers, etc

NabiLab2015 alpha
[Miscellaneous Android Development] DarkAngel:
Looks like we are back at it on the Nabi2....... Update times... :p

Updated some on the Nabi2 Wiki to include the new info.......
[Miscellaneous Android Development] n3wt:
OK, so, if you have followed this post and want to try out a stripped down version with all the fuhu/nabi/keenhi stuff taken out then grab KK3.0.13.zip and put it on your external sdcard, do a good wipe (might have to wipe addon as well) and install in TWRP.

It's pretty cool as it is but my plan is to fix it up some more (I'm thinking like 4-way reboot menu and maybe a some other small mods) and hopefully with some feedback I can make it into something that lots of us can really enjoy, so try it out and let me know what you think! :cowboy:
[Miscellaneous Android Development] homephysician:
Hey dude this is awesome. I'm pumped up for this. I will download and give you feedback. I would love to have all of the Nabi stuff gone. man I was just about to update to stock 3.?. Glad you posted. Thanks, hp
[Miscellaneous Android Development] n3wt:
keep in mind that you have to follow the directions in the other post also except for actually restoring the stock 3.0...so, getting the right TWRP and installing the new bootloader.
[Miscellaneous Android Development] aicjofs:
Nice work n3wt. The Nabi2 continues it's run! We don't even use the Nabi2 anymore here so I sold one and the wife says I need to sell the other but I try to explain the hours I have put in to this thing in this thread and that it's not that easy for me to part with it.

You know every time I see Aang I think it's funny we picked the same picture. Same image I have used forever for Last Airbender folder in XBMC.
[Miscellaneous Android Development] DarkAngel:
I am game for helping out on this. Already starting on one mod ;) ........ I wonder if by using your stripped down version & then De-Odexing I can fit it in. As it is now, I De-Odexed and was not able to fit all the files back in, literally doubled all three folders together in size. Oh and aicjofs, your NabiLab Update works great!

Edit on De-Odex.....Got it down to 160 MB for all three framework, app & priv-app. :good:
[Miscellaneous Android Development] DarkAngel:
Nabi2 mmcblk0 Partition Info

Dropping this here incase anyone needs the info for say backing up their nabi2's or making images........

I am updated to the latest TWRP and latest KitKat version. All working great for me.

:good:
[Miscellaneous Android Development] DarkAngel:
3Minit Battery Mod

Just wanted to share a mod I did to my Nabi2.

http://xdaforums.com/android/themes/theme-3minit-battery-mod-stock-v3-0-13-t3046290
[Miscellaneous Android Development] Macanage:
Hi guys,

Hoping someone can point me in the right direction. I just updated via OTA to the latest "kitkat." I lost root and twrp in the process. I noticed the last twrp available is (2.8.4 or 2.8.5) is the "installer" version. Is there a twrp that I can flash in fastboot? Also noticed that you can not store any apps on the SD card. Looks like a Kitkat issue (security fix). However, I do not care about the security issues and really would like to be able to store apps on the SD card. Any solution to that would be appreciated.

As far as rooting????

Thanks,

Macanage
[Miscellaneous Android Development] katinatez:
Download the last twrp 2.8.5.0 zip file and extract twrp-recovery.img . Then use fastboot command to install twrp recovery then flash SuperSu.zip file for root.
[Miscellaneous Android Development] Macanage:
Thanks, I did extract 2.8.5 from the zip and flashed it in fastboot. All loaded fine. Rebooted into rom then rebooted into recovery and twrp will still not come up. Do I need to flash the SuperSu.zip before I try and go to recovery? Also where can I get the SuperSu.zip?

Sorry, new to all this!

EDIT: I did find the latest SuperSU.zip. V2.46 in Chainfire's thread.
[Miscellaneous Android Development] katinatez:
Commands to install recovery

adb reboot bootloader

fastboot flash recovery twrp-recovery.img

fastboot reboot

Google SuperSu.zip
[Miscellaneous Android Development] n3wt:
so you did "fastboot flash recovery <name of recovery file>.img"?

You can get SuperSu.zip from here.

---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------

ninja'd!! Did you check your pm's?
[Miscellaneous Android Development] aicjofs:
I don't know how it effects app2sd or whatever you guys use but try this to make sdcard writable. Need to get SU working first, you can edited the file live and reboot when done. Make sure you make no typo's though.

http://trendblog.net/fix-kitkat-sd-card-write-restriction/
[Miscellaneous Android Development] Macanage:
Yep, that is exactly how I did it. Terminal response was:

sending 'recovery' (8190 KB)...

OKAY [ 1.496s ]

writing 'recovery' ...

OKAY [ 1.129s ]

finished. total time: 2.627s

Then after fastboot reboot, when the rom loaded, I did ADB reboot recovery.

It rebooted in to what looks like the Original recovery with the green android with the triangle in the middle.

I checked in the root of the platform-tools folder to make sure there was only one recovery image in there and also made sure it was the 2.8.5 recovery image.

kinda of confused!
[Miscellaneous Android Development] DarkAngel:
Ha........dang.......I forgot to mention this when I did this. It was the first "MOD" I did when I updated to Kitkat LOL. Titanium backup would not read the External SD card as I have my backup there.
[Miscellaneous Android Development] Macanage:
Thank you. I did get the latest but still struggling to get TWRP to come up

---------- Post added at 05:44 PM ---------- Previous post was at 05:39 PM ----------

As soon as I can get TWRP to work and get root I will do this. Thank you !!!!
[Miscellaneous Android Development] n3wt:
and you are sure you did "fastboot flash..." and not "fastboot boot..."?
[Miscellaneous Android Development] Macanage:
from the terminal:

"fastboot flash recovery twrp-recovery.img"
[Miscellaneous Android Development] n3wt:
hmm, not sure why it didn't "stick" ...maybe try to flash again but this time when get it booted to TWRP go ahead and install the SuperSU.zip.
[Miscellaneous Android Development] Macanage:
Can't get to boot into TWRP or I would flash the SuperSU.zip. Is there a way to go from the bootloader after flashing TWRP directly into the recovery? Will "fastboot boot recovery.img" work?