Database Info

[HOW TO] Root Nextbook8 Premium (and install market app) [UPDATED 1-17-12]

PLEASE BE ADVISED: THE AUTHOR OF THIS POST NO LONGER PROVIDES SUPPORT FOR THIS THREAD. HOWEVER YOU ARE MORE THAN WELCOMED TO CONTINUE USING THE FILES AND METHODS AT YOUR OWN DISCRETION. GOOD LUCK!!
INTRO: For all those searching the internet trying to find answers as to how to gain root on your Nextbook8 Premium and also gain access to the wonderful android market from which we were greatly deprived (as is the case with many low-priced tablets these days), the wait is over thanks to a certain someone who goes by the name of DEVMONKEY. Of course I take absolutely NO CREDIT for this and only took the liberty to re-write it thus adding a little more detail to the process. Enjoy!!!
DISCLAIMER​***I HAVE NOT TESTED THIS PARTICULAR ROM WITH MY N8 WHEN I HAD IT BUT AS THE PROCEDURE TO FLASH IS STILL THE SAME ALL SHOULD GO WELL. HOWEVER, I AM NOT RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN IF YOU USE THIS AND DAMAGE YOUR DEVICE. PLEASE FOLLOW ALL STEPS CAREFULLY***​
[HOW TO] Root and install Market on your Nextbook8 Premium​
UPDATE: This is post has been updated with a new rom to replace old one. Method of flashing is still the same so no worries. All those who want to upgrade to this rom from the one I previously posted in this guide when I first wrote it can just repeat the steps over again with the new rom package.​
This rom is based on Samhain's release: SamDroid v1.13
Modifications (mostly GUI / cosmetic tweaks):
1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.
2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)
A couple of things to note once you have installed the rom:
- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.
- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.
- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.
- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).
- You can also grab Adobe Flash 11 from the market and it'll work correctly.
- This release boots MUCH faster, and is even more responsive than before.
- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.
VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.
​Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.
NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.
Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.
NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.
Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:
Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)

Thanks! worked great.

I signed up, so i can say thank you. this worked perfectly.. i was skeptical and scared i'd ruin this tablet, as i got it as a gift, and was obviously disappointed to see no market on it, but this worked. thank you.

How about Nextbook Premium 7?

Thank you!
This worked great, I was able to get the android market installed and working.

Android version?
What version of Android does this install?
Cheers, Greg.

It's work, your are wonderful,thank you Sunnyboy167

Great job! Good to have root and Market working. But anyone else get FC when opening Camera app?

Perfect! I have rooted many Android devices and this is one of the easiest ones. Just read the directions carefully and you'll do fine.
Hopefully someone will release an ICS update for this device soon..after using my Galaxy Nexus, Gingerbread seems so...obsolete.

I'm glad you enjoyed this info just as much as i did
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!

THANK YOU!!!!
I was about to throw this tablet out the window!!! Followed the instructions and it works perfectly!!!! Thanks SO SO much!!!

Thanks to you I had a very Merry Christmas haha thank button has been pushed repeatedly!

Hi Sunnyboy,
Just want to say a big thank you for the detail post. I was about to give up on on this tablet when I came across your post.
Chris

help help!!!
hi sunny boy,
i just got my nextbook8 yesterday... come across this website and trying to root my nextbook last night at home...
I encounter this problem...when i plug in my nextbook into the PC USB ..it turn on from the off mode. and the pc started to scan the driver and it actually install successfully. I am running on win7. after that i cant install the driver required.. can anyone help me out here cos i try to run exe. file. it cant root my nextbook... i am helpless now...

I am also having problem with the camera. I'll have this error:
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.

HELP HELP HELP...not able to on the device after updated the driver....PC shows device found after plug in USB, which shows the device is working but just cannot on it.. a total IT dummy and not sure what's going on..someone said the ROM is damaged which cause this.....any way to recover the tablet..i just bought it for less than a week. HELP HELP HELP!!!!!! (tried reset but still no response)

Sunnyboy167 said:
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
Click to expand...
Click to collapse
I have already been to this website and successfully added the market to my Next7. I do want to root it and flash a custom ROM, but I have not found anything useful. Thanks though.

Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??

