yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
Here are links to forums related to the original Ares 8 with the baytrail processor and Android 5 and 5+:

https://xdaforums.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165

https://xdaforums.com/android/development/nextbook-ares-8-stock-5-1-rom-modified-t3496110

https://xdaforums.com/android/development/nextbook-ares-8-stock-5-1-1-problems-t3576224

https://xdaforums.com/android/development/ares-8-5-0-upgrade-to-ares-8-5-1-t3581153

TWRP 3.1 for the Ares 8, not the 8A:

https://androidfilehost.com/?fid=817550096634761287

Here is a link also to another rom vampirefo ported to the Ares 8 but while it worked on my device for some time, it is not nearly as good as the newer 5.1 roms he ported later to it. Personally, if my Ares 8 still worked, I would never use this again as the the newer ones, which came from the newer Ares 8's that came from the factory with 5.1.1, are so much better in almost every way:

https://xdaforums.com/android/development/ares8-5-1-rom-i708q-t3320040/post65450751#post65450751

Repartitioning for the i701Q and Batville ROMs only:

https://xdaforums.com/android/development/partition-ares-8-tablet-linux-windows-t3327595

As far as your bricked device that you attempted to put Window on, I have no clue how to fix that. I have never had any compelling reason to even attempt to do that, as all of my Ares 8A's run great with Android 6.01, rooted with Magisk unofficial and tuned with apps such as Kernel Aduitor and lspeed.
[Miscellaneous Android Development] codyw1996:
It's an Ares 8A. The error was probably an issue with my Fastboot binary. I'm using the newest version of Minimal ADB and Fastboot on Windows.
[Miscellaneous Android Development] martyfender:
I have the previous version of Minimal ADB and Fastboot on my Windows partition and never had any problems with it, although I never used the fastboot format command in it, if I recall correctly. I now use Linux Mint most of the time. It has been a couple of months, or more, since I have even booted into Windows.

From my OP the most recent adb and fastboot I have used in Windows:

Here are the steps to install adb and Intel drivers, in the proper order:

The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:

https://xdaforums.com/showthread.php?t=2588979

Install process for 15 sec adb:

1. Run it (Require administrator privileges)

2. Press Y/Yes to install ADB and Fastboot

3. Press Y/Yes to install ADB system-wide

4. Press N/No to skip installing Drivers

5. 15 seconds passed - finished!

6. Now install the Intel drivers listed above and here, again:

https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices

I'm not sure if that version of adb/fastboot will be any different though. I believe they both use Googles adb and fastboot binaries.

If you just type fastboot and hit enter in the command prompt, it will list the available commands. This is, of course, when the tablet is booted into bootloader/fastboot mode.

Mine, for example on Linux Mint for fastboot, erase and also format:

erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
[Miscellaneous Android Development] Steve60901:
Ok originally I had come in here because of boot loop caused after removal of specific apps. This has been an issue even before I managed to get it rooted, I still wouldn't mind a streamlined fast alternate rom for my nxa10 but figured out the boot loop issue. Just go back into twrp and factory reset... it wont replace the apps you removed... kind of a weird roundabout way to debloat but hey if it works haha.
[Miscellaneous Android Development] martyfender:
[MENTION=4753701]Steve60901[/MENTION] It sounds like you may have removed some system critical apps to get a bootloop. What did you remove? Is that a Nextbook 10A? If so, where did you get TWRP for it? If you have a TWRP backup you could restore that maybe? I am always very careful what I remove such as play books, play movies and tv, play music, Nook, Hangouts and vudu. Those are apps I never use and as far as I know, are not system critical. The only thing I have noticed from doing the above that in logcats I sometimes see messages about them. Some gapps are critical to proper system function.
[Miscellaneous Android Development] TheMadScientist:
So i got a gen 2 11a i guess

Followedthe guides i saw and it kept leading me here for twrp

I did the fastboot boot twrp and junk then when i went to exit it had install as system app and junk up

Now all i got is efi fast boot and such but system will not boot

