Nabi 2 Disney return to stock for Dummies?
Pretty much what the title says, I've got a Nabi 2 Disney model that I rooted (at least I think I did) in an attempt to free up more space on the tablet, and would now like to restore to stock so we can get the OTA 3.0 to KitKat update.
While there are a lot of informative posts here some of this stuff is beyond me, even being an IT guy myself (but not a lot of experience with Android, other than what comes with our phones, tablets etc.).
Are there any guides to returning the Nabi 2 to stock from a beginners standpoint, or really good step by step that even someone like me can understand? Here is the information that I have:
Model
NABI2-NV7A
Edition
NABI2-NV7A-US-D
Android Version
4.1.1
TWRP v2.8.5.0 Nabi Jellybean
To make things more interesting (of course) I cannot locate the stock image to recover it with, when I go into recovery in TWRP there is no package to restore, checked the external microSD and there is nothing there either. The original laptop I used to root the Nabi originally has since been wiped so I can't even look for it there.
Can this thing be restored to Disney stock without losing the "Disney" customization? Can TWRP be removed to allow the OTA update to install? We can download the OTA update just fine but when it reboots the Nabi goes right into TWRP.
Any help would be appreciated.
TMOSteel said:
Can this thing be restored to Disney stock without losing the "Disney" customization? Can TWRP be removed to allow the OTA update to install? We can download the OTA update just fine but when it reboots the Nabi goes right into TWRP.
Any help would be appreciated.
Click to expand...
Click to collapse
Should be possible. Yes TWRP can be removed, it depends on the OTA but TWRP can sometimes deal with the OTA as long as it's not a 2 part update.I would do the following, EXCEPT I don't have a Nabi Disney, and the restore I made has never been tested. Up to you if you want to try but Nabi Disney is almost impossible to brick.
-You should have a backup of your current system before starting.
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.4 Disney ROM and bootloader.
- Download 304 stock ROM http://www.nabtabhacks.com/downloads/304D.zip
- Put SD card in 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 304D.zip 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 3.0.4 ROM.
- Download the KK304bootloader zip attached to bottom of this post.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card 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 KK304bootloader.zip you downloaded and install it.
- Reboot
At this point you should start using the KK TWRP going forward. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
If all this works you wont need to restore stock recovery as you will be on the latest. Of course you are the first one to attempt to use this 304D AFAIK.
aicjofs said:
Should be possible. Yes TWRP can be removed, it depends on the OTA but TWRP can sometimes deal with the OTA as long as it's not a 2 part update.I would do the following, EXCEPT I don't have a Nabi Disney, and the restore I made has never been tested. Up to you if you want to try but Nabi Disney is almost impossible to brick.
-You should have a backup of your current system before starting.
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.4 Disney ROM and bootloader.
- Download 304 stock ROM http://www.nabtabhacks.com/downloads/304D.zip
- Put SD card in 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 304D.zip 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 3.0.4 ROM.
- Download the KK304bootloader zip attached to bottom of this post.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card 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 KK304bootloader.zip you downloaded and install it.
- Reboot
At this point you should start using the KK TWRP going forward. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
If all this works you wont need to restore stock recovery as you will be on the latest. Of course you are the first one to attempt to use this 304D AFAIK.
Click to expand...
Click to collapse
Just what I needed, thanks for this, hopefully by Sunday I'll get to this and report back how it went (can't handle anymore "Daddy when are you going to fix my Nabi" questions...).
It worked like a charm, followed your instructions to a T, shut it down once or twice as it seemed to get stuck on "loading" or "syncing" screen (sorry, forgot which) after the modules were updated but eventually everything loaded and then we had to sign in with the Nabi ID like it was the first time.
All the Disney apps are still there that we didn't remove to make room for the update but I'll think we'll trim things down more as there is now less than 500MB of free space on the internal memory.
Still a lot of demos she doesn't play with so I'll let her enjoy things for a few days and then we'll start thinning things out.
Thanks again for all your help, people like you are what make the internet a great place.
TMOSteel said:
It worked like a charm, followed your instructions to a T, shut it down once or twice as it seemed to get stuck on "loading" or "syncing" screen (sorry, forgot which) after the modules were updated but eventually everything loaded and then we had to sign in with the Nabi ID like it was the first time.
All the Disney apps are still there that we didn't remove to make room for the update but I'll think we'll trim things down more as there is now less than 500MB of free space on the internal memory.
Still a lot of demos she doesn't play with so I'll let her enjoy things for a few days and then we'll start thinning things out.
Thanks again for all your help, people like you are what make the internet a great place.
Click to expand...
Click to collapse
So glad it worked. I owned a Disney edition for about a day and a half however many years ago, and I had to make that ROM by just reverse engineering it up to the latest version. Never had a chance to see if it actually worked until now. So thank you!
Can i use this rom on my non-disney version? would it add all the extra disney stuff?
mjw2k11 said:
Can i use this rom on my non-disney version? would it add all the extra disney stuff?
Click to expand...
Click to collapse
The partition sizes for "system" and "addon" are different between the Nabi2 orig, Nick, and Disney versions. For example if the the system partition for the Original is 500MB you can't install the 800MB ROM for the Disney, it won't fit.
That said, with nvflash it is possible to change the partition sizes... but for even the above average technical person it's not possible.
Related
[See post http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123 for the new version of this post with updated links/pointers to Succulent's recent CM10.1 builds as well as CWM/TWRP recovery tool compilation].
[Caveat emptor: adopt/follow this guide at your own risk].
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc).
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly.
Obtain and copy to the SD card the following files:
MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img.
the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use).
Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post.
Select Wipe data & factory reset.
Select install zip from SD card and install cm-10 zip file.
Select install zip from SD card and install gapps zip file.
Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot).
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored)
A few additional points worth noting:
Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact.
To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9.
CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its archive format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV).
To restore from backup data, boot into SD card and select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT.
I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do.
See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
My thanks to all the developers who collective work created this wonderful ROM as well as the tools and info I made use of to install it. IMHO this ROM helps make the Nook Tablet one of the best-value tablets for the money (at least at the moment).
great post...fwiw here's my experience to get two NT16's up and running (I started with an old CM7 on both of them).
Backup nook with titanium backup on existing 32GB card.
Take screenshots for replacements
Reset nook to stock (1.4.2) and update to latest (1.4.3) with a fresh SD Card with repart.img copied to root (my red 2GB card):
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
http://www.youtube.com/watch?v=Nu6e4m62tFc
c. 1.4.3 can be downloaded from B&N site directly. (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/)
Create a CWM SD Card (ideally 4GB SanDisk) as per these instructions - http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
Copy CM7 BETA and compatible GAPPS onto this card or another blank one. You can get the files from here: http://forum.xda-developers.com/showthread.php?t=1481826 and http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Boot into this CWM Card, wipe data/wipe cache and dalvik cache. Install zip from sdcard (either current or pop in the new one). Choose cm-7 beta first, then gapps. Remove sd card. Reboot. Wait a while for it to set itself up.
Go into settings/applications and clear the cache for google market/play.
You now have CM7 installed and can setup the basics (google, wifi etc..)
Insert your 32GB (or 16 or 8 or whatever) Sandisk SD Card (it should ideally have the Titanium Backup folder from step 1, any media you want in Music and Movies folder and the CM10 and gapps zip in the downloads folder -- and that's it!)
Once mounted, download Goo Manager from the google play store and run it, accepting superuser requests.
Choose settings menu and "Install OpenRecoveryScript" and it should install openrecovery twrp recovery manager. Once it has installed and informed you of success, reboot into recovery (this is important), upon reboot hold the "n" and choose internal emmc recovery from the menu.
You will now find yourself in TWRP. From the install menu, add the CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode and then the gapps-jb-20121011-signed.zip and swipe to confirm flash. This is it. Fingers Crossed!
NOTE: On one NT 16 (I have two), step 12 DID NOT WORK. It wouldn't install the CM10...zip -- and simply rebooted itself or hung...so I powered off, and rebooted to the CWM Card in #6..and used CWM to wipe caches etc… and then installed the two zips...and voila.
hope it helps.
digixmax said:
I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc.
Click to expand...
Click to collapse
How do you feel about it now that you've installed it internally? I took the plunge as well today, but I'm not sure it's runs any better internally than it does from the sd card. Having said that, it runs so incredibly well from the card, so it's really hard to beat, but still... I'm actually having more issues with the internal install than the sd version.
I had had enough of the stock reader (that I'm actually pretty fond of) not remembering my place in sideloaded books, so I didn't feel I had anything to loose and am glad I made the install though. Installed once makes it easier to reinstall when an even better build comes along.
I made the switch since the stock ROM was so barebone and clumsy I virtually never use it since I had the NT, and the rooted stock ROM is just marginally better -- I found out there are so many apps I 've been using on CM10 that are simply not available for BN's (Android) Gingerbread. I also like the fact that I can now reboot (if ever needed) untethered.
I think performance-wise it runs about the same as it was running on SD, if it's better then it's not yet noticeable.
What kind of issues are you having with your new setup?
Some apps misbehaved. Didn't install properly or gave error messages. I decided to re flash and this this second install hasn't had any issues at all. Same files from the same card.
It is nice to have it internally and be able to switch sd cards should I want to.
Sent from my Barnes & Noble Nook Tablet using Tapatalk 2 and SwiftKey
I ran into a problem with v12/08: when I connect the NT to the PC I do not get the “USB connected” notification with option to “turn on the USB storage”, and thus cannot access neither the emmc media partition nor the sdcard. The problem exists with both CM10 running on emmc and running on sdcard. Furthermore when running on sdcard, hitting “storage” in “settings” results in a force-close of “settings”.
I am curious if anyone else has the same problem, or I am just missing some setup setting somewhere.
In the meantime, I am back to running another ROM off SD.
Those storage setting issue I had with the 1118 build but not with later ones. Connection to PC work fine but I don't think I need to do the turn on USB thing. No PC nearby at the moment
Edit: I am now near a PC, and I do get the "touch to turn on USB" or words to that effect. So it works as it should..
Sent from my Nook Tablet using Tapatalk 2 and SwiftKey
Thanks, I've tried reinstalling a couple of times (as well as installing a different ROM) without success.
I found the answer to my problem: I was used to getting the full-screen alert “USB mass storage” (upon insertion of tethered USB cable), and didn’t notice the tiny alert “USB connected” on the status bar (which when pulled down would in turn launch the “USB mass storage” alert).
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
Question: I'm not new to rooting and flashing, but am new to NT. I rooted my wifes NT, installed a launcher to switch back and forth, and loaded a few apps. I did not change the stock recovery and used a boot sdcard to run an older version of CWM. I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Cm7 is a gingerbread rom, it can be flashed by cwm 5 and 6 both. But cm10 is jellybean and must be flashed with cwm 6 only (or twrp) . And once you have cm7, you get cyanoboot (2nd bootloader) which is necessary to load cwm6, whether its internally flashed recovery or SD card recovery.
If you still have your bootable SD card, boot into recovery and check the version (cwm 5 most likely) , then do the longer, but simpler method - stock > cm7 > flash cwm6 internal and boot into it from cyanoboot > cm10.
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Sent from my SAMSUNG-SGH-I317 using xda premium
Dean1650 said:
...
I forgot to hack OTA off so while messing around the darn thing upgraded to 1.4.3. The stock rom is such an old version of GB it is really worthless. So here is my question. Can I use this method to go directly to CM10? Im not too concerned about the issues mentioned in this thread, but more concerned about the method and the type of issues I might encounter. I see some threads say to flash CM 7 first, why I'm not sure. It almost looks to simple. Just looking for confidence. If it were mine I wouldnt care. Thanks for any help.
Click to expand...
Click to collapse
Yes, you can use this process to go directly from stock or rooted stock to CM10 -- I used it to go from rooted 1.4.3 directly to CM10. With SD-based flash, there is no need to go the circuitous multi-stage flashing process.
And if you use Succulent's CM10 builds from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/ his ROM zip files all include emmc recovery so you don't even have to separately flash recovery as you would have with other ROMs. I think his approach, in addition to being convenient, has the benefit of avoiding intermediate states where there is potential incompatibility between ROM and recovery versions (which I think is conducive to causing bootloop).
Of course if for some reason you later prefer a different version of recovery than the one he includes (CWM 6.0.2.5) you can always reflash your particular choice of recovery by itself.
FWIW I am running Succulent's cm-10-20121225-acclaim-HD.zip (GCC 4.6) at the moment and it works great.
Dean1650 said:
I see the difference between the 2 methods..a few more questions. I dont see where or how recovery gets flashed in the first method. Looks like either/both are used but not flashed. In both methods, I dont see any sdcard additional partition requirements so can I assume everything can get copied to the boot partition? Haven't looked at the card I made yet, but if CWM is current enough for CM7 it should work fine. I appreciate this thread. It has cleared up a lot of questions.
Click to expand...
Click to collapse
Everything that gets flashed via recovery (either CWM or TWRP) comes in zip archive form, and this applies to ROM, gapps, as well as recovery itself. (If you ever want to flash recovery, the simplest way is to get a recovery zip file, such as one of those with keyword emmc from http://forum.xda-developers.com/showthread.php?t=1640958, and flash it from SD using the process in the first post, just as you would flash a ROM build or gapps).
If you are curious about what gets installed and where, just open (but don't extract) the to-be-flashed zip file (e.g., using winrar/winzip/7-zip): everything except the META-INF folder is what get installed, and the updater-script file in META-INF\com\google\android\ (which you can open using a text editor like notepad) contains installation script detailing where (i.e., which partition on the NT) various components of the zip file get installed.
Typical ROM builds zip contain boot.img which gets installed on /boot partition, and a bunch of system files and apps to be installed on /system partition. Succulent's ROM builds also include recovery which gets installed on /recovery partition. Finally gapps apps get installed on /system as well.
Really, really appreciate this OP, the replies, and the knowledge. VERY helpful. Wont do this til the 1st and will let you know the results... Again, THANKs
Sent from my SAMSUNG-SGH-I317 using xda premium
Well your method worked flawlessly. I had a few minor operator errors but it went just as you explained. I did, however, have a fatal bug in the rom. Not sure who to report it to, but while messing around in settings I tried to change the color of the clock in the status bar. It totally blew away systemui. I tried everything I knew of to restart and recover but had to resort to wipe/factory reset. Could not figure out what data file got corrupted. That in turn made me have to flash the gapps again because none of the Google apps worked including play store. The net result is to add 1 more step to your method. BEFORE messsing with settings, and after the initial setup is complete, boot to recovery and do another backup..I forgot to mention I flashed 20121231, which is the latest release. Thank you so much for your knowledge and reseach. STOCK ROOTED TO CM10 RELEASED.
Sent from my SAMSUNG-SGH-I317 using xda premium
Stuck on backup in CWM 6.0.1.2
My 16gbNT is currently running Team_B CM7. I'm trying to install Kuzma30's CM10.1 from a SD card. Following the instructions from this OP. While trying to perform my backup the process gets about 3/4 of the way through and then sticks at the file named "generic11.lda". It doesn't continue after that and I have left it alone for a considerable amount of time. Any idea what's causing the stick? I've tried it about three or four times with occasionally sticking at different files but it is still about 3/4 of the way through. Backup will not finish.
Any help is greatly appreciated.
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Backup success, Install failure
digixmax said:
I'd suggest trying a version of CWM that is considered compatible with CM7, e.g., CM7-9_CWM_v5.5.x_8gb-16gb_tools_sdcard.zip from http://forum.xda-developers.com/showthread.php?t=1640958 (but then remember to flash CM10.1 with 6.0.1.2).
Also check and make sure that you have enough space on your SDcard (you can/should remove backup data associated with failed partial backup attempts).
Click to expand...
Click to collapse
Backup successful! Thanks button pressed. Now on the install I used CWM 6.0.1.2 and I'm not allowed to complete the install. It aborts installation and gives the following error:
"Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10.1-20130102-UNOFFICIAL-acclaim.zip
(Status 7)
Installation aborted."
Any ideas?
Your guide is quite clear but somehow it is not working for me. I have a fresh NT 8GB with stock 1.2 on it.
I obtained the 6 files you mention:
- u-boot.bin
- MLO
- flashing_boot.img
- recovery.img (= cwm_6012_sd.img)
- gapps-jb-20121011-signed.zip
- cm-10-20121231-NOOKTABLET-acclaim-HD.zip (from: http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/)
I copied them to a 16GB 10x SD card and placed the SD card in my NT.
The problem is that whatever I do, it always boots the stock os and never into Cyanoboot. I know I have to connect the NT to my computer with USB and wait for it to boot, but even then it only load the stock OS.
Am I doing something wrong here?
Help much appreciated!
Hi There
Such a great program is the Nabilab thank you!
Ive tried to serach the forums but am getting burried under so much info that I dont all fully understand, please forgive my ignorance. Im also not even sure if I am posting in the right place (trying to do this at work when boss isnt looking which is hard).
I have a backup and restore question please related to UK version of the nabi2.
I downloaded the full version of the nabilab tools software including the stock condition to my PC. I then ran the full installation (option 1) and all worked brilliantly (little trouble with the drivers but solved).
But now, 4 weeks later, the nabi has lost wifi which I understand from reading is an issue with OTA (which I didnt know about and hadnt realised was turned on).
So from what I can tell, I need to basically blank the nabi2 and then restore it. But I have just had the thought, is the stockbackup file within my internal SD card actually a backup of my own system created when I ran the tools setup/installation (which I think is the case), or is it a copy of the downloaded stockbackup that came with the nabilab tools and was automatically copied across during the tools installation?
The reason for asking is that I just thought, that because my Nabi2 is a UK version (I did update the OS as instructed before running all the nabilab tools installation) then if the stockbackup is from the downloaded pack, and thus not UK, then trying to restore that might cause me problems with the UK version and maybe the uk nabistore??
Would I be better going into Nabi parent-mode and using the option in the settings to reset to factory defaults (will this work to restore nabi to earlier version?) or am I ok to use the stockbackup that is sitting on my internal sd card?
Should I use twrp to "wipe" first before trying any backup or should I just run restore?
Do I use the nabilabs menu to try and do the restore or should I go into TWRP to do the restore?
Id really really appreciate any help please as Im very new at all this and not very knowledgable. The Nabi2 is my sons. He is 4 and has autism and doesnt have any communication or language so doesnt understand that his Nabi ran out of storage space thus I used the root to be able to use an app swapping internal-external sd cards for more space. His Nabi means everything to him and its starting to look like it will help his communication, he doesnt understand why parts of it are now not working which leads to huge upsetments (really huge) and we cant explain to him that it will be fixed soon, and so im desperate to fix it as quick as I can.
Please any help would be wonderful.
many thanks for even taking the time to read my post.
Alex
alexbobspoons said:
Hi There
So from what I can tell, I need to basically blank the nabi2 and then restore it. But I have just had the thought, is the stockbackup file within my internal SD card actually a backup of my own system created when I ran the tools setup/installation (which I think is the case), or is it a copy of the downloaded stockbackup that came with the nabilab tools and was automatically copied across during the tools installation?
Click to expand...
Click to collapse
If you look in the TWRP/BACKUPS/yourserial/ folder the folder called "stockunrooted" should be your Nabi's backup. A folder called "abcdstock123" is the stock backup the Nabilab would create, but it will only create this if you ran the restore "Nabi to stock" from Nabilab. Honestly before you do anything else, if you find the folder stockunrooted COPY THAT TO YOUR COMPUTER. I can't stress that enough, we don't have near as many UK owners here. If something goes wrong we have plenty of north american versions the users here can get for you, but not many if any UK ones.
alexbobspoons said:
The reason for asking is that I just thought, that because my Nabi2 is a UK version (I did update the OS as instructed before running all the nabilab tools installation) then if the stockbackup is from the downloaded pack, and thus not UK, then trying to restore that might cause me problems with the UK version and maybe the uk nabistore??
Click to expand...
Click to collapse
I would definitely try and restore your stock backup if you have one. I have no facts on this matter but the UK store could react negatively to something such as your build.prop being different. Also there might be a difference in WiFi configuration as I think there are some differences between power in channels 12 and 13 outside North America. I would avoid restoring the Nabilab one unless it was a last resort. If you don't have your stockunrooted, someone out there likely has a UK backup. We would be better off seeking them out and seeing if they would upload you one.
alexbobspoons said:
Would I be better going into Nabi parent-mode and using the option in the settings to reset to factory defaults (will this work to restore nabi to earlier version?) or am I ok to use the stockbackup that is sitting on my internal sd card?
Should I use twrp to "wipe" first before trying any backup or should I just run restore?
Do I use the nabilabs menu to try and do the restore or should I go into TWRP to do the restore?
Click to expand...
Click to collapse
-Either a factory reset, or restoring the stock backup of your Nabi(not the stock from Nabilab) should work. A factory reset won't revert you to an older Nabi revision it will simply wipe everything from the tablet, and leave you on whatever version you are currently on. The restoring of your backed up version will more or less result in the same since you upgraded before backing up. However the major difference will be your backup will have the Nabi setup done, where a factory reset will erase it. Also it will WIPE your stockunrooted backup that I talked about at the beginning, we don't want that without you copying it to your computer first. So you skip the step of setting up parent mode, and your wireless password would likely be there so you would save yourself 2 minutes.
-If you restore your stock backup of your tablet, and restore boot, system, and data there would be no reason to wipe first. Although out of habit I always clear cache and dalvik cache anyway, even though it gets wiped by the restore. No need to clear system as TWRP will format that partition before restore anyway.
-Go into TWRP. Select restore tab. Find folder called stockunrooted and select. Restore all. Boot, system, data check. I assume you have gotten into TWRP fine but just in case: From powered off, press and hold both vol+ and power, then select recovery kernel.
-Or you could just do a factory reset. The differences I highlighted above.
-Either option will break root, and gapps. To get them back use options 3 and 4, instead of 1 like you did last time in Nabilab. Gapps only, Root only, since you would already have stockunrooted no need to make a second one.
Thank you so much for your reply the info is invaluable.
Sorry for spelling your name wrong.
Sorry also for posting this in the wrong place (as I have since found from browsing)
Thanks again for the help.
Ill backup the stock to my pc, then will try using twrp to resotre that backup and then use the nabilab again to root. Then I guess its simply logging into the nabi and google store to download any missing apps.
Thanks you so much
Alex
PANIC
Oh no ive gone to the folder on my nabi through the usb cable and the stockunrooted folder appears to be empty.
I did choose option one when I did the nabitools so I just dont understand why theres nothing there.
When I looked into twrp last night it seemed to think there was a backup there for stockunrooted so I dont know if its dissapeared or whether it was never there in the first place.
PANIC
As there is not supposed to be many UK nabi backups out there (and im time limited due to my son relying on the tablet) am I now only left with the factory defalt reset? (not quite sure how to do that really)
I know I cant use the one in the nabilab because that is USA version.
Please help
Alex
alexbobspoons said:
Oh no ive gone to the folder on my nabi through the usb cable and the stockunrooted folder appears to be empty.
I did choose option one when I did the nabitools so I just dont understand why theres nothing there.
When I looked into twrp last night it seemed to think there was a backup there for stockunrooted so I dont know if its dissapeared or whether it was never there in the first place.
PANIC
As there is not supposed to be many UK nabi backups out there (and im time limited due to my son relying on the tablet) am I now only left with the factory defalt reset? (not quite sure how to do that really)
I know I cant use the one in the nabilab because that is USA version.
Please help
Alex
Click to expand...
Click to collapse
I would go into TWRP. Then in the advanced section use the file manager. Navigate to /data/media/TWRP/BACKUPS/serial/stockunrooted and then see if it is blank or if there are files in it. boot.wim boot.wim.md5, etc etc
If it's gone then it will have to be a factory reset.
aicjofs said:
I would go into TWRP. Then in the advanced section use the file manager. Navigate to /data/media/TWRP/BACKUPS/serial/stockunrooted and then see if it is blank or if there are files in it. boot.wim boot.wim.md5, etc etc
If it's gone then it will have to be a factory reset.
Click to expand...
Click to collapse
Hi
Did that, folder empty and no files in it.
Have done a factory reset and YAY all good.
Have re-signed in to nabi account, have redone the root using nabilab, have then installed the ext-to-int sd card app and the big card is now in memory.
So now its just a case of sitting back and slowly reinstalling all the apps from the nabi store and then the google store. Once all thats done ill then go into TWRP and do me a proper full backup.
Phew!
Thank you so much for your help it has been invaluable. My deepest gratitude!
Thank you!
Alex
alexbobspoons said:
Hi
Did that, folder empty and no files in it.
Have done a factory reset and YAY all good.
Have re-signed in to nabi account, have redone the root using nabilab, have then installed the ext-to-int sd card app and the big card is now in memory.
So now its just a case of sitting back and slowly reinstalling all the apps from the nabi store and then the google store. Once all thats done ill then go into TWRP and do me a proper full backup.
Phew!
Thank you so much for your help it has been invaluable. My deepest gratitude!
Thank you!
Alex
Click to expand...
Click to collapse
So glad its working again! Make sure to copy that backup you make to your computer
aicjofs said:
So glad its working again! Make sure to copy that backup you make to your computer
Click to expand...
Click to collapse
I surely surely will (multimple copies)
Thank you again. Its hard to explai how much my son relies on his Nabi so its hard to explain how grateful I am you are a hero!
Alex
UK Nabi 2 Rom
Hello All, I`m looking for a UK version of the 1.9.37 rom after wiping my daughters Nabi, forgetting to make a backup way back when i was rooting it last year. I`ve tried the stock version but when it tries to do the second of the two part ota i get the dead robot and Nabilab doesn`t see it when connected.
Any help would be greatly appreciated.
Hi everyone
I bought 3 tablets for Chrismas for my nephews
I have been able to root and install gapps (to have google store) on two of them using NABILAB FULL GUI.
However, the third one didn't work, even I was using the same tutorial....I think It was a UK version tablet
After rooting, the tablet didn't have the gopogle store, and didnt have the wifi as well , I have tried to delete evry thing to return to the factory setting but I ended up with a tablet with no OS, When I turn it on, I get a black screen with the table 'NabiSetup' on the top left.
I contacted NAbi support, But they said that it was an error if rooted tablet, so they don't give any support :crying:
Is their any way to reinstall NABI OS ??
Thanks
Anyway to install, or have you installed a custom recovery on the tablet?
Sent from my GT-I9505G using Tapatalk
If you are in the US you can try this --
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi. Otherwise, install it.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
Hello my fella Developers.
lets do this again. i have the threat all typed up with details and closed it by an accident.
anyways
I have htc one max 8060-t6dug Chinese variant without OS. HTC-1
I had issues with this one, it came with bloatware and lots of it. some of it is pornographic. (got kids who play with my phone)
i decided to root, got the TWRP Recovery. flashed with latest SuperSU. got titanium pro (paid) to get rid of unwanted bloatware. i guess i missed out on something. as soon as i connect with wifi. it starts to download apps. and formatting doesnt help. so i thought maybe repeat the process. BUT in recovery i accidentally wiped system.
i have been through xda developers forums completely found some roms but dead links.
went though several other sites without any luck.
went though Chinese forums (Baidu i think) found some firmwares but TWRP gives me error trying to flash it.
i have tried to flash these with adb command, but mostly get remote not allowed error or space not allocated error.
came back to xda forums and found this
http://forum.xda-developers.com/htc...m-ruu-htc-one-max-809d-t6dwg-sense-5-t3006498
i know this is for t6dwg variant.
t6dwg and t6dug are both Chinese variants and dual sim. i have tried all roms listed on this thread. TWRP Flashed it fine but now when it boots up and gets to lock screen, when i unlock it it show HTC white screen and restarts after a min or so.
I went to the store and purchased another htc one max, same variant. HTC-2
i thought maybe make a nandroid back up and flash it to HTC-1
i repeated the steps and got HTC-2 rooted, latest TWRP, and made the back up. but i am unable to flash it into HTC-1
HTC-1 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111
issues, NO OS!
http://picpaste.com/pics/htc1-l8ImCwQL.1462326306.jpg
HTC-2 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111, boots perfect,
issues, bloatware
http://picpaste.com/pics/htc2-BrCDb5Tw.1462326402.jpg
lets not forget its been about a month since i am trying to figure this out without disturbing developers and wasting their time. this is my last resort
any help would be greatly appreciated.
Thanks in Advance
Anyone out there to my rescue?
@waqas9240 So you made the backup with TWRP? Why not backup to an sdcard one the working one. Place the sdcard in the non-working one and do a restore.
waqas9240 said:
Anyone out there to my rescue?
Click to expand...
Click to collapse
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
waqas9240 said:
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
Click to expand...
Click to collapse
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Flyhalf205 said:
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Click to expand...
Click to collapse
thats what i thought at first. i confirmed the path on both phones. i even got to push the back up in the non working htc to restore from the root as it was located in the working htc max. still does the samething. the second folder after TWRP is serial number folder. i even renamed the serial number to the non working htc ( i dont know if that would have made a difference or not) but still running the same issue. i dont have both phones on me right now. they are at home. let me finish work and will try it again as you explained.
meanwhile if you can figure out something else that would be great bro!
Thanks
Since there isn't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Oreo took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
https://drive.google.com/open?id=1lBsTd04Un6xJQkA0E6LpWxeDX7bhwsai
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD/EXTRACT zip file from above Google Drive's link to your PC
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage SD card)
browse to that folder and open that SD card's TWRP backup folder, using your PC
go to last folder where you should see some files, delete them then
Copy EXTRACTED files from (Google Drives) into TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card.
Where xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP
RESTORE everything showing there (all those three partitions)
REBOOT to system
IF you can't see those copied files on your tablet then you have missed something. Restart back into TWRP
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Hi, I have a T380, I thought about installing this, but before I do, will this work on the t380? Because you have T380T, and I have T380. And if I want, can I put some of the stock apps back on?
Indeed it works on a T380
CaptainChris2018 said:
Hi, I have a T380, I thought about installing this, but before I do, will this work on the t380? Because you have T380T, and I have T380. And if I want, can I put some of the stock apps back on?
Click to expand...
Click to collapse
I just installed it on my T380.. Be sure to follow the directions entirely. And remember to reboot TWRP after putting the sdcard with the backup files back in or else it may not read it (mine would not).
zanophol said:
I just installed it on my T380.. Be sure to follow the directions entirely. And remember to reboot TWRP after putting the sdcard with the backup files back in or else it may not read it (mine would not).
Click to expand...
Click to collapse
followed the directions but device wont read the backup file. would you mind posting all the steps you took to do the backup.
I had the same issue, so when the proper backup files are in place on the ext sdcard and reinserted into the device, but the device won't read it -- for me, I had to reboot the device into recovery and THEN it would read it.
Hi,a friend is running android 9 stock on the T-380.Does not have alot of apps installed,but hardly and internal memory left.I was thinking of rooting it,and uninstalling some system apps. Can you possibly tell me which system apps are safe to uninstall on this tablet?
bobbylo said:
Hi,a friend is running android 9 stock on the T-380.Does not have alot of apps installed,but hardly and internal memory left.I was thinking of rooting it,and uninstalling some system apps. Can you possibly tell me which system apps are safe to uninstall on this tablet?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...-safe-to-remove-ktu84p-m910vvru1anj5-t2976286
always change apk extension with .APKbak
so if you got into mess you can rename the APKbak into .APK
if i got android 9 can i do this it?
Is file support with t385??
I want to personally thank you for this TWRP image! I completely hosed my sm-T380 that I just got as a backup tablet while trying to root it.
This did the trick Thank you again!!!
I did this using internal memory and all ok. thanks.
I need to say THANK YOU BRO!!!! You just saved my ass!!
But can't tell how much a custom ROM is needed for this device.
Only things to do, is to remove all the bloat left whit the link you provide above and that's it.
Once again, 3 thumbs up! (don't ask me where I found the third one lolll)
it's a great work .I want download it, but I can't download google file directly(site blockked), I have to through VPN.So the speed is not quick enough for me,I can't complete the downloading within an hour when google vary the token.The download work can't continue and must restart from the beginning.
If you have time,would you please split it into several parts,each size blow 300M?Thanks a lot,this file I think useful and can give me big help and save me time.