yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] I got my tablet as a bday gift and it was one that didn't need any verification, I just went through the setup wizard like normal, so do I have v1.1.1?
[Miscellaneous Android Development] martyfender:
Yes, based on the two tablets I have looked at.

Download aida64 from the playstore. Launch it and go to the android tab and look at the Build ID to see if you have V1.1.1 or V1.2.0. If you have a different version, let me know. I am only aware of the two build IDs.

You can also view the build ID in settings, about tablet. It is the very last entry. Sorry, I forgot about that. However, aida64 is valuable to view much more info about the tablet.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Ok I have V1.1.1, can I get a tutorial on how to do this? Are you going to type the tutorial down in here or are you going to upload a tutorial as a youtube video?
[Miscellaneous Android Development] martyfender:
Did you try opening the adb folder then hold the shift key, right click on an empty spot in that same folder, then a drop down contextual menu should appear and choose open a command prompt here:

The command prompt should then open.

type:

fastboot devices

Hit enter on your keyboard to comfirm fastboot is working

Your device should then be listed.

once confirmed, issue:

fastboot boot Ares8A_recovery_twrp.img

Hit enter on your keyboard to boot into temp TWRP.

That is a broken link, The first one in the OP is correct, it is the root link where all of my files are stored

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

I found that old post and changed the link in it also.

"I issued the command, the adb response was to tell me " can not load 'recovery': No such file or directory"

That should be a fastboot command response, not an adb one.

You use adb commands when the tablet is booted normally.

Type adb only for a list of commands

You use fastboot commands when the tablet is booted into bootloader mode.

Type fastboot only for a list of fastboot commands.

If the above does not work then something is wrong. You never did tell me how you got adb and fastboot installed, if the installer didn't work. Does your adb folder have all of the files I mentioned earlier.

Minimal ADB is another one I have used in Windows in the past. Also the Android SDK Tools has it, but I have never installed it that way.

Just as a test, I downloaded adb-setup-1.4.3.exe, renamed it to adb-setup-1.4.3.zip and was able to extract the files that way. Of course that was only a test a I won't use those 4 files in Linux. You can do the same in Windows and you only need those 4 I mentioned previously in the C:\adb folder.

Is this file in your adb folder: Ares8A_recovery_twrp.img ?

"i extracted the nextbook ares 8a 3.04 files TO Adb file."

The Ares8A_recovery_twrp.img is not contained in my V3.0.4, TWRP backup, as it is only a ROM backup. The Ares8A_recovery_twrp.img is contained in any of my modified boot.img files on Android File Host. just don't use the boot.imgs or system mode SuperSu from those archives.

It sounds, upon re-reading your post that you only have my TWRP backup ROM in your adb folder. If you ever want to restore the V3.0.4 ROM, you would need those files either copied to the ext. SD or int. SD card in the proper TWRP folder hierarchy and naming, or you could restore with your V3.0.4 TWRP backup. If you ever do either, be sure to uncheck recovery in the restore options or it will overwrite the TWRP recovery with the stock, Android one.

Please let me know if that was it. Maybe I will eventually upload an archive that just has TWRP in it so there is no confusion in the future. Please let me know if this solves your problem.

I also updated my Quick Start Guide with that info about the Ares8A_recovery_twrp.img.
[Miscellaneous Android Development] martyfender:
I have uploaded a TWRP only archive to AFH:

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

I also updated my Quick Start Guide with the above link, also. I have added so much info in it that it is not really a quick start guide, anymore.
[Miscellaneous Android Development] martyfender:
Please read again what I wrote. that is a V3.0.4 rom backup and does not contain TWRP. I Updated my Quick Start guide and added a TWRP archive only, to AFH.

Time to go to work.

You need the Ares8A_recovery_twrp.img in your adb folder not the backup rom files.
[Miscellaneous Android Development] discod2124:
Ok i see all the updates etc.. but im lost so many updates i have the latest build 3.0.4 android 6.0.1 can you give me just a straight run through from start to finish in order with the updated way to do it i already did usb debugging and oem unlock not sure how to get into boot mode on this device
[Miscellaneous Android Development] martyfender:
If you mean bootloader/fastboot mode, there are 2 easy ways:

