yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] shizzyraw585:
Something definitely seems wrong here.

This morning I went into the files folder of the jmzrootpackage and opened a command window there. I renamed the gapps (already replaced with t449's last night) to abc.zip . Opened the gapps-openrecovery script and changed the first line to install /sdcard/abc.zip .

adb reboot recovery

adb push abc.zip /sdcard/adc.zip

1252 KB/s <52047601 bytes in 40.580s>

adb reboot-bootloader

boot normally

Once the tablet is booted I can see there is a file abc.zip in the root of internal storage. The push was successful and the directory does exist.

adb reboot reboot recovery

adb push gapps-openrecoveryscript /cache/recovery/openrecoveryscript

9 KB/s <49 bytes in 0.005s>

adb reboot recovery

Greeted with the following error at recovery launch

E:Can't open /sdcard/abc.zip :confused: :mad:

(No such file or directory)

I'm sure this is a classic example of PEBCAC but this seems like it should be pretty straight forward. The recovery is flat out not recognizing a file that is clearly there. I'm no dev but I've been dabbling since the original myTouch and this one has me whipped. I would definitely appreciate any more ideas you guys have.
[Miscellaneous Android Development] cruise350:
Have you tried using an external sdcard? I'm assuming you must have the touch calibration error since you are not using twrp to flash the zip file. Twrp always behaves better with external sdcard s so try that if you haven't.
[Miscellaneous Android Development] aicjofs:
Anyone want to guinea pig a TWRP build I made?

It's version 2.3.3.0 with the latest Nabi kernel. I don't think it will fix touchscreen issues but worth a try. EDIT: Some early results are indicating it is fixing touchscreen issues.

You can try it without installing it permanently

extract recovery.img from TWRPrecovery.zip to your adb directory

adb reboot-bootloader

fastboot boot recovery.img

That won't put it on the device just boot it to ram and you will maintain your current TWRP after a reboot. To make it survive reboot obviously you would need to

fastboot flash recovery recovery.img

http://home.comcast.net/~aicjofs/TWRPrecovery.zip
[Miscellaneous Android Development] shizzyraw585:
Bro you have been officially upgraded to god status. You just ****ing fixed the touchscreen issue. Been trying to get this this flashed for literaly about 15 man hours. I love you.:highfive: :victory:
[Miscellaneous Android Development] gijosh28:
Thanks for working on this!
[Miscellaneous Android Development] t499user:
I haven't had a chance to test it yet, but there were quite a few improvements in the newer versions. Thanks for taking the time to do this, if I had known how, I would have done it. Maybe you could do a guide?

If it all comes out well, I will add it to my package. This combined with the new gapps should def cut down on the issues people are having.
[Miscellaneous Android Development] aicjofs:
Yes if this works we really need to do a whole new package. recovery.img, gapps and also fix the install.bat so all options work.

Edit: Also if it works I must partially credit jmztaylor I used his BoardConfig.mk as reference and made new changes and built source from there.
[Miscellaneous Android Development] t499user:
I am going to go put an alternator/radiator back on a car, and when I get back I will test it out. I can't test the touchscreen issue as I never had it. I will add it to my package later today if all goes well. I don't know if jmz will update his, I still haven't heard back from him.
[Miscellaneous Android Development] shizzyraw585:
It works bro. I flashed gapps and root within one minute via touchscreen. You rock. And yes I suffered from touchscreen issues.
[Miscellaneous Android Development] t499user:
If you have the touchscreen problem, please try this and confirm if this is working for you or not.
[Miscellaneous Android Development] shizzyraw585:
My touchsreen problems were fixed after flashing this recovery.
[Miscellaneous Android Development] gijosh28:
I think he is trying to make sure a few other people have the same good results you did. Duplicate results. Scientific method...
[Miscellaneous Android Development] aicjofs:
Well I am glad it worked. Both my touchscreens work fine with old TWRP, but I feel bad for all those having issues so I was thinking that it might be kernel related as the recovery.img from first post has the older kernel not the newer one, but maybe it was something wrong in an earlier version of TWRP. Since I made both changes I guess we will never know.

To be honest I hope it works for everyone. I made a CWM recovery image so people could use the buttons instead of touch and I was having a hard time mounting the internal sdcard properly. Add to the fact that the scard actually resides on data partition and I wasn't sure if someone wiped the data partition if CWM would deal with moving the sdcard data prior to the wipe.
[Miscellaneous Android Development] t499user:
I would be willing to bet that it is kernel related, but the new version of TWRP did improve mounting as well. Either way, I have tested some backup and restore operations and it all seems to be going well.

I have updated my package to include your recovery, thanks for working this out.
[Miscellaneous Android Development] elijahbrown:
I think if we want to get our own forum, and we need to start posting these great mods in the general forum in their own thread. Also any questions people have that are not related specifically to this thread.

I'm sure it would go along way if we used xda standards when creating new posts. Just start all new threads with [NABI2]

For example, if please post this new recovery under [NABI2 ] [KERNEL] LATEST TWRP

or [NABI2 ] [APP] latest gApps

In order to make sure your question or thread is not overlooked, you can always post a link to the thread in here.

As soon as I get some time this weekend I'll put out some mods to try and fill up the general section. Anything anyone would like to see ported over, and or maybe a feature implemented? I'm open to suggestions.

Sent from my NABI2-NV7A using Xparent ICS Tapatalk 2
[Miscellaneous Android Development] t499user:
Cyanogenmod ;)
[Miscellaneous Android Development] aicjofs:
OK if that's what the group wants, I'll post it if we get some more feedback that it's working.