eybarra2 said:
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
Click to expand...
Click to collapse
u can reboot the device by using a paperclip and press in the reset button.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Thanks for the detailed guide Sunnyboy167~ Anyway devmonkey just release a newer mod which works better than the previous. Do check it out

hi all,
I rooted my new nextbook8 ...and it works just nice...
just need some help on whether possible to use my iphone as a modem for my nextbook? as i realized it cant detect my wifi network from my iphone. While my colleague 's motorola zoom works fine with my iphone...any solution on this?
Caduser from singapore...

[WINDOWS] {05/22} WET_ANDY * a UNIVERSAL splash screen converter and flashing tool

Meet Wet Andy, a UNIVERSAL splash screen tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, you heard right, this is a tool that can take any standard image (jpg, png, bmp), convert it to the exact screen size of your device, and flash it to your device.
Custom splash screens have never been easier! It will work with API7 through API15 without issue (on the 8 different devices I tested). This is a self-contained package, no installers, and can be used from a flash drive with no additional downloads required. All the tools are right there!
STEPS:
1. Connect your Device and enable USB Debugging. Start the "Wet Andy" program by clicking it.
2. Hit the "TEST ADB" button, it will tell you if your device is connected. (output can be seen as ADBTEST.txt in the folder)
3. Hit "PICK" and you must pick an image file that is JPG, BMP, or PNG using the file chooser.
4. Hit "CONVERT", you will not see the progress on screen, but when you see your image, display.txt, and splash.img in the program folder it has worked!
* This program auto converts the image to the size of your screen, so you can use any image. If your phone does not display its screen size in the props, the default is 480x800
5. Close the program. (ffmpeg has something weord where it keeps going, but don't worry as it WORKED.
6. Restart the program and "TEST ADB"
7. Once you see it is connected, hit "Install"
* The phone will freeze, then reboot into the bootloader. From there, it will do the install.
* Once you see the screen go blank and the program show "Installing", it has installed and is rebooting
* You will see the new image as it boots!
TO REUSE AND FLASH ANOTHER IMAGE TO THE SPLASH, DELETE THE SPLASH.IMG !!!!
DOWNLOAD: http://dl.dropbox.com/u/58849669/WetAndy.windows.zip
Say THANKS and/or DONATE if you like the program!!!
NOTICE: BY USING THIS PROGRAM, YOU AGREE TO THE RIGHTS AND PRIVILAGES OF GOOGLE AND THEIR SDK TOOLS

Good
Sent from my GT-I9100 using xda premium

Very cool. Thanks
**EDIT** Works fantastic on my evo 3D. thanks again.

^^OP
This works for all phones?
My boot.img contains logo in form of rle
That is initlogo.rle
Then?
What if I want splash screen in form of initlogo.rle?

This is not your boot.img, this is the system splash which is before your kernel and such. Messing with your Boot.img is a different matter.
Works on all devices that use the splash standard set forth by Android.
This is not a boot animation. This is just an image at startup.
Requires Root, shell, and fastboot access. SGS2 users need to be running AOSP packages that use the base system standards.

What?
I have Micromax A70 and we have first boot logo inside the kernel i.e zimage and second bootlogo is from boot.img which is initlogo.rel
We dont have any splash partition to flash splash.img via fastboot
So this is not for our device?

This is unfortunately, not going to rip your boot image, replace the image and zip it all up again. Kernel code requires that you compile your own after doing the conversion.
I can make a converter and compiler for kernel code that puts your image in there with links to the source code.
They basically made those areas blank and put no beginning splash. What you are seeing with the kernel start and boot start is not a splash image. Your images are built into your running code, so not your boot splash.
Running as the zImage and uImage pieces is not true native Android code and does not really adhere to the base code standard. They basically put a micro layer between the OS and the hardcoded chip firmware. They run it as a standard OS.

Great tool, do you know if this works on the Toro Galaxy Nexus?

Just try it. There is literally no harm that can come from this program. If you have no splash ability on your devices, well can't help you there just yet.
Its just using fastboot to flash the splash image. The fancier bits are in the device recognition with display specs and file conversion.
For the SGS2 users and those whose boot images are in the kernel, I can make a image converter that automatically compiles the kernel, then pushes it and flashes the new kernel. I can also add some fuctionality for rle image conversion for some of the more odd implementations.
Tell me if you want it. I can do it. Not that hard.

How long does it take for a file to be converted? It has said file loaded for a while and seems to stay there?
Ok never mind I restarted it duh LOL and it seemed to install but the splash screen is the same, will try again

Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...

You got it Bill!
Hopefully this takes the guess work out.
Its really a GREAT way to insure your device has another layer of safety because you can make an image that has your name and personal contact information that the person who finds it can you to get a hold of you. Also, regardless of if someone manages to boot into recovery mode and completely wipe your data or flash a new image, they CAN'T wipe this. That is unless they are a very diligent thief and find this tool!

Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
billbowers said:
Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...
Click to expand...
Click to collapse

Strange.. Mine took about 10 seconds...max

You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
camblue said:
Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
Click to expand...
Click to collapse

Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Childofthehorn said:
You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
Click to expand...
Click to collapse

camblue said:
Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Click to expand...
Click to collapse
After that, you should see your img file in the folder for the program.
Close Wet Andy, restart it, check your adb connection, and Then run INSTALL.
It will install and reboot your device!

Fuhu Nabi2 Backup - Recovery - Root - Gapps on Ubuntu Linux

Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img

Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!

Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex

Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!

Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.

I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.

Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A

Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2

Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse

Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.

Glad it worked for you! I would love to see some JB action on here.

Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:

Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?

caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.

t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse

DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674

ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...

DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd

DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.

Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html

[TOOL][WIN]Gstreamer emergency toolbox, for devices with broken lcd or digitizer ;)

Hi all, i passed trough the bad experience of a phone with a broken screen, all my data was trapped inside the device and i couldn't see nothing on the screen :crying:
So i decided to develop a little app, in order to be able to break into my phone again and save the more stuff i could.
Gstreamer (aka Ghost streamer) is able to let you see your device screen once again (that was the primary purpose...) and deal with it by clicking and swiping with your mousepointer on your phone screen picture (yes, it's slow but it gets the job done )but without the need to install softwares like VNC and similars (Gstreamer only allows you to gain access your files in a way or another and try to save it),.
If your dead phone was rooted and with a custom recovery, then yur life will be easy in case of broken screen , but if not , then the music changes a lot, that's why i thought my software could help other people to solve theproblems i meet during my data rescue attempts.
No matter the device screensize, it will adapt to your device screensize and will make your life easier if you broken your phone screen.
I'm still adding features to it, and planning to organize it in a better way, correcting some bugs, testing it on different phones and android versions,but it's actually working and improving day by day
if someone is interested in testing it with me, and report then the experience i'd be happy to cooperate.
at the moment this is the pre-alpha stage for me , but this is how it looks now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you are having bad times with your phone screen this may help you :fingers-crossed: just contact me if interested
use at your own risk it's still experimental, download it from the link below
http://www.filedropper.com/gstreamerv1000release

open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build on my git, just click on the "Download ZIP" button. (link below)
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip

BrainBooster said:
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build here https://github.com/TheBrainBooster/Gstreamer just click on the "Download ZIP" button.
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
Click to expand...
Click to collapse
new changelog! V1.2.1.0 release
added dpad navigation buttons
minor bugfixes
redesigned main panel
new changelog! V1.2.2 is available for the download
added swipe buttons
added memory info
minor bugfixex
check it out and let me know testers are welcome
01/02/2016
new changelog!
minur bug fixes
added file push , pull and sideload functions
...sadly i don't have feedback so i can't be sure it will work with all the android versions

...many changes heve been done, stay tuned for the next release

Hello,
tried you app, but it does not recognize my phone, because it has not debugging mode activated. I tried even "RSA ADB key inejection and..." but with no luck. For anther device, which has debugging mode active, I was able to get its data, but for the one with broken display and no debugging mode, it doesn't.
Any hints?
Regards,

can you provide some more informations about your device?
maybe you could try to repeat the procedure but in recovery mode

Hello,
Thanks for your time. So far you're the only one who gave me something as an information, or tip/hint.
My phone is an Samsung i9300i, with stock rom, only recently when trying to get the data through ADB, I have installed via ODIN an image named "CWM Recovery v6.0.3.6.tar", but still no effect in ADB.
Before replying to you I have tried recovery mode as well (power button, home, volume - and after 5 seconds volume up- as those were the steps required for my model to get into download mode). But I cannot get your up to recognize my phone. I tried with another one (HTC One M8s), with debugging mode on and the app recognize it in a flash. But with the broken one, no luck.
Are there necessary some custom drivers? Do you think some print screens could help?

a screenshot could help for sure
installing the proper adb drivers too, try with this --> http://forum.xda-developers.com/showpost.php?p=50008343&postcount=486
also installing the official kies software by samsung may help
whas the phone rooted?
can it boot normally?
do you see something on the screen?
what is the damage on you phone?
android version?

Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
Regards,

sorry for the late post edit, but it came to my mind after i wrote
by the way... are you sure you booted into recovery mode?
my software shoud see the phone anyway when you hit the test conection button

Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,

miborion said:
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
Click to expand...
Click to collapse
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup

BrainBooster said:
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
Click to expand...
Click to collapse
Indeed I have had installed CWM (if by that you are referring to "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307)), as I thought the debugging mode would be activated, but it seem it doesn't. Please can you give me more details about what did you want to say by " moreover you said maybe you have a CWM recovery installed..."? Is it a bad thing? Should I flash to a stock rom?
And no, it does not show any devices like device-1234afsadsasdasd.
Regards,

what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other

BrainBooster said:
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
Click to expand...
Click to collapse
Ok, now I understand what is the purpose for that img.
So, bottom line is I cannot seem to install proper drivers. I'll try different combinations of uninstall plus install drivers from your link (i had used the ones from Samsung site, released this year), plus computer reboot, as so far I wasn't able to have ADB listener list my device (or your application).
Regards,

Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i

BrainBooster said:
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
Click to expand...
Click to collapse
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight

miborion said:
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
Click to expand...
Click to collapse
anytime
if you need further help , just ask

BrainBooster said:
anytime
if you need further help , just ask
Click to expand...
Click to collapse
Hello,
I've just finished all leads meaning I have successfully rooted the phone by using your link; I got PASS message in ODIN using the exact image as the tutorial indicated. But, still I cannot connect to the phone with ADB, or by using your app.
If I boot normally I can hear the sound, see the top buttons lid and have the popup message in windows which tells me I can browse the mobile phone's content (onStdBoot.jpg).
If I boot in recovery mode (can see COM0 used in ODIN and can flash successfully) I get the devices on the second print screen (BootInDownloadMode.jpg) but cannot access it.
Could you please advise if there is anything else I can try?
Regards,

if you successfully rooted your device, booting it in recovery mode should make it show in my software

NuVision TM800A510L- General Info (Root, Recovery, Unbrick)

This thread intends to be a general thread for all things about the NuVision Tablet. The aim is to help other users of this tablet to be able to root their device, get a temporary recovery and to unbrick their device. I will add the guides for the following posts below in time. This would not have been possible without help from @andrei_kr.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical Specifications:
Display: 8-inch IPS HD capacitive touchscreen
Resolution: 1280 x 800
Operating System: Android 4.4 Kit Kat
Processor: Intel® Atom Processor
Memory: 1GB DDR
Storage: 16GB
Micro SD Card Slot: Yes, expandable up to 64GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer

Backup/Root/Recovery
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
How to backup of your stock ROM, install CWM and Root your device.
Requirements
ADB/Fastboot Drivers
Intel Android USB Drivers
SDcard (8GB of higher)
Temp recovery script
SuperSU
Steps
Download and unpack IntelAndroid-FBRL-07-24-2015.7z
Power off tab.
Hold Vol+ and press Power on the tab 5-10 seconds
You can see logo about 10 sec and after that DROIDBOOT will load
Connect USB cable to PC
Run launch.bat from IntelAndroid-FBRL-07-24-2015 folder
Type ACCEPT and press Enter
Type 5 and ENTER (cwm.zip)
Type T3 and ENTER (or T4)
CWM will load after 10 sec.
Select backup to external sd card.
After the backup is complete, copy it to the PC to ensure it's safe.
Follow steps 1-10 again and go to install zip from sdcard or external and select the SuperSU zip file and flash it.
NOTE: DO NOT FLASH ANY ROMS WITH THIS RECOVERY IT IS ONLY TEMPORARY. I DID NOT TEST XPOSED SO BE CAREFUL.
Credits
@andrei_kr
@social-design-concepts
@vampirefo
@Chainfire

Unbrick your Tab!
To unbrick your device all you simply have to do is go back to the CWM and restore your backup that you created earlier. If you don't have one, here is a copy of a working backup ---> Google Drive. Credits to @andrei_kr, say thanks!

How to fix touch!
If you unbricked your tablet and your touch isn't working, there is no need to worry. @andrei_kr has provided a guide on how to fix that touchscreen. Credits to him.
NOTE: If your touch is working then do not try this, it will mess up your touch!!
You probably got this touchscreen issue by flashing a different kernel with incorrect drivers.
Now your configuration is likely to differ from the native. You can view the konifig in command prompt or in the terminal :
Code:
cat /proc/gt9xx_config
(only mtk) or using the gtp_tools apk (it is in the attached file below).
It starts with the byte sequence: 0x41 0x1C 0x02 0xC0 0x03
0x41 - 65 version
0x1C 0x02 - 540 horizontal resolution
0xC0 0x03 - 960 vertical resolution
Touch must somehow work to press the button, if there is support otg, then it's easier, you can connect a mouse.
1. Install the gtp_tools_v2.6_20140126_special.apk
2. Go to the option Firmware update. Click refresh, see IC Version: 913_1020 then touch GT913 firmware and 1020.
3. Go to the option Config Settings, press read, the data were considered. Under Normal Config we have:
65 version
540 horizontal resolution
960 vertical resolution
4. Click browse, select click browse to the native config.
5. Native configuration take from your device, in the same paragraph, press the save (saves the backup config file). Native configuration for Fly IQ446 in the attached file. Press send.
6. If nothing has changed, look at the version you have and native config. Then change the version of the file in the native config in your hex.
Example: 0x41 = 65 home, a stranger 0x49 = 73 => replace the 0x41 to 0x49.

Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk (711.77 KB)
Number of downloads:
11,141,690 in total · 8,610 in the last 24 hours
MD5 checksum:
de4f0dc569f96dbcc5668d40fa76040b
Uploaded on:
Tuesday, May 20, 2014 - 21:59
Changes:
- Fixed a crash with some apps (Disa, Rdio)
- Some minor UI improvements
- A few translation updates
Now either use an android terminal emulator or ADB and run these commands
1. su
2. echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
3. chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Now you can install the Xposed framework.

max0r4axor said:
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk .
Click to expand...
Click to collapse
Thanks for report.

First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?

Jingbadguy said:
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Click to expand...
Click to collapse
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?

kirito9 said:
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
Click to expand...
Click to collapse
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...

Jingbadguy said:
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Click to expand...
Click to collapse
Oh I thought they were working. Follow the procedure above to fix.

NuVision TM101A510L
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry

Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...

ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)

williamglick said:
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Click to expand...
Click to collapse
I think the models numbers are specific so I can't say for certain that this will work with your tab. Try the fastboot/rooting procedure first and then maybe you can just restore the system partition only not corrupting the boot/kernel.

Unidave199 said:
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
Click to expand...
Click to collapse
You're welcome. I waited months also before finding a working backup.

Jingbadguy said:
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
Click to expand...
Click to collapse
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?

kirito9 said:
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
Click to expand...
Click to collapse
ill let you know just as soon as i can get back to working on those devices... im prety sure if memory serves correctly, that I was getting some errors regarding unable to mound sd or ext sd. I could be wrong but thats what comes to mind.
Im up to my neck in jobs on other devices. (rooting galaxy S5, changing imei on another S5, IMEI change on a LG Stylo 2 plus, Galaxy Tab 2 system issues need to diagnose, and several screen and lcd replacments)

STUCK
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?

after ive flashed super su, when i go to restor the working backup i see a list of backups... including yours but when i select it i always get :
checking md5 sums...
md5 mismatch!
what now?
(i tried just flashing the boot but even that comes back with same error)
I know on other devices the recovery is an img file any the one you provide is a rar... i extracted to my desktop and was gonna try flashing with abd/fastboot but since its not an img file, im thinking it wont work...
any thoughts?
Im still unsure how to flash the recovery that u supply in the section for fixing bootloop....

Jingbadguy said:
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
Click to expand...
Click to collapse
The too many links error is common for this device. Touch doesn't work with TWRP on this device so CWM is out only go. You can root and using cwm like any other root method.