Database Info

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

[ROOT][TWRP][Unlock] Chuwi Hibook by kostyamat

Hibook-ToolBox​
For first - to write my english is bad, bad, very bad... But I understand english
I allowed myself to write a few batch files to help newcomers, as well as other users, under common title "Hibook-Toolbox".
Русскоязычная версия: http://4pda.ru/forum/index.php?s=&showtopic=741766&view=findpost&p=49156807
It allows you to:
Unlock the new tablet Bootloader.
Unprotect system partition from changing (remove "Verity Boot").
Install TWRP-recovery ver-2.8.7.0, which I have ported to this tablet.
Get the correct ROOT in the right way.
Flash custom firmware (which do not have to wait long, I think so)
And other…. I will add if still need to be.
Attention! Whatever you do, you do it at your own risk!​
Download (needrom.com): http://www.needrom.com/download/unlocktwrproot/
Preparation:
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ".
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
Usage:
1.Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the prescriptions of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes (I'm shocked, but it's true), then the device will reboot in Android pristine clean.
2.Unlock_Verity-boot.bat - Run second. It will unlocking the System partition to can be changed. Carefully follow the prescriptions of the script and on the screen of the tablet. The device will reboot. Data on external MicroSD and Windows will not suffer. After all unlock actions, be sure to enter the option for developers and turn ON the item "Factory unlock".
3.Outside_boot-TWRP-recovery.bat - (It is optional. For obtain ROOT access). The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!).
4.Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
5.Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ADB_shell.bat - Just a comfortable CMD-window for ADB-debugging and work with Android Shell.
Flash-Custom_FW.bat – My flasher to flash custom firmware, which I am sure will appear in future.
Useful console commands (ADB_shell.bat):
ADB reboot bootloader - reboot to FastbootDroidboot (flashing) mode
ADB reboot recovery - reboot to TWRP or native Recovery mode.
ADB root – restart ADB-debug service as ROOT.
ADB remount - remounting Android system partition to write (you need root-adb mode see adb root)
ADB shell - run Android-console (ash) through which you can run Linux-scripts, internal system commands, etc.
fastboot boot * *.img – run user-compiled boot.img or recovery.img
fastboot reboot – reboot to system from DroidbootFastboot (flashing) mode.
fastboot flash [boot, recovery, system, data] [boot, recovery, system, data]. img - In DroidbootFastboot mode, It will flash specific image to specific partition, example: fastboot flash system c:\Custom_FW\system.img - will flash only system.img to Android system partition.
PS. Under any circumstances, when using TWRP, never do not wipe system partition! Also make sure the TWRP-settings option "Use rm-R instead of formatting" is ON and never leave it. The fact of the matter is that "Verity Boot" marked System partition itself. Withing format the label disappears - the tablet won't boot to Android! This problem can be solved, but why You would make a problem?
If You like may work, buy me a coffee. Please :|

Hibook-Toolbox was updated 06/04/2016

Nice work, it is really great to see the android side of the hibook 10 has root. this is an excellent tablet and I am ordering it as of now.
I hope you and others will continue working with this tablet, as android n would be great on here.
Thanks. :good:

Hi ! Can you share what tools you use for modding TWRP for HiBook and what files you have changed ? I need to do the same for Chuwi Hi10 DualOS, based on the same hardware, i want to port your TWRP on it..

I have installed root too whit this tutorial. It works perfect. If someone is interested in modding whit kernel or custom Rom i have accsess to all partitions from ubuntu on the tablet. Please ask me if you interested in somthink. The stock Rom and kernel are not the best.
Sent from my Samsung Galaxy S III using XDA Labs

kostyamat said:
Hibook-Toolbox was updated 06/04/2016
Click to expand...
Click to collapse
It works also on Chuwi Hibook pro??

Hi,
I´ve got my brandnew CHUWI HiBook Pro 2 in 1 Ultrabook Tablet PC (10") today. Could you pls confirm that your toolbox is suitable for this tablet as well?
I won´t brick it on the very first day using wrong software ...
many thanks in advance
cheers Andreas

I think its OK. It works perfekt for me. But if you not sure for yourself than dont do it. Thats all we can say. If you dont try it you dont See if it works or not. Its your choice. And dont get panic if the first vor second try dont work. I dont know how many trys i used and some times i was realy scared about my chuwi. But than i realized that i made something wrong vor forget somthing. After all the work and the shocks my chuwi worked perfect. But if you dont try it you dont know if it works.
Sent from my Samsung Galaxy S III using XDA Labs

Hi, it shows the links are broken, can you please update new links
thanks

I confirm successful rooting for chuwi hibook pro, too.
I want to ask... Do we update supersu from Play store??

Hi man
I will proceed later today to do this.
2 questions...
1) how did you compile the TWRP for our needs? or is it a general one?
2) regarding custom fw, is there cyanogen/remixos 3/anything else based on android 7 available??
Thanks
regards
Luca

