yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
If you go to 3.0.4, you will more than likely loose sound from your speakers and headphones. There is really no benefit for you to go to v3.0.4. I think the changes are in the IFWI, which can't be transferred without some major risks, if at all possible.

I rarely have issues with memory because I swipe away apps in recents when I am done using them. This does go against what is recommended in Android and its LMK.

I also use Lspeed and Kernel Aduitor to tune some settings and Greenify to hibernate some apps, also.

Furthermore, I switched all of my devices from SuperSU to Magisk 15.3+ by using the Unsu.zip to remove SuperSu, reflashing the particular ROM versions stock boot.img, then the Magisk.zip and busybox.zip, all in TWRP, before wiping the dalvik cache and cache and rebooting.

I am using unofficial builds with the latests fixes and commits here:

https://github.com/kantjer/MagiskFiles

Here is the link to the unofficial thread:

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

If you decide to switch to Magisk, it is probably better to start with the lastest, stable version, as of this writing: 15.3

https://xdaforums.com/apps/magisk

If you used: 2017-12-01--23-51-18_V2.1.5.MMB29M.20170327.212634.zip, it contains the stock boot.img and stock recovery. You need to unckeck recovery when you flash it, or it will overwrite TWRP.

In addition, the stock boot.img needs to either be patched, before reboot after flashing, either with SuperSu systemless: SR5-SuperSU-v2.82-SR5-20171001224502.zip or Magisk-v15.3.zip.

As explained in updated instructions at the bottom of the OP, I no longer recommend flashing my modified boot.img with it. You never explained what you mean that it failed until you flashed 1.2.0, first. Not doing the above is maybe why it failed?

If you flashed the V2.1.5 backup then rebooted without a patched boot.img (patched with either SuperSu or Magisk), it would probably not boot correctly, such as a black screen on reboot or a verification error.
[Miscellaneous Android Development] hammergunner:
yeah if I already have the 2.1.5 up and running you should assume I know what to do.

but i didn't know what was causing the error, like a mentioned before it was given to me with a bad root attempt and would randomly stop services, reboot and repeat.

removed the SD card as it was corrupted, placed the 2.1.5 on a good SD card and upon trying to restore the backup I got error 225(or something like that) at about 9% install.

Swapped cards, redownloaded the file , extracted using a different archiver tool all to no avail install would fail at 9% with the error.

figured it was an issue of going from the bad 2.1.3 to 2.1.5, I've had this issues with other devices before and a roll back to earlier firmware usually got passed those issues, and it worked just like I thought.

1.2.0 installed with no issues booted right up, rebooted and went back to recovery and restored the 2.1.5 backup this time with no errors or issues what so ever so it was the bad 2.1.3 build that was preventing the 2.1.5 install from my speculation, as I don't dig to deep into these issues.

2.1.5 up and running fine without any broken features, and it was Firefox that was crashing my tablet haven't had an issue since I switched to another browser.
[Miscellaneous Android Development] martyfender:
Myself, I always use Firefox with ublock origin extension and adaway for ad blocking with no problems.
[Miscellaneous Android Development] hammergunner:
anyone having any success installing xposed framework x86 ?
[Miscellaneous Android Development] martyfender:
As far as I know, there is no known version of xposed that works with this ROM. These tablets have a non-standard version of ART which xposed is not compatible with.
[Miscellaneous Android Development] Greymage:
Boot manager & FTM mode?

I am fairly new to next book tablets and development in general. So please excuse me if my question sounds a bit noob-ish.

What exactly are the boot manager (volume up+power when device is off) and FTM mode (option in bootloader) used for on this device? They both look to be something similar to a BIOS on a windows computer, and I know other next book's are windows/android dual boot. So I guess what I'm trying to ask here is, is it possible to dual boot the next book Ares 8a with android and windows?
[Miscellaneous Android Development] NyTR0S:
Maybe. Givin the hardware specs on some of the Next Book modeles, it just might be possible. However, due to how slow they are, you would be lucky to get Windows 95-Xp to work. Ang again, that's a hard MAYBE.
[Miscellaneous Android Development] martyfender:
the boot manager is the uefi bios interface similar to what is used in Windows.

I am not certain what FTM mode is used for.