I saw some one mention using this devices backup to restore mine
[Miscellaneous Android Development] martyfender:
I have never owned an 11A so I am not sure of any of that.
[Miscellaneous Android Development] martyfender:
I just found another Ares 8A with Intel and Android 6.0.1, so there are still some left in Walmarts. V2.0.3.MMb29M.20170621.014754. I have rooted it with the latest Magisk Unofficial build V16.8-unofficial by [MENTION=3306843]kantjer[/MENTION] and it is working great.

EDIT This appears to be an older version of the rom than the one on my newest tablet: V3.0.4, but it has the same IFWI version of M882_JJ.023_JJ and a much newer manufacturing date of February, 2018.

So far, it appears to be the best version of the tablet so far in terms of speed and the battery life is much better. I hope the external SD card reader continues to work, unlike 3 of my 4 other tablets.

Using Apps2sd's SD card Booster test app to test the external SD card speeds it also appears to be much faster.
[Miscellaneous Android Development] martyfender:
Magisk 17.1 unofficial is working great on all of my devices so far. The stable release should work good also, as far as I can tell. this is a major update to Magisk and fixes many outstanding bugs since the 16 release. I strongly recommend that you upgrade.
[Miscellaneous Android Development] IvanKholodnyak:
I purchased the Ares 8A, with Marshmallow 6.0.1. This tablet has an Intel Atom x5-Z8350, 1.92 ghz, Cherry Trail processor in it. After flashing the boot.img, the sound of the tablet disappeared. Can you have the original boot.img to this tablet, or TWRP backup device?

I will be very grateful.
[Miscellaneous Android Development] martyfender:
[MENTION=9428200]IvanKholodnyak[/MENTION] All of the updated info in the OP recommends not using my patched boot images. The new recommendation there was to let either the official SuperSU systemless or Magisk patch the boot.img.

Only if you pair the same version of the boot.img with the same version of the rom will you have sound. In Android settings, about tablet you will see a build number and an IFWI version. for example:

build number:

V2.0.3.MM29M.20170621.014754

IFWI version:

M882_JJ.023_JJ

Without the build number I have no way of knowing which tablet you have. The TWRP custom recovery is linked in the OP. There are at least 6 or 7 different builds of this device maybe more. I have 5 of those builds and one more version on Android file host. The build listed above was purchased last week and I have not uploaded its rom yet.

Why did you do this without doing the recommended backup in TWRP, again recommended in the info in the OP? It almost appears that you did not read the info in the OP, especially the most important updated information.

I can't remember if flashing the wrong boot.img will show the build number for it or if it will still show your original build number. The IFWI number will, for certain, be the same.

EDIT: I just temp booted a different boot.img on one of my tablets and your original build number will still show.

Please provide both the build number and IFWI version to see if I have a boot.img for your build.
[Miscellaneous Android Development] IvanKholodnyak:
Thank you very much for the information. I do not have a backup. I do not know the assembly numbers either.

I only know Model number: NX16A8116K.

serial number of the device YFGV0617004995, cpu z8350 and color - blue.

How do I know the build number by these parameters?

At me now works on 882_JJ.021_JJ and v1.2.0.mmb29m.20170216.211208
[Miscellaneous Android Development] martyfender:
You have the v1.2.0 tablet. Here is the link to the twrp backup. The boot.img is ther and is named boot.emmc.win. The boot.emmc.win.md5 is only a checksum verification. You can flash it in twrp followed by Supersu official or magisk official 7.1 to patch the boot to disable encryption and dm_verity. I recommend reading especially, my updated instructions in the op, (opening page) thoroughly.

https://androidfilehost.com/?w=files&flid=197764
[Miscellaneous Android Development] martyfender:
In Android settings, about tablet you will see a build number and an IFWI version. for example:

build number:

V2.0.3.MM29M.20170621.014754

IFWI version:

M882_JJ.023_JJ

So to confirm, is this your build number: v1.2.0.mmb29m.20170216.211208?

I just got home from work and my v1.2.0 tablet has the same build number, but a different IFWI number of: M882_JJ.119, so it is very slightly, older and should work with no problems, as far as I can tell.

And to make it simpler, here is also a copy of my stock boot.img.

The latest SuperSU:

https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

The just released stable build of Magisk 17.1:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

The latest UnSu to remove system mode or systemless SuperSu before flashing either SuperSu or especially for Removal before flashing Magisk:

