yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] CaptnSpaulding:
I'll try and get it tomorrow or Sunday if anyone could post instructions on how to do it then I'll upload it to you guys to share.

Thanks again
[Miscellaneous Android Development] aicjofs:
Get the 2.6.3 TWRP image and put in the ADB/Fastboot folder.

Reboot the tablet to the bootloader

At a command prompt in fastboot/adb folder:

fastboot boot recovery.img (Note: boot not "flash recovery" or you will overwrite their stock recovery.

backup the system, boot, recovery, and addon partition(addon partition is not entirely necessary but it's good to have for the full backup)

When backup completes, hard power off the Nabi by holding the power button.(If you don't it will rename install-recovery.sh to install-recovery.bak, and you could accidentally install SuperSU)
[Miscellaneous Android Development] DarkAngel:
Looks like the UK, Disney edition and a few other got the update finally.
[Miscellaneous Android Development] katinatez:
Hello aicjofs, I could not remember the fastboot command to just boot the recovery but now I know. I was thinking it could also been done with open recovery script but your way is easier. Now hopefully the Nabi community can have a UK stock firmware zip to share.

On another note have you been able to update your android_device_fuhu_mt799 github with the newest kernel of 2.3.11?
[Miscellaneous Android Development] CaptnSpaulding:
Just doing the backup now, don't have an SD card large enough to backup the addon though :( Will it be ok without it?

How do I get rid of TWRP after the backup? Do I just follow the last step in your instructions on the original post here and use the recovery file in your zip folder?

---------- Post added at 05:27 PM ---------- Previous post was at 05:03 PM ----------

Oh also, now the backup is finished, does it matter that it's a different serial number? Can I just use this backup and install it using TWRP on my son's Nabi?

Thanks
[Miscellaneous Android Development] aicjofs:
TWRP was in RAM turn it off and no more TWRP. You can verify by booting to recovery kernel should be the dead android. Serial number is not important for what you want to do. Only really useful if you had different devices and moved one Sd card around to all of them, so you could keep track of what's what. Also TWRP wouldn't install the wrong device if you were moving that one card around.
[Miscellaneous Android Development] CaptnSpaulding:
Oh damn, I was impatient and used code - fastboot flash recovery nabi2_original_recovery.img - whilst in your zip folder and the nabi was in bootloader.

I don't think I borked it as theirs was only on v.2.0 and I updated it to 2.1 fine OTA.......... at least I hope I've not broken it :eek:

I've just installed the backup on my sons Nabi and it seems fine, although it has all our friend's stuff on there. If I now do a factory reset and do a new backup with my son's now UK ROM, I can then upload a clean UK ROM for you guys? Does that sound right?
[Miscellaneous Android Development] aicjofs:
I haven't updated the github yet. I need to make another branch as there are differences between ICS and JB that need to be different.

I would imagine it's fine as long as it was the original recovery. Again you can always verify by booting to recovery.

You probably restored their "data" partition, you didn't have to do that but no big deal. Yes you can factory reset if you want and do a backup. It doesn't really matter because that only affects the data partition. All people really need is boot, recovery, and system, no need for data partition, so you could just upload those 3 partitions from their backup(which is 2.0?), and then you could upload yours(2.1?) or however you want to do it. Yours may have modified install-recovery.sh and installed SuperSU depending on how you did it so it might not be completely stock.
[Miscellaneous Android Development] CaptnSpaulding:
Here you go - https://www.dropbox.com/s/x03s5p4347cp2v1/UK 2.0.zip

That's a UK 2.0 backup without the data files. Hopefully it will work for you all.

Currently updating to 2.1 on my son's now UK Nabi, I'll upload that and when I go to 2.2 or 2.3 I'll upload that too if you want.

---------- Post added at 06:59 PM ---------- Previous post was at 06:30 PM ----------

Here's a UK 2.1 backup - https://www.dropbox.com/s/vxjc6pqej6wusvz/2.1 UK.zip
[Miscellaneous Android Development] katinatez:
You could plug in Nabi to computer then copy and paste the twrp backup to computer for safe keeping, then delete the backup from internal sd card and then continue to backup addon partition, then repeat process of storing in a computer hard drive for safe keeping.
[Miscellaneous Android Development] CaptnSpaulding:
I've now updated to the latest version (2.2 in the UK) with the Play Store and everything seems fine, so thank you to everyone for your help.

Just got another huge favour to ask though. I'm now trying to do the same with my other son's Nabi, which has been on US 2.3 version for a while. I would leave it as it is but I don't think I did it right back a few months ago and it's performance isn't great compared to the other one.

Anyway I'm trying to do the same thing here, stuck the UK 2.1 backup on SD Card and went to 'Restore' in TWRP. It can't see the backup. I've then gone to factory reset and it keeps failing. It says it cannot find any partitions or frameworks or something. I went into backup to try and backup the Nabi but it can't see any partitions, system, restore, date or anything - yet the Nabi boots up fine and has everything on it!?

---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------

I'm trying to return it to stock and this is what I get;

Ignore external SD card error if you have none installed

This files are 1.2GB this will take many minutes. Please wait.

mount: mounting /system on ext4 failed: No such file or directory

mount: mounting /cache on ext4 failed: No such file or directory

mount: mounting /data on ext4 failed: No such file or directory

mount: mounting /addon on ext4 failed: No such file or directory

mkdir: can't create directory '//data/media/TWRP/BACKUPS/0123456789ABCDEF/abcdst

ock123': No such file or directory
[Miscellaneous Android Development] katinatez:
Backup 2.2 UK with Play store with all partitions including addon, then place in the backup directory in second (son) nabi.

The problem is your trying to restore 2.1 (which is Ice Cream 4.0) with JB twrp recovery. Assuming you installed JB 4.1 twrp on son nabi with US 2.3.11
[Miscellaneous Android Development] CaptnSpaulding:
Any way to backup without SD Card? My SD Card is only 4GB :eek:

---------- Post added at 12:17 AM ---------- Previous post was at 12:03 AM ----------

You were right though. I forgot I needed to flash the JB version of TWRP after 2.2 :o
[Miscellaneous Android Development] CaptnSpaulding:
Got there in the end and now have UK 2.2 on both - however I'm missing apps on the latest one I did such as the Nabi Store and Camera etc. Also when setting up, it set up via Google rather than Nabi!?

Don't think it's right somehow.

How would I go about installing 2.1 or 2.0 over 2.2? Would I stay with JB TWRP and use the 2.0 backup or would I have to downgrade TWRP?
[Miscellaneous Android Development] n3wt:
did you happen to just restore a backup of 2.2 on the one that's giving you problems? even if that's not the case, I think a comparison of cat /proc/partitions on the two nabi's might shed some light.
[Miscellaneous Android Development] katinatez:
You could try factory reset on the nabi with missing apps. The missing apps will be restored, then do a comparison of both nabis.
[Miscellaneous Android Development] CaptnSpaulding:
I updated TWRP to latest JB version and used the 2.2 backup. At first it looked like it had only 'updated' as it had kept all apps from the previous 2.3 such as nook, and some apps I'd downloaded so I did a factory reset both through settings and through recovery - TWRP was removed by itself it seemed as I had the dead android when I went to recovery kernel.

After both resets the apps are still missing and both times I had to set the Nabi up using google/stock android setup by entering google info and location etc, not the Nabi OS setup where you skip the video etc.

I noticed when I chose to do the restore with the 2.2 that only system and boot was selectable even though I has backed up recovery too. Had no way to backup addon as my SD card isn't big enough.

Maybe if I could go back to 2.0 with the backup and data files I got off our friends the. I might be able to restore the missing apps then just do OTA updates?
[Miscellaneous Android Development] CaptnSpaulding:
Got it!! Have now got 2.2 UK on both running fine. I ended up getting a new SD Card and I just backed everything up on the working Nabi from yesterday and restored it onto the other so it was a complete replica if you wish.

The only difference is, it shows more storage space on one than the other, and the cache is nearly full on one. Here are photos using nabi MD;

Any ideas?
[Miscellaneous Android Development] katinatez:
The addon partition is critical because it stores the apk that are restored when a factory reset is performed.

Also use file explorer like Solid explorer and compare system/app & data/app
[Miscellaneous Android Development] n3wt:
I don't think the cache is a big deal, that number probably fluctuates anyway as the system needs more room to cache New things it removes old stuff out whatever. the storage space difference is probably because one tablet was updated to JB with the UK ota and the other with the US one.
[Miscellaneous Android Development] littlewave:
Hi,

Thanks so much for uploading these!

I'm using these to try and make my way to stock uk 2.3 too having previously lost my stock backup. I have managed to restore the UK 2.0 backup you posted above using TWRP 2.6.1.0 and then completed the OTA update to 2.1 on that but the subsequent 2.2 update then fails with the red exclamation mark half way through the update.

I've also tried restoring the 2.1 backup above to see if that would work with the 2.2 OTA update but TRWP fails mid way through the restoring the system partition.

If anyone has any idea what might work it would be hugely appreciated!
[Miscellaneous Android Development] CaptnSpaulding:
Did you remove TWRP/flash stock recovery before doing the OTA update after restoring to 2.0?

I will upload the 2.2 (latest UK update) backup tonight if I have time. This is what I last used and worked fine. For some reason I couldn't get the 2.1 to work either but the 2.0 should work as that what I used on the first Nabi and then just updated OTA to 2.2.

---------- Post added at 10:58 AM ---------- Previous post was at 10:40 AM ----------

The only other thing I can think of which I did before updating to 2.2 apart from making sure I was on stock recovery was a factory reset as the initial backup included data files which included someone else's details/passwords (which I luckily knew to bypass into parent mode). Perhaps try going back to 2.0 again, flash stock recovery, factory reset and then update OTA.

If it still fails, then try the 2.2 which I'll try uploading tonight.
[Miscellaneous Android Development] littlewave:
Thanks, I'm fairly sure I didn't remove TWRP as I had originally assumed (wrongly?) the restore would overwrite the recovery and boot partitions too. I'll try that to double check tonight, hopefully that will solve the problem.

I definitely did do a factory reset to wipe data/cache etc. after the 2.0 restore... I found that without a factory reset the restore would just boot loop.

Hopefully the recovery restore will solve the problem, but if you do get a chance to upload 2.2 that could be a great help.

Thanks for the help!
[Miscellaneous Android Development] Ste_J:
Hi, just tried factory reset but no improvement. Also tried update without sd card being present in the nabi just in case it was trying to read that and seeing back up files

Bit stuck now

Is there anyway to debug whilst it's trying the OTA?
[Miscellaneous Android Development] littlewave:
Okay, I checked my recovery after a successful OTA upgrade from the uploaded 2.0 to 2.1 and the recovery is definitely stock (I'm fairly sure the OTA upgrade wouldn't work without stock recovery anyway). Trying to upgrade from 2.1 UK to 2.2 UK at that point still failed... it seems like there a few people with the same problem.
[Miscellaneous Android Development] metalheadkicks:
Someone please help, my 2-1/2 year old driving me insane since I made the stupid mistake of unrooting from TRWP and OTA update to 2.1 and now I am unable to update to 2.2. I had used TWRP to sideload GAPPS before, now I am stuck with unrooted 2.1 OTA update. No matter what I try I can never get it to update to 2.2, it fails with the dead Android screen and gives the following error - update failed error in /cache/nabi-2-update.zip.

Please someone help!
[Miscellaneous Android Development] CaptnSpaulding:
Sorry guys, as some know we've had terrible storms in the UK recently and we were affected and been without power for a few days. Finally managed to upload 2.2 including addons so the file is around 1.4GB.

https://www.dropbox.com/s/w1fqfaip6lxtyhq/2014-02-09--06-17-51 JRO03C.zip
[Miscellaneous Android Development] Ste_J:
Hope everything is ok with the power. I am in the northwest and not had it so bad. Few roofs gone in the wind and trees not so happy but so far no power cuts or floods up here
[Miscellaneous Android Development] Ste_J:
I can only assume that I have messed this Nabi right up......

Restored from the 2.2 and get stuck on the Nabi screen. At one point I could not progress at all and had to get myself into fastboot but nabilab would fire over a previous TWRP install

Managed to get back to 2.1

Anybody have any ideas or suggestions?
[Miscellaneous Android Development] katinatez:
Change out the TWRP to JB 4.1, then restore all partitions including addon. See if that helps
[Miscellaneous Android Development] aicjofs:
For others following this we were talking about this over here http://xdaforums.com/showthread.php?t=2644361&page=2 and in this thread.

As I noted over there, restoring a 2.2 UK boot, system, and addon is the easiest method but without taking the OTA the bootloader will not be updated to Jellybean and the result will be stuck at Nabi symbol.

There are two ways to do this without taking the OTA.

1) Have someone pull their UK Jellybean bootloader with nvflash(I don't know if I have uploaded the JB bootloader for US it may be the same as UK), and upload it, then use nvflash to put it the tablet.

2) Or get the blob out of the OTA and make a small install zip that copies the blob to the staging partition. This method is easiest because you don't have to mess with nvflash and APX driver. What I can't answer is if that is possible for people stuck at 2.1 and the OTA is failing. In the US version there were two OTA's, and only the second had the blob, so if you fail the first you can't download the 2nd to pull the blob out.

Here is a template to do that. It will not work as is someone needs to modify the template JB Bootloader updater script BLANK

Someone get the official UK 2.2 OTA zip from Nabi(part 2 if is two part). Open the zip. There should be a blob file in the root of the zip. Copy that blob out and put the blob in the root of the zip template above. Then "restore" 2.2 UK boot, system, and addon, then before rebooting "install" the modified zip with the blob in it. TWRP won't work anymore, you will have to use JB TWRP.

For the more daring, here is the US Jellybean bootloader blob installer. No idea how that effects UK users, but it should actually work judging how some UK users have turned their tablets to US(but they are using a US bootloader/US ROM vs US bootloader/UK ROM). Same idea, restore the 2.2 UK boot, system, addon. Then install the US bootloader for Jellybean below to the UK Nabi2. Reboot, and rejoice!! OR possibly reboot, then curse aicjofs. Both are possibilities ;)

JB Bootloader updater script for US Nabi's
[Miscellaneous Android Development] Ste_J:
Think I will give the US version a try. Will give this a go once I finish being told that my Lego builds are not up to scratch!
[Miscellaneous Android Development] Ste_J:
Bootloader based on the 2.2 OTA update

Managed to use a combination of the 2.2 back up file which was kindly provided above. Then took the 2.2 OTA from my Nabi (backed out of the update at the reboot stage and then grabbed the OTA from the Nabi) And modified the bootloader file

Used TWRP to restore the 2.2 back up file and just before I rebooted the system I installed the bootloader file. Rebooted and after a while the Nabi fired up into 2.2!!!!!

Next I used Nabilab to load the stock recovery and I am now in the process of doing a full reset

Been at this for hours but I really do need to thank everybody who has helped to get me this far. I really do appreciate it and was on the verge of replacing the nabi with a nexus 7
[Miscellaneous Android Development] Ste_J:
2.2 OTA file https://www.dropbox.com/s/67c3qunnj09cuyd/ota.zip

---------- Post added 16th February 2014 at 12:32 AM ---------- Previous post was 15th February 2014 at 11:34 PM ----------

Big time rejoice mate. Thank you
[Miscellaneous Android Development] aicjofs:
No thanks necessary, I have been somewhat neglectful of UK owners. Sorry about that. Very nice job snagging the blob and making an installer. So that bootloader.zip will be a JB bootloader installer for UK owners correct?
[Miscellaneous Android Development] Ste_J:
Yes it's the blob from the UK 2.2 OTA added to the zip file you gave. Worked a treat on mine

The only snag I have now is that the factory reset failed but it's not a big issue. Factory reset in nabi results in android eating an atom and then dying. Factory reset in TWRP resulted in nothing at all.

Checked for updates and system now saying everything up to date
[Miscellaneous Android Development] aicjofs:
The stock recovery you are using won't work. You must have the jellybean kernel version of the stock recovery. If you used the Nabilab or what not it's the ICS kernel. I can't believe TWRP didn't work. Did you do factory reset from Android? That reboots the tablet to whatever recovery you have installed and will wipe it. Difference is the stock recovery wipes /data/media(internal SD), where a "factory reset" inside TWRP does not. To wipe internal SD also you need to go to advanced wipe and select data. Of course that is dangerous because alot of people have their stock backups on /data/media, and no one including myself has EVER made that mistake and wiped their backup. Hahaha
[Miscellaneous Android Development] Ste_J:
Thinking about it. I updated TWRP on the fly and kept it on throughout. It's still present now and therefore I could not have gone back to stock recovery.

Nabi running a treat at the moment and already getting filled with games
[Miscellaneous Android Development] crispy514:
Hi, i'm in a similar position and sure how to do the above :(

I returned my Nabi to stock 2.0 (UK) using Nabilabs, restored the stock recovery and performed the OTA update to 2.1 (UK). However it fails the part 2 update with the dead android :(

I have the 2.2 recovery image from above. How do I install from TWRP? (never had to do that before) and how do I install the bootloader?

Sorry to ask but I've been reading all this for days and can't find an easy guide.

Thanks
[Miscellaneous Android Development] aicjofs:
I'd go about it like this if you already have the original Nabilab(not Nabilab GUI) installed.

Install TWRP

- Download this: http://xdaforums.com/showpost.php?p=50431160&postcount=97

- Copy that zip to the Nabi

- Use Nabilab to just put on the old recovery. Nothing else, just install that older TWRP version.

- Now update TWRP to 2.6.3 by going into TWRP and "Install" the zip you downloaded and put on the Nabi.

(setup for next step) - Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Note where you are backing it up to(internal or external storage) If you are space limited I recommend external, and if something goes wrong and you can't boot its easier to work with, otherwise you will have to be adb pushing files.

Install 2.2 ROM and bootloader.

- Download this http://xdaforums.com/showpost.php?p=50341726&postcount=85

- In Android(or if you can put you external SD in your computer) Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.

- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder

- Unzip the file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 2.2 ROM.

- Download this http://xdaforums.com/showpost.php?p=50356162&postcount=91

- Copy it to the Nabi. This will be for the bootloader update.

- Reboot to TWRP

- Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.

- You should be able to select boot, system, and addon and skip the others.

- If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.

- Reboot
[Miscellaneous Android Development] crispy514:
Thank you so much! I had got so far but couldn't get the TWRP I had installed to restore the Addons.. Followed the above and have 2.2UK version with full google store and JB loveliness!
[Miscellaneous Android Development] Ste_J:
I am so glad I didn't give you instructions. The above is a much more graceful way than mine which consist of much more swearing, rebooting, late nights and head scratching. You get the same result though!
[Miscellaneous Android Development] crispy514:
I'd done a great deal of the above before I gave in and asked! ;) Still, finally have a happy 5 year old again... :)
[Miscellaneous Android Development] aicjofs:
Glad it worked out!

Don't sell your effort short. There were a number of important contributions and you getting the bootloader blob and uploading the zip was one of them. That's half the fun of all of this(or perhaps only fun in retrospect? haha), people from around the world working and contributing to a common issue.
[Miscellaneous Android Development] DarkAngel:
Very true..... I have been wanting to update the Wiki with OTA's, full Roms, etc for some time now as there are quite a bit UK Nabi users that come on here but OTA's and Roms come short at sometimes. Anyone is welcomed to modify the Wiki and add their linked files and contribute to the Wiki. The more files and information we have in the Wiki, the better.
[Miscellaneous Android Development] DarkAngel:
Just wanted to point out if everyone has seen this app I came across? It's been out for a bit now.

{APP}{ROOT} TWRP Recovery Installer {Updated UI}

Now as stated in the thread it basically communicates with the TWRP Servers and the Device in question but of course our Device/s are not listed as a supported device by Team Win or on the Goomanager. aicjofs just wondering if you have placed any thought into this?

Just wanted to see if anyone else saw it. If it was mentioned I am sorry for not seeing it.
[Miscellaneous Android Development] Ste_J:
That looks really handy. thanks for pointing it out
[Miscellaneous Android Development] Herk718:
Never mind I figured it out my self! anyone out there stuck or this mind bottling task, shoot me a PM and I will see if I can help the best I can

P.S Big thanks to the OP ( ran out of thanks for the day but will def give some to u in 24 hrs bro thanks!

Hint* When in stock recovery, and u see the android man laying down with that famous red symbol on his chest... press and hold vol - followed by vol+ and then waala!!! magic!!! the hidden recovery menu we been so desperately looking for to flash those 2 part OTA'S...

(You'd be surprise how many people are stuck at this point!)

Enjoy...