I believe both of these may be stored in the IFWI firmware.
[Miscellaneous Android Development] Greymage:
So is it possible to put windows on the tablet? If so could you or someone explain how one would do so?
[Miscellaneous Android Development] martyfender:
I don't know how to do that, however you would need a usb otg cable to hook up a keyboard and mouse to interact with the bootmanager bios settings. My guess is that if you manage in some way to install Windows on it that you would have to be able to choose Windows vs Android in the bootmanager. But I know very little about this. I personally think it is a waste of time.

You would be much better off buying another tablet that has Windows already installed on it or one that has both dual boot with Android, also. Maybe others will have better knowledge than me in this matter.
[Miscellaneous Android Development] Jabrams7848:
Marty, can you or someone here help me?

I purchased the Nextbook Ares 8A from walmart. It is:

Processor Type: QuadCore-A64

Model Number: NX16A8116KP

Android Version: 7.1.1

Kernel Version: 3.10.65

Build Number: V3.0.0 N9F27C.20171128

I don't seem to have access to Bootloader and ultimately Fastboot. it just boots to the Nextbook screen and stays there.

I have chosen to allow unlock bootloader option in settings.

Enabled USB debugging in developer options.

Please tell me there is a way to unlock bootloader and ultimately rooting this device?

Thanks

Jason
[Miscellaneous Android Development] martyfender:
My method is only for the Nextbook Ares 8A with an Intel processor and Android 6.0.1.

I purchased one, tested it then returned it since I have no method to root it at this time.

I also purchased a Smartab at the Walmart Black Friday sale with Nougat on it also and bootloader mode seems to be disabled on it also. So without more information, unfortunately, I don't know how to root either tablet.

Nextbookusa doesn't even list the new 7.1.1 version on their website, the last time I checked. In the past I had emailed them and they weren't even aware of the new model.

It almost seems that the manufactures purposely disable fastboot on these devices to to foil would be rooters. If anyone has any info on this, please let us know.

I do know from frequenting the Magisk root forums, that the flagship devices with newer Android versions have fastboot mode.
[Miscellaneous Android Development] dannybz:
Hey, not sure if this is the right thread, but its the only one I found. My nextbook Ares 8A is stuck on the boot logo, even when I put it to charge it get stuck on the charging battery logo. Any ideas what is happening and how to fix it?
[Miscellaneous Android Development] martyfender:
I need more information. What did you do to the device before this happened?

Also, is it the Intel 8A with Android 6.0.1, or is it the newer model with an ARM processor with Android 7.1.1? This recovery and root is only for the Intel version of the tablet.
[Miscellaneous Android Development] Jimmy2526:
Hey Marty I just sat here for the last 4.5 hrs and read this entire post... now a 12 pack of Pepsi an ill mad wife that's locked me out the bedroom and about 5 packs of cigarettes later I'm sure your the man to help me.. I have the 1.20 version I'm thinking and it's completely stuck on the logo screen with" DNA FASTBOOT MODE.." I know it's the model num NX16A8116K PR at 1 time I've seen the build.prop for this device and if I'm a rectulecting properly it's the 1..20. Can you help.. it's so stuck if I. FASTBOOT boot Ares8A_recovery_twrp.img it will just sit there for like 45 secs or so and then it will reboot itself back to DNA FASTBOOT.. I've even tried doing the osloader flash and it actually showed me a bunch of errors on the tablet screen then went to UDMboot failure then went to the bios after it said that the boot file is completely missing.. then it will take me to file manager which is empty so I reboot and start all over.. every fastboot cmd returns failed unknown cmd
[Miscellaneous Android Development] martyfender:
I've never seen anything like this on any of my Ares 8A's to know how to help. I did see something similar on my original Ares 8 but the 8A has an entirely different partition layout than the 8. On the 8, I did flash an osloader to fix it. However that osloader would be entirely different on the 8A. Where did you get an osloader for the 8A? Or did you use the one from the 8 thread? If you did it would not be compatible with the 8A and may be why you are having problems. If that is the case then I have no idea how to fix it.
[Miscellaneous Android Development] Jimmy2526:
I'm gonna try and post some screen shots when I get off work.. Seems that I have a good paperweight unfortunately
[Miscellaneous Android Development] dannybz:
ares 8a screen stucked

