yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] rpelljr:
Help, (thats original I know)

I have a NABI2-NV7A. In TWRP Version 2.6.0.0 (Nabi 2.0.5). I am Stuck, I do not know where to post this at because i cannot find much information on on TWRP 2.6.0.0 on a Nabi 205. I have tried flashing several roms, I had it boot twice to stock Android with no wifi, Tried the wifi fix with no luck. Then when reboots it boots to lock screen, unlocks and black screen with only clock. Does nothing. I completely wiped the entire device. Tried to flash stock 2.0.5, get checksum error on almost every zip i try to flash. And by the way. My dumb self did not do a full back up before I got to far. I have been flashing roms since before android existed and never had problems i could not fix thanks you the wonderful devs at XDA. Please I need to know if i need to flash a different version of TWRP, Flash a different ROM that with fix the MD5 checksum error. sorry, and this is my second version of TWRP, the first one had the touch screen issues thats when i went to the latest version. Please HELP....
[Miscellaneous Android Development] katinatez:
First there is not several ROMs for nabi, only different firmware versions. If you are trying to flash firmware 2.1.27.zip or any other zip file you downloaded from nabi wiki, they are all non flashable zip files.

First step is to backup recovery to external card since you wiped the system. Now TWRP made a file directory, unzip 2.1.27 copy and paste in a folder and place that folder where the recovery folder is located on external.

Boot in TWRP then restore you should see 2 restore points, 1 recovery, 2nd 2.1.27. Restore 2.1.27 reboot & do ota 1 & 2 to get to JB.
[Miscellaneous Android Development] rpelljr:
Thank you.. I actually figured it out the hard way before your answered. And did do exactly what you said. And my apologies about the roms comment, my eyes and brain cells start to blur sometimes when I'm reading for hours. Thanks for the correction though. The nabi was a gift to my stepson that just had a bonemarrow transplant and he loved the tablet but hated the monarch UI, which is gone. I have it as close to stock android as I could. Pretty confusing with so many firmware to a single device. Thanks again for the fast reply....
[Miscellaneous Android Development] Eric Karz:
Look more goodies for aicjofs to play with haha

http://youtu.be/LlL9EepBr4E
[Miscellaneous Android Development] aicjofs:
Some people have needed an ICS flashable version of 2.6.3.

The JB one Eric made here: http://xdaforums.com/showpost.php?p=48973853&postcount=82
[Miscellaneous Android Development] DarkAngel:
I love the QR Code usage. I was going to suggest that about the DL's.

:good:

---------- Post added at 04:24 PM ---------- Previous post was at 04:21 PM ----------

Been wanting to take mine apart to paint it satin black for some time now or that rubber like texture on many plastics I have seen that gives it grip and makes it look satin black.
[Miscellaneous Android Development] Eric Karz:
aicjofs

I see there is a TWRP 2.7 on the main site .

HINT HINT lol
[Miscellaneous Android Development] aicjofs:
Only booted and did a backup of boot, didn't restore. Up for testing. I'm interested in seeing if all Nabi2's(Original, Disney, Nick) on Jellybean can use a single recovery without having touch screen issues,etc. I think it's time to retire the recovery for ICS. 2.6.3 will be the last for ICS Nabi2, unless someone else wants to build it.

What's new in 2.7.0.0:

Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar

Allow sideloading from /tmp on encrypted devices

Check for a crypto footer before asking for a password to prevent user confusion

Additional checks for validity to auto generated backup names

Text wrap in the console output

Proper caps lock support in the keyboard

Mouse support via USB OTG for devices with a broken digitizer

Improve scanning of storage locations for OpenRecoveryScript

Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions

Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)

Update SuperSU to 1.93 and improve installation process

Added selinux contexts restoration to fix permissions

Load RTC offset on Qualcomm devices to fix the date/time in recovery

USB Mass Storage fixes Add SELinux support checking

Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)

Add 4.4 AOSP decrypt support

Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)

Various SELinux fixes and bug fixes

Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.

Flashable version below via Install in TWRP(if already on your device), or extract twrp-recovery.img and fastboot it.

