yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] DarkAngel:
I believe your talking about posts 1590 and 1592. deskjet390 had it almost going with a Nexus 7 ROM ( Liquid Smooth 4.2.1 )

http://xdaforums.com/showpost.php?p=45062147&postcount=1590

http://xdaforums.com/showpost.php?p=45090007&postcount=1592

Until my vacation got pulled from me.......:mad: , I was going to try and play around with that ROM as well.
[Miscellaneous Android Development] aicjofs:
Can't you just sideload the Mee Genius app if you have it on other devices or is it a drm thing?

deskjet has an image of the Jellybean Disney tablet. Haven't heard from him since then.

I was talking to jmz yesterday. He had a good suggestion about symlinking Wings from /vendor/app to somewhere on /data. Of course alot of people have low space on data as it is. Of course you could free some space by also symlinking some of the fuhu apps from /data/app to data/addon_res since that is a duplicate of over a 1GB. All this for people that want the entire Nabi experience but with gapps and root.

I also figured out how to get nvflash(forced recovery) working on the Nabi. I have bootloader.bin, made what I think will work as flash.cfg, BCT and ODM. Haven't worked up the courage to wipe the NAND and see if I can rebuild it.

So even if Fuhu has given up on Original Nabi2 we haven't here. Right? Can I get a right!! haha.
[Miscellaneous Android Development] Bait-Fish:
Right! :)

Thanks for keeping the Nabi 2 going.
[Miscellaneous Android Development] WFG:
Xposed Framework & XTheme Engine work great on the Nabi2..

[[XTHEMES]] THEMES PLANET [MIUI & x86 Supported] [[Updated-11TH OCT 2013]]
[Miscellaneous Android Development] Ken Esq:
Timer Function

Has anyone been able to separate out the new timer function and install it? I'd love to have that functionality as the Nabi Mode seems to block all other parental control software like Qustodio.
[Miscellaneous Android Development] chlor3:
Done.

I am just finishing up a script to do exactly that. It runs a modified init.rc to symlink the vendor folder to the addon_res. It is tricky since somethings are hardpathd to the vendor/firmware. I shuffle files around and end up storing bakcups on the external sdcard. I have ~40% empty system and a full Nabi2 experience. I have done one of my Nabi's and am testing it out on the second now.
[Miscellaneous Android Development] Eric Karz:
Nice post I was able to get it working on my xd as well

whats the name of the theme in the picture? I found red and urbanx.
[Miscellaneous Android Development] WFG:
It's called Crimson Cobalt.

http://xdaforums.com/showthread.php?p=43842391
[Miscellaneous Android Development] Eric Karz:
thank you . it worked Sweeet
[Miscellaneous Android Development] mcangeli:
Trying to install the 2.1.27 update via this zip. It should be as easy as downloading it to my sd card, booting to twrp and installing correct?
[Miscellaneous Android Development] hilltopper06:
You wouldn't happen to have a version of this so I can get from 1.9.37 to 2.0.5 would you? I removed monarch on my 1.9.37 so I can't update to 2.0.5 or to 2.1 from there and I really don't want to blast the device if I can help it.
[Miscellaneous Android Development] aicjofs:
It's not an install, it would be a restore. Open those zips up and extract to your TWRP directory in a folder called whatever, lets call it restore. TWRP/BACKUPS/XXXX/restore, where XXXX is your serialnumber(you could generate for you if it's not there by making a quick backup of just boot in TWRP). Should need only boot and system to restore. Then restore in TWRP.

There is a zip floating around to go from 2.0 to 2.1 did not that work for you?

I don't. You could restore a 2.1 ROM like above and then delete monarch stuff in TWRP, then install root and gapps and doubt you would have to start over.

Both of you make a backup first so at least you are back to this point should something go wrong.
[Miscellaneous Android Development] mcangeli:
The tablet has a weird issue where when it reboots for updating it powers off but does not restart. I was having an issue getting the stock recovery image back on it.

I was able to get the stock recovery back on with fastboot though and do the update OTA. Then I was able to get the TWRP you had created back on it and use adb to push root and gapps to the tablet. Happy to say its rooted with 2.1.27 running on it and google play and all the goodies I had before! I did have to remove wings (I wasn't going to pay $50 for something they wouldn't use too often) but I love the time controls on this build (they need to release that to the play store).

Yay!

