yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] shizzyraw585:
Could definitely be a possibility. I'm not drunk like I was when I was successful with the first two. I do think the touchscreen troubles in recovery some of us are having are at least a little fishy though. And no, the backup and restore have not been altered in anyway.
[Miscellaneous Android Development] gijosh28:
I'm not a proud man. I have redrunk myself to duplicate things before. In fact I spent about 3 and a half years in korea trying to duplicate every night :). The recovery thing is wierd too. I wonder if theres is a serial number correlatiotion to that.

---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------

The back and restore thing is not in regard to your situation. I am having some backup and restore problems myself, and I can't seem to find anyone else thats tried backing up and restoring.
[Miscellaneous Android Development] tikiral:
1. Thanks x1000!!! So awesome. Picked it up and didn't even realize that it didn't have Play on it. I thought I had seen Cut the Rope on one of the ads. Guess I was wrong.

2. Was still on the original 1.9.17 or something like that when I bought mine (Black Friday @Walmart). Tried the root toolkit but had to manually do the driver in Device Manager (just pointed it at the generic Android Composite ADB) and could only get the install.bat to install TWRP. No problems though, just adb push'd the root and gapps files and bam! worked like a charm.

3. Got the email from Nabi on an update today so went to install that, saw you had uploaded a 1.9.23 ota zip and tried that. Seemed to install fine (everything in TWRP looked good) but still said it was on 1.9.17 (or whatever) when I restarted. Did the normal update though for both 1.9.23 and it downloaded and updated correctly. Just used Voodoo's OTA Rootkeeper to restore root after the update.

4. (3) doesn't seem to work for 1.9.37, though it probably did. I didn't manually do TWRP again after 1.9.23 and it just booted into normal Android recovery. Booted up just fine though and was able to get TWRP reinstalled using the tool. Still getting the Android upgrading message after each reboot, but I just haven't read enough of the thread to take care of that yet.

Background: Been rooting and flashing since the Behold II a few years back and have like 9 Android devices now, and while this one was a little more manual than some, it worked terrifically. Thanks again! Now if they'd only get Bad Piggies to work... Sent off a tweet and they just responded that the Nabi didn't have Play on it (duh!) and that there were ways to install other markets (again, duh!) but even when sideloading the app the touch and drag doesn't want to work.
[Miscellaneous Android Development] ALD3:
After watching for this tablet and knowing that Walmart was really the first one to carry them and Walmart always buys a large amount at a time. My guess would be that Walmart has a bunch of the very first ones made. I got 3 at hhgreeg and they were one of the last to stock them. So I would guess the early ones have the touch problems. Seems like all from Walmart have the most with problems, don't think it Nabi doing anything to block root. All of the good and affected have the same build date....it might actually be a touch sensor problem. That seems more likely and why it was mentioned you might consider returning them, with a complaint of touch control not working correctly.
[Miscellaneous Android Development] gijosh28:
#4 is an easy fix. Flash t499's gapps linked on about page 90 or so (give or take 10 pages). Or, you can manually find and delete the two odex files that are causing the problem. The info on that is listed here somewhere too. But the easiers solution is just to flash t499's gapps file.

---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------

Ald is right. I would return them on principal alone. It may be a precursor to a problem later on down the road.
[Miscellaneous Android Development] ALD3:
There is a gapps fix posted by t499, it stops the upgrading android. Still can't install most angry birds from Play. If you instant 1Mobile Market, it will let you install more than Play does and doesn't need root. That is 1 of the 2 that Nabi mentioned, open Fan Tech and it will take you to the link for install of 1mobile market
[Miscellaneous Android Development] gijosh28:
http://xdaforums.com/showthread.php?p=35887804

Thats the link to t499's gapps file.
[Miscellaneous Android Development] tikiral:
Thanks. Yeah, thought I read something previously in the thread about it, we just don't restart it a lot so I have been frustrated enough with it to go back and look for it =)