Confirm, root sucess for chuwi hibook pro.
Thank you

Root works fine, thank you
I had to install SuperSU.zip from the SuperSU Website.
Reason: Binaries couldn't be updatet.
One problem with TWRP left.
Touch input isn't working well.
Seemes that the touch mask is shifted.
I have to connect a mouse via OTG
[EDIT]
I found another posting with newer TWRP Version (3.0.2.0).
Problem Solved.
modaco.com/forums/topic/377883-recovery-twrp-302-0-for-chuwi-vi10-plus-hi10-plus-hi10-pro-hibook-pro/

Hello,
After launching the first .bat file my tablet does not automatically restart. It restarts when I click the power button, and start when the tablet starts normally without data loss as specify
I attached pictures of my tablet after restarts automatically after launching the .bat file
What to do ? I am stuck.
{
"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"
}

It`s ok, I didn`t have reboot neither, nor data loss.

Hey guys, new Chuwi Hi10 Pro owner here. I just want to make sure this will work with the build number for my tablet. It's currently running 5.1.1-B2016081102, Remix OS version 2.0. I'm pretty familiar with rooting Android devices, but I still like to make sure I'm following the proper steps before attempting anything. Thanks in advance.

Nippylicious said:
Root works fine, thank you
I had to install SuperSU.zip from the SuperSU Website.
Reason: Binaries couldn't be updatet.
One problem with TWRP left.
Touch input isn't working well.
Seemes that the touch mask is shifted.
I have to connect a mouse via OTG
[EDIT]
I found another posting with newer TWRP Version (3.0.2.0).
Problem Solved.
modaco.com/forums/topic/377883-recovery-twrp-302-0-for-chuwi-vi10-plus-hi10-plus-hi10-pro-hibook-pro/
Click to expand...
Click to collapse
you have hibook or hibook pro? because modaco only have twrp for hibook pro.. is it compatible for hibook also?

eltdesign said:
you have hibook or hibook pro? because modaco only have twrp for hibook pro.. is it compatible for hibook also?
Click to expand...
Click to collapse
I have the HiBook Pro

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.

Alcatel 1 Root Achieved

Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"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"
}

Thanks dude, that worked perfectly.
Any idea how to get GAPPs working?

What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.

I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...

Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.

ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu

Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.

ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed

With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.

I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?

hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.

Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!

FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?

Sometimes the phone gets stuck on boot, any clues?

No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo

I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!

Solution
@caish5
 @FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.

Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse

I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.

Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?

[ROM][TWRP][ROOT] Vizio Smartcast Tablets

TWRP
XR6M10
Here
XR6P10
Here
Stock firmware
XR6M10 Version 03.99.01.04 - Marshmallow - Latest
Here
XR6P10 Version 03.02.00.04 - Marshmallow- Latest
Here
How to flash twrp and or stock firmware
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8936.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl"
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
Root
Once you flash twrp you can install magisk via the flashable zip
Some info on what i have found about the device
There is really no security on this tablet. The bootloader will always report as bootloader locked, green dm-verity and secure boot being enabled this is because the LK doesn't seem to have ever been completed on it. Because of this everything it reports is static and the fastboot implementation is broken and doesn't work. This means we will need to EDL to flash the device which I provided instructions above on how to do.
Notes
Some XR6P10 may require more work because there is multiple variants of it made by vizio but what i have uploaded works on mine.

Screenshots:
Root:
{
"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"
}
Magisk:
TWRP:

Is it just me not able to boot into EDL through ADB? I have a EDL cable arriving later this month I could use but I figure the device should have it. reboot edl through adb just reboots the device normally which is unfortunate.
XR6P10

Hey. And where to get the driver. And then I have two devices without an Android driver and an ADB Interface hanging in my device manager?

I cannot get anything to work on my XR6P10 either. Every time I try to "download" with the QFIL application it just fails.

@deadman96385
In regards to EDL mode am I missing something obvious. I tried EDL cable that has shorted pins which seems to not work "maybe a bad cable?" and ADB reboot edl seems to not work. I've tried ADB on two different tablets to boot into EDL mode but have yet to see the device pop up in device manager.
*I believe after Dec 2017 security patch ADB reboot EDL was removed, ill check the version on the devices since it should be fairly close to this year.

I'm having the exact same issue. adb reboot edl simply reboots the tablet. It does not enter it into EDL mode. I'm assuming you don't need an EDL cable to do this since we're doing this through the ADB interface. Or did I get that part wrong?
edit: I was able to enter EDL mode on the device itself using the following directions I found from another thread
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
edit 2 I'm coming across two errors when downloading the ROM. The first is a Sahara Error which is due from not running QFIL immediately after entering EDL mode. Apparently the full connection does not remain open for that long. The second issue that I'm still dealing with is a Firehose error. I've googled this one and nothing seems to work to get around this.

Any update on this? Can't seem to get my XR6M10 rooted following these directions. Running into the same Firehose error as stefanpolo. Thanks!

stefanopolo said:
I'm having the exact same issue. adb reboot edl simply reboots the tablet. It does not enter it into EDL mode. I'm assuming you don't need an EDL cable to do this since we're doing this through the ADB interface. Or did I get that part wrong?
edit: I was able to enter EDL mode on the device itself using the following directions I found from another thread
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
edit 2 I'm coming across two errors when downloading the ROM. The first is a Sahara Error which is due from not running QFIL immediately after entering EDL mode. Apparently the full connection does not remain open for that long. The second issue that I'm still dealing with is a Firehose error. I've googled this one and nothing seems to work to get around this.
Click to expand...
Click to collapse
Its flashed through EDL not ADB and thanks for the tips ill give it a shot. To my knowldege that button combo is just for hard resets on most devices. As of 2017 I believe the security patch removed adb reboot edl as preventive measures to some exploits. I believe that was the last security patch for the device and its dated Jan 1st 2017 for my security patch date. Although I believe it was late 2017 when this was released. Ill give some feed back if I can flash the patched boot file later.
The cable is also just for shorting pins on the USB port which is also a way to trigger EDL most on some devices. I have the cable and it does not work either.
---------- Post added at 03:40 AM ---------- Previous post was at 03:27 AM ----------
Post your log output from QFIL you can hit save log if you right click the Status area.
---------- Post added at 03:45 AM ---------- Previous post was at 03:40 AM ----------
Ah nvm I see what you mean that it just times out on you. I tried flashing TWRP and it just hangs at start download after specifying the working folder

removed

removed

So after restoring to 5.1.1 and fiddling around with QFIL and constructing things from scratch myself the solution is as follows and most likely applies to any variant of these devices. 6.0.1 Is on the device and with TWRP/Root. Next up is a lineage port to the device as 6.0.1 sucks not having OK google working while the device screen is off whereas 5.1.1 did. 6.0.1 and up is the bare minimum for certain apps to install and other various functionality.
1. Hold the volume buttons and PWR buttons until the device vibrates. The screen will be powered on but black instead of off which is in EDL mode. adb reboot edl does not work. I'm not exactly sure how the OP managed to use that unless he had an older build with the functionality or perhaps ADB removed the ability to pass the argument in newer builds past X date and I currently use the latest. Either way this is the only method to get EDL mode without opening the device to my knowledge as EDL cables even did not work for myself.
2. You need to flash within roughly 10 seconds of entering EDL mode. The window is small and you will see a 3 second timer in QFIL if you got it right. If not just reset the device again with step 1. You can have the device plugged in prior to entering EDL mode and QFIL pointing to the proper directory in advance to make things easy.
3. You need to modify the rawprogrammer0.xml that is provided as its making references to files that do not exist. File types that do not exist such as sparse images of which system.img is not a sparse file. I made the mistake here initially by commenting out lines instead of just removing the referenced file which soft bricked the device. I've uploaded the modified file which should work fine for any device and also retain user files. The original worked for the OP due to its his cached files/content/userdata but it will soft brick the device until the cache/data is cleared. I had to do this with TWRP in order to get the device to boot.
Using the provided xml file should be fine for anyone. Try to take a backup of the device in the rare event you play around with things and overwrite your MAC address with another. Its not a huge deal if you do but there is a super slim chance that it would cause problems if another device was on the same network with the same MAC. In short ensure you do not overwrite the persist partition if you do experiment with the firmware.
If anyone else has issues feel free to post here and I can address any questions despite there is probably not much interest in these devices as they were discontinued and I do not even think the new 2020 models are bringing back tablets from vizio. These things make great PDF/screen readers along with being a house hold tablet to control various devices.

I'd be really interested in that Lineage port if it wouldn't take a lot of work. I think these little tablets are a great buy for the price and they look great on the dock. I've already picked up 2 of them.
EDIT: And officially soft bricked one of them... Stuck in a boot loop after attempting to flash TWRP. It fails because it can not find NON-HLOS.bin when flashing TWRP. Obviously the file is not in the directory but I don't understand why it won't skip the file.
EDIT 2: I managed to get it out of the boot loop with a factory reset, but I still can't get the original firmware or TWRP installed on my XR6P10. It always fails because there isn't a file in the folder to flash.

So any Lineage port yet, did anyone verify the original firmware was built from CyanogenMod if so there is a good chance of lineage working. Does this OEM (not Vizio) have other tabs that have been rooted and ported? My P tabs work great as Logitech harmony hub controllers with the harmony app and as small tablets. We will need to get this working soon as developers and the play store end support for Android 6.xx.

Solace50 said:
So after restoring to 5.1.1 and fiddling around with QFIL and constructing things from scratch myself the solution is as follows and most likely applies to any variant of these devices. 6.0.1 Is on the device and with TWRP/Root. Next up is a lineage port to the device as 6.0.1 sucks not having OK google working while the device screen is off whereas 5.1.1 did. 6.0.1 and up is the bare minimum for certain apps to install and other various functionality.
1. Hold the volume buttons and PWR buttons until the device vibrates. The screen will be powered on but black instead of off which is in EDL mode. adb reboot edl does not work. I'm not exactly sure how the OP managed to use that unless he had an older build with the functionality or perhaps ADB removed the ability to pass the argument in newer builds past X date and I currently use the latest. Either way this is the only method to get EDL mode without opening the device to my knowledge as EDL cables even did not work for myself.
2. You need to flash within roughly 10 seconds of entering EDL mode. The window is small and you will see a 3 second timer in QFIL if you got it right. If not just reset the device again with step 1. You can have the device plugged in prior to entering EDL mode and QFIL pointing to the proper directory in advance to make things easy.
3. You need to modify the rawprogrammer0.xml that is provided as its making references to files that do not exist. File types that do not exist such as sparse images of which system.img is not a sparse file. I made the mistake here initially by commenting out lines instead of just removing the referenced file which soft bricked the device. I've uploaded the modified file which should work fine for any device and also retain user files. The original worked for the OP due to its his cached files/content/userdata but it will soft brick the device until the cache/data is cleared. I had to do this with TWRP in order to get the device to boot.
Using the provided xml file should be fine for anyone. Try to take a backup of the device in the rare event you play around with things and overwrite your MAC address with another. Its not a huge deal if you do but there is a super slim chance that it would cause problems if another device was on the same network with the same MAC. In short ensure you do not overwrite the persist partition if you do experiment with the firmware.
If anyone else has issues feel free to post here and I can address any questions despite there is probably not much interest in these devices as they were discontinued and I do not even think the new 2020 models are bringing back tablets from vizio. These things make great PDF/screen readers along with being a house hold tablet to control various devices.
Click to expand...
Click to collapse
Thanks for the write up. Just purchased one for a home automation setup. I am running into so odd issues. I have tried multiple versions of QFIL and finally got a better error with 2.0.0.2. I am having a few errors, downloaded another copy of the firmware and unblocked the files. also grabbed the xml file you uploaded but same issues. Any help would be great as some apps require marshmallow and edl flashing is new to me. Would a full factory reset help from the recovery menu?
FireHose Log: Host's payload to target size is too large
Fail to open image file: C:\test\sec.dat
Error reading the C:\test\rawprogram0.xml
Download Fail:FireHose Fail FireHose Fail:Failed to Upload the emmc images to the phone using Firehose.

Is hope for further updates on this project done?

I found the xml was not right, in addition the max send size needs to be backed down to 4096 in firehose config. I am uploading the files I had working successfully to get TWRP lit up. Hmm doesnt let me post cause I am too new. guess I will code paste the xml I used.
I dont know how far I am going to dive into a device like this, but its nice to be able to do *something* with it now.
this is my contents of rawprogram0.xml
Code:
<?xml version="1.0" ?>
<data>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="recovery.img" label="recovery" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="false" start_byte_hex="0xe38c000" start_sector="466016"/>
</data>

Has anyone managed to get any further with this, i've been using mine as a trusty Sonos controller but been Android 6 it is no longer unsupported.
If not, does anyone know of any other similar device, eg thin, light, no camera, wireless charging with stand?

Yeah. Unfortunately I'm not moving to S2 yet as these are my primary hardware sonos controllers. It's really sad that such a perfect little tablet for this duty is being left by the wayside because there isn't enough of a following for them.

Yeah, wish i'd not upgraded to S2, you're not missing much!