Thanks for the reply
[Miscellaneous Android Development] aicjofs:
Well I completely bricked my daughters Nabi playing around with nvflash. I got to a point where pressing the Vol and power buttons wouldn't bring up a bootloader menu, and with further devastation I created: nothing happens at all... screen doesn't even power on.... except APX.... and this was intended ;)

I was able to wipe the device emmc, recreate partitions, install partition table, bootloader, BCT, etc and eventually restore the whole device with the backup I had created with nvflash prior to all of this. In fact she is playing with it now, after getting quite irritated with my slowness. I admit I wasn't sure it was a promise I was going to be able to keep in the time I laid out to her.

For anyone that has used nvflash(forced recovery) here is what I believe somewhat works for the Nabi2 original US edition.

I can't really see any normal use for this as TWRP takes care of most situations we will ever face on this particular device because we don't hack the bootloader. It's possible to re partition with this, I was unable to however as it complains that the BCT(the nabi.bct, using kai.bct doesnt have that issue) is full of bootloader calls. Using a hexeditor you can see the 4 duplicates of the device configuration(nabi.bct), and that information is repeated almost 100 times, probably need to write 00's somewhere but I havent went that far because it looks like you have to write a AES-CMAC checksum to the first 0x10 of the file.

It's a dangerous program and really I only post it for anyone that has experience using nvflash. You can easily brick the device(or bring it back from the dead if you know how, it's really unbrickable if you get all the files, only thing that can stop you is a dead NAND, USB port or CPU in which case you are done anyway)

backup.bat - will backup everything but the system, data, and addon partitions. I'm going to update TWRP to have the ability to backup addon(almost anyone can run this as long as your device is working properly not much can go wrong as it's only backing things up, you should be able to recovery from anything with these backup files)

--after running it you will also have a partitiontable.txt and nabibricksafe.img, along with the partition images.

flash.cfg - I reconstructed this from looking at source and partition table pulled from the device

flash800.cfg - Same as above and what I believe "may" be right for the Disney and Nick tablet

bootloader.bin - The bootloader from the device

bootloader.bin.sourcecode - A bootloader from Nabi source

nabi.bct - The BCT from the device

kai.bct - A simple Kai BCT.

help.txt - list of nvflash commands

I believe the odmdata is 0x40098000

Nabi NVflash

You will need the APX driver for any of this to work. Probably use this one http://xdaforums.com/showthread.php?t=2263822
[Miscellaneous Android Development] chlor3:
I just ran backup.bat and now I am suffering these symptoms.
[Miscellaneous Android Development] aicjofs:
I duplicated this. The script I was using to test was backup1.bat and I uploaded backup.bat. So I made a change to the backup.bat in the download so download it again into a different directory.

Are you at a point where if you press vol and power and you get no "menu" at the boot loader but it continues to boot?

If yes let it bootloop for awhile and you will eventual end up in TWRP. In TWRP reboot, then select bootloader. Now is the menu back?

If yes go back into forced recovery(or if to start this whole thing you are at a black screen)

Did the program write bricksafe.img in the original directory you ran the program from? If yes, in that directory type:

nvflash --bl bootloader.bin --odmdata 0x40098000 --rawdevicewrite 0 3072 bricksafe.img --sync

If it didn't download bricksafe.img or the above didn't work. Go to the new downloaded directory and try:

nvflash --bl bootloader.bin --odmdata 0x40098000 --rawdevicewrite 0 3072 bricksafe2.img --sync

If for same reason in TWRP the reboot-bootloader doesn't bring up a menu but reboot to no menu, try fastboot reboot-bootloader to get the menu.
[Miscellaneous Android Development] chlor3:
Oh I am way ahead of you. :) I fixed the boot loop entirely. I now just get the nabi logo. No spin. no menu. just the logo. no boot. I void warranties.

Yes i have verified all the files from the script were pulled from the device.
[Miscellaneous Android Development] aicjofs:
When you get Nabi logo do you see anything in device manager? Fastboot is usually up then if it doesn't boot anything. THen you can fastboot bootloader an I have always had menu come back.
[Miscellaneous Android Development] chlor3:
Windows7 reports NABI2-NV7A

Ubuntu reports Nvidia Android and upon disconnect gives me a MTP error.
[Miscellaneous Android Development] aicjofs:
That should be fastboot then. Which I though was weird and installed the fastboot driver. What happens when you fastboot reboot-bootloader?

