yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] aicjofs:
New update for everyone, and Waleslie this might fix your touchscreen issue. If not I have one with logging enabled to try, but see if this one works first.

TWRP 2.6.0.0 for Nabi2

What's new in 2.6.0.0:

Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!

-Can encrypt a backup to prevent theft of private data from your backup files

-Updated graphics / icon courtesy of shift

-Updated exFAT to latest commits

-Fixed a problem with Samsung TouchWiz decryption

-Update SuperSU binary

-Fixed saving of backup partitions list

-Fixed saving of last used zip install folder

-Fixed backup of datadata on devices that use a separate partition for datadata

-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)

-Fixed some problems with partitioning a SD card

-Various other bug fixes and tweaks

Notes about encrypted backups:

Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

Nabi Specific: Edited minuitwrp events.c to remove lis3de_acc as an input device to try and fix touchsceen issue

Download
[Miscellaneous Android Development] Waleslie:
Unfortunately, this version still has the same touchscreen issues. I was going to try your play store link from the previous post, but I'm not sure how I would get it installed without being rooted and having not file manager installed to sideload from...
[Miscellaneous Android Development] aicjofs:
Can you try this version

TWRP 2.6 with logging

It won't fix the issue but I need to see a more verbose log of what's happening. Boot this TWRP and immediately go to advanced tab and then copy log to SD card. Then boot normal and just grab the recovery.log from internal storage. I know that requires a swipe action. Best way is to use two fingers, one on each side and try and lift one. If it can't be got that way you could:

adb pull /cache/recovery/log

Zip it up, upload to pastebin, or something so I can see it.
[Miscellaneous Android Development] Waleslie:
The adb command says it can't find that file... did it not get generated or is the command off a bit?
[Miscellaneous Android Development] aicjofs:
Were you in TWRP or Android when you ran that? I wasn't very clear. In TWRP you can grab it by

adb pull /cache/recovery/log

if in TWRP and you were able to swipe the copy log to SD you could use

adb pull /sdcard/recovery.log

if rebooted to Android and you were able to swipe the copy log to SD while you were in TWRP then you could just find the file in windows explorer as the Nabi mounts MTP. Just use "My Computer" and browse to recovery.img
[Miscellaneous Android Development] Waleslie:
Ah... okay. Got it.
[Miscellaneous Android Development] aicjofs:
Did you use this version of TWRP(the one linked below)? Log has no touch input at all. Did you touch the screen at all during this? It doesn't look like the verbose logging version was the version you used.

TWRP 2.6 with logging
[Miscellaneous Android Development] Waleslie:
Sorry about that. I thought I was just supposed to immediately pull the log and send it to you.

Here's a new one. I loaded into recovery, pressed the advanced button, pressed the copy to SD button, unsuccessfully tried to swipe a few times to confirm the action, then hit the back button to go back to the main menu. At this point, I issued the adb pull command to copy the log.
[Miscellaneous Android Development] aicjofs:
I think this is the issue

Event object: lis3dh_acc

I'll try and edit events.c and have TWRP ignore it as input. Very similar to what happened with new style NabiJR. I'll get to it as soon as I have some free time.
[Miscellaneous Android Development] aicjofs:
Ok I removed lis3dh_acc as a touch input interface. Also centered Nabi image when in standby in Y axis. Download and try the version linked below.

TWRP 2.6 touchscreen fix attempt
[Miscellaneous Android Development] Waleslie:
That worked like a charm! Thank you!