1: when the tablet is completely shutdown, hold the volume down and the power button at the same time until it boots to bootloader mode. You should see the green Android guy on his side with a black background.

2: This assumes you have adb working and the tablet is booted normally:

From your computer command prompt issue:

adb reboot bootloader

Hit the enter key on the keyboard and you should now reboot to bootloader mode.
[Miscellaneous Android Development] discod2124:
Now device not found in adb
[Miscellaneous Android Development] martyfender:
[MENTION=8852759]discod2124[/MENTION] In bootloader mode? you have to now use fastboot commands, for example:

fastboot devices

That sounds like the Intel drivers are not properly installed. After you installed the adb and fastboot, did you install the Intel drivers linked in the OP? If so, open the Windows device manager and check to see that your device shows up as either Intel Android Composite adb Interface or Intel Android adb Interface when the tablet is booted normally.

When booted into bootloader mode the tablet should show up in the Windows device manager as: Intel Android Bootloader Interface.

If they don't show up as this in the device manager, double click it in the device manager, choose the driver tab, click update driver, browse my computer for driver software, let me pick from a list of device drivers on my computer, uncheck show compatible hardware and choose the ones I mentioned above: Intel Android Composite adb Interface or Intel Android adb Interface when the tablet is booted normally and: Intel Android Bootloader Interface when booted into bootloader mode. What version of Windows are you on, by the way?

In the 15 seconds ADB Installer v1.4.3, if you don't uncheck install drivers in the installer, it will install the default, Google drivers, which are not the proper drivers for this Intel device.

In bootloader mode you have to use the fastboot commands, not adb commands.

fastboot devices

hit enter on the keyboard on your connected computer

your device fastboot name and serial number should be listed. It will be different than what is listed in adb devices, when the tablet is booted normally.

This is the number one issue I see with users: getting the drivers, adb and fastboot setup correctly.

I recommend copying the Ares8A_recovery_twrp.img into the adb folder, which should be at: C:\adb. Hold the shift key, right click the mouse in an empty place in that folder and when the contextual menu drops, choose: open command window here.

I would also suggest rereading the preparation info to set up your device in the OP, prior to the Quick Start guide. Please let me know how it goes.

By the way, the V3.0.4 tablet you own is the latest version I am aware of and it and the V2.1.5 have no issues that the earlier versions, V1.1.1 and V1.2.0, have. The Sd card reader has apparently failed on my V1.1.1, which is sad, as it runs great in every other way with the Magisk root I am testing on it currently. I have relegated it for testing new things, which I don't want to risk my newer tablets for.
[Miscellaneous Android Development] discod2124:
Went to device manager found the device intel android and interface but when I go into adb no device is found when in bootloader it is there if the device is in android mode
[Miscellaneous Android Development] martyfender:
First of all, did you use the installer I linked in the OP (Opening Page), to install adb and fastboot? It almost sounds like the fastboot.exe is not in the C:\adb folder.

Here is what I see in Linux when booted normally" In Linux one has to use the sudo command to get root:

mint@mint ~ $ adb devices

List of devices attached

YFGV0317037600	device

mint@mint ~ $ adb reboot bootloader

mint@mint ~ $ sudo fastboot devices

CHTT011AC12A	fastboot

mint@mint ~ $

mint@mint ~/Downloads $ sudo fastboot boot Ares8A_recovery_twrp.img

downloading 'boot.img'...

OKAY [ 0.457s]

booting...

OKAY [ 0.033s]

finished. total time: 0.491s

Now booted into temp TWRP recovery.

On Windows make sure you have the following files in your adb folder: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe? Again, what version of Windows are you on?

When booted into bootloader mode, the tablet should show up in the Windows device manager as: Intel Android Bootloader Interface. Do you see that?
[Miscellaneous Android Development] discod2124:
Yes I used your op and in the adb folder fastboot is there as well like I said I can see it in adb when the tab is all the way on just not in bootmode am I suppose to select any option in the boot mode
[Miscellaneous Android Development] martyfender:
You never answered my questions. I often edit my post after I first send them, so the questions may not have been there in th e reply initially.