Also how exactly did you "fix" the bootloop? After the bootloop it should kick you into recovery.
[Miscellaneous Android Development] chlor3:
Lets just say I have plenty of room on all partitions. If you were to add up all the free space on the internal partitions it would probably equal about 8gb. See "fixed." No more boot loop. :)
[Miscellaneous Android Development] aicjofs:
Oh... Ok so how did you accomplish that? What did you do to wipe things? If you see the Nabi logo you didn't completely erase the flash, bootloader.bin still has to exist or you would see nothing. You need to get back to APX to recover.
[Miscellaneous Android Development] chlor3:
I was restoring my various TWRP backup and wiping partitions before restore. I got ahead of my self on the last one and rebooted before the restore. so now I am trying to get it into APX
[Miscellaneous Android Development] aicjofs:
In Win7 when device is at Nabi logo, what does device manager say for device-details-device instance path?

What if you let it set at that screen for 5 minutes or so?
[Miscellaneous Android Development] chlor3:
USB\VID_0955&PID_7102\015D2109AD0C1006

Not much for 5 minutes... Status changes to a "This device cannot start."
[Miscellaneous Android Development] aicjofs:
Did you try editing your driver inf for that and forcing it to a fastboot/bootloader interface?

PID_7100&MI_00 is usually MTP

PID_7100&MI_01 is usually ADB

Not use to seeing 7102, 7000 is usually fastboot. Trying forcing that to fastboot driver.

EDIT: I guess it could be ADB, what about adb reboot-bootloader
[Miscellaneous Android Development] Eric Karz:
just a note that the only thing that I had a problem with was the lock screen .

I was able to remove 3 lines in public.xml to make the default work like normal. it works on nabi 2 nabi xd and nabi jr. If interested in the file pm me. thanks again
[Miscellaneous Android Development] chlor3:
Manually enter recovery mode:

I did it. I am in APX recovery ( interface USB\VID_0955&PID_7330 ).

I found the terminals to connect after opening the device and removing the center screw in the motherboard and the cpu-cover/heat-spreader (removing the center screw is not required but recommended if opting to not remove the heat spreader).

Do this as last resort!

(Your device should already be bricked and you cannot enter APX mode by holding down the power/volume+/volume- at the same time, if this the case a disclaimer about the dangers is a bit unnecessary at this point. But yea doing this you can break it...permanently... or bring it back from the dead like I did.)

Manually enter recovery mode:

power off the device.

To open the device only the 4 outer screws at the corners need be removed, then use a sharpish prying tool to work your way carefully around the edges releasing the edge clips.

Remove cpu-cover/heat-spreader: The terminals are located on the button side of the board above the center screw. It may be possible to connect the terminals without removing the heat spreader and only removing the screw, but the risk is grounding against the heat spreader (not recommended). An added benefit of removing the cpu-cover/heat-spreader is to verify good contact between the thermal pad and heat-spreader/cpu (mine was only contacting about 25% so I added some thermal grease to increase the contact surface area.)

connect the two silver solder pads closest to the word "Recovery" ( I held a bent paper clip against them ),

power on the device, while the pads are still connected.

APX mode is instantaneous if done correctly

enjoy APX mode.

The word "Recovery" is partially covered by the center screw (screw and heat-spreader are removed in image):

This is an image of the recovery terminals with the center screw and heat-spreader installed:

Edit: An update:

I have successfully re-flashed my bootloader using aicjofs commands for nvflash and restored access to the bootloader menu. From there I restored a TWRP backup and am back in business.
[Miscellaneous Android Development] aicjofs:
Just when you think we know everything we are going to know about the Nabi.
[Miscellaneous Android Development] alexbobspoons:
Heres an interesting question....

Can you get the nabi-store app (and thus account login) on a standard android device??

Im just looking at how much I have spent on my sons nabi, and considering it took a real tumble the other day, if It were to break, would I consider a different tablet, easier to expand the memory, yet retain the apps I purchased?

Just wondering.

Thanks

Alex
[Miscellaneous Android Development] aicjofs:
Well some more messing around with nvflash and I have a proof of concept. Below is 2 different Nabi's

Both devices work normal. One has root, gapps, and NO Wings. The second Nabi has root, gapps, AND Wings. Notice the partitions. The top is a normal Nabi. The lower one is modified through nvflash with new partition layout. The Cache partition sacrificed some space and System partition grew.

