yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] aicjofs:
After fastboot flashing you have to actually boot TWRP BEFORE going in to the ROM.

After

sending 'recovery' (8190 KB)...

OKAY [ 1.496s ]

writing 'recovery' ...

OKAY [ 1.129s ]

finished. total time: 2.627s

don't do "fastboot reboot"

Use the arrow keys(vol + and vol -) to go back to bootloader and then select recovery kernel.

What is happening is there are 2 files.

/etc/install-recovery.sh

recovery-from-boot.p

When you just boot the ROM it run's install-recovery.sh, this file reads the recovery partition, if it doesn't match the SHA1 hash it expects(and it won't since TWRP is there) it reads the kernel from the boot.img plus some of the ramdisk and patches the rest of the ramdisk with recovery-from-boot.p patch and writes it back to the recovery partition. This basically restores the stock recovery. If you load TWRP first before the ROM and exit TWRP normally it will rename recovery-from-boot.p to recovery-from-boot.bak and end all this nonsense ;)

EDIT: and yes" fastboot boot" would work too. Once TWRP has booted go to the reboot tab, and select reboot bootloader(it will rename the recovery-from-boot.p at that time) and then "fastboot flash recovery xxxxx.img"
[Miscellaneous Android Development] n3wt:
fastboot boot recovery.img will boot into /your local current directory/recovery.img

but you said you got into TWRP once, right? I was thinking you'd just repeat whatever steps you took to get there the first time.

AND what aicjofs said! lol
[Miscellaneous Android Development] Macanage:
Nope. Never got into TWRP. I will do what aicjofs said!
[Miscellaneous Android Development] DarkAngel:
Like aicjofs stated, this also happens with many phones as well. All being my Samsung Galaxy Phones........
[Miscellaneous Android Development] Macanage:
Aicjofs, I love you in a rooting-TWRP kind of way!

That worked, thanks! Made a backup and will work on the next mod to be able to write to the SD card. Are you guys running the de-bloated version of KK without all the Nabi stuff?

Thanks a ton guys!!!
[Miscellaneous Android Development] DarkAngel:
I am, and De-Odexed as well. Look in the Nabi wiki for the latest updates so far.
[Miscellaneous Android Development] Macanage:
I looked on the wiki and all I see is the "Minimal Nabi - katinatez." Is this what you used?

Also, I did the mod to be able to read and write to External SD card, however, there does not seem any way to move apps to the External SD card. I tried some of the App2SD apps but they are only UI for moving those apps native to the ROM. Is there any custom rom's or mod's that will allow me to move them to the external card? Possibly a way to partition the SD card and mount it, so the tablet thinks it is the internal storage?

Kitkat is nice but fairly useless unless I can figure out a way to get some free space.
[Miscellaneous Android Development] n3wt:
There's a debloated KK version that I did here: http://xdaforums.com/showpost.php?p=59089544&postcount=2546

I'm pretty sure that's what he de-odexed and is using now. At some point I'll be releasing a de-odexed version with some mods and maybe some light theming.
[Miscellaneous Android Development] Macanage:
Nice work! I like it so far. I did just the normal wipe and still ended up with all the Nabi stuff. So I did go back in and wiped everything except the Ex-sdcard and now it seems to be solid. My only question is how do you wipe "addon?"
[Miscellaneous Android Development] n3wt:
What I did was mount it and then 'rm -rf /addon/*' or something to that effect.
[Miscellaneous Android Development] Macanage:
Thank you very much! That got rid of last few stragglers. I LIKE it! :D
[Miscellaneous Android Development] rrrrrrredbelly:
quick question, I have the Nabi2 running JB 4.1.1 and am looking to root it in order to remove all of the google system apps like chrome, bloat, etc.

What's the best way to root it starting from scratch? I'm familiar with rooting devices & fastboot

Thank you

Dan
[Miscellaneous Android Development] n3wt:
Firstly, you might want to consider upgrading first...we are up to 4.4.2...

Either way, you'll want to grab the correct version of TWRP for your software version and then either let it root for you (if you stay with 4.1.1.) or grab SuperSU.zip and flash that.
[Miscellaneous Android Development] rrrrrrredbelly:
Thanks. Is the kk update an official one? When i go to settings - about - updates, it says system is up to date. I've read back a few pages, saw the links in #2502, will those work with the state I'm in?
[Miscellaneous Android Development] n3wt:
the kk is official for nabi 2 us, is that what you have? are you on 2.3 or what exact version of nabi software?
[Miscellaneous Android Development] mr_tris:
Theres no Superuser in the apps so I guess the toolkit it never installed it. Im a bit rusty with adb can you give me the prompt commands to install them out of the toolkit. Thanks.

Just out of curiosity, what version is everyone on. I bought this yesterday and its at 1.9.29.

EDIT: Just realized I cant install SU cos I'm not rooted still, so I would have to manually root first too?!! I wish id never bothered with all this now cos its making me ill! LOL!
[Miscellaneous Android Development] ALD3:
Not sure what the adb commands are, someone else will have to help you there. Are you sure about you version? I got mine 4 weeks ago and had an update to 1.9.23???????
[Miscellaneous Android Development] mr_tris:
Maybe this could be my problem and the newer update on it has fubared the toolkit. The tablet still works fine for now, just TWRP is screwed and no root. :(
[Miscellaneous Android Development] ALD3:
Did you try and run the tool kit again? You must run superuser on First bootup to finish the rooting process and let it update the su file.Explore
[Miscellaneous Android Development] mr_tris:
It never boots up the last thing it does is reset into TWRP and stay there the log shows this.
[Miscellaneous Android Development] Clarkiss:
Ok this is really easy and you cant really mess it up with these simple directions... Start all over mr_tris.. Go and download "jmz Root package" and unpack it to a folder of ur liking. In the folder you will find a folder called "files" and a windows batch file called "Install". To be sure just real quick open the "files" folder and make sure theres 10 items in there including "gapps.zip" and "root.zip". Then go back and click on "Install" and a command window will appear with 2 options... First choose option 1 (Install Recovery, Root and Gapps) and follow the steps that appear in the command window and make sure you do word for word what the steps tell you WHEN they tell you... After you get threw all that then your going to need to do everything again but this time around your going to choose options 2 (Install only recovery and root)! Because for whatever reason option 1 does not successfully root the Nabi. You DO NOT need root access to sideload Gapps first so make sure you follow what I have just said in this order. I bought 2 Nabi's one for my son and another for my sisters son and did everything this way on both Nabi's with no problem everything worked fine.. let me kno how u make out then after you can join the trying to swap Internal Storage and Sdcard party :rolleyes:
[Miscellaneous Android Development] mr_tris:
I have tried everything you have both asked but to no avail. I'm just stuck in the same position.

Thanks for all your help guys, the problem is that it won't mount and fails to find the SD card in the recovery log and everything fails. It doesn't even re-boot after the toolkit trys to finish it just goes back to TWRP and I have to shut it down to restart the tablet manually. Its all a bit weird.
[Miscellaneous Android Development] ALD3:
Have you tried to do a factory reset from within Twrp? Just what ever you do, do NOT do a SYSTEM wipe. Just a wipe cashed and dalvik cashed and factory reset
[Miscellaneous Android Development] mr_tris:
I'll have a try tonight, it's time to collect the little reprobates from school and I need to keep this hidden till they're in bed! :eek:
[Miscellaneous Android Development] -RioT-:
I had Problems too. I found that I was to low on space to make the backup so it stopped the script and didn't install root and gapps so ended up flashing the root then gapps from within twrp. I had a backup that I've done earlier so I saved it to my computer. But really, the backup is really important.

Mr Tris, I would definitely try to do a factory reset and run this script first before installing stuff. Its probably something simple.
[Miscellaneous Android Development] mr_tris:
Couldn't do anything from within TWRP it failed a factory reset with it, I re-installed the stock recovery with adb fastboot and then did a reset from ICS which worked.

So after the reset I tried again and it still did exactly the same things with same as always

unable to mount '/data' (tw_mount)

failed to mount data (invalid argument)

unable to mount /data/media during GUI startup

unable to mount /data when trying to read settings file

failed to mount data (invalid argument)

An update request has failed

failed to mount data (invalid argument)

System

failed to mount data (invalid argument)

Data

failed to mount data (invalid argument)

Boot

failed to mount data (invalid argument)

An update request has failed

failed to mount data (invalid argument)

Compression is on

An update request has failed

failed to mount data (invalid argument)

-- Could not mount :/sdcard

-- Aborting

Backup failed!

Done processing script file

failed to mount data (invalid argument)

This is a new device I have all the storage space from new and out of the box. This is the first thing I tried to do before any installing. Storage space definitely isn't the issue.

I have also notice that with stock recovery it is also failing to mount /sdcard?! That can't be normal right?
[Miscellaneous Android Development] -RioT-:
That sucks. Did you do all the ota updates?
[Miscellaneous Android Development] mr_tris:
I'm at the latest version straight out of the box - 1.9.29
[Miscellaneous Android Development] jmz:
Are you familiar with flashing stuff via command line using adb/fast boot
[Miscellaneous Android Development] mr_tris:
Im still learning but I have used adb several times to flash and some more advanced stuff under tutorial. I have the android-sdk folder pack on the root of my C: drive ready to go.

Thanks for your help? Can I ask you is it normal for stock recovery to not be able to mount /sd card because nabi has made it sd card2?
[Miscellaneous Android Development] jmz:
I'm not sure about stock recovery. If you didn't have an sdcard installed then that might be why you are getting that message.

If you want to do it manually,

Adb reboot-bootloader

You might have to install drivers here again.

Once you have the fast boot menu on the screen,

Fastboot flash recovery recovery.IMG

You can get the recovery IMG in my zip

then fastboot reboot

Then adb reboot recovery.

Mount SD and copy rootgapps over from my zip

Then just choose it in recovery.

My script does nothing fancy. It does all this but a little more in depth.
[Miscellaneous Android Development] mr_tris:
Everything you instructed goes well but when I finally go in to TWRP after adb reboot recovery the SD card will still not mount neither will /data. :confused:
[Miscellaneous Android Development] ALD3:
Nabi 2 announced a software update today on Facebook. Went ahead and checked and there is. I downloaded it and Nabi 2 went to android 4.0.4 and version 1.9.32. I was rooted with Google play before the update, still have Google play and it works, lost root but kind of expected that. Waiting for jmztaylor to check this before I root, as I'm over a return date. Lol

Also lost TWRP custom recovery FYI
[Miscellaneous Android Development] -RioT-:
Ill try it after work with ota root keeper. That has worked for me on 2 phones and a tablet.
[Miscellaneous Android Development] DZLRULZ:
So they're savvy...removing our root via ota. Sounds like everyone needs to reject the newer than v1.9.23 updates until jmz evaluates.

Struck by my Anthrax Infected Viper4G Ev_O_nE using Forum Runner
[Miscellaneous Android Development] rrrrrrredbelly:
Build J R O 03C, product v 2.1 release keys, do i need to update to 2.3?
[Miscellaneous Android Development] n3wt:
Well, 3.0.13 is the latest but I'm not sure why yours is telling you that you're up to date.
[Miscellaneous Android Development] rrrrrrredbelly:
Ok thanks. I'll search around and get that up to date, once i am, will the links in that post work for flashing twrp?
[Miscellaneous Android Development] n3wt:
yeah, once you get updated then that TWRP 2.8.4 should work ok, but I think maybe there's a 2.8.5 somewhere that fixes the problems some people were having with 2.8.4.
[Miscellaneous Android Development] aicjofs:
Are you "up to date" because it's a Disney or Nick version? They are on 2.1.

Run DeviceInfo.bat with tablet plugged in. Actually anyone can use it, should work for all Nabi products, it's just a script from NabiLab 2015
[Miscellaneous Android Development] rrrrrrredbelly:
Yeah, it's a nickelodeon one, sorry - didn't realize that mattered. Does that affect how is rooted?
[Miscellaneous Android Development] aicjofs:
Nope all the Nabi2's are rooted the same. extract the twrp-recovery.img and fastboot flash recovery twrp-recovery.img it.

This TWRP 2.8.4 http://xdaforums.com/showpost.php?p=58453164&postcount=2502 should work for automatically rooting in TWRP. That version might have touchscreen issues on some Nabi's though. In which case you have to go back to 2.7.0 http://xdaforums.com/showpost.php?p=51172788&postcount=101.

I know that sounds like a mess(my fault on a typo). All the touchscreen issues were fixed in 2.8.5 http://xdaforums.com/showpost.php?p=58923464&postcount=2522 HOWEVER.....

I'm not sure what the version will do for backups. In 2.8.5 we changed Nabi over to KK kernel. KK changed to SElinux enforcing, and 2.8.5 will save the se contexts in to the backup. I don't know what will happen if a JB kernel(like the Disney/Nick have) tried to read one of these restores when booted.
[Miscellaneous Android Development] rrrrrrredbelly:
So I'm having issues with the device being recognized with adb. All i really want to do is be able to install apps on the SD card. Is there an easy way to do that in JB that I'm missing? I've tried a bunch of apps in the play stote but none work.

Edit - I've installed the drivers through the nabilab but it isn't showing in adb. I've used adb from this computer on other phones, not sure why this isn't working

Edit2-when i plug in the nabi, it tries to install the drivers and is searching windows update, and then pre-configured folders... after about 5 minutes it comes back saying it can't find the drivers for fastboot
[Miscellaneous Android Development] aicjofs:
Drivers are always a pain on the Nabi's, that's been one of the biggest issues if you look back through all this history. Which Nabilab did you use? Nabilab original, or Nabilab 2015 alpha?

You really have to manually force install the driver sometimes, auto is pretty flaking depending on driver store.
[Miscellaneous Android Development] rrrrrrredbelly:
I first used the one on post #2088 from this thread, then tried the full version from the original post. I did the auto install, I'll try that manual one tonight. Is there a newer version? (I'll look now to see the date from #2088 .)

Edit- yeah, didn't realize that was 2013. Do you have a link to 2015 one?

Thank you
[Miscellaneous Android Development] aicjofs:
It's alpha but I added some driver stuff to it. Maybe it will help.

NabiLab2015 alpha 2
[Miscellaneous Android Development] aicjofs:
Ok I managed to fit everything in the recovery(exfat/super user) at 8MB and changed the color space so that Aroma works but the colors aren't all crazy. Added the Nabi theme back in.

3.0.13 users can flash 285 for KK

Everyone else(Disney, Nick, UK, original 2.4.6 and below) should use 285 for JB

EDIT: Note Disney and Nick have received KK update since this post was made.
[Miscellaneous Android Development] katinatez:
I'm impressed, how did you cut the fat off the recovery? Have you pushed your commits to github yet?
[Miscellaneous Android Development] aicjofs:
True type fonts are pretty huge, that made a lot of difference. I made a new kitkat branch.
[Miscellaneous Android Development] rrrrrrredbelly:
Thanks for all the help, this got it rooted.

Last question, still trying to move apps to the sdcard, is there an easy way to do this that I'm missing. Was planning on using titanium backup, not sure when that option was pulled from the app.

I saw the "external to internal sd" option, might try that.

Thanks

Edit- so that app did the trick, thanks again for all the help.
[Miscellaneous Android Development] Desertio:
I lost root on my nabi somehow. Im running android 4.1.1 on Nabi2-nv7a, and kernel 3.1.10-gb0aadc1

I guess i need to start from scratch i guess. idk. Any guidance is greatly appreciated.
[Miscellaneous Android Development] aicjofs:
Use the JB TWRP a couple post up.

Looks like Disney and Nick get the Kitkat update? Hopefully you're next UK people ;)

Disney

http://updates.fuhu.com/updates/android/NABI2-NV7A/US-D/xxx/2.1.2/updates.json?

http://cdn.firmware.fuhu.com/nabi2-...ate-2.1.2.us.disney-to-3.0.4.us.disney_v2.zip

Nick

http://updates.fuhu.com/updates/android/NABI2-NV7A/US-N/xxx/2.1.2/updates.json?

http://cdn.firmware.fuhu.com/nabi2-nv7a-us-n/nabi2-ota-update-2.1.2.us.nick-to-3.0.5.us.nick_v2.zip
[Miscellaneous Android Development] ozlo:
Does this option even work? The last I remember people had all kinds of issues when they tried swapping external and internal SD storage.

And on that note, is there an effective way to move/install apps onto SD for the Nabis? Is link2sd the best option, and if so, should the 2nd partition on the SD card be ext4 or ext2? I've read ext4 doesn't always work.
[Miscellaneous Android Development] rrrrrrredbelly:
The swap app mostly works. Sometimes it doesn't stick after a reboot, so i have to open up the app and do it again (one click). but other than that is fine
[Miscellaneous Android Development] jaxbierley:
I've got my kids nabi 2S rooted. I don't see much chatter about the 2S however. Anyone else have one.

Anyway, is there anyway to boost the sound in this thing. It has speakers in the back, which sucks in the first place and they are good awful low most of the time.
[Miscellaneous Android Development] Desertio:
I know that i saw it before but i cant seem to find where the post is that shows the necessary procedure for installing the new .zip Any help is appreciated
[Miscellaneous Android Development] DarkAngel:
Here you go, Post# 2510:

http://xdaforums.com/showpost.php?p=58786524&postcount=2510

@pvman

Follow the steps in the link above to get you to the latest 4.4.2 KitKat update. Simple as it gets. Also for more info and links click on the wiki link below.
[Miscellaneous Android Development] pvman:
okay, but I don't have the Nabi 2S. Just the Nabi 2. Was KK ever released for it? As far as the OS is concerned, I am trying to stay 'legal'.

Additionally, I still have some questions:

If I go with the above method, won't I lose my data?

If I update TWRP first, can I then update using an OTA Update (and not lose my app data)?

Using either method, will I lose "root"?

Should the best OTA update method be to go back to stock recovery, update, and then load the appropriate version of TWRP and re-root?

What exactly is the compatibility issue? Is it an issue of bootloaders and other things?

The reason I use TWRP/root is because I also use Link2SD. With it, I've loaded about 12 GB of apps/data and kept the full Nabi load.

That's all
[Miscellaneous Android Development] jaxbierley:
What would consider "illegal"?
[Miscellaneous Android Development] pvman:
2 rhings: 1 figurative, the other literal. First, the figurative: I surmised from the posts in this thread that the KitKat releaae was for a newer revision of the Nabi 2. To me that implies a possible hardware change. That could mean some instability or incompatibility if I load it on my " old" Nabi 2, but not necessarily. That's why I asked.

Now, the literal: As much as I'd like to get the " Watch Disney" app, Fuhu only licensed it to be distributed with the Disney version of the Nabi 2. That is why that edition was more expensive than the regular Nabi 2. For me to "obtain" that release and install it probably violates my EULA with Fuhu, is unfair to those that actually paid for it, and sets a bad ethical example for my kids. After all, it is a tablet I gave to them to use.

I may be off base, but that's how I currently perceive reality.
[Miscellaneous Android Development] jaxbierley:
I was unaware about the Disney thing. Your reasoning sounds perfectly logical
[Miscellaneous Android Development] pvman:
Yeah, the Google Play Store will not let that Disney app install on our "device". Of course it has no issue with our Nexus. Doesn't make total sense to me. I figured rhe reason was legal, but whatever . . . .
[Miscellaneous Android Development] aicjofs:
Yes 3.0.13 is an official KK release for the Original Nabi2 and what you get if you follow the post that was linked. It's a little confusing because that post was right after 10-15 posts about the Nabi2S. KK is legal on Nabi2 original. Yes converting to Disney\Nick is unethical and

mostly impossible

for even the above average user anyway.

Additionally, I still have some questions:

If I go with the above method, won't I lose my data?

Hard to tell. You shouldn't but with any upgrade things can go wrong. Especially if you are making a jump from 1.9.37 to 3.0.13 for example.

.

If I update TWRP first, can I then update using an OTA Update (and not lose my app data)?

If you want to take the OTA use the stock recovery. That really only applies from going from 2.4.6 to 3.0.13. Normally TWRP can apply a Nabi OTA without issues(assuming you haven't modded any files). However in the 2.4.6 to 3.0.13 update there is a routine that runs the update in a 2 or 3 part process I forget. i.e. it does something, reboots to recovery again, does some more stuff and reboots again. There was some issue with TWRP handling that right. However if you follow the linked post it takes you directly to 3.0.13 so no need to worry about OTA.

.

Using either method, will I lose "root"?

Yes. Actually the su binary will still be present, along with daemonsu and all. At the end of the OTA though it sets permissions for the entire /xbin folder and removes the SUID bit and therefore root will not work.

.

Should the best OTA update method be to go back to stock recovery, update, and then load the appropriate version of TWRP and re-root?

That would work fine assuming you haven't modified any system files the OTA will SHA1 check.

.

What exactly is the compatibility issue? Is it an issue of bootloaders and other things?

If Nabi is on ICS then the last useable TWRP was 2.6.3 for ICS. If using this TWRP ICS on a JB bootloader you will be able to boot but not mount partitions. This a common issue on the forum I see. Usually because less experienced people are still using the old Nabilab which was ICS based(there is also a repacked original Nabilab using JB TWRP)

If Nabi is on JB then there is a version from 2.6.3 to 2.8.5. All the versions between 2.7.0 to 2.8.5 MAY have touchscreen issues because of a typo I made in the code. So 2.7.0 and 2.8.5 is good for all Nabi2's. 2.8.5 has a JB and a KK version that should be used with whichever the device has on it. If booting a JB TWRP with an ICS the tablet won't boot, if using the KK bootloader tablet will boot and TWRP will work.

If Nabi is on KK, then 2.8.5 is the only option. Touchscreen should work for all. Should boot for JB and KK bootloaders.

If using the KK TWRP on a JB Nabi the backups will included SElinux information for ext4 and we still don't know how that might effect a restore when the boot kernel can't read it.

.
[Miscellaneous Android Development] pvman:
Thanks! Great info. Wish me luck. I'll report the results, either way!