No, you don't need to select and option. From your computer command prompt issue:

fastboot devices

hit enter

I just fired up a Window 7 laptop and I see this in the command prompt window:

C:\adb>adb reboot bootloader

C:\adb> fastboot devices

CHTT011AC12A fastboot

With Ares8A_recovery_twrp.img copied to my adb folder I issue:

C:\adb>fastboot boot Ares8A_recovery_twrp.img

downloading 'boot.img'. . .

OKAY [ 0.484s]

booting. . .

OKAY [ 0.047s]

finished. total time: 0.530s

C:\adb>

I am now booted into temp TWRP recovery. I do have TWRP permanently flashed, this is temp booted for demonstration.

While still booted in bootloader mode I have the device manager open and I see:Intel Android Device, in the drop down of that I see: Intel Android Bootloader Interface.

If you don't see that you can go to the action menu in the device manager, choose: add legacy hardware, install hardware I manually select, scroll down to Intel Android device, next: Intel Corporation: choose Intel Android Bootloader Interface. when I did this it added a second one. I had to choose uninstall, as I already had it installed. I would recommend rebooting the computer after this. I have also occasionally seen where people have had to try different USB ports on their computers.

I am assuming you have USB debugging turned on in the developer options and you approved the Androids security prompt dialog on your tablet, when booted normally, after typing adb devices, or any other adb command?
[Miscellaneous Android Development] martyfender:
When I uploaded the stand alone TWRP archive, I inadvertently uploaded the original, password protected version. Please redownload it at the new link:

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

Sorry for any problems this may have caused.
[Miscellaneous Android Development] Goolz1333:
I recently purchased a next book Ares 8a brand new from a guy I know he said he had the receipt for the activation code but he had to find it. ,of course he didn't find it. Today I managed to do a work around to access the tablet very fast and easy but when the device restarts it always goes back to the activation code screen any ideas how to disable the feature with access to all the settings. ............

The work around I found was to let the battery be so low that when u unplug the usb cord from the device it shows a low battery notification when it pops up touch over the top to pull down settings ,as I said this is in the activation code lock screen ,then touch settings and u can gain access that way ,or if u can manage to hold power button down until prompts u to reboot etc touch the middle bottom to see if u can access google assistant that will also give you access ,but as I stated there is still an activation screen to remove. Any ideas guys.
[Miscellaneous Android Development] martyfender:
Do you have the box for the tablet? the DISA code is on the box and you can enter that code at this site to activate it:

https://www.getyourcode.com/#/

On that site there is also a live chat button and this message:

"Don't Be Another Victim

Knowing that your product requires an activation code will help prevent you from purchasing stolen, unusable items on marketplaces like Facebook, eBay, Craigslist, OfferUp, and more. Before purchasing, remember to look for the yellow lock logo."

If you don't have that DISA number, you may be SOL!

Caveat emptor

Caveat emptor /ˌkævɛɑːt ˈɛmptɔːr/ is Latin for "Let the buyer beware"[1] (from caveat, "may he beware", a subjunctive form of cavēre, "to beware" + ēmptor, "buyer"). Generally, caveat emptor is the contract law principle that controls the sale of real property after the date of closing, but may also apply to sales of other goods. The phrase caveat emptor and its use as a disclaimer of warranties arise from the fact that buyers typically have less information about the good or service they are purchasing, while the seller has more information. The quality of this situation is known as 'information asymmetry'. Defects in the good or service may be hidden from the buyer, and only known to the seller.

A common way that information asymmetry between seller and buyer has been addressed is through a legally binding warranty, such as a guarantee of satisfaction. But without such a safeguard in place the ancient rule applies, and the buyer should beware.

I have only purchased my tablets from the only official retailer for the tablet: Walmart.
[Miscellaneous Android Development] Naghual80:
Hello.

Where can I find a stock ROM for this tablet? For flashing through stock recovery.