https://xdaforums.com/showpost.php?p=63615067

Flash in this order while booted to TWRP and do not reboot between:

Flash UnSu.zip

Flash the unzipped boot.img in TWRP: hit the install button, then the image button at the bottom and select the boot.img which must be in either internal or external SD.

Flash either SuperSu.zip

OR Magisk.zip

I highly recommend the latest, just released, Magisk V17.1. I have it on all 5 of my tablets and it is working great and allows the tablet to pass Safety Net. In addition there are many addon modules to increase the functionality of this tablet. There is a systemless busybox module, a greenify4magisk module, syconfig patcher module to allow playservices to be dozed in battery optimization to save battery and many others. Kernel Aduitor, L Speed, Adaway are just a few of the root apps that I use to increase performance and usability of this tablet.

If your tablet is already unencrypted from the previous root, you can just reboot.

If not, you must factory reset to delete the data partition and create a new, unencrypted one. You will in this case loose all of your data and have to set it up as new. I sounds like that the tablet is already not encrypted if you flashed one of my modified boot.img's so a reboot should be sufficient.

Furthermore, if it is not clear, do not flash this boot.img, without patching it with either Magisk or SuperSu, or you will get a verity error and it will not boot properly. flashing systemless Magisk or SuperSu will patch it to remove encryption and dm_verity. After flashing it and one of the above root solutions, you should see a message in TWRP that it has successfully patched your boot.img.
[Miscellaneous Android Development] IvanKholodnyak:
Thanks for the help.

I already tried to restore from the archive 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208.zip, but the sound does not work, everything else works. I guess I have some other version of the device.

---------- Post added at 09:41 AM ---------- Previous post was at 09:28 AM ----------

I would also like to experiment with backup version V2.0.3.MMB29M.201710621.014759.

Where can I download a backup?
[Miscellaneous Android Development] martyfender:
From my experience, flashing a v2 rom on a v1 tablet works, but you will have no sound from the external speaker. Bluetooth sound does work, however.

The v1.2.0 rom should be the one for your tablet. You are not the only one who has reported no sound with it though. I'm not sure why. I had it happen and reflashing it solved it for me. I believe you must factory reset though with it.

Since I just got that tablet, I have not yet uploaded the rom from it to Android File host.

UPDATE: I am uploading the v2.0.3 archive now and will post a link later, when I confirm it uploaded ok. It is very slow uploading, on this free hosting service.

Unfortunately, the upload failed and it is time to leave for work. I will try again later.

I'm home and I am attempting to upload again.

V2.0.3 archive is now uploaded, at this link. If you flash this to your device be sure to uncheck recovery in TWRP, or it will overwrite TWRP with the stock recovery.

In addition, be sure to flash either Magisk.zip or SuperSu official SR5 systemless, in TWRP before rebooting.

https://www.androidfilehost.com/?fid=1322778262903997985
[Miscellaneous Android Development] martyfender:
@ IvanKholodnyak I just had a thought, upon reviewing the info you posted. Did you report the build number you have

after

you flashed my V1.2.0 ROM?

The reason I ask is because your IFWI number is the same for one of my tablets that has V2.1.5 and would explain why you lost sound with the V1.2.0.

If so, I do have a V2.1.5 backup ROM posted on my Android File Hosts site.

https://www.androidfilehost.com/?fid=673791459329065002

If you solve this, please report back to me if this is true or not. It may help me the next time I am trying to help someone else.

Thanks
[Miscellaneous Android Development] mad_10:
my nextbook only goes into recovery mode will there be any rom to be able to relive it?

Ares 8A
[Miscellaneous Android Development] martyfender:
From complete power off, you should be able also to boot into bootloader/fastboot mode by first holding the volume down, then hit the power button until it boots to bootloader mode. If you give me the IFWI number listed there it will give me a possible, but not certain clue about what version of the tablet you have. Also, if you still have the box it came in there will be a manufacturing date on it.

All of my TWRP backup roms should work on it but only one in the same series as yours, such as v1, v2 or v3 will have sound from the external speakers. Most of the time in my experience, bluetooth sound will work if the wrong version is flashed to your tablet.