I have the same prob with my NX16A8116KP. Stuck on boot logo. I just want to fix it. Whatever it takes.
[Miscellaneous Android Development] Jimmy2526:
I'm just getting home from work and I'm hoping the wife is gone to her ladies only margarita mixer and hopefully some of us can sit down and get our heads together and fix this.. I know it's a cheap inexpensive tablet but mine has some great sentimental value of a friend who is no longer with us attached to it... one of those things that some people don't understand whereas to me no amount of money could buy it.
[Miscellaneous Android Development] martyfender:
I do love a challenge, but do you have any info into the steps that you did to this tablet that led up to this? Did you try to flash files that were not even intended to be used with the Ares 8A with Android 6.0.1? Maybe the osloader for the Ares 8 with Android 5.+?
[Miscellaneous Android Development] Jimmy2526:
See the sticky on the tablet my friend had stumbled upon the tablet at just some random chicks house and it was dead the battery had come undone.. must of been assembled early Monday morning or late Friday afternoon in my opinion. But anyways so he is looking at it and him knowing that I knew my way around adb (I know just enough to get me in trouble) he starts talking smack to this chick and she's telling him it's broken that he couldn't do anything blah blah blah.. so for the next 3wks straight there was this lil game they had and of course I had the tablet running 30 mins later but that's neither here nor there. But for 3 weeks he had this thing and he was ready and willing to bet his first born that he could root it himself to just set adb up on his laptop and he was gonna learn the rest by himself... I swear he through everything he could possibly find on XDA even if it wasn't for this model he flashed and would brag to her.. he has files from the 5.1 files for the NX10LTE the NX11 something on his laptop hell I think I even see his own cooked up file for the kitchen sink in there.. unfortunately the tablet is in the condition it's in. Another unfortunate is that he was murdered 5 wks ago over 200 bucks and truck.. So I don't care where I gotta go and what's gotta be done this tablet has to be fixed. He was more like my brother than my blood brother and I don't think his soul is gonna be at rest knowing that I couldn't get it going just to give it to his life long crush.. sorry that was long but I'm hoping you see the importance of getting it fixed. I'm sure someone can relate a lil bit

---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------

I'm trying to pull all the files in a zip and upload them so maybe you can see all this on here... WOW IS all I can say just wow.. I do know at some point back in February he could boot it to twrp but it won't even do that now
[Miscellaneous Android Development] Jimmy2526:
Here is some pix of the what I can get it to do
[Miscellaneous Android Development] martyfender:
I'm afraid I am not knowledgeable enough to help with this. From what you wrote above it appears that files from other devices with different partition layouts were flashed to this device, bricking it. It does look similar to what happened to my original Ares 8 but in that case I used the files posted by [MENTION=4821597]social-design-concepts[/MENTION] for the Ares 8 to fix it. I do not have these files for the 8A, nor do I know how to get them for it. I flashed them in fastbootmode. They were esp and efi boot files. I do know they will not work with this device. For one, this device doesn't even have a esp partition.

Attached is the partition layout document I have stored on Google Drive for the 8A.
[Miscellaneous Android Development] Jimmy2526:
He has some interesting files from github downloaded also like build setups and stuff.. kernel quilts and more can't I just possibly rebuild this thing
[Miscellaneous Android Development] martyfender:
Can you get into bootloader/fastboot mode where the little green Android guy shows up? Turn off the tablet by holding the power button for some time. Now hold the volume down button and power button at the same time to boot into fastboot/bootloader mode. When plugged in to the computer, what is the result at the command prompt for adb devices and fastboot devices? Are you on Windows? In the Windows device manager do you see Intel Android adb device or similar?
[Miscellaneous Android Development] Jimmy2526:
Windows manager shows Intel android adb interface,,,, by holding power+volume down returns the Nextbook logo screen with powered by Android at the bottom with (DNX FASTBOOT MODE..) In yellow top left screen,,,, power plus volume up returns me to the boot manager screen tells me to use. (+ -) to scroll through options to boot or hit escape to exit.. how am I to hit escape when I have no escape button. Did you see the pics I posted some of this is in those pix..

---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------

I've also tried to change the Windows manager to the Intel bootloader interface but no luck either

---------- Post added at 02:29 AM ---------- Previous post was at 02:09 AM ----------

Also I think the last time I seen him and he was working on this he was in twrp manager and he was trying flash something and it kept failing and when he would try to exit it would give him the warning of (Are you sure you want to exit there is no OS loaded) or something on those values

---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------