EDIT: Wow! This Nabi thread is hella active. Thanks for the posts. I actually went ahead and installed 1Market, Amazon and GetJar. Have access to pretty much any app I could want at this point.
[Miscellaneous Android Development] ALD3:
Wasn't sure what you meant about backup and restore. Yes I have used TWRP backup and restore with no problem several times and in a few different ways. I have made a backup other than the stock unrooted made by jmz before rooting. I have screwed the Nabi up and restored both the unrooted and they rooted backup. They both worked fine for me. I have also downloaded the 1.9.37 first gapps fix of 1.2 G and unrared it will,then copied it into my TWRP backup and did it in a restore using TWRP, that worked, then restored to my backup with android updating again so I could install t499 gapps fix and that went well. I have help 2 folks that did not have a working backup to download and restore their messed up Nabi via PMs and they got the Nabi back working.
[Miscellaneous Android Development] gijosh28:
Well, the problem I am having is I have one Nabi that is set up perfect now. Exactly how I want it. I would like the make the second Nabi an exact duplicate of it. When I restore the stuff from the first Nabi onto the second nabi everything seems right, except for the screens in nabi mode. It has the stock icons on it still and if you click one of the icons to one of the apps that i removed it says something about the app not being available. When I look in the app drawer, all the apps I paid to install are there, but their icons are not on the nabi mode screen. So the restore is restoring most of the other tablet to this tablet, except for the nabi mode layout. Make sense?

---------- Post added at 07:18 PM ---------- Previous post was at 07:17 PM ----------

I have to run out for an hour. This new Nabi that I picked up last night has a busted volume button. Seems like maybe FuHu has some quality control issues.
[Miscellaneous Android Development] ALD3:
If I understand you, it's mostly the paid apps that are giving you problems? Buying from Nabi, I can't really tell you anything but with Play, for them to work both tablets have to be signed in with the same Gmail for paid apps to work. They look for that when openings. When I restored the Nabi, I didn't have but 2-3 apps on the Nabi mode desktop but they were all in the app drawer. Even if I did a factory/reset it was the same, don't get that. If apps are missing in Nabi mode check the + - app in Parent mode and see if they are in there but unchecked, if so then check them and they should be in the app drawer on Nabi mode. Is that even close to what you were wanting to Know?
[Miscellaneous Android Development] shizzyraw585:
Tikiral would you mind giving a quick run down of how you did the adb push? I thought of that as well but gave up after I tried an adb remount and was told that it wasn't allowed:( .
[Miscellaneous Android Development] ALD3:
Nabi Credits

In case you didn't catch it yet. Nabi has given everyone 60 coins and another 60 on Monday. For all the trouble their site has been having. I looked and have 60 credits. You can keep up with any Nabi News by liking them on Facebook.:good:
[Miscellaneous Android Development] gijosh28:
Iam not explaining it clearly. Hypothetical:

You have two Nabis brand new in the box. You take the first one out. Turn it on, in Nabi Mode, go to the third screen and try to move the icon for Spinlets+ Music. It doesn't move. It's locked in place. Spinlets also can

not

be uninstalled.

So you install TWRP, root the Nabi, and put gapps into it. In Mommy mode install ES File explorer with root permissions, and delete Spinlets+ Music. You do this by deleting the Spinlets+ Music APK from /vendor/apps. Now when you switch to Nabi mode on the third screen where Spinlets+ Music used to be is a blank square. The icon is gone. Go back to Mommy mode and purchase, download and install Plants Vs. Zombies (PvZ) through Google Play store. Make it accessable in Nabi Mode, by using AddApps in Mommy mode. Go into Nabi Mode, open the app drawer, and drag the icon for PvZ to where the Spinlets+ Music icon used to be. Reboot into TWRP recovery, make a backup of the nabi.

(skip some obvious steps about copying backup to harddrave on your computer)