By recovery mode do you mean the stock recovery or have you previously flashed TWRP custom recovery to it. You need TWRP temp booted or permanently installed on it to restore my backups. Links for my backups and TWRP are listed in the OP. It must, in your case be placed on an external Micro SD card in the proper folder hierarchy for it to be seen in TWRP.

Several times throughout this thread I have listed this hierarchy:

/TWRP/BACKUPS/NX16A8116K/2018-08-28--22-57-57_V2.0.3.MMB29M.20170621.014754/

Above is an example of a backup I did on my newest tablet. The last folder in the hierarchy is the date of backup and the rom build number.

Finally, if you can post the IFWI number, I can recommend a version that may work with sound.

EDIT:

Before you do all of this though, have you tried to boot into TWRP and do a factory reset in it?
[Miscellaneous Android Development] martyfender:
[MENTION=8335755]mad_10[/MENTION] I was wondering if you solved your problem with my instructions? I have not heard back from you. I hope that is a good sign?
[Miscellaneous Android Development] mad_10:
Yeah i solved my problem

Thanks Bro
[Miscellaneous Android Development] thejunkie:
im stuck in a bootloop, for couple months, i just found this tablet and i would like to recover it. i dont have any backups or anything on it, like at all. just a bootloop, and some options when i hold power and vol down. the model is nx16a8116k pb from walmart. its an intel one.. Can someone provide me with a image for it, and steps on how to do this please. thank you
[Miscellaneous Android Development] martyfender:
Do you remember what version of the tablet you have? v1, v2, v3, etc? you must flash the same series to get sound and possibly wifi. Once you determine that you can flash the TWRP backup rom for it I have posted on AFH. You can temp boot TWRP assuming you can boot the tablet in to bootloader/fastboot mode and it connect properly to your PC that has the correct drivers installed on it. There are updated instructions in the OP and throughout the thread for you to be able to do this.

Do you know what you did to the tablet that caused the bootloop?

Sometimes just temp booting into TWRP and choosing factory reset in the options may solve the problem without reflashing a whole rom.
[Miscellaneous Android Development] martyfender:
Do you remember what version of the tablet you have? v1, v2, v3, etc? you must flash the same series to get sound and possibly wifi. Once you determine that you can flash the TWRP backup rom for it I have posted on AFH. You can temp boot TWRP assuming you can boot the tablet in to bootloader/fastboot mode and it connect properly to your PC that has the correct drivers installed on it. There are updated instructions in the OP and throughout the thread for you to be able to do this.

Do you know what you did to the tablet that caused the bootloop?

Sometimes just temp booting into TWRP and choosing factory reset in the options may solve the problem without reflashing a whole rom.

EDIT: I just searched the thread and you apparently have the V2.1.1 tablet and the link you provided for your Google Drive account still has your original tablet backup on it, so you should use that as I have never posted the rom backup on AFH for it, just the modified boot.img, SuperSu and TWRP.

Your gdrive link:

https://drive.google.com/drive/folders/0ByKzF9zbs6seemg0WG11UGNYaXc

For months now I have been using the original, stock boot.imgs an rooting with Magisk. When flashing Magisk, it patches the boot.img so there is no longer a need to use my modified boot.imgs to remove encryption and dm_verity.

On 4 out of 5 of my devices, my external SD card reader has failed. I hope yours has not because that is where you need to place the backup to flash it, since you don't have it copied to the internal sd. Because of this failure I keep stock, new backup on the internal of each tablet.

Each tablet still works great except for the ext. SD card failure.

Magisk is so much better on these tablets than SuperSU ever was.

With Magisk the devices pass safetynet and has many useful module to install, all, systemlessly.
[Miscellaneous Android Development] N1ghtS7alker:
Hello all, my nephew has an Ares 8 and it is stuck on the boot screen showing "Nextbook" or if I try to reboot it will say " Your device has failed verification and may not work properly". I have tried wiping the cache and also doing the factory reset but it has not fixed anything. I downloaded ADB but because I cannot get into the device to enable developer tools it does not find the device. If I select to load from ADB in the recovery menu I get the following but I cannot do any of the recovery commands:

C:\adb>adb devices

List of devices attached

0123456789ABCDEF sideload