(I have a cranked LCD and only part of it operational. So I can use only stock recovery)
[Miscellaneous Android Development] martyfender:
Do you know what version of the tablet you have? Go to settings, about tablet, scroll to the bottom, the build number will tell you what version you have. I still have stock recoveries for V1.2.0, V2.1.5 and V3.0.4. The stock V1.2.0 should work on the V1.1.1 tablet. I lost the stock V1.1.1 recovery.

You can't use TWRP because touch does not work on the tablet? It seems to me that the tablet is almost useless without the touch screen working. I have Roms for V1.1.1, V1.2.0, V2.1.5 and V3.0.4, just not stock recovery for the V1.1.1. I take that back, I just found V1.1.1 recovery on gdrive. Most of my ROM backups on AFH have only twrp, in addition to the boot.img and system.img in the form of twrp flashable backups. They might be flashable through fastboot, if they are renamed from, for example, boot.emmc.win, to boot.img. The system ones, however, are in 2 parts, so I am not sure how that could be done in fastboot. I have never used TWRP's feature to create a system.img, as I have always used TWRP to flash my ROMs. I think TWRP splits the system images because of the FAT32 file systems limit of a maximum of 4Gbs for file sizes. The external SD card and internal SD, use the FUSE file system vfat, so that max, 4Gb file size applies.
[Miscellaneous Android Development] martyfender:
There is no stock ROM available, as Nextbook never released one and in the cases of this tablet, several versions. They never released it for the Ares 8, either.
[Miscellaneous Android Development] martyfender:
I have now switched from SuperSu to Magisk v15.3 on all of my devices. With Magisk Hide and the Magisk Manager hidden in the settings, all of my devices pass all Safety Net checks. I don't currently use any apps such as Android Pay that require this, but I'm sure that some of you do use apps that have this requirement. However, there are some apps that can detect root in other ways, so will still fail to run or install.

In the Magisk xda forums there are troubleshooting guides with possible solutions to be able to run such apps.

In addition, Magisk has a whole module add on repository to add many useful features. I use the Greenify4Magisk to make Greenify a privileged system app, systemlessly. In the past I had to install it into the system to achieve this. Doing so improves Greenifys functionality.

Another Magisk moduleI use is Sysconfig Patcher, which allows Google Play Services to be added to the doze battery optimizations for better battery savings, in addition to some other energy saving tweaks. I am however, not certain how effective this is.

I may test a couple of other modules in the future, but I strongly recommend being conservative in using to many modules, as they may break other things in Android.

I recommend sticking with the current stable version of Magisk, v15.3, as of this writing, or newer.

I however like beta testing so I have [MENTION=3306843]kantjer[/MENTION] unofficial builds on my devices.

He updates it with topjohnwu's latest commits on github. Be warned though, it has the potential for being unstable, although I haven't had any problems since the first 15.0 release train wreck.

15.0 had a major bug where it did not patch boot.imgs properly on some devices and this device was one of those affected by that bug. Upon install the system froze at the first splash screen.

v15.1 and later, fixed that problem.

The last release, SuperSu SR5 2.8.2 has no known problems on our devices, but CCMT purchased it from ChainFire and has not updated it in many, many months, as if development is dead for it, hence the switch to Magisk that many xda users have done, as Magisk is in very active development and as of v15.1, has been very reliable on the Ares8A.
[Miscellaneous Android Development] Naghual80:
Hello martyfender. Thank You for trying to help me.

No I don't. Tha tablet is currently unbootable. The model No: NX16A8116B.

I see your point. I want to use it like a TV media device. I will use it with wireless mouse-keyboard and a TV throught HDMI.

That's not a very optimistic as for me... Or, maybe, my english is not so good to understand your message ))).

Now I may connect a tablet to PC and run a TWRP temporarly through fastboot mode. After that, being at TWRP I connect the tablet to TV through HDMI cable. But the TV picture is at album proportion and the tablet is at the portret, so I can see on a TV just a part ow TWRP screen.

I see something like this (unblured): [IMG="Unblured is what I see on a TV"]https://image.ibb.co/iLoqPG/TWRP_visible_part.jpg[/IMG]

Please, guide me to next level.

)))
[Miscellaneous Android Development] martyfender:
can you use the keyboard and mouse to navigate the TWRP buttons and menus?

I have never purchased an OTG cable to try a keyboard and mouse.

Does the install and restore buttons work in TWRP? if yes you may be able to restore a backup ROM copied to an external SD card in the proper TWRP folder structure. The other problem is that we need to know the tablet version because any ROM version will boot on this tablet, however, if it is not the correct one, you will loose sound and maybe wifi and bluetooth.

Boot the tablet into bootloader/fastboot mode and you will see listed The IFWI version listed which should give us a good idea what version of the tablet you have. It will also show if the bootloader is unlocked and secure boot is disabled.

A ROM in the same version series should work: v1, V2 or V3. Somewhere a few pages back I list known IFWI versions and their corresponding tablet version numbers. Once we know that you can download the correct TWRP backup I have uploaded to AFH, (Android FIle Host). It must be copied to the proper TWRP folder structure also. Back somewhere in the threads I list that exact folder structure.

This is assuming you have a pc to do all of this with a card reader. I assume since you have twrp that you already unlocked your bootloader.

Also I assume you have the proper drivers that are tested and working on your computer and adb and fastboot are working correctly. The op shows how to test this.

I have never connected one of these tablets to a TV through HDMI. So you don't have to be able to get into Androids settings, for it to work? It is just plug and pray (play)?
[Miscellaneous Android Development] Naghual80:
Mouse - yes. Keyboard - don't know. Will try later, but I think it will work OK.

Uder Restore button I can't see any of back ups. Maybe it is because I use incorrect restore path?

If it will boot but with some problems - that already will be a success. A part of success.

Will try to do that at evening and provide photos.

Will try this.

I'm not sure about that. I boot into TWRP directly from fasboot. TWRP is not installed.

Yes. It is fully mirror a screen on TV.

But, as I say earlier, screen is not complitely visible.
[Miscellaneous Android Development] nik-1973:
the author say please, this firmware is suitable for ares 8 NXA8QC116
[Miscellaneous Android Development] martyfender:
Apparently, there is a problem of proper translation, but:

No, it is not suitable for ares 8 NXA8QC116. That device has completely different hardware, Android version and partition schemes. If you try to flash it on that device, it will more than likely brick the device. vampirefo's updated 5.1.1 rom works great on that device, if you have the original, 5.0 version. There are about 5 threads concerning the Ares 8 where you can find plenty of info.
[Miscellaneous Android Development] nik-1973:
спасибо!
[Miscellaneous Android Development] icyicy ice:
i fixed it,last night i was messing with my tablet and finally fixed it. didn't need the files just had to reset it and install all of the files i needed to then change the /data to ext4 so it would work, and it finally works
[Miscellaneous Android Development] hammergunner:
does anyone know the difference between the builds?

have NX16A8116K that was messed up from a failed root by the last owner, rolled it back to the 1.2.0 twrp and then upgraded to 2.1.5 it was on 2.1.3 but didn't make a backup since it was already having issues.

Is there any Improvements on the 3.0.4 build?
[Miscellaneous Android Development] martyfender:
The v3.0.4 will work on your tablet but you will loose sound from the built in speaker and headphone. Bluetooth sound will probably work. This is all based on trying it on my v1.2.0 tablet. You have a V2 series tablet so it is best to stay on the one you used: v2.1.5. They all have the same Android and kernel version. Nextbook never released what was changed, if any thing, between versions. I suspect very little. Each version has a different IFWI (Intel Firmware Interface). I believe that is where the UEFI bios resides and I have not found a way to copy that to other tablets without the risk of bricking the device. Is it working good on the V2.1.5 Rom? If so, I would stick with that.
[Miscellaneous Android Development] hammergunner:
yes so far everything is working haven't had any issues with anything being broken.

However I do have what I believe is a memory issue, once I have enough apps open I get a random reboot so

that's about it......tablet was free so I'll take what I can get.

I'm going to make my backup then go to 3.0.4

but as you said when I rolled back to the 1.2.0(only twrp backup I could get to restore completely) I lost Bluetooth and sound, once I had a 1.2.0 in the 2.1.5 backup restored without issue.