Take the second new Nabi out of the box. Go through initial setup, flash TWRP, root, install gapps. Copy the backup from the first nabi to the second Nabi and restore the backup through TWRP. Now boot this second Nabi into Nabi Mode. The Spinlets+ Music icon will be on the third screen (although it shouldn't be because we restored a backup from the first Nabi that had PvZ there). When you click on the Spinlets+ Music icon it says something about it not being available. If you look in the app drawer PvZ is installed and Spinlets+ Music is not.

Summary:

So despite what backups you restore, they don't seem to affect the Nabi Mode screens. Moreover, if Spinlets+ Music icon is there how do you delete it. To delete it on the first Nabi, I deleted the Spinlets+ Music APK from /vendor/apps, but on this second Nabi that APK isn't there (because of the restore). So how do i remove the icon that can't be moved? Why isn't the backup backing up the Nabi Mode screens from Nabi number 1, or why isn't it restoring the Nabi Mode screens on Nabi number 2?
[Miscellaneous Android Development] t499user:
Take a look at this, http://xdaforums.com/showthread.php?t=2016463

gijosh28,

I have done probably 20 backups/restores cycles without the issues you explain. I think you are missing an important step somewhere, maybe the OTA updates, or you are only backing up/restoring the system partition. Are you using stock roms? Doing all of the OTA updates? Which partitions are you backing up and restoring?

---------- Post added at 09:14 PM ---------- Previous post was at 09:06 PM ----------

Though I disagree with this, if the problem is only in the recovery and is easy to work around I would not return it. It is something that can probably be fixed with a new TWRP, definitely can be fixed by creating a CWM recovery for it. Returning otherwise fully working hardware is just going to drive up costs for everyone in the long run. I'm sure that the $15 that Fuhu is making from each sale wouldn't take long to get eaten up with returns.

---------- Post added at 09:19 PM ---------- Previous post was at 09:14 PM ----------

Is this happening on the stock rom or one of the backups posted?

---------- Post added at 09:25 PM ---------- Previous post was at 09:19 PM ----------

I don't think that Nabi is directly trying to keep the play store off. I think I read somewhere that they are waiting for 'certification' so that they can have the play store.

If you get root.zip and gapps.zip on there, it is very simple to have TWRP install it when it boots without you having to use the touch screen. Just create a text file called openrecoveryscript with the proper contents and push it to the proper location. Take a look at my directions http://xdaforums.com/showthread.php?t=2016463 is a more manual method, has the command to push the openrecoveryscript to your device, and open up the openrecoveryscript and take a look at it, you can mod it for yourself, it's just a plain text file.

Have a look at all it can do. http://www.teamw.in/OpenRecoveryScript

Once you have pushed the files, have it boot into recovery and the openrecoveryscript does the rest.

---------- Post added at 09:29 PM ---------- Previous post was at 09:25 PM ----------

I'm not sure about all of them, but watch as they will run in the background doing licence checks and such, so expect a change in your battery life.
[Miscellaneous Android Development] tikiral:
GetJar and 1Market won't or shouldn't be doing any real license checks as they're only free apps. (GetJar does just that, just lets you download the jars =)) At any rate, I'd assume they do update polling at some interval and if they do, I'll just turn that off. Not too terribly concerned about it, but thanks for the post anyway. It's probably a good thing to note in case anyone else read my post and didn't already know the implications.

Speaking of posts

@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...

After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.

Thanks again for all the info @t499.
[Miscellaneous Android Development] shizzyraw585:
deleted
[Miscellaneous Android Development] pamulli:
How to install OTA after root?

Sorry if I've missed this, I've read a good bit of this thread and haven't come across this answer.

I used the utility in the OP to root my Nabi before I did the OTA. I got it completely setup with google apps and everything was working fine. I then ran the OTA and after that I couldn't get into TWRP. I would instead get the green android logo with a front panel open and an exclamation point. This looks very similar to Download mode with Samsung devices. The only way I could get into TWRP was to run the root tool again and let it re-install TWRP and then I could only get into it that one time. If I reboot and go into Android and then back to recovery it wouldn't work and I'd get the Android logo instead of TWRP.

I ended up restoring my backup from before the OTA and now everything works again.

So my question is, if I have already rooted my device and installed the custom recovery, what is the proper step to update to the latest OTA? Aside from wanting to get the latest bug fixes, I want to get rid of the annoying upgrading Android bug on every boot.

Thanks,
[Miscellaneous Android Development] shizzyraw585:
Where does the openrecovery script look for the gapps and root .zips? I opened the one inside the files folder and it just says install /sdcard/gapps.zip install /sdcard/root.zip . When I plug the tablet into my PC it shows up as a portable device. Clicking on that there is a drive labeled internal storage. Opening that I can see the root and gapp .zips in there. When the script is executed when the recovery restarts it says that the E: gapps.zip directory does not exist and proceeds to the recovery as normal.
[Miscellaneous Android Development] t499user:
That is going to depend on what they update. :)