Leaves some interesting ideas for those that want to get rid of all the Nabi apps and run bare. You could recover system space, and the entire 1.5GB on the addon partition and add it to Data partition. Or perhaps one day have the Nabi with JellyBean and all the Nabi apps.
[Miscellaneous Android Development] knoxploration:
Oh, yes please!!
[Miscellaneous Android Development] vitaminwater:
Finally got root, twrp, and gapps on mine but when i reboot it says "google services framework has stopped" and will not allow me to sync my account. So I hopped onto goo.im and grabbed the gapps from there and installed those in recovery and I get the same error. I have wiped dalvik and cache but have not done a full wipe

I also get "google partner services has stopped and "tak has stopped" upon boot up.

Would someone be kind enough to shed some light on this?
[Miscellaneous Android Development] codest3r:
In case this saves you any frustration... I wasted about an hour myself.

So I just upgraded my 3 Nabi 2's to 2.1. First TWRP, then flashed ZIP and missing libs. All seemed well after first boot.

However I thought I'd go to superSU to confirm root is still there... And it said it needed to install new binary. Wouldn't let me into the app without running it. Every attempt to upgrade would fail. Then realized I'm an idiot. Spent so much time trying to get it to take.

I found downgrading SuperSU from Play Store let the app work fine again. Root worked fine just the latest SuperSU app was giving me the heartburn.
[Miscellaneous Android Development] katinatez:
How did you downgrade?
[Miscellaneous Android Development] codest3r:
Go to market, installed apps, then select SuperSU and Uninstall. Leaves original version, just removes the update.
[Miscellaneous Android Development] katinatez:
Learn something new every day, side note Nabi 2 are going on sale Black Friday 2013 [MENTION=2636293]walmart[/MENTION] $99 buying 2 of them.
[Miscellaneous Android Development] DarkAngel:
Quick question....

Am I able to run a root checking app and have it say I am rooted? If so then I have lost or may have messed up root access along the way some how. I have been trying to update BusyBox but it just wont budge. Rootchecker stated I am not properly rooted.

If this is the case, I can always do as aicjofs stated before.....

I am pretty sure the root file is not limited to the updates/version correct? I made my own script to just load the root.zip file but that didn't seem to fix my problem. I mean SuperSU does show, open up and permission requests do come up to allow apps when they request access for root, except for BusyBox or Rootchecker letting me know there is something wrong with root access. Maybe switching from Superuser <---> SuperSU at some point may have left it open but with errors? Any insight is greatly appreciated. I do have backups from before 2.1 so I can always go back but I rather learn about all this which would also be better in case someone else is having/may have the same issue/s.

====================================

11-26-13

Small update ..... I took my tablet back to one of my old backups on 2.0.5 and regained my root. Updated from 205 to 210 and was good to go. Rootchecker let me know I was good, re-installed BusyBox and all is well. I then began playing with Xposed Installer, again granting root access to the modules so they load up and wouldn't you know it.......lost root again. I guess one of the settings in a module or a module modified certain system files to make me loose access, my best guess at the moment. Have not used the module after going through the process all over again and all is well, and I was starting to like the ease of modifying the tablet with that module.
[Miscellaneous Android Development] ProCision:
I had to send my Nabi in for replacement. I just got it back and they sent me a new one. Good for me. Just dont know if I can root it now. Here is the ver. they sent me

2.1 -release-keys

Kernel ver. is 3.1.10-00421

when I check for update its on the latest one.
[Miscellaneous Android Development] DarkAngel:
That's exactly where I am at as well and yes you can root it. I am rooted with all GApps running. I am about to root a neighbor nabi2 for them removing all the Nabi Apk's and installing GApps. Should be fun.
[Miscellaneous Android Development] ProCision:
So just follow the same steps as I did when I first got it?

Sent from My Note 2 on Tapatalk 4
[Miscellaneous Android Development] aicjofs:
Well interesting development today since I finally had a few hours of free time.

Disney Jellybean version will indeed run on the old Nabi2, of course that's with my Nabi modified for 800MB system partition. I deleted some stuff and it can still fit on and old Nabi with 500MB partition if you get rid of the Disney specific apps, and time controls and university, at that point though it's hardly usable as a Nabi mode device. I guess you still can dictate what your kids can play. The key is modifying the bootloader.
[Miscellaneous Android Development] Eric Karz:
Can you upload something for science? lol
[Miscellaneous Android Development] aicjofs:
It comes with a boat load of caveats at this point.