TWRP 2.7.0.0 Jellybean only
[Miscellaneous Android Development] Eric Karz:
aicjofs

As always I appreciate what you do for our nabeez <- - thank you sir.

I was able to back up and restore successfully.

only thing that I have encountered is in the time zone .

in order to get a the correct time zone for EST I had to use UTC-4 ) Atlantic time. not a biggie
[Miscellaneous Android Development] aicjofs:
I did notice that there is no option to back up recovery yet it still backed up recovery when I selected boot. As if it always backs up recovery. Did you get the same? Screen rendering seemed lightening quick maybe that's placebo though.
[Miscellaneous Android Development] Eric Karz:
I missed that - no Recovery option

I have a 1.27 meg -recovery log - with a lot of

"Failed to get selinux context: Operation not supported on transport endpoint"

erros

Recocery is being restored if u made a back up in 2.6.3 and use 2.70 to Restore(that recovery is restored)then you fall back on to 263 -(Recovery (8meg))

when using 2.7 and you make a new back up the Recovery isn't Restored. no options for it

the main thing is it does work . I have used restore boot.img many times . I like the option to restore what you want instead of having to Restore every thing.

2.7.0 does respond nice with touch
[Miscellaneous Android Development] aicjofs:
TWRP 2.7.1.0

Nabi Specific: Add 2.4.6 kernel

TWRP Changes

Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.

Various bugfixes to backup and restore

Improvements to USB storage handling

Added a class to search for files to make finding the correct brightness file automatic in most cases

Various other bugfixes and tweaks

NABI2JBTWRP271.zip (fastboot)

twrp-recovery-JBNV7AUS-271.zip (flashable)
[Miscellaneous Android Development] chlor3:
I did a fastboot boot recovery.img of the file contained in NABI2JBTWRP271.zip and it just hangs on the Bootloader menu text dialog... ideas? I didn't want to commit until i saw it working...
[Miscellaneous Android Development] aicjofs:
Need to update some information. I saw a question in XDA assist this morning with someone running an old version of TWRP. I have not done a good job maintaining this thread because without a Nabi forum so much of our talks and development ends up in the "main Nabi thread" http://xdaforums.com/showthread.php?t=1905674&page=263

However it's apparent people are getting lost trying to find information. This is where the latest TWRP is

http://xdaforums.com/showpost.php?p=59452953&postcount=2592

and I will also update the OP.
[Miscellaneous Android Development] Moises170:
Help me please

I have a nabi 2 tablet, the tablet it´s bricked, when I tried to update the tablet got stuck on logo and I don´t know what to do, I tried to do a hard reset but didn´t work, I need to flash the software to unbrick the tablet but I don´t know how can I do that help me please I don´t have money to buy another tablet, I´m from venezuela for that reason I need your help to repair my tablet because I don´t have money to take the tablet to USA, I received the software update notification and when the tablet try to install the software appears an android robot with a red triangle and them the tablet didn´t work again
[Miscellaneous Android Development] aicjofs:
I'd start here and see if you can gain a little more information as to where the tablet doesn't boot. Can you get to the bootloader? Fastboot? etc

http://xdaforums.com/nabi-2/general/nabi-information-t3229119
[Miscellaneous Android Development] pjtx33:
Help please

The recovery installer for Nabi link does not work. Is there some place else to get it? I'm having difficulty installing a recovery to my Nabi Jr NV5A.. any suggestions?
[Miscellaneous Android Development] aicjofs:
Everything I've made should be here:

https://www.androidfilehost.com/?w=files&flid=41986
[Miscellaneous Android Development] John877:
My brother got a Nabi2 Tablet he wants to get rid of everything currently on it and have stock KitKat and rooted etc.

Its currently got 1.9.37 on it and completely stock. Im currently trying to get TWRP installed but everything says signature verification failed. Ive tried the ICS TWRP on the androidfilehost site for ICS.

Ive also had no luck with NabiLab as well. It wont see the tablet. Drivers are installed but ADB wont see it. USB Debugging is turned on.