With my readings and research I've come to find out that DNX FASTBOOT is the one that is capable of flashing Bios..
[Miscellaneous Android Development] martyfender:
In that first picture you sent I clicked on full size image and zoomed several times to try and read what it say but it is too faded to white to read.

When in the bootmanager, if you have a usb otg cable, supposedly one can connect a standard keyboard and mouse the choose the options. I do not own a usb otg cable, so I have never tried this.

It sure acts like my original Ares 8 where I had to flash the esp files and efi files in fastboot to get my bootloader/fastboot mode back. Unfortunately, I do not know how to do this or know how to get the files to do it for the Ares 8A. The files I used to do it for the Ares 8, I downloaded from [MENTION=4821597]social-design-concepts[/MENTION] post in the Ares 8 root thread by [MENTION=2472806]vampirefo[/MENTION]. Those files will not work on the Ares 8A, though. I suspect those are what might have been flashed to your tablet, or other, that has caused your issue. He may have tried to flash [MENTION=2472806]vampirefo[/MENTION] 's ported Android 5.1.1 to it. Flashing that a second time on my original Ares 8 is what caused that issue on my Ares 8. I'm not sure why.

After I fixed my bootloader partition issue, I was successfully able to flash the ported 5.1.1, to my original Ares 8 with no issues. And don't confuse that bootloader partition with the boot.img, as they are different.
[Miscellaneous Android Development] Jimmy2526:
So I'm taking a wild shot in the dark and gonna say that he was at the twrp manager and couldn't exit because of no OS and when he passed the battery died and then when I plugged it up and tried to fire it that since the OS was gone that it has no commands or leader if you'd say to follow to actually boot anything up
[Miscellaneous Android Development] martyfender:
Even if the system is deleted, you should be able to boot to fastboot/bootloader mode if that partition is intact. A couple of times I have mistakenly deleted the system in twrp, when I intended only to delete the dalvik cache and cache. However, the boot.img was still there. I'm not sure how it boots if that was also deleted. You said you can't temp boot twrp with:

fastboot boot Ares8A_recovery_twrp.img

And are you sure you are using the TWRP from my downloads section and not one for the Ares 8? It is named, as above: Ares8A_recovery_twrp.img.

You could also try to this:

fastboot flash recovery Ares8A_recovery_twrp.img

However if you can't boot to bootloader mode in the first place, neither of the above will work.

I also assume you have the proper adb and fastboot exe files installed on your system, which, since you never stated, I assume is Windows.

I have info in the OP on how to setup drivers, adb and fastboot.
[Miscellaneous Android Development] Jimmy2526:
Her is a pix of all the files he has loaded and of cmd.prt.
[Miscellaneous Android Development] martyfender:
Looking at your cmd window your device is showing up with it fastboot serial number and that is good. It looks like you opened the command window from the desktop, though.

Instead, navigate to the minimal adb and fastboot folder I see in the photo and issue the command there. It is possible that is what is causing your issue, at least partially. That command would not work from the desktop because the TWRP file is not there

Have you tried the above command I gave you by left clicking on an empty spot, then right clicking on that empty spot in that folder and choose: open a command prompt here, from the drop down menu then enter in the command window:

fastboot boot Ares8A_recovery_twrp.img

to see if it will temp boot into TWRP. Make sure you are in the same folder where I see the Ares8A_recovery_twrp.img Opening a command window from anywhere else will not work unless the files path is also in the command, hence the need to open the command prompt in the folder where the file is stored.

If the temp TWRP does finally boot, you can restore the TWRP that I also see in that folder for the tablet version you have, which you thought was v1.2.0.

The TWRP backup files must be unzipped in the proper folder structure for it to be recognized. and here is the catch, they need to be on an external SD card in the tablet or in the internal SD card of the tablet, in this folder structure: TWRP/BACKUPS/NX16A8116K/2017-09-05--23-35-58_V1.2.0.MMB29M.20170216.211208/ , for example of one of my v1.2.0 tablet backup folders.

If you do finally get TWRP to temp boot, you will need to get a micro SD card to put the TWRP backup files on it as I see no way to get the files to the tablets internal storage in it's current state. You would have to copy the files to the micro SD by placing it in a card reader on the computer. Most micro Sd cards come with a SD adapter, since most computers only have SD slots.

Let me know if you do get temp TWRP to boot.