-We must use nvflash to modify the bootloader which can go wrong and brick the tablet(although at this point I think it's unbrickable if you take it apart)

-The key combination seems different to get the bootloader screen. It still seems like power and vol+ but I have to hold power for a few seconds then vol+

-TWRP for NABI2 will not wok, you now must use TWRP for Disney

-You have to delete your data, I was unable to figure out how to get out of a bootloop otherwise. You will keep internalSD data.

-When it boots the first time it hangs while "setting up the Nabi". After rebooting it seems normal.

-Its very lagging during the intial boot up.

-I have deleted all the apps I think are Disney Nabi specific

-I had one random reboot

The general idea is this

Back up everything in TWRP, or just stop now.

Download NABI2JB.zip and JBimage.zip, and APX driver(get the last one here http://xdaforums.com/showthread.php?t=1998650 )

Extract NABI2JB.zip

Boot Nabi to forced recovery

Install APX drivers

Run the Jellybean.bat

---This will backup important partitions of tablet and should make it impossible to brick

---It will write JB bootloader to tablet

---It will write TWRP for Disney

Boot into TWRP for Disney(Here is where it's tricky on mine with the key combo)

Make a backup of just boot to where you plan on putting the JB image to restore(i.e Internal or External storage. We must do this to get the new TWRP serial number path)

Extract the contents of JBimage.zip to the TWRP/BACKUPS/xxxxxx/JB

---this will be boot.emmc.win, etc

---xxxx is the serial number of the Nabi now in TWRP(It's changed, mine was 0f41000001000000 and might be the same for everyone. NabiXD does this)

---Make the JB folder yourself or whatever you want to call it.

Factory reset

Restore both boot, and system

Don't delete the files this creates(i.e. 04_EBT_raw.img etc) they will be used to get you back to normal tablet. In fact take them and store them somewhere safe.

Run ICS.bat to return to normal bootloader, and TWRP.

PM me if you want the links, it's far too dangerous and complex this early on. Otherwise talk about issues in the open forum.

EDIT: Oh you will need Gapps for JB, not the old Gapps for the Nabi.

.
[Miscellaneous Android Development] DarkAngel:
This is awesome! I have been wanting to go to JB since the XD for some time now. Great news!

I finished up a neighbors Nabi2 last night. Another neighbor of mine has one also which I am pretty sure they don't even use anymore as they don't have a charging cord for it. I am going to see if they would want to part with it. Honestly if I could get it for a good price, I would send it over to you for further testing and development. I had also rooted and installed Gapps on that one as well LOL.

---------- Post added at 10:34 PM ---------- Previous post was at 10:30 PM ----------

Yes but you have to make sure you delete some APK's from the monarch ui, as aicjofs stated before ,in the system/vendor/app through TWRP to make some space for the Gapps or they will not take. The recovery.img ( or TWRP ) can be swapped in from the newest version if you want from the downloads available. TWRP should be installed first like the directions stated in the very beginnings as that is what is flashed first here ------> Ubuntu Linux . This is the method I use to do mine.

If you can't get it going let me know. I made a full backup of it through TWRP already rooted, Gapps and not yet signed in to all the Google accounts if you need it.
[Miscellaneous Android Development] Eric Karz:
You re now a true nabi master ...lol the science works .

only thing I don't get is " Don't delete the files this creates(i.e. 04_EBT_raw.img etc) ' where is that ? .but thanks its like having a new nabi 2

oh yeah there is a update showing but I didn't bother ...Wait for master to do his magic ..lol

Edit : I didn't have to do anything with gapps ?

---------- Post added at 06:13 PM ---------- Previous post was at 05:18 PM ----------

Walmart has nabi2 for 99 bucks on there black(Thursday AT 6pm)Friday special
[Miscellaneous Android Development] aicjofs:
I just included the Gapps to remove one more variable.

What I meant by don't delete the files is that the ICS.bat looks for one one of them, and any other script in the future might use them. Most aren't specific to the tablet so they could be uploaded but that wastes everyones bandwidth. Easily the most important file is the bricksafe image, if you keep one, keep that one.

You are the master at finding bugs, what did you find so far? Did you have any of the issues I listed?