I really wish the links in all your other posts about this tablet worked still.
[Miscellaneous Android Development] aicjofs:
I know my hosting is really messed up. Nabtabhacks has been broken for awhile, its free so I dont complain much, and I ditched Comcast so those links are dead. Most everything I think is of importance except the Nabilab installer is on AHF. I have about everything in my personal files if you need something specific.

Anyway what signature verification is failing? For windows drivers or in TWRP? Drivers are a nightmare in general because Nabi uses their own USB identifiers, and when you need to install a composite ADB driver to get both ADB and MTP its also a pain. You might just use the fastboot method to get ICS TWRP on the device then go from there.

fastboot to load TWRP ICS.

install KK bootloader zip from TWRP

fastboot to load TWRP for KK

restore the Nabi KK backup
[Miscellaneous Android Development] John877:
Hi, thanks for replying, Im new to this tablet and such and after seeing how old it is I had little hopes of any links working really anyway.

After some fiddling I have managed to get it back to 1.9.3.7 and actually booting again. :D I had issues getting NabiLab to see it and so I tried the alpha version of the GUI version. That somehow saw the tablet but then in fiddling with that I had managed to get it stuck at the Nabi boot screen by trying to put 3.0.1.3 KitKat on. Apparently I didnt update the bootloader or something as well so it halted. I did manage though to get TWRP 2.3.3.0 on it. I did have 2.6.3.0 on but in using i think NabiLab it installed 2.3.3.0. I have also since managed to get the APX and ADB drivers installed after noticing that I had to restart windows to disable the signature verification for drivers. So now the commandline NL works which I think I have more confidence in.

Right now it sits with 1.9.3.7 pure stock ROM as part of the NL Full version, unrooted, TWRP 2.3.3.0 installed.

Brother wants Rooted KitKat without all the Nabi kids stuff installed. TWRP version isnt really relevant as long as it works. I would really like the simplest procedure how to do this without a mess of files or whatever to hunt through. I know all of this might be old by now to some but he just got this used and would like to have a basic tablet.

btw selecting fastboot doesnt seem to do anything on the tablet screen. It still sits at the menu, is that normal?
[Miscellaneous Android Development] aicjofs:
If you select fastboot the screen should switch. Wen it doesn't its either a cable issue, or a driver issue. Often times even if the driver is installed when you select fastboot windows doesn't autoload it especially if it isn't signed so after you click fastboot you can look in device manager and see. As soon as the driver is load the screen should change. Do a "fastboot devices" at a command prompt where you have the fastboot exe an if it finds a device you are good.

I'm sorry NabilabGUI doesn't work, without the website some of it's auto functions don't work. Although you can manually add the need files it seems more difficult. Honestly it would be easiest to put the stock recovery back on the device and let it update to 3.0.13 on it's own, but this is the manual way:

Like I said in the previous post I would

Get TWRP for ICS: https://www.androidfilehost.com/?fid=24269982087011784

Extract the zip to the folder you have fastboot.exe

Put device in fastboot mode and at command prompt

fastboot flash recovery twrp_recovery.img

Reboot to recovery kernel

Get KK bootloader https://www.androidfilehost.com/?fid=24269982087011778

Get that on the device, best way is microSD card.

In TWRP go to install tab and then select the bootloader zip.

Then in TWRP reboot the tablet. It shouldn't boot at all but let it reboot to do the bootloader update. It should show the Nabi logo though, let it sit there for a 15 seconds.

Get TWRP for KK: https://www.androidfilehost.com/?fid=24269982087011783

Extract the zip to the folder you have fastboot.exe. This will overwrite the ICS TWRP image.

Put device in fastboot mode and at command prompt

fastboot flash recovery twrp_recovery.img

Then follow #2 in the recovery bricked device section https://xdaforums.com/showpost.php?p=63388400&postcount=3

skip steps i and o that have to do with the bootloader.
[Miscellaneous Android Development] John877:
Tried all of this, didnt work.

Extracted the 3013Stock.zip to the TWRP\Backup\XXX\KK\ folder and tried restore and recovery didnt see anything present. Tried just in the XXX folder as well. Tried in the SD root too. It saw nothing.

EDIT:

I think I really ****ed up now. I wiped /data as well and now TWRP gives me an error when I go to reboot, it tells me There is No OS Installed. I have managed before doing that though to copy the TWRP recovery created by NabiLab of 1.9.3.7 prior but when I did have it on the device or on External SD TWRP wont see it now.

Im trying to restore to stock with NabiLab Full but I'm at the point where I'm supposed to hit Restore and wait for that to finish but it cant see anything there so I cant do it.

Is there some way to just fastboot a ROM on maybe or ADB it on? Even if I have to start at 1.9.3.7 again I am fine with that as a starting point to try this all again.
[Miscellaneous Android Development] aicjofs:
Does the TWRP log say anything about not being able to mount /system or /data/ etc?

OK so which version of TWRP are you booting right now? The Kitkat 2.8.7? If you are then the bootloader is for KK, and it's working so it's really not worth going backwards.

When you made a backup of just the boot partition in TWRP 2.8.7 what folder did it create for XXX. Was the folder called 123456789 or did it actually look like a serial number?
[Miscellaneous Android Development] John877:
Currently I put 2.3.3.0 back on it cause I thought that that version is what the backup was created in so it had to be that version to see the backup from NabiLab.

I can put the 2.8.7.0 back on but it still wont see the backup.

I did create another backup but it didnt have a serial number type, it had a date and time stamp instead and was 16mb cause there was no data partition I'm guessing.

Also yes it does tell me unable to mount /data /system /cache etc
[Miscellaneous Android Development] aicjofs:
The backup are linux tar files, there are some incompatibilities but in general in doesn't matter. In this case you need to restore 3013 from TWRP 2.8.7 because it needs to deal with the SElinux permissions correctly.

Interesting. So you can boot with 2.3.3.0 and 2.8.7 and they both boot fine? If you are getting unable to mount errors that is the issue, it won't even see things on SD card correctly. It seems like the KK bootloader.zip didn't actually install. Did you install it from 2.3.3.0 or from the TWRP ICS 2.6.3.
[Miscellaneous Android Development] John877:
2.3.3.0 and 2.8.7.0 both boot into the recovery fine but no OS to boot to.

As for the KK Bootloader, I dont recall if it was in 2.3.3.0 or 2.6.3.0. I'm not even sure its still there though since I did use NabiLab up until the Restore procedure since there was nothing for it to restore cause it wasnt there and couldnt see it on ExtSD either.
[Miscellaneous Android Development] aicjofs:
It doesn't seem like the bootloader install worked/completed. The unable to mount, and missing OS are signs that the TWRP version and bootloader are mismatched. I would give it bootloader install another try. Are you saying no TWRP can see a sdcard at all? Or just can't see restore files?
[Miscellaneous Android Development] John877:
Cant see the restore files.

TWRP log file:

http://i.imgur.com/h3VayrH.jpg

http://i.imgur.com/1c5EXn2.jpg

Can I use fastboot or adb to put on the bootloader to make sure it works. I would also like to maybe use one of those to load the ROM on too if possible instead of going through recovery.
[Miscellaneous Android Development] aicjofs:
From your pics does the log say the same thing with TWRP 2.8.7 and 2.6.3? The fact you can't read anything in 2.3.3.0 would indicate the bootloader has been update. In which case the 2.8.7 should be working(as far as being able to read the internal and external storage.

No fastboot for bootloader, the only manual way is to place the nvblob in the staging partition. This requires you to be in some form of recovery, mount the staging partition and cp it over. Even if you could fastboot the ROM over it won't help(for 3013) because you still have to have an updated bootloader for it to boot.
[Miscellaneous Android Development] John877:
OK I flashed 2.8.7.0 on now and it sees the 16mb total size backup I for some reason did that doesnt have anything there really. The original 1.9.3.7 backup from NabiLab is still there but it cant see it on the internal or on SD card. the abcstock123 folder under the TWRP backups folder exists right now on both internal and external. Internal reads 400some mMB free of 4.2gb. Explorer wont show any other files than the TWRP folder.
[Miscellaneous Android Development] aicjofs:
It can't see it probably because as TWRP evolved from 2.3 to 2.8 they changed they way it grabs a unique serial number.

Depending on the version of TWRP when the device boots up it gives assigns the device a unique number(This can be from CPU, bootloader stored value, or a default number etc). When you make a backup or restore in TWRP in puts or looks in only 2 spots, and ONLY two spots.

/data/media/TWRP/BACKUPS/XXXX or with symlinking /sdcard/TWRP/BACKUPS/XXXX these are the same location

the other location

/external_sdcard/TWRP/BACKUPS/XXXX

XXXX in the above examples are that number TWRP creates at bootup. Those are the only locations it looks, so if you don't put your restore files(the .win files) in a folder in that path it won't see it. One of the problems when you have to jump between TWRP versions is that the method of selecting that number(the XXX) changes. So say on TWRP 2.3 it's /data/media/TWRP/BACKUPS/26578123 and on TWRP 2.8 its /data/media/TWRP/BACKUPS/11223344. You will not be able to see anything not corresponding with that unique number.

The second issue that crops up when using internal storage(this shouldn't effect you using the external SDcard) is the Android change from using /data/media to using data/media/0 for multiple users. So the KitKat TWRP will again not see files in just /data/media/TWRP.... it will only see /data/media/0/TWRP. This was fixed in later versions where it will look in both locations.

From the looks of it, the 3013 ROM files(ext4.system.win, etc) you want to restore are not being seen because of the above. There are no errors in the log for TWRP 2.8?
[Miscellaneous Android Development] John877:
No errors in the 2.8 log except some font thing if i remember right.

I have since, in 2.8 flashed the 3013 bootloader, that succeeded. I then went on to flash the KK3013.zip thats 290mb or so since its supposed to be a stripped, rooted, ROM of KK. That succeeded as well and now boots to the ROM. Only thing Im having an issue with now is that I cant seem to delete the TWRP folder in ES Explorer even though its got root privilieges.
[Miscellaneous Android Development] aicjofs:
The sdcard has weird write permissions in Kitkat. Or is it on the internal? You are correct you should be able to delete it though with root permission with ES.
[Miscellaneous Android Development] John877:
Yeah I know theres some weird write permissions with KK but this was on the internal. Ive played with it a bit some now and have managed to delete that TWRP folder on the internal in TWRP not in KK. I also managed to figure out how to delete the 2 Nabi videos and 50 or so song files that were on here from the previous user. My brother got the tablet used.

Im currently doing a complete (All boxes checked) backup in TWRP 2.8 on the external SD card then gonna move that or copy it at least off the tablet.

If this ever has issues I have also downloaded the Stock 3013 too.

I guess this is the last about this since I got it working now. So thank you for your time and for creating the NabiLab utility as that did save me earlier as well when I screwed it up. :D
[Miscellaneous Android Development] s09eng:
Hello. It's good to see that there is still some activity regarding this. My oldest son's Nabi 2 no longer has working wifi. I'm not sure how long it has been this way. The android version is 4.1.1. I hope that if someone could give me some instructions tailored to my specific situation that I could get it fixed. I do not mind going back and doing OTA updates. I just do not want to download a bunch of files that I do not really need. I do have a newer Nabi 2 that is still working properly if that helps at all. Any information would be appreciated. Sorry if this is a silly question or in the wrong place. Thanks.
[Miscellaneous Android Development] buksh0t80:
no os

I had exact same problem and flashed twrp 2.8.5.0 jb and bootloader and it brought everything back I tried kk right before it lost os
[Miscellaneous Android Development] B.Goods_Dre:
any chance someone could reload working link??
[Miscellaneous Android Development] xXRockGamerXx:
Links dead, can su re-update please?? just if you can
[Miscellaneous Android Development] aicjofs:
Sorry I am late to all this, have stepped away from all this for awhile.

Did you check my post here? Section 8? https://xdaforums.com/nabi-2/general/nabi-information-t3229119

Does that have what you want? I can look through my server archives if not.
[Miscellaneous Android Development] xXRockGamerXx:
Now I can boot into bootloader and just get back logo, I can't boot system. I was trying to boot (not to flash) a recovery.