[GUIDE][TOOL]Restore non booting Dreamtab - Fuhu Nabi 2

Symptoms​
This is for a Nvidia Dreamtab NV08B. Due to a system change you made, or an official Nabi OTA update the tablet now no longer boots.This could be the tablet hanging/frozen/stuck from any point from when turning the tablet on up to the Dreamworks characters screen and never boots any further. You have attempted at least 2 factory reset through the stock recovery and it still does not boot.
NOTE: If your Dreamtab was recently working and you made no system changes, or system updates but is now hanging at the Dreamworks characters try this first: https://forum.xda-developers.com/nabi-2/general/guide-dreamtab-hangs-characters-t3528698
Solution​
Restore the tablet to software version 1.3.12 stock condition: Unlock the bootloader to allow tablet modification. This will wipe ALL the data from the tablet. Format all ext4 partitions and check filesystem integrity. Reinstall recovery, boot, system and addon partitions. Optionally install the fsck binary that is missing on the tablet. Reinstall bootloader
Procedure​
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
To get an understand of how the device works with fastboot, ADB, and recovery read through this :http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
You will need to install ADB and fastboot drivers yourself. I have included a copy of Nabilab drivers for 32bit and 64bit computers in the download in the driver folder. Refer to the link above to understand driver installation and booting the tablet to fastboot. This is a script driven restore of the tablet, most of these task are automated.
General flow:
-- Download the Dreamtab_NV08B_restore.zip
-- Extract the zip file to a location of your choosing on your computer.
-- Connect the Dreamtab powered off to your computer via USB cable.
-- If you want to install the driver provided in the zip do it now.
-- Open the file recover_dreamtab file
-- A command prompt opens and the script runs as below. The script has the instructions in it, the below is just a summary.
(automated = script will do it for you. User = you need to take action)
(automated) Extract the files you will need for recovery.
(user) Boot the tablet to fastboot pressing vol+ and power button. Use vol- to select fastboot protocol.
(automated) Check fastboot operational
(user) If script hangs here, user will need to check drivers)
(automated) Initiate bootloader unlocl
(user) Use vol- button to select yes, and vol+ to acknowledge
(automated) Wipes userdata and cache and unlocks bootloader
(automated) Formats data partition
(automated) Boot TWRP 3.0.0 recovery temporarily
(automated) Check data partition integrity
(automated) Format and check cache partition
(automated) Check CPU serial number for TWRP backup
(automated) Push the restore files, bootloader, and fsck patch to Nabi internal storage
(automated) Restore recovery, boot, system, and addon partition files.
(user) Prompt user to install fsck binary that the stock Nabi is missing. I recommend this. but there is a no option.
(automated) Install fsck patch if selected by user
(automated) Install 1.3.7 bootloader
(automated) Remove restore files from tablet
(automated) Reboot
Note: The boot loader is left unlocked. Sometimes you will get a google play service error during first boot.
Download​
AHF Download Link: Dreamtab_NV08B_restore
___________________________________________

---

I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?

---

CriticalComposer said:
I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?
Click to expand...
Click to collapse
Sorry about that, I re-uploaded.
Yes you could copy the files over, or do the script by hand. Drop and drag is by far the easiest especially if you use external SD card. Part of me wants to know why the script isn't working for you though.

---

I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.

---

CriticalComposer said:
I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.
Click to expand...
Click to collapse
Go to the mount page in TWRP and disable MTP. When MTP is enabled it's really an ADB "composite device", when it's disabled it's a "single" interface.
To fix the ADB issue try adding
tools/adb kill-server
to the beginning of script.

---

Disabling the MTP worked like a charm. I would highly recommend adding that to the script as an echo so that others don't run into the same confusion. My tablet is up and working again. Thanks a ton for putting this script together. I would rather have had Nabi release factory images but this works just as well!

---

Thank you very much for the procedure.
is there any solution for Intel Version? (IN08A)

---

Thank You Thank You Thank You. This worked when everything else failed. Couple notes: Yes I had to Disable the MTP. No biggie. Then when I got to the Yes/No prompt to install fsck binary, I typed yes hit enter and the command prompt closed! I started over and and tried typing "No", same results. I actually tried the entire process a couple more times before I just used the TWRP to Reboot... all went well... I did see the Google Error but hit Ok and everything continued till it got to the setup page.. All in All an excellent script Thanks for your time and effort to do this.

---

Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!

---

phil_socal said:
Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!
Click to expand...
Click to collapse
Nothing comes to mind. The only time I have seen that failed message was on a tablet where the flash had gone bad, but the tablet wouldn't erase data and cache like it looks like yours did. Anything else plugged in, cables good? You could try the -i switch although I don't recall seeing a Dreamtab that needed it, I am mobile and cant remember. It's like fastboot -i 0x0489 oem unlock or something.