Yea, that message is annoying, just flash the new gapps package from twrp. http://xdaforums.com/showthread.php?t=2065878
[Miscellaneous Android Development] DarkAngel:
Oh thanks for this link. I try and search as much as I can for things related to the Nabi2 as I want to try everything out on mine before I do anything to both my daughter's tablets. I subscribe to all the ones I find.
[Miscellaneous Android Development] pamulli:
Well to be more specific, how do I go from a rooted 1.9.19 with TWRP to a rooted 1.9.37 with working TWRP?
[Miscellaneous Android Development] t499user:
It looks for them in /sdcard/ as it is, but you can change it to anything you want as long as the script knows where it is. But when you push root or gapps using:

adb push root.zip /sdcard/root.zip

It ends up in /sdcard/

---------- Post added at 10:21 PM ---------- Previous post was at 10:16 PM ----------

I would say the best way would be to restore your backup, then do all of the OTA updates, and then redo recovery/root/gapps.
[Miscellaneous Android Development] ALD3:
You lost root when you did the OTA some do. First you should go to setting>about tablet>update and check for it, you need to update to 1.9.37 before you root, you will have 2 manual updates to do ....maybe 3. Then run jmz again like the first time.
[Miscellaneous Android Development] t499user:
You are welcome, if you use the files from where I linked you will have the new gapps that doesn't give you the 'android upgrading' message on every boot.

