yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] aicjofs:
Do you have a sample file or description of how you flashed grouper via fastboot so we can walk it backwards? I'm not sure you can use another tablets bricksafe image. Some Nabi's have different partitions I think we learned back then(18 vs 19) or something like that. I thought every nvflash thing I posted makes a bricksafe before it starts. You should have a copy of your original, check the file dates but it should be just bricksafe no numbers.(the one the gets created)
[Miscellaneous Android Development] SMcC2:
The ROM included a batch file something along the lines of:

fastboot wipe boot

fastboot wile recovery

fastboot wipe cache

fastboot wipe data

fastboot flash boot boot.img

fastboot flash recovery recovery.img

etc....

I don't even remember which ROM it was at this point. I've had a lot going on in the personal life.

The nvflash tool did create it's own bricksafe.img, but I thought that wouldn't be any good if the tablet was already in a non-bootable state.

I used the Nabi2Resize zip and now can get in to TWRP 2.6.3.0 Disney Version (I think that's the number, I don't have it with me right now).

I would just like to get the thing back to stock at this point, so I thought I'd ask for help.

*EDIT*

This is not a Disney version Nabi. FYI
[Miscellaneous Android Development] aicjofs:
Don't worry about the "Disney version" It's just text, it doesn't read anything, and for the most part interchangeable with the TWRP for Nabi2 Jellybean.

My guess would be the bootloader got messed up somehow. I think you are best served with the original bricksafe(the one the program created), it includes the BCT(which should be the same among Nabi2's except it possibly contains flash bad blocks which would be device specific), the PT(partition table only read by nvflash ignored by kernel), and the bootloader.

The other thing I think you ran in to was that the reason the "bootloader hung with no spinning circle" is that you have a mismatch with flashing a ICS bootloader and TWRP JB, or vice versa.

Since you ran Nabi resize let see what the partition situation is first. If you have TWRP working, use adb(or terminal in TWRP)

cat /proc/partitions

and

df
[Miscellaneous Android Development] SMcC2:
Output from the commands you listed:

G:\CELL PHONE STUFF\Nabi 2\adb>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 7634944 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 500392 48 500344 0% /dev
/dev/block/mmcblk0p4 473704 16812 432828 4% /cache
/dev/block/mmcblk0p11
4414636 1356884 2833496 32% /data
/dev/block/mmcblk0p11
4414636 1356884 2833496 32% /sdcard
/dev/block/mmcblk0p3 810328 17208 751956 2% /system
~ # ←[6n^A

Mounted paritions are System, Cache, and Data.

TWRP tells me it is unable to mount Addon

I'm unsure of where to really go from here.
[Miscellaneous Android Development] aicjofs:
Hey look at that your have a bigger system partition!(800MB the script works hehe), addon doesn't mount probably because it's not formatted.

Ok doesn't the script also output a partitionstableOLD, and MOD or something like that?(Can't remember) Can you post them, want to know if you have an 18 or 19 partition Nabi to begin with.

Also can you list the directory the script is in? Need to see all the ".img" and their sizes, and file mod dates.
[Miscellaneous Android Development] aicjofs:
Ok looks like you have 18 partitions. Make a copy of bricksafe.img, before starting.

I would think this would work without us having to do anything custom for your situation.

Grab restore.bat and put in that folder and run it. It will take awhile to restore addon. http://xdaforums.com/showpost.php?p=48672236&postcount=1895

Then use the hawkcore.zip to put bootloader to jellybean(not that it isn't jellybean already just we don't know if your original was corrupt from grouper flash) http://xdaforums.com/showpost.php?p=49435879&postcount=2182

Run hawk.bat

That jellybean bootloader is older, so just for completeness I'd flash in TWRP the 2.4.6bootloader http://xdaforums.com/showpost.php?p=54871957&postcount=2342

You may or may not need to restore a system backup.
[Miscellaneous Android Development] SMcC2:
Just got to work. It'll be 10 to 12 hours before I can give this a shot. I'll let you know how it goes.
[Miscellaneous Android Development] SMcC2:
Follwed the steps you suggested. Was able to restore my TWRP backup! :good:

I had some problems with some of the programs force closing, so I installed the latest TWRP in fastboot and then flashed the 246stock. Everything is working great except I still don't have access to '/addon'.

Current partitions:

shell@android:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 7634944 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 823296 mmcblk0p3
179 4 481280 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 32768 mmcblk0p6
179 7 1536000 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 65536 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 4485120 mmcblk0p11
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
shell@android:/ $ df
df
Filesystem Size Used Free Blksize
/dev 487M 32K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/obb 487M 0K 487M 4096
/system 791M 484M 307M 4096
/cache 462M 8M 454M 4096
/data 4G 719M 3G 4096
/forever 62M 4M 58M 4096
/storage/sdcard0 4G 719M 3G 4096
[Miscellaneous Android Development] aicjofs:
Looks like everything didn't take during force closes. Still have 800MB system partition instead of 500MB. Would explain /addon problem as well. Up to you if you want to try and fix it. It stole the space from /cache to add to /system so it's not like you are really losing usable space. Question is what else might be blank(like addon), for sure the GPT didn't get copied back.

addon probably isn't formatted. You can grab one of the newer TWRP's and use the new feature to format the partition ext4 or use these commands.

adb.exe shell /sbin/mke2fs -t ext4 -b 4096 /dev/block/platform/sdhci-tegra.3/by-name/UDB

adb.exe shell /sbin/e2fsck -y /dev/block/platform/sdhci-tegra.3/by-name/UDB

It should then mount, then have to restore an addon backup.
[Miscellaneous Android Development] SMcC2:
Used the commands. Was able to mount /addon in TWRP. Flashed 246stock including addon without a problem. Device is booting right now. Everything looks good.
[Miscellaneous Android Development] aicjofs:
Nabi2 is unbrickable ;)

(Hardware failure not included)
[Miscellaneous Android Development] katinatez:
TWRP 2.8.1.0

What's up everyone? Just dropping this here! No theme just your basic updated twrp recovery. Confirmed working just flash in recovery.
[Miscellaneous Android Development] Desertio:
I just updated and lost root.
[Miscellaneous Android Development] idkillforyou:
Nabi 2 Totally messed up?

I have messed with my Daughters Nabi for 2 days now - the last time I worked on this thing there was barely any info available about TWRP and rooting them seems things have changed. Anyways I tried to update TWRP and the Nabi version and things have been messed up majorly and I can't figure out where to even start now hopefully someone here can help. Currently TWRP 2.3.3.0 is installed and there is no OS at all anytime I try to do anything in TWRP I need up with

E:Unable to mount '/cache'

E:Unable to mount '/data'

and so on with pretty much any folder looking at some of the recent posts I ran the same commands suggested to another user and came out with this

~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 15558144 mmcblk0
179 1 15554048 mmcblk0p1
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 500380 48 500332 0% /dev
/dev/block/mmcblk0p1 15538848 190520 15348328 1% /external_sdcard

I can still get into TWRP but I can't do anything pretty much I am hoping there is a solution or someone with more knowledge than me has a few ideas. I have manually tried to upload 1.9.37 through adb but in TWRP it doesn't show under Restore - If I go into Mount Menu I can't even check System, Data or Cache. If I load TWRP 2.6.1 under Mount it says the Internal SD and External SD are both 0 KB in size. I believe my partition table is totally ****ed but I don't want to start ****ing with it until someone can give me a better idea of where to start.

Thank you guys my daughter would be pretty excited if I can get this thing going again.
[Miscellaneous Android Development] katinatez:
We need more information to help. I am guessing since you have twrp 2.3.3.0 you are still running android 4.0 also known as Ice Cream OS. We need to know the last working OS you had running. Also twrp recoveries are OS specific that is why you have "unable to mount" also when upgrading twrp you have to back up something to create the new file structure inside of either external sd card or internal sd card. For example you could just backup recovery into external sdcard (don't have one, it's a good time to buy one ) it will make the process much easier then adb push command.

Here is a link to another Dad that was freaking out about her daughters Nabi, and the process to get it back up again. Read the entire conversation before doing anything to gain understanding.

http://xdaforums.com/showpost.php?p=48942644&postcount=2071
[Miscellaneous Android Development] idkillforyou:
Sorry I didn't get everything in the first post, from the best I can recall her Nabi was on 2.0.5 (whichever version was the last ICS version) - Unfortunately when I did the last setup on her Nabi I did it at work and I am no longer at that job so I have no access to the computer I did the work on anymore and I believe the Backup from the original was on that machine. The other issue I have is that the sticker that had the Serial number on it is missing, not sure if my daughter peeled it off or if it just fell off but either way its not there, my wife is currently looking for the box to see if the serial is on there somewhere still. Does the serial number need to be accurate for a restore to work?

I'll check out that other post and look it over, if you have anything else I should know I would appreciate it.
[Miscellaneous Android Development] katinatez:
You did not read the entire conversation. Long story short we can bring back nabi to life without your backup or serial number(tell your wife she has the day off).

I guess I need to lay out steps

place this file in external sd cardtwrp-recovery-ICSNV7AUS-263.zip then flash this in twrp recovery, latest recovery for ics

boot into new recovery, and make backup of recovery partition to external sdcard it will look like this TWRP/BACKUPS/xxxxxserial number xxxx/recovery

Pull external sd card from nabi and plug into home computer and find the directory where recovery partition was stored

download this file 2127stock.zip extract file on home computer

Place extracted files in folder named 2127stock next to the recovery backup in external card

file directory in external card ---->TWRP/BACKUPS/xxxxxserial number xxxx/2127stock/extracted files

boot into recovery hit restore from external/ click on stock2127

Reboot and do all ota thru wifi

Give back to happy daughter :D
[Miscellaneous Android Development] idkillforyou:
I tried to follow the process as you wrote it and it wouldn't work - SO on a hunch I tried to do the same process with twrp-recovery-JBNV7AUS-271.zip and 246stock and that worked so I must have been wrong about having ICS last - I know at one time I was talking to my boss about JB for his android phone and I must have updated and totally forgot I did. Either way things seem to be working now so thank you!
[Miscellaneous Android Development] docj:
touch calibration

Anyone know how to manually calibrate the touchscreen? I've replaced the front case/screen on my nabi 2 and the calibration is off. I know nabi says it calibrates itself on startup, but this isn't correctly calibrating. Is there any app to recalibrate, or a system file I can edit? I have my nabi rooted if that makes any difference. Thanks.
[Miscellaneous Android Development] jaxbierley:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
[Miscellaneous Android Development] n3wt:
There's a Nabi 2S??? There's a nabi2 running kitkat??? is it 16GB??
[Miscellaneous Android Development] jaxbierley:
There is. Only 8 gb but has sd slot.
[Miscellaneous Android Development] katinatez:
You could try to boot to twrp and flash SuperSU by Chainfire v2.42 Since I never heard of Nabi 2S you could extract recovery.img from the zip a few pages back then type this

adb reboot bootloader
fastboot boot recovery.img
install SuperSU.zip from external card
reboot

This of course is precautionary steps since we do not know the partition table or if they changed it in some way. But if TWRP boot install root and be happy.

Remember that you are NOT overwriting your recovery just booting into twrp to take care of root business.
[Miscellaneous Android Development] jaxbierley:
Since TWRP is generally device specific and there is no TWRP (that I know of) for the 2S, I could risk bricking it by doing this??
[Miscellaneous Android Development] aicjofs:
The command "fastboot boot recovery.img" that was given will only load the image to RAM. You shouldn't brick anything.

There may be some hurdles however since we know nothing about this Nabi2s

-Locked bootloader

-Kitkat SE policy

-Possible different CPU? (Get CpuZ from play store and see if it's still Tegra3, maybe they moved it to tegra4 so it will be inline with Dreamtab, BigTab)

But you shouldn't brick anything, it just won't boot. If you want to be ultra safe and it does boot, then don't do anything in TWRP and exit TWRP by pressing and holding the power off button(so it doesnt try to mod anything on system partition. Then come back and let us know the results.
[Miscellaneous Android Development] jaxbierley:
Alright I'm at work now but will try tonight. When say it won't boot, how would I fix it if it won't be bricked.

I'm pretty decent with rooting at what not I've got several rooted devices, but feel like I'm a guinea pig with this nabi.. I wife will kill me if I brick this thing.
[Miscellaneous Android Development] aicjofs:
You are partially right as being the guinea pig, you can tell by everyone's surprise that none of us were even aware of a KitKat Nabi2. Although I have heard comments on the Nabi facebook page of getting all the devices on Morphos 2.0 launcher or whatever they call it. If it's the old Nabi2's that are getting it remains to be seen or if it's new hardware in a Nabi2 shell.

However, the risk of bricking is very minimal. What won't boot is the recovery not the main tablet OS. Think of it as booting your personal computer to a USB flash drive, CDrom, or God forbid a floppy. You are booting off that medium not off the main hard drive. So unless that boot medium is automatically making changes to the main hard drive, your PC is untouched. In this case there is only one thing TWRP does automatically and that is to rename a file that installs the original recovery. It does this when you exit TWRP normally, which is why I was telling you to exit by hard powering off with the power button. It also does a 2 thing which is to install root, however it asks yes/no to install and you can also get around that too by hard powering off. All of this assumes it boots the recovery at all. The other thing I mentioned to increase safety was verifying that the tablet is Tegra3 before trying with CPUz from Play Store, at least then you will be booting a kernel that knows how to properly init the base hardware.

Most important is not to get confused with the commands:

fastboot boot recovery.img <---Do this

fastboot flash xxxxx xxxxx <---NOT this

Also be aware of a locked bootloader. If it won't let you do the above it may mean the bootloader is locked. Fuhu has been allowing unlocking by

fastboot oem unlock

^^^^ The above command will factory reset the tablet(Possibly resulting in wife firmly placing a pillow over your face in your sleep. Haha. Sorry, that was morbid). So be aware if you need to do that what it entails, you would have to setup tablet again and lose any games saves, etc.
[Miscellaneous Android Development] jaxbierley:
Wel, I get into the bootloader and whether I fastboot boot recovery.img or fastboot oem unlock, I just get waiting for device
[Miscellaneous Android Development] jaxbierley:
Here's what the bootloader looks like. Nothing I'm familiar with seeing on any device I've rooted.

Continue just boots the nabi.

Reboot well, reboots it.

I have a thought tho. Out of the box it came with JB, it had an OTA to KK. Im going to try to restore it back to factory setting and see what happens. I'm not to worried about losing anything, as my son got it for Christmas and hasn't had much of a chance to get to much on it.

Of course another thought is, even if I root it with JB, if I update to KK I'll most likely lose root. Not sure if having root is worth giving up KK.

UPDATE: Still no luck. Terminal just hangs on "waiting for device" with any fastboot command.
[Miscellaneous Android Development] aicjofs:
That's a common default tegra bootloader

Do you have fastboot driver installed? Check in device manager to see if fastboot driver is loaded or if you have yellow exclamation point.
[Miscellaneous Android Development] jaxbierley:
I do have fastboot driver installed. Any other device I hook up I have no issues with. As far as looking in device manager, I recently switched to Linux (its been a hell of a trip learning) and there isn't any equivalent to device manager like in WIndows.

I went through the entire process of sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update

and

sudo apt-get install android-tools-adb android-tools-fastboot

and still no luck. fastboot devices returns nothing.

On a side note, thanks for the help. Having a device I cannot root drives me nuts and I refuse to believe it cant be done.
[Miscellaneous Android Development] aicjofs:
"waiting for device" is usually a driver. I forget what it looks like when you need the -i switch

fastboot -i 0x0489 xxxxxx (where xxx is the command like "devices"

fastboot -i 0x0489 boot recovery.img

Try those. I can't even remember how I figured that number out if it's different on yours.

EDIT: I was just thinking maybe it matched the USB device ID is how I found it. So you could find it with "lsusb" in a terminal. I'm not sure if you should add a udev rule so it's detected every time.
[Miscellaneous Android Development] jaxbierley:
Dude you are a genious. first command were xxx=devices returned my serial number. Tried second command return bootloader locked. About to try oem unlock, will update shortly. Freaking genius man
[Miscellaneous Android Development] aicjofs:
Awesome. When you do oem unlock there is some text on the screen you have to use the vol+ or - to select on the tablet itself. I didn't look like a genius the 15 minutes it took to figure that out a year or so ago. ;)

---------- Post added at 04:00 AM ---------- Previous post was at 03:53 AM ----------

Yeah that's what I was afraid of. It's likely one of 2 things. Either the updated bootloader doesn't like the old Jellybean kernel, or the kernel it's self doesn't work. Did you ever figure out if this is a tegra 3 or tegra 4(with cpuz from play store)? Just to be sure which TWRP version did you download?(link?)
[Miscellaneous Android Development] jaxbierley:
Its tegra 3 and i used the image from this link http://xdaforums.com/showpost.php?p=56900475&postcount=2469
[Miscellaneous Android Development] aicjofs:
I haven't tried that TWRP but it surely works or it wouldn't have been posted. You said this was on Jellybean once? Maybe we can reverse engineer the OTA for it to get the boot image, or you can go about trying to root it with an available exploit. Judging by the kernel build date a lot of the exploits are going to have been patched.

Let me work on seeing if I can find out the OTA url. It's on 2.0 release keys now right? Do you happen to remember the number of the previous software? What was the Jelly bean version? 4.2.1 4.2.2 4.3? Any of that would help.
[Miscellaneous Android Development] jaxbierley:
Yes, out of the box it was on jellybean. The first thing I did was check for an update and updated to KitKat. It's on 2.0 release keys and I want to say it was 4.2.2 but I can't be certain. It's coming up on 1100 pm my time so I'm gonna have to put out this on hold for the night. At least we got the boot loader unlocked. That's half the battle. My guess is going to be waiting for the 2S to get more mainstream or other nabis getting KitKat and someone smarter than me gets twrp working for it. Thanks again for all your help and if you figure something out or want to try something by all means, I'm willing to give it a shot, short of bricking it.
[Miscellaneous Android Development] mjw2k11:
hi katinatez, thanks for your work, i can also confirm it works, any chance of a nabi themed version to match older recoveries?
[Miscellaneous Android Development] mescalinedreamz:
I hope someone can help me. I used nabilab to install twrp onto my daughters Nickelodeon special edition. I used a newer version of twrp v2.6.3.0 (nabi 2.3.1.1) is what it says in twrp. After it installed and I was left with twrp , I then exited twrp and it asked me if I wanted to install supersu. I clicked yes and the nabi rebooted. I then went to play store and got the supersu which booted me back into twrp.

I booted back into the nabi parent mode and tried to delete a file in the /fuhu_media/ it was a mp4 video file with es file explorer. Supersu asks me and I grant it, it won't delete the mp4 file. I then tried to delete it with root explorer, wouldn't work.

I then tried link2sd to move apps to an external sdcard and that wouldn't let me. I looked up the error and it said that I didn't have root access? And then somehow link2sd is now part of system apps and cannot be deleted! I have the external sdcard divided , half fat32 other half ext2. Link2sd sees both. I then clicked the option in link2sd to install new apps onto external sd . I tried to install an app and was denied with insufficient space. I looked into storage of the system and it says total 1.23gb then says used is 1.17gb and free is 58.70mb. So I clicked the option to install apps to internal in link2sd and now it let's me install apps.

Do I even have root? Aren't you allowed to delete anything once you are rooted? How do I delete link2sd if its now a system file?

I did install directory bind and tried to move the android file to external but that wouldn't work either. That also said that I didn't have permission or access. I had read that if there isn't enough room when you try to root / install twrp then it won't do it fully. My daughter was trying to install apps before I rooted it because she was getting insufficient space pop ups. Is there any way that I can start over fresh? Like stock bootloader, fresh factory nick version nabi?
[Miscellaneous Android Development] n3wt:
To check if you have root you can either grab a root checker app or grab terminal emulator and do an su command which will fail or change your prompt to # instead of $. I prefer https://play.google.com/store/apps/details?id=jackpal.androidterm

As far being able to delete things once rooted...in ES you have to go to tools and where you turn root explorer on and off, you have to have it on AND press on the words root explorer which will bring up some options...press mount r/w...and select rw for /system and/or / (which is the root directory). The reason for this is that android by default mounts critical directories in read only mode to prevent rogue apps from changing things. I think root explorer automates all that but I still prefer ES.
[Miscellaneous Android Development] n3wt:
Dang, still no luck on this? I tried hard to guess the correct naming scheme to grab the it with wget and got nowhere.