yashsingh1/xdaforums huggingface dataset:
[Fuhu Nabi 2] QA Bot:
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Fuhu Nabi 2] Eyebolt:
State of Nabi 2 Root as of 12/14?

So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.

So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://xdaforums.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
[Fuhu Nabi 2] aicjofs:
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).

katinatez repackaged it for jellybean here:

http://xdaforums.com/showpost.php?p=48987089&postcount=2088
[Fuhu Nabi 2] jaxbierley:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
[Fuhu Nabi 2] aicjofs:
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477

http://xdaforums.com/showthread.php?t=1905674&page=248
[Fuhu Nabi 2] Firepants:
Stock Restore

Hi

I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
[Fuhu Nabi 2] aicjofs:
What version of software? Use Nabilab2015 http://xdaforums.com/showpost.php?p=59073456&postcount=2544

It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
[Fuhu Nabi 2] ashahin1:
Hacking Nabi2 to Allow Data2SD

I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.

Warning: I am not responsible of any damage as a result of following the next steps. Always make backups

Note: I have the last update (KitKat) installed in the Nabi2

1- Dump the boot image from an adb shell:

su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img

2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743

Warning: do not do anything in the tutorial, just wait

3- Format an sdcard as one partition of ext4 type

4- Insert the sdcard in the nabi2

5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line

/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA

with

/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA

which switches the data partition mount point to be on the sdcard

and the line

/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto

with

/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12

which mount your old data partition into the directory of the external sdcard

6- Repack the boot image as mentioned in the url in step 2

7- Copy the new boot image to the nabi2 sdcard

8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:

su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX

9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)​
[Fuhu Nabi 2] ashahin1:
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
[Fuhu Nabi 2] ashahin1:
If you don't have the time to do all these steps, I have the modified boot file attached here.

Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:

fastboot flash boot new_boot.img
[Fuhu Nabi 2] Aytul:
Nabi2 not found

Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
[Fuhu Nabi 2] Aytul:
Swipe to restore

I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
[Fuhu Nabi 2] n3wt:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.

did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
[Fuhu Nabi 2] Aytul:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?

I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
[Fuhu Nabi 2] n3wt:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
[Fuhu Nabi 2] Aytul:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
[Fuhu Nabi 2] n3wt:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
[Fuhu Nabi 2] Aytul:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
[Fuhu Nabi 2] n3wt:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
[Fuhu Nabi 2] Aytul:
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately
[Fuhu Nabi 2] n3wt:
Ahh, I gotcha. So, what are the symptoms of the wifi prob exactly? Will wifi not turn on at all or just not connecting or what?
[Fuhu Nabi 2] Aytul:
It won't show any networks, it allows me to turn it on. Scan doesn't respond and when I check, there is a Mac address but no IP
[Fuhu Nabi 2] n3wt:
The fact that it turns on and has a MAC address suggests that it's (at least partially) functioning...try booting into TWRP and wiping dalvik, cache, and data (it's under wipe/advanced wipe) then reboot and see if that helps. I'm think the configuration file for wifi somehow got borked. If you have root you could even just try deleting /data/misc/wifi/wifi_supplicant.conf and then reboot.
[Fuhu Nabi 2] Aytul:
I've just tried the wiping, but no luck. I can find the data file but there's nothing in there pointing to wifi? Misc doesn't exist and I've tried manually looking in the folders for it too. This is through file manager on TWRP? Any other suggestions on finding the file?
[Fuhu Nabi 2] n3wt:
If you wiped data that should've wipe that file too...the reason you can't see it in TWRP is because the partition isn't mounted.

I'm not sure what you need to try next, maybe [MENTION=4939189]aicjofs[/MENTION] will chime in with some better advice.
[Fuhu Nabi 2] Aytul:
Hi, any luck with this issue?
[Fuhu Nabi 2] aicjofs:
Usually with Nabi wifi issues you don't even get a MAC address. The fact the file isn't there is concerning as it is if you have rebooted after the wipe. You can try Nabilab2015 alpha3 and do a "restore all factory". You already have TWRP installed and working so that should be all you need to do. Use an external SD card and make sure to chose that option.

http://nabtabhacks.com/downloads/NabiLab2015alpha3.zip extract and run the .exe
[Fuhu Nabi 2] Aytul:
Hi, I've ran the exe from my laptop, I see a reboot recovery option but not restore all to factory. I tried the reboot recovery and it didn't do anything?
[Fuhu Nabi 2] aicjofs:
You need to select nv7a US to see the restore to factory. But yes use the tools on the main page to make sure ADb and fastboot is working first. Plug the tablet in and boot to TWRP before hand.
[Fuhu Nabi 2] Aytul:
I have managed to download the Stock file and start the Restore, however it doesnt run all the way through (on Windows). I completed the restore on the device, through TWRP but the devise isn't restarting as it should. It hangs on the Nabi logo, although I can load into TWRP
[Fuhu Nabi 2] aicjofs:
So you were able to restore on the device? I would do a "wipe data" in TWRP.

Also on main screen what software version does it say if you click the about device
[Fuhu Nabi 2] Aytul:
The restore from abcstock was successful on the device. Issues now: won't boot, doesn't recognise the extrernal SD, isn't recognised on NabiLabs (which I think is down to the USB debugging reset). TWRP boots, but when I try to wipe etc I get errors saying 'failed to mount, directory doesn't exist'
[Fuhu Nabi 2] aicjofs:
Which version of TWRP is on the device? What does it say at the top of the TWRP screen? If you are getting failed to mount it's usually because the TWRP version is now not correct after you have changed the software/bootloader version.

You can switch 3 TWRP versions around by using the NV7A screen in Nabilab even without ADB.

-Boot the tablet to bootloader (power and vol key and selecting fastboot protocol)

-On the left side of the NV7A screen you have 3 radio buttons to select software version. I would start with 3.0.13

-Then use the install recovery button(you will get an ADB error but you can continue on)

You have to get a TWRP version that doesn't get any failed to mount errors or you are using the wrong version.

Once that is done you should verify what is on your external SD by putting it in a computer if you can, but the file manager in TWRP will work too. You should have a folder TWRP/BACKUPS/xxxx/abc123stock in that folder there should be system, addon, recovery, and boot files and on the root of the external SD card should be a KK3013bootloader.zip

You should restore in TWRP addon, system and boot

then if that is successful BEFORE rebooting

"install" in TWRP KK3013bootloader.zip

Side note: Sometimes between TWRP versions you will get a different xxxx number in TWRP/BACKUPS/xxxx/abc123stock. If this happens TWRP will not "see" any backups to restore. To get around this do a backup of just "boot". This will create a new folder for you with the right path, and you can copy the files to the correct spot so they can be "seen"
[Fuhu Nabi 2] Aytul:
Ok, so far so good. I managed to update TWRP, Restore and install boot loader. All looks to have worked, but whenever I go to reboot I get a message saying 'No OS installed' and then a message saying 'Install SuperSU? Your device does not appear to be rooted'. If I swipe to install it says 'running script' and reboots but still hangs on the NabiLab logo. I reboot to TWRP and it loops the same issues

The device is now showing on NabiLab but says 'TWRP +[1.9.37] and device info says 'Device - mt799, android version - 4.4.4, boot loader - 5.3 & nabi serial is blank
[Fuhu Nabi 2] aicjofs:
OK. That means there is no files on /system. It sounds like that has been the problem. The system backup on the SDcard is probably incomplete because you said there was an error or something. It probably didn't copy the full files.

On the main screen in Nabilab there is an option to open directory. That will launch an explorer window, in there should be a folder called "install". Open that and you should see 3013stock.zip. Extract that to your SDcard in that abcstock folder overwriting the other files(system.win, addon.win etc) put it back in the Nabi and restore.

Or you could try and install through the program again. It takes a long time so you have to wait 30 min or so.
[Fuhu Nabi 2] Aytul:
I managed to restore from NabiLab as the file (restore) on the SD card wasn't being picked up. Unfortunately the wifi is still not working, I have the following - 'unfortunately, FoozKids OOBE2 has stopped'

I also have another,, working Nabi, is there much difference in the UK / US / Disney software packages?
[Fuhu Nabi 2] aicjofs:
Still no wifi though? It might not be a software issue then. Usually you dont get a MAC address when it was software, and you said at the beginning you did have one listed.

UK and US are pretty much the same, Disney is it's own beast, whole different partition layout.
[Fuhu Nabi 2] Aytul:
Sounds that way, previously i had a mac address now there's nothing at all. Thanks you for your help

Is there a way to manually install apps etc, so it can be usable without the wifi?
[Fuhu Nabi 2] aicjofs:
Google side loading apk.

I still wish you didn't get the fooz kids oobe error. This would be the first time I have ever seen in the 2 plus years of the nabi2 where a restore does not work completely even if the wifi is a hardware issue. You did do a wipe data in TWRP a second time just to be sure?
[Fuhu Nabi 2] Aytul:
I didn't wipe directly before the latest install but I will try it..I'm not hopeful, it does look like the wifi is shot.

Is there a guide to side loading for Nabi please?
[Fuhu Nabi 2] Aytul:
I'm trying to step back to the UK version, as I am getting a lot of crashes & errors on the US (3013) version. NabiLab2015 doesn't launch anything when Nabi UK is selected ..what's the best way to re-install the UK version please?
[Fuhu Nabi 2] aicjofs:
It hasn't been added yet, I was hoping the would get KitKat soon and didn't want to do extra work.

Now you get the general idea you could do it your self manually with this:

http://nabtabhacks.com/downloads/232UKstock.zip

Or you could put this in the Nabilab install folder and rename it to 3013stock.zip and then trick Nabilab in to restoring the UK version when you click on restore 3013.
[Fuhu Nabi 2] Aytul:
Ok thanks I'll give it a go, does it matter what version of TWRP I use? I was trying to reinstall last night, from a zip and other than the mount errors, I was getting an E:/ partition error?
[Fuhu Nabi 2] Aytul:
Hi, sorry to be a pain. I've come tried to revert to the uk version, which seems to install but when I try to reboot it hangs on the Nabi logo. I've tried all previous suggestions to try and get it to work, but with no joy. Can you help please?
[Fuhu Nabi 2] aicjofs:
Since you tried 3013 for US you might have wrong bootloader(US KitKat), try the UK bootloader version from this thread(not the whole ROM installation directions just the bootloader). Only thing I can think of if it looks like the restore was "normal"

http://xdaforums.com/showpost.php?p=50431606&postcount=98

This is the link directly to bootloader http://xdaforums.com/showpost.php?p=50356162&postcount=91
[Fuhu Nabi 2] Aytul:
I've just tried it with no joy, it installs ok but still hangs on the nabi logo. I tried restoring directly from the unit but I get a partition error. That's the only thing I can identify that fails..?
[Fuhu Nabi 2] ehscoto:
How long did you have to wait for the files to transfer? Also, during the process did the Nabi go from the TWRP menu screen to the TWRP logo screen during the file transfer?
[Fuhu Nabi 2] Aytul:
It took a while, and when it finished loading it rebooted to the Nabi logo..where it just hangs
[Fuhu Nabi 2] ehscoto:
When trying to restore to factory during the file transfer, the TWRP goes out if the menu area and gets stuck at TWRP logo scree than when finished the screen says device error. When I go into the restore menu, no folder exist. Did that happen to you as well!
[Fuhu Nabi 2] Aytul:
Hi, can you assist any more with this issue please? I have tried all variations of TWRP / Restore versions and nothing is working..everytime I think it's successful it hangs at the logo. When I try to restore from TWRP (manually) I get the partition errors

Also, is there a quick / easy way to revert to UK software from the US version please?
[Fuhu Nabi 2] aicjofs:
What you are seeing is the stock recovery(android with exclamation point), it has no USB(more specifically no MTP/Mass storage or ADB) so there is no USB interface to see. You can not restore with the stock recovery. You can't do anything with stock recovery execpt update, and factory reset.

You need to use fastboot to get TWRP back on the device. To enter fastboot mode do the same thing to boot tablet to where you are selecting "recovery kernel" except select "fastboot protocol". Nothing will happen if you don't have a driver installed for fastboot so check in device manager in Windows. At that point you could then install TWRP with fastboot.

Since you are in position where you can't make things worse you could try the alpha version of Nabilab GUI http://nabtabhacks.com/nabilabgui2015/publish.htm

You have to use Internet Explorer when you go to that page to install it. If that doesn't work download directly here http://xdaforums.com/showpost.php?p=59450453&postcount=2591

Can you get a TWRP log, or at least a screen shot(using a camera) of the partition errors.
[Fuhu Nabi 2] ehscoto:
Ok, I will try it. Appreciate the help.
[Fuhu Nabi 2] Aytul:
I am running through the install again then I will attach screen shots of the errors. In regards to my working Nabi, I still have the US version and dont want to 'break it'. Do you have simple steps to go back to the UK version please? Thanks
[Fuhu Nabi 2] Aytul:
Hi

attachments uploaded, this was running through restoring to stock using NabiLab 2015. I replaced the stock file with the UK version, as previously advised. I am still hanging on the logo when rebooting. I installed the UK bootloader, but cannot access the recovery file from my SD card to show you the errors previously received. The SD card is available but the folders / recovery file is not showing
[Fuhu Nabi 2] aicjofs:
I think you asked earlier and I never answered. I don't know if the TWRP version matters. As far as I know you are the first person to try and go from US KitKat back to UK Jellybean. I see you are using the kitkat TWRP, I would try the Jellybean one, as it might be writing SElinux stuff that you don't want.

I know I linked you to this to get the bootloader. Have you tried running this procedure step by step?

http://xdaforums.com/showpost.php?p=50431606&postcount=98

This should be entirely possible to do, but there is no previous history, its not done as often, I don't have a UK version, etc. Screenshots were helpful, I really do want to help so more information the better.
[Fuhu Nabi 2] Aytul:
Hi, I hae tried variations of TWRP etc, but not sure / don't remember how far I got with them. I'm not sure if a format of the device caused problems with missing folders / partitions etc. this is the closest I've gotten with it. I tried going back to UK from the US working device and both are now hanging at logo..says that it is either the TWRP version or the UK build..? I'll try JB TWRP and then see what happens :)
[Fuhu Nabi 2] aicjofs:
It's just really hard to guess where the problem is. Most times on the Nabi the bootloop is 1 of 3 things.

1) The boot.img is not matching the ROM(files on system)

2) The bootloader doesn't match the boot.img(passing wrong kernel commandline)

3) The data partition wasn't wiped(The data on the partition is corrupt, or is created by a JB ROM, but trying to run KitKat ROM, or vice versa). This doesn't mean "wipe data" in TWRP, that wipes internal SD as well as data, a factory reset should accomplish the same(just without wiping internal SD) and resolve a bootloop if it was the problem.

However in your case and the partition errors it's hard to know if TWRP is even restoring things right. Another thing that comes to mind is: can we actually downgrade the bootloader. The way the bootloader zip works is copying the bootloader image to the staging partition. Upon boot the device checks if there is anything in the staging partition and applies it. What I don't know is does it check versions, and not do it if the version already installed is newer. I don't think it does that, but it could be doing it. In which case you would have to use nvflash to override that.
[Fuhu Nabi 2] Aytul:
Ok I understand your train of thought..I doubt it's corruption as I've now tried it on the 2nd device without formatting / messing around with anything. It was a straight US -> UK swap. I've reverted to JB on it and tried to reboot. At the moment it doesn't look promising so I may need to re-install the UK software? I ran the bootloader.zip from it before rebooting, but not following the step by step instructions so I'll do that now

Is there anything I can send you from the device that may help investigate further?