Will this version work on all Nabi 2s or is it something specific to this one I have?
[Miscellaneous Android Development] aicjofs:
Took awhile but glad we got it worked out. This version should work for all Nabi2's. There is a list of inputs that are blacklisted, and TWRP ignores those, so the accelerometer in yours is now in the blacklist so it doesn't change anything for Nabi's that don't have that accelerometer. Since I fixed the Nabi circle centering(how on Earth did I miss that?) this version is the one everyone should have from an aesthetics stand point.
[Miscellaneous Android Development] DarkAngel:
I am wondering...... are we able to theme on our version of TWRP as others on thier phones are? I don't remember if members were making themes for the Nabi2 prior to 2.6.
[Miscellaneous Android Development] aicjofs:
Yes you should be able to make/skin any theme you want. I didn't look to deeply into how to make themes that you can apply, the documentation was so old I wasn't sure what to make of it, so I just built the "nabi theme" straight in to TWRP. This TWRP has it's stock theme obviously different then the stock TWRP theme, but it shouldn't interfere with theme packs.(making theme folder and placing ui.zip in there). The only caveat would be that some themes are old. TWRP has changed at least twice in last few major updates it's general layout, so a theme made by someone a year ago for 2.4, wouldn't work on 2.6, the other thing that comes to mind is a horizontal/vertical theme, i.e a theme that is 1024x600 or 600x1024 are not the same(TWRP doesn't rotate) . Otherwise I can't see why a theme made for 2.6 at our screen resolution(1024x600) wouldn't work.

Also 2.6.1.0 is out fixing a compression bug, I may need to get on this, and add the new Nabi kernel too.
[Miscellaneous Android Development] aicjofs:
There is a TWRP 2.6.3.0 out there but it's a bit too new so we will go with 2.6.1.0, note the bug fixes for permissions and compressed backups, might be wise to make a new backup.

What's new in 2.6.1.0:

Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)

Initial support for f2fs file system formatting (Moto X)

Update SuperSU install for 4.3 ROMs

Fixed a permissions bug on files created during backup

Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match

Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible

Ignore lost+found folder during backup and size calculations

Various other minor bug fixes and tweaks

Nabi Specific:

Kernel for 2.1.27

TWRP 2.6.1.0 Download
[Miscellaneous Android Development] DarkAngel:
TWRP 2.6.1.0 working great for me. Thank you.
[Miscellaneous Android Development] chlor3:
I can confirm TWRP 2.6.1.0 is working for me on NABI2-NV7A-US 2.1-release-keys.

Edit: My Google Play Store is non-functional. On open it says "no connection", yet wifi and all my browsers are connecting the internet. See my next post.
[Miscellaneous Android Development] deskjet390:
Need link or mirror to this asap pretty please! Or attach it....I'm gonna need to install twrp on the new jelly bean nabi 2 in the morning I want 2.6.1.0 word! The link ain't working
[Miscellaneous Android Development] chlor3:
Google Play not connecting and cannot revert to previous nandroid backup after NABI 2.1 upgrade.

Nabi install upgrade history:

Started with a fully functional Nabi v2.0.5 with a gapps 4.3. ( I am attempting to locate the gapps 4.3 I installed but can't seem to locate it... Does anyone know where this exists?)

Performed a nandroid backup of system, data, boot.

Installed TWRP 2.6.1.0 ( manual adb sideload )

Downgraded to my origional unrooted 1.9.37 and performend the OTA update to NABI2-NV7A-US 2.1-release-keys.

Restored only the data partition from (v2.05) and rooted the device from TWRP.

At this point I have a working 2.1 NABI and all my apps and data restored, however google play just says "no connection", (Gmail works fine.)

I knew about the 2.1 bloat issue so I removed the wings app (94mb) and reinstalled a older version of gapps (since I could not find the gapps4.3 one...) Google Play "no connection" issue remained.

Performed a nandroid snapshot backup of system, data, boot (NABI 2.1 / Gapps 4.3).

Now here is where it gets wierd:

Since Google Play was not working I decided to restore to the origional NABIv2.0.5/Gapps4.3 doing a full system,data,boot restore

Upon completion it boot loops at the monarch login. (actually it is more of a "Monarch loop" since it never reboots just keeps trying to restart the Nabi Mode UI.

Restored the NABI 2.1 / Gapps 4.3 snapshot and "Monarch loop" is gone, but Google Play is still broken/not connecting.

Is the monarch loop a TWRP 2.6.1.0 issue or did upgrading to NABI 2.1 fubar the partitions to prevent downgrading?

---------- Post added at 10:53 AM ---------- Previous post was at 10:46 AM ----------

I installed this one:

I just tried downloading it again and it appears to work.
[Miscellaneous Android Development] aicjofs:
I am not sure which is at fault. Obviously the full 2.0.5 backup should restore normally. I do know I have had tons of issues trying to get "fancy" with mixing and matching system and data backups in the past and have got the Monarch boot loop. I have never figured out exactly what happens or why it does that. I usually clear the caches when restoring, I don't know if that would help.

I have a feeling you need to go into settings/apps and clear data for the Google stuff associated with the Play Store for your 2.1 install.
[Miscellaneous Android Development] Eric Karz:
Gapps 4.3 is for JB 4.3

try gapps for android ICS 4.0.4 -20120429

HTH

http://goo.im/gapps/gapps-ics-20120429-signed.zip
[Miscellaneous Android Development] chlor3:
Thanks, I downloaded that version and installed it and it worked, kind of. I uninstalled a bunch of google apks (using Ti Backup) before I installed the gapps-ics-20120429-signed.zip, however I managed not to uninstall the google play store ver4.3 (even though I was planning on it). And it worked somewhat. I could browse the play store however couldn't download anything. I deleted my google account and re-added it to the android os and everything was workingb (google . Now the strange part is that Google Play is still 4.3 even though the rest of the gapps are 4.0 (as seen by Ti backup). So at the end of this... TWRP 2.6.1.0 is working fine.
[Miscellaneous Android Development] aicjofs:
What's new in 2.6.3.0:

Proper backup and restore of SELinux contexts (thanks to Tassadar)

Pull in some ROM information for backup name generation

Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3

Add 1200x1920 theme (thanks to Tassadar)

A few other fixes and tweaks

Nabi Specific:

Changed external storage name to MicroSD card.

Added ability to backup /addon partition

Added ability to adjust screen brightness

TWRP 2.6.3.0 (ICS)

TWRP 2.6.3.0 Disney/Nick Edition (JB)

TWRP 2.6.3.0 Original (JB)
[Miscellaneous Android Development] DarkAngel:
Just a heads up, I thought I had installed the JB edition on mine when I noticed "Disney" on the TWRP main screen when I booted into the recovery.
[Miscellaneous Android Development] bowtieduece:
Hi I just installed 2.6.3.0 on my nabi 2 version 2.1 release keys.

I want to make a bakeup before I remove apps and flash gapps, but it isn't recognizing that I have an sd card inserted. while in android the card is usable.

Also i tried to mount sd card in recovery but it will not let me check that box either.

Is there something I am missing?
[Miscellaneous Android Development] aicjofs:
Updated version of TWRP 2.6.3.0 for Nabi2 original with JB update(v2.3.11)

Nabi specifc:

Fixed Original Nabi listed as Disney

Added kernel for v2.3.11

TWRP 2.6.3.0 Original (JB)
[Miscellaneous Android Development] amebiasis:
My sons tablet is still on 4.04, when I try to install the new update it goes to TWRP I tried installing the update found in the cache but it wont allow me, will this new recovery let me do it? Thanks!
[Miscellaneous Android Development] aicjofs:
If you are still on 4.0.4 use the 2.6.3 for original Nabi(ICS), then use the JB after it's all done.
[Miscellaneous Android Development] arvati:
wont able to get in fastboot

hi there.

I am trying to get in fastboot mode to install TWRP and root my device that just updated to jellybean OTA but i am not able to get in fastboot

I ve tried to use an win 8.1 computer, 7 and xp and all have the same result:

On Nabi hold <Power> and <Vol+> down at same time to turn it on.

Resulting Menu:

Boot Normally

Fastboot Protocol

Recovery Kernel

Forced Recovery

Use <Vol-> to move the selected item.

Moved selected item down to "Fastboot Protocol".

Use <Vol+> to "enter" selected item.

New Menu:

Bootloader

Continue

Reboot-bootloader

Reboot

Poweroff

Selected "Bootloader", and entered(<Vol+>).

And goes back to menu:

Boot Normally

Fastboot Protocol

Recovery Kernel

Forced Recovery

And selecting again Fastboot Protocol does not enter in fastboot and goes back to Menu:

Bootloader

Continue

Reboot-bootloader

Reboot

Poweroff

on computer command fastboot devices never recognize my nabi.

any ideas?
[Miscellaneous Android Development] katinatez:
Have you set up your fastboot directory? Mine is at the root of C:\
[Miscellaneous Android Development] Eric Karz:
in post one is a good way to test if the recovery is going to work

"-Method 2 (manual temporary install, will keep your current recovery)"

this is the temp method that lets you install twrp.

I put the recovery.img in the same folder where all the adb files are -then-

SHIFT +MOUSE 2 on a clear spot in a folder and choose "open command window here.

In that new command window is where the magic is

with nabi connected to pc by USB enter the first line in command prompt

" adb reboot-bootloader" * nabi should boot to bootloader- give a few seconds. If you do not get to bootloader then * Stop* - you have a problem.

IF you do pass to this point then enter the 2nd command.

"fastboot boot recovery.img " you should now see recovery image pass from the folder to the nabi2 .If you pass this you now have temp recovery.

last -kill the adb sever or it will be running

in the commang prompt .

"adb kill-server"

I would not do method 3 until you know that the temp version is working properly .

HTH
[Miscellaneous Android Development] aicjofs:
If you were having touchscreen issues on 2.6.3 I built a new version, same links as before.

TWRP 2.6.3.0 (ICS)

TWRP 2.6.3.0 Disney/Nick Edition (JB)

TWRP 2.6.3.0 Original (JB)
[Miscellaneous Android Development] mjw2k11:
I have just tested the updated 2.6.3 Original (JB) and it is working fine, touchscreen issues have gone, thank you very much!!
[Miscellaneous Android Development] katinatez:
Does aroma file explorer 1.91 work with this update?
[Miscellaneous Android Development] katinatez:
Updated recovery, tested aroma file explorer 1.91 & failed, also still storing in a generic serial " folder.
[Miscellaneous Android Development] arvati:
Erik, thanks for answer but i did get on recovery the problem was that fastboot did not start anyway. What i did to get fastboot to work was connect with an ubuntu machine and it worked perfect. No way to get fastboot protocol on windows xp, seven or 8.1 ....
[Miscellaneous Android Development] katinatez:
Download android SDK for Windows, then set your path to sdk/platform-tools, & SDK/tools. By going to computer/system/advance system settings/Environment Variables/System variables/Path. Example mine looks like this

C:\AndtoidApp\sdk\tools;C:\AndroidApp\sdk\platform-tools;

Then open cmd and type fastboot or adb; if done correctly you should see a fastboot table of commands.

Good luck

I have adb & fastboot running on Windows 7 64
[Miscellaneous Android Development] Eric Karz:
IF you are already have twrp installed this zip will update to 2.6.3.0 .

some graphics changed . Recovery by aicjofs

Put zip file on sd card

boot to TWRP

use install in TWRP

reboot or reboot to recovery.
[Miscellaneous Android Development] katinatez:
Is this for Jellybean 2.3.11?

Never mind I read the file, starts with JB
[Miscellaneous Android Development] Eric Karz:
yes its for JB nabi 2 USA version

I think its easier to flash a zip to update then to use the adb method.

plus I was able to tinker with the graphics like the keyboard.
[Miscellaneous Android Development] ravx25:
So I'm a little confused. I used a guide with bat PDAnet, JMZ installer and everything to root and install gapps on this Nabi originally. Using the JMZ bat file it just starts TWRP but I can't figure out how to install it like I did CWM to my Galaxy S2.

Right now, I have 1.9.37 and I am wanting to take it back to stock so I can sell it. My SD card got corrupted so I lost my backup, but I downloaded a 1.19.12 recovery zip, but I can't figure out how to get it flashed. With CWM, its so easy. I just hold down all my vol buttons and power, let go of power and CWM opens up. Toggle down to flash zip, choose it and usually success. Is it not this easy this way? I can use JMZ to get into TWRP, but when I choose the 208MB stock ZIP file (like I would CM 10 on my galaxyS2) I expected it just to flash and be back to normal. Obviously, I'm lost here......can someone provide a little direction?
[Miscellaneous Android Development] DarkAngel:
Are you familiar with ADB and Fastboot? The Stock recovery image is available in the wiki. I go through Ubuntu for all my flashing. Just so much easier for me. Although it shows it in Ubuntu (linux ) one can also do the same on windows with the correct drivers installed. I always flash my TWRP (recovery.img) files using Ubuntu through the Command Prompt Window as stated in the links.

For Rooting, installing recovery, and back when one needed to flash Gapps w/ root:

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

Here back to stock.

http://xdaforums.com/showthread.php?p=35287470
[Miscellaneous Android Development] katinatez:
Works great, yes much easier to flash, by the way which program did you use to unpack .img?
[Miscellaneous Android Development] ravx25:
I'm not overly familiar with ADB and Fastboot, no. I've looked up several Youtubes and XDA articles on how to install it, but I don't seem to be making much progress with it. I downloaded the ADB tools to a SDK folder on my root drive. I can open up to the fastboot option on the Nabi even. I installed the PDAnet stuff and it's recognized, so I can get the serial number from recognized devices. I just cannot, for the life of me, figure out how to get into the touch screen TWRP interface without using the JMZ bat file. Even when I did it that way, I chose the 208 MB zip file and it wouldn't work. Shouldn't it be as simple as choosing a ROM....that's all this is right? CM takes a bit to install but when I slide the indicator to install this stock ROM it just seems to fast, like its done nothing at all, which is confirmed when I have to hard reboot.
[Miscellaneous Android Development] Eric Karz:
unmkbootimg .

I think this is where I got it .

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

I have used this to unpack also windows

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

this also does it but its a lot of reading and setting up . there is some much to it but probably the best way for the entire rom . I think if someone gets good at using it we could get a CM version from it .

http://xdaforums.com/showthread.php?t=633246
[Miscellaneous Android Development] aicjofs:
Have you built aroma from source or using some prebuilt?

I built from source with Nabi2 device tree. I don't know if this works on the Nabi2 because the kids are at a friends house with both of them but it works on the XD.

Aroma test build

Do you not like the file manager in TWRP? I've never used aroma before, I guess you have to mount system before "installing"/booting it?

About the serial thing, that's been like that on The JR-B and XD since I started building them, I do need to figure it out. It's kind of nice because it take the guess work out of the serial if everyone has the same, but not so good if you have one SD card you take between devices.

I think it would be fun to make an extended recovery, screen shots, rotation, etc. But then I think why? The idea is never to be in recovery! haha https://www.copy.com/s/xDoPC3fzRDKu/ex-twrp-screenshots/TWRPScr-005.bmp
[Miscellaneous Android Development] katinatez:
Thanks for replying on New Years Eve, and building this aroma but it still not coming up full screen and the touchscreeen is way off. For example you have to touch screen where I have the arrows just for aroma to register your touch.

It's not that I dont like TWRP file manager it's just that I grew accustom to aroma having it on all my external cards. And I brought to your attention about generic serial # folder for current TWRP 2.6.3.0 JB I thought it was a simple fix. And the extended TWRP looks nice, have not compiled recovery but would like too, if you need help on this pm me, I am a college student with a programming background. Enjoying Christmas break so I could help at the moment. I am all about great recoveries; I had a couple HDD (on computer) crash on me and I am all about backing up data. So here is a picture of the aroma file.

​

---------- Post added at 02:03 AM ---------- Previous post was at 01:39 AM ----------

I think I will go with the kitchen I already have Ubunto 13.10 installed on a ssd, and Windows 7 64 on another ssd, so swapping ssd takes 5 minutes to switch between Windows and Linux.

Thanks again
[Miscellaneous Android Development] aicjofs:
Yep you are right, I get the half screen on a Nabi2 too, yet the XD is perfect....hmmm I saw one comment about half screen in the Aroma thread and they reply was it's a kernel bug. I rebuilt a Nabi2 TWRP with the XD kernel(since it will boot the Nabi2) and still half screen. I don't quite understand why that is, that would leave the Nabi2 TWRP source as the commonality, yet I don't see what would be causing XD to work and 2 not too, major difference is the screen resolution obviously.