We are going to still need more development.

We really only have gapps, a Nabi ROM image with root and gapps, a ROM image with root and gapps with Nabi stuff removed, maybe this TWRP, lockscreen modding, some accessory mods(i.e. back plate). Other devices have single threads with more pages then all our Nabi stuff, don't get me wrong, I'm all for it but we are pretty light still.
[Miscellaneous Android Development] knoxploration:
Yes, it makes sense to give each separate development its own thread. Even if it doesn't merit us our own forum, it will help organize people's thoughts rather than the thread being a mishmash of unrelated stuff.
[Miscellaneous Android Development] katinatez:
Happy Guinea Pig

Tried your recovery, all I could say it's perfect. Touch screen in TWRP recovery is 100%. Have ben plagued with the touch screen error in recovery prior to aicjofs latest 2.3.3.0 TWRP recovery.

jmztaylor, aicjofs, t499user, e2950 deserve the XDA Nabi 2 award. Have owned the tablet maybe 3 weeks, in that time was able to restore from soft brick, get a working gapps witout 'Android Upgrading", and new updated 2.3.3.0 TWRP recovery. Got to Love XDA community.

All we need now is our own forum :laugh:
[Miscellaneous Android Development] Eric Karz:
thank you sir

tried it then flashed it
[Miscellaneous Android Development] aicjofs:
Alright I posted a thread on the new TWRP recovery that seems to be fixing touchscreen issue.

http://xdaforums.com/showthread.php?p=36083895#post36083895

I normally like to fly a little more under the radar on the internet, but since there seemed to be demand to make a new thread... I'm doing it for all those little kids and there Nabis out there. LOL. Feel free to stop by so I don't feel so stupid by myself ;)
[Miscellaneous Android Development] ALD3:
TWRP 2.3.3.0

I for some reason had trouble with adb code. Booted into bootloader but kept getting not found. Recovery.img is in my sdk tools platform. Any who, I just replace jmz recovery with 2.3.3.0 and ran install.bat, also replaced gapps with t499 gapps renamed. Pulled usb after recovery flashed and all works fine. I didnt have the touch problem so can't add to that. Wish I had gotten adb to work. Thanks for the new recovery. I know the ones with touch problems are really glad.
[Miscellaneous Android Development] stkiswr:
wow thank you so much for the new recovery it fixed my touchscreen issues!!!!!!!!
[Miscellaneous Android Development] reade0871:
I reached out to dees_troy and he compiled twrp 2.3.3.0 for the nabi as well but I never posted it because I was trying to figure out how to do this myself. Sorry.
[Miscellaneous Android Development] DZLRULZ:
Wonder if the screen layouts are stored outside /system or /data...like in /.Android or something on the internal storage?

Struck by my Anthrax Infected Viper4G Ev_O_nE using Forum Runner
[Miscellaneous Android Development] gijosh28:
Strangest thing, but the last time I did it, it worked. I had completed making One nabi totally kid safe with full versions of all the games worth having, and took a brand new Nabi out of the box, pushed TWRP to it, and restored a backup of the good Nabi is it worked perfectly. The menus are correct any everything. Like t499 said I must have been doing it wrong. Whatever it was I did wrong, I did it wrong about 5 times. Either way, I turned the tablets over to the kids this morning and they are totally stoked. I can't thank the people in this thread that helped me out enough. If anyone else needs my help let me know. In the end, the only thing I couldn't lock out was pocketchange, but the kids can't buy anything or log into it, so it doesn't matter if they find their way into it.
[Miscellaneous Android Development] oniddy:
???????

I can't seem to make ovoo work I can't video chat my camera is black ......I like to steal this incredible tablet from my kids at night loL :D but in ovoo nobody could see video chat :eek:
[Miscellaneous Android Development] caughron01:
Anyone that could help me I would appreciate it. My computer is recognizing my tablet but I am getting errors in TWRP see pics below of what they look like after trying option 1 and 2 they are not installing anything it install trys to run for a couple of seconds then just returns to TWRP menu screen.
[Miscellaneous Android Development] t499user:
Which TWRP are you using?

Edit: If you are using the files from the first post, use this gapps.zip instead: http://xdaforums.com/showthread.php?t=2065878

As well as the new recovery: http://xdaforums.com/showthread.php?t=2074501

If you want a more manual approach, check out: http://xdaforums.com/showthread.php?t=2016463
[Miscellaneous Android Development] caughron01:
I tried that manual approach and I am not that familiar with cmd and what command lines to use to make it work, I'm using windows 7.

I get apt-get is not recognized as an internal or external command, twrp version 2.2.2.1
[Miscellaneous Android Development] t499user:
Basically you don't use apt-get(package manager on linux) you would install ADB and Fastboot for Windows.

Then the rest of the commands, just remove sudo from the beginning, and it will work for you.

---------- Post added at 02:19 PM ---------- Previous post was at 01:49 PM ----------

Here tikiral explains a bit more about installing ADB and Fastboot on WIndows.
[Miscellaneous Android Development] caughron01:
I think my device is jacked, it wont go to regular home screen anymore just shows nabi loading picture. I can goto recovery but when i type a command it says waiting on device..... Is it bricked?
[Miscellaneous Android Development] t499user:
Read the third post on the manual method I explained, it tells you how to get into Fastboot manually, if you can get into fastboot then you can fix it.

If you need to go back to stock, check out http://xdaforums.com/showthread.php?t=2041224

Edit: If you can get into fastboot protocol on the device, then it is not bricked. But you will probably have to go back to stock and then go from there.
[Miscellaneous Android Development] caughron01:
You think you could help me over the phone with this? I'd be willing to paypal you some cash I'm stressing that I broke my kids tablet lol

Im trying but just don't want to make things worse
[Miscellaneous Android Development] t499user:
I am about to head out from the house, but if you don't get it working, then I can help you out when I get back. Can you get into fastboot on the device?

You can PM me your number, and $ will be unnecessary ;)
[Miscellaneous Android Development] katinatez:
For those using Windows 7 cmd this is an excellent tutorial to set up ADB and Fastboot directory once, and use cmd without having to go into the directory of core files. Basically run ADB or Fastboot commands by just opening cmd.

http://xdaforums.com/showthread.php?t=1162034

Sent from my GT-I9300
[Miscellaneous Android Development] caughron01:
K, pm sent thank you. When I fist get to menu screen options I have are,

Bootloader

Continue

Reboot-bootloader

Reboot

Poweroff

when I click bootloader it brings me to next menu which gives me fastboot protocol option I click it and it brings me back to main options.

Is that the right fastboot option?
[Miscellaneous Android Development] katinatez:
Yes, redo the steps, and when you get to Fastboot protocol. Then plug in USB cable, then you should see Fastboot device. Then Nabi is ready for Fastboot commands.

Sent from my GT-I9300
[Miscellaneous Android Development] caughron01:
not working, lost right now and my brain hurts from reading over it all
[Miscellaneous Android Development] ALD3:
If yoou use the apk Quick Boot, you can boot to Reboot ,Recovery ,bootloader, Power Off and Hot boot with a simple click, iits a lot faster to recoot, go to recovery or Bootloader.

Just thought I would pas the Tip along for anyone that might like ti.:cool:

---------- Post added at 04:50 PM ---------- Previous post was at 04:31 PM ----------

I was having major problems, till I copied recovery.img into sdk/tool with the fasrboot. Then just booted into bootloader and ran fastboot flash recovery recovery.img and it worked fine. I also along time ago put cmd in my tool folder with a shortcut on my desktop (PC).

I never saw bootloader device in bootloader, I see recovery device in recovery.
[Miscellaneous Android Development] caughron01:
I don't think I am getting how to use fastboot correctly or something I type the commands,

I am following steps here minus the sudo apt-get install android-tools-adb android-tools-fastboot, When I do that it says invalid command or cannot find file

ok ill just type what I am doing step by step to see if I am missing something or doing something incorrect.

1. Tablet plugged in and currently on the black screen with options boot normally, fastboot protocol, recover kernel,

forced recovery

2. Enter recover kernel

3. then type in cmd fastboot flash recovery recovery.img then CMD promt just says waiting for device

If I click fastboot recovery it just returns to previous menu where it has

Bootloader, Continue, Reboot-bootloader, Reboot, poweroff
[Miscellaneous Android Development] katinatez:
Tablet has to be unplugged from PC until you click volume+ button on tablet, when you enter Fastboot protocol. Then plug in USB cable to tablet. Also nabi twrp 2.3.3.0 , you might have to extract first. recovery.img has to be in the same folder as the Fastboot.exe. First type in cmd Fastboot devices, your tablet serial # should appear if everything is correct. Then just type

Fastboot flash recovery recovery.img

Then type

Fastboot reboot

Sent from my GT-I9300

---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------

If you dont understand my instructions, take the time to read my previous post with link to setting up your adb & fastboot on Windows 7 64

Sent from my GT-I9300
[Miscellaneous Android Development] caughron01:
When I click volume + on Fastboot protocol it doesnt do anything and then when I click it if it is plugged in it returns to previous menu. Does that mean something is wrong with my fastboot?
[Miscellaneous Android Development] katinatez:
My guess is you have not set up/ or not given ADB & Fastboot a home folder in your computer, also when trying to type commands you have to be in the same directory as your ADB & Fastboot folder

Sent from my GT-I9300
[Miscellaneous Android Development] aicjofs:
Added a Recovery installer that can install TWRP 2.3.3.0, 2.2.2.1 and return Nabi to stock recovery(needs testing). Decided to stick with same style that jmztaylor used since everyone is familiar with it.

Nabi Recovery Installer Download

http://xdaforums.com/showthread.php?p=36083895#post36083895

You should have fastboot at this screen(run the fastboot flash recovery recovery.img in this screen)

Bootloader

Continue

Reboot-bootloader

Reboot

Poweroff

You don't want to be at this screen, there is no fastboot available

boot normally

fastboot protocol

recovery kernel

forced recovery
[Miscellaneous Android Development] caughron01:
Now I am showing 2.3.3.0 twrp and my touch screen is not respoding correctly, this is just getting worse and worse....:confused:

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

Old Platform-Tools Folder setup

Tablet Menu

Using your new Downlaod link and info this is my setup-
[Miscellaneous Android Development] aicjofs:
Did you update your Nabi before you started all of this? Am I correct in you not being able to boot your Nabi to Android mode right now?

That 2.3.3.0 installer part wasn't necessarily meant as a reply for you, but that's ok. It doesn't look like you have extracted it correctly though.
[Miscellaneous Android Development] caughron01:
I tried to update but it said there were no updates, yes I cannot boot to android mode.

So what can I do now?

---------- Post added at 12:24 AM ---------- Previous post was at 12:10 AM ----------

Ok put 2.2.2.1 back on it and touch screen is back to normal but still cannot boot to android mode.....
[Miscellaneous Android Development] cruise350:
Seems like you need a redo so go to this post, follow his instructions and restore his backup to your Nabi. This will get you up and running, rooted, and ready for fun.

http://xdaforums.com/showpost.php?p=35819585
[Miscellaneous Android Development] wolfballz:
I can't seem to find the drivers for this for adb... i have not read all the pages in the thread. When i plug in the nabi it installs some usb drivers but i get stuck at nabi logo when trying to do option 1...
[Miscellaneous Android Development] caughron01:
OK this is where I am with my tablet problems my system partition has an extra partition anyone here had this problem or know how to fix partitions?
[Miscellaneous Android Development] aicjofs:
Here is default

And here is fstab

# mount point fstype device

/recovery emmc /dev/block/mmcblk0p1

/boot emmc /dev/block/mmcblk0p2

/system ext4 /dev/block/mmcblk0p3

/cache ext4 /dev/block/mmcblk0p4

/misc emmc /dev/block/mmcblk0p5

/staging emmc /dev/block/mmcblk0p6

/data ext4 /dev/block/mmcblk0p11 length=-32768

/external_sdcard vfat /dev/block/mmcblk1p1

/addon	ext4 /dev/block/mmcblk0p7

This is why his isn't mounting data and sdcard
[Miscellaneous Android Development] Amon37:
Use pdanet.

I just want to say I restored the backup someone posted pages back and the nabi is fully working with YouTube, thanks for the backup if I could the post I'd thank it
[Miscellaneous Android Development] aicjofs:
The more I think about it the less likely I think it is that somehow you added a partition 7 that shifted the rest down. I can't imagine even if you wiped a partition that would happen. The reason I think it's not is that you were unable to mount "data" right from starting the script from the download in initial post. TWRP is hard coded to try and mount /dev/block/mmcblk0p11 to /data, and the internal sdcard, is on that data partition in /data/media so neither are found because your /dev/block/mmcblk0p11 isn't your data partition, you couldn't have done anything in that time to add a partition 7 and move your data partition to /dev/block/mmcblk0p12.

What we need is to see if anyone out there has a Madagascar version Nabi. According to Nabi the latest Nabi version for Madagascar version is 1.9.34. We need someone that has one to do a "cat /proc/partitions" to see if the partition structure of yours is right or wrong. The catch is that if someone has a Madagascar version and it's like yours they would have likely failed already too so we would have known about it.

Regardless your Nabi isn't booting. It's hard to tell what happened or why that happened. We were able to manually mount /dev/block/mmcblk0p12 to /data and could see stuff on your data partition, so it's there. You could try restoring someones 1.9.37 system partition that is posted but I'm not sure it's compatible with yours if it's a Madagascar 1.9.34. Whats important to realize that if you do perform a restore it's not going to be possible in TWRP to restore "data" It's possible to do all this is adb shell with dd command but we don't have images for 1.9.34. It will all come down to if you are or arent suppose to have an extra partition in there.

As a side note. To everyone that was asking earlier where the 8GB of internal storage went look at the size of /dev/block/mmcblkp7(or 8 on his) ;)
[Miscellaneous Android Development] ALD3:
Root External 2 Internal

I finally got Root External 2 Internal to run automatically. Took about 10+ times, as I mentioned it would swap but not swapped on boot. Kept deleting cashe and data in settings>application and retrying. I was in settings and kept clicking s3 Rom to read a quick message that pops up, it was saying vold not found, all of a sudden it said vold found. Finished setup and rebooted and was changed automatically. 4 boots later and still swapping automatically.Took :highfive:
[Miscellaneous Android Development] t499user:
Hopefully someone else will come along with a Madagascar Nabi that can be compared. Having that extra partition explains a whole lot, and it will probably have to have a custom Madagascar recovery made. Maybe the recovery can be recompiled to mount the other partition. I hope that it's something that can be fixed rather easily.

I would check on the back of the Nabi, see if there are any different markings, hopefully there is something that we can say, THIS model is different.

I would consider exchanging for a non Madagascar version if possible.
[Miscellaneous Android Development] wolfballz:
So after installing the pdanet drivers i am getting the twrp recovery but when it tries to do gapps and root i get e:Can't open /sdcard/gapps.zip (no such file or directory)

am i supposed to download gapps and do i have to have a sdcard in this thing?

In recovery there is a file manager and i see /sdcard/gapps.zip but it fails to load and script stops... need some assistance.

Booted into recovery myself and installed gapps just fine... wouldn't work through script for some reason. now going to just try option 2 and root.
[Miscellaneous Android Development] katinatez:
If you have root & gapps zip in sdcard already. Just boot into recovery and install both zip files.

Sent from my GT-I9300
[Miscellaneous Android Development] wolfballz:
I rebooted into recovery and installed gapps myself. I will try the script for just rooting now cause all i saw in there was just the gapps and nothing about root. also if i root it and use a program to uninstall nabi mode will it just boot into a normal android mode???