If you use the jmz package you can replace the gapps.zip in the files folder with this one, or just flash the new gapps.zip after with TWRP.(I have asked him to update his package, but haven't heard anything back) http://xdaforums.com/showthread.php?t=2065878
[Miscellaneous Android Development] tikiral:
Sorry it took me so long to get back to you... Couldn't remember the name of the file. Looks like with a more recent upgrade they started ye olde' recovery-from-boot use. Most people using TWRP don't have to worry about it anymore because the install from Goo Manager automatically takes care of it, but since there's not an "official" release of TWRP, we have to do it ourselves. So this is what you need to do:

1. Flash TWRP Recovery however works best for you: jmx's toolkit or fastboot it yourself
2. Boot into Recovery (if using jmx's script you'll already be here after you install TWRP)
3. Go to Mount and Check the "Mount System" box
4. Click the back item and next go to Advanced > File Manager
5. Scroll down to /system
6. Rename recovery-from-boot.p to recovery-from-boot.bak (If you only see a bin folder, you didn't do 3)

Now just reboot system and you're golden. That recovery-from-boot.p file is something that Google put in more recently that will overwrite a custom recovery on boot. Once you've renamed it, TWRP will stick until you manually remove it.
[Miscellaneous Android Development] pamulli:
I actually didn't lose root because I first installed the OTA root keeper, but I couldn't get TWRP to work again.

My kids will kill me if I keep this tablet any longer so I'll have to wait a few days before restoring to stock and doing the OTA.

Thanks,

---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------

Wish I had asked this before I restored back to my rooted 1.9.19. Now I have to do the OTA again. Oh well I appreciate you answering my question.
[Miscellaneous Android Development] DarkAngel:
Ah okay, good to know. I had his downloaded already but will update with these you stated before I try. I notices the other link where the Nabi2 was taken apart. We seriously need a section for this tablet now and maybe a spot in the wiki section as well. I would love to mod mine with GPS for sure. Would complete the package for me. Thanks again.
[Miscellaneous Android Development] t499user:
root.zip deletes /system/recovery-from-boot.p

So if you follow the steps in post 1 and do your OTA updates first...
[Miscellaneous Android Development] shizzyraw585:
OK, so no matter where I adb push the gapps and root .zips to on the internal storage of either of the two tablets purchased today I get the same error E :Can't open (wherever directory the zips are in) . For example E :Can't open /sdcard/Download/gapps.zip . Even though I can clearly see the files in that folder when I plug the tablet into the PC !!! WTF!!!! The only other thing I can think of trying next is an external sd. How would I tell the the openrecovery script to look in the root of an external SD? install /sdcard1/gapps.zip ?
[Miscellaneous Android Development] tikiral:
Ah-Ha! That's what I was missing. While the first option in OP's set up says "Install Recovery, Root and Gapps", it actually looks like it only does Recovery and Gapps according to the script. root.zip only gets copied to the device in option 2.

For those of us that OTA'd post script though, this is still something to look out for. Personally I just fastboot the recovery and don't flash root.zip anymore, instead opting for OTA Rootkeeper.
[Miscellaneous Android Development] gijosh28:
Ok so I returned the last Nabi with the broken Volume button and now this new Nabi won't connect to my wifi right out of the box. So I cant set the damn thing up. I booted into fastboot mode, push twrp, and pushed the wifi fix file, and installed that, and now the tablet cant see any wifis much less connect to one. So now I am just trying to restore my other backup to this tablet. This is getting old.

---------- Post added at 01:13 AM ---------- Previous post was at 12:18 AM ----------

Finally. I adb pushed my backup from my good one to the new one and restored it, and everything is working perfectly. I have no idea why it worked this time. All the icons are correct and everything. Either way it's good and I can finally give these things back to my little ones. Thanks to everyone that helped me out. Big Thanks to t499, ald3, and jmztaylor!!!

---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------

Also if anyone has two of these and buys the screen protectors from Fuhu, they come two in a package. I didnt see where it said how many came in a package so I ordered to packages, but would only have needed one. Just an FYI to everyone.
[Miscellaneous Android Development] t499user:
You can also leave the original protector on and just use an alcohol wipe to clean the printing off of it = free screen protector :)
[Miscellaneous Android Development] dottat:
You may need to boot the tablet up first after installing the custom recovery. I've had this problem in recovery and once I allowed it to boot to the rom it was fine the next time in recovery.
[Miscellaneous Android Development] katinatez:
Your adb push command is incorrect, I quoted my post to show the correct commands. I also use TWRP openrecoveryscripts to do everything since the recovery touch screen is off.

The correct command is

1. adb push gapps.zip/sdcard/Download/gapps.zip

2. openrecoveryscript are viewable & editable in Linux OS, I use Ubunto 12.10,

3.install /sdcard2/gapps.zip

Good luck

---------- Post added at 12:48 AM ---------- Previous post was at 12:34 AM ----------

If you can see the folders already in sdcard this is what I would do.

Boot into TWRP recovery> plug USB cable to PC> place a openrecovery script named install.openrecoveryscript with this command in Home folder in Linux OS (I use Ubunto 12.10)

install /sdcard/root.zip

install /sdcard/gapps.zip

In terminal type this, 1 command at a time

sudo adb start-server

adb devices

you should see a serial number after the last command & recovery

after that type this in terminal

adb push install.openrecoveryscript /cache/recovery/openrecoveryscript

then this command

adb reboot recovery

all this should install root & gapps

Good Luck