C:\adb>adb reboot bootloader

error: closed

The data I can get from the Boot menu:

Product Name - NXM882CAP

Variant - N/A

HW_Version - Type 1 - TBD by OEM

Bootloader Version - kernelflinger-02.20

IFWI Version - M882_jj.019

Secure Boot - DISABLED

Lock State - unlocked

From the Recovery Menu:

Android Recovery

Intel/NXM882CAP/NXM882CAP

6.0.1/MMB29M.20170313.231247

Any help is appreciated so I can try and get this working again for him. I am pretty computer literate just I do not know where to get the files I need and the steps to flash since I cannot enable the developer debug for USB.

Thanks in advance :)
[Miscellaneous Android Development] martyfender:
You really mean Ares 8A, don't you? You appear to have v1.2.0, (or close, as your build date is about a month newer than my v1.2.0) of the Ares 8A tablet, based on the info you provided. It is failing verification because the bootloader is unlocked or the system has been modified.

Can you boot the tablet into fastboot/ bootloader mode? From power off on the tablet, hold the volume down then the power button to get there. While connected to your computer in that mode, issue fastboot devices, enter in the command prompt and you should see the device serial number listed if it is connected in fastboot mode. It must be connected for the below to work.

With my Ares 8A 1.1.1and1.2.0.zip unzipped in your computers adb folder, you should be able to flash the v1.2.0 boot.img, which has verity and encryption disabled, then hopefully you can boot normally then.

There may be a lot of other things you may have to do though to get this to work. If it boots successfully after this, I recommend flashing the TWRP recovery, putting the SuperSu.zip on the tablet, then flashing that while booted into TWRP to gain root access.

Since your bootloader is unlocked, I can only guess that SuperSU may have been already flashed to the device? Or it was unlocked and the boot.img that disables verity and encryption has not yet been flashed to the tablet. That could also explain your verification error.

The OP has detailed instructions and different and more advanced things I now recommend doing, but hopefully this will get you back in business.

https://www.androidfilehost.com/?fid=745425885120754824

Also, here is a link to my TWRP flashable backup rom for the v1.2.0 tablet:

https://www.androidfilehost.com/?w=files&flid=197764

Use only the rom versions listed for your tablet or you may loose sound and or wifi.

For all of the above to work you must, of course have the proper Intel drivers on your computer and adb and fastboot installed and to be able to connect to the tablet.

One thing I forgot, if your tablet successfully boots after the above, be sure to go in an enable developer options and in it enable USB debugging. then watch for the Android security prompt to allow it, first time. Check the always remember box, also.

Also, since it appears you factory reset, deleting userdata, the first boot can take a very long time, Sometime up to 5-7 minutes, in some cases. You will see the Nextbook boot animation for some time and it will appear that it is in a bootloop, just be patient, it will usually boot to the Android setup screen eventually. It takes some time to rebuild the unencrypted userdata partition.

In addition do not attempt to flash files for the original Ares 8 with Android 5+ on it or xposed as this may brick your tablet, they are not compatible with this newer device.

Please let me know how it goes or if you have any other questions.
[Miscellaneous Android Development] N1ghtS7alker:
Thank you so much I really appreciate the time you took to help me. Your steps and files worked like a charm and the tablet is now up and running again. He swears he did not try to modify it but he is a tinker so he may have. I am just glad I was able to get it working. You are amazing thanks so much!!!!
[Miscellaneous Android Development] martyfender:
[MENTION=9555441]N1ghtS7alker[/MENTION] I am very glad to hear that.
[Miscellaneous Android Development] Yami94:
Is there a wifi fix??

ok so i have a problem i been trying to fix for my nextbook ares 8A. the problem is i have a model NX16A8116K version 6.0.1 that i had rooted using your software to root it everything went fine until i went to turn on the wifi. the wifi doesnt turn on or it stays stuck on and it doesnt respond i tried everything and i cant seem to fix ways to fix it. i came to you because i thot maybe you knew how to fix this situation that other people are also having. PLEASE TELL ME YOU HAVE A SOLUTION TO THIS I BEEN HAVING THIS PROBLEM SINCE 2017 DECEMBER WHICH IS WHEN I GOT IT:crying::crying::crying: