yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] y0kiua:
yes patched

Versions IFWI are different, maybe this is the problem.

Nobody tried to port Remix OS on this version, I see only on Nextbook 8, but not on 8a?

Possible installation Remix OS may be decided with sound problems and gave new life this tablet
[Miscellaneous Android Development] shaun279:
Also unfortunately I won't be able to test the bypass method as my second nextbook I used for testing is hardbricked from modifying the UEFI settings. It can't be fixed without flashing the UEFI which is not possible without proper equipment. So lesson to anyone that enters UEFI, don't change anything :)

Try this boot.img
[Miscellaneous Android Development] y0kiua:
Thanks, this boot need patched afterward with SuperSU or Magisk?
[Miscellaneous Android Development] shaun279:
already patched with magisk i believe
[Miscellaneous Android Development] martyfender:
Usually, the no sound problem occurs when the rom and boot.img versions are not the same version. Is that your backup or is it the one I have on Android File Host?

Have you tested bluetooth sound, it may work.

If you used a rom and boot.img pair that wasn't the same as came on your tablet, you will not get sound from the external speaker, but in my experience, bluetooth sound will work. Neither sound will probably work though, if the rom and boot.img are not the same version.
[Miscellaneous Android Development] y0kiua:
Yes, I flashed your backup from Android File Host

now I can not find the correct version boot.img or backup

wifi and Bluetooth its works, sound - not
[Miscellaneous Android Development] martyfender:
[MENTION=4164606]y0kiua[/MENTION] Yes, the tablet I use the most daily, has IFWI version: M882_JJ.023. The v1.2.0 tablet that I have has IFWI version M882_JJ.019. Is it possible you have that tablet version and just flashed the wrong version of my backup? That would explain why you have the issues that you do.

I would recommend flashing my v1.20 version of my backup and see if that solves your sound problem, if you think you actually have that version of the tablet.

This was the first version of the tablet that I know that used the DISA activation.

If my memory serves me correctly, that V1.2.0 backup is a SuperSu pre-rooted rom and I had patched the boot.img in Android Image Kitchen to remove dm_verity and encryption. I believe that version also has SElinux patched to be permissive.

Attached is what I believe to be a stock boot.img for that v1.20 rom. You must, of course, unzip it before flashing it in TWRP. It can be also flashed in fastboot, but it is much easier to do it in TWRP, choosing install, image, buttons. If you choose to use it over the prepatched version, you must flash it in TWRP followed by flashing either the latest SuperSu systemless version beta.zip, or the latest official released version of the Magisk.zip, which is v18.1. Either will patch the boot.img to remove dm_verity and encryption. Sometimes you have to extract the Magisk Manager and install it from the zips common folder, if flashing Magisk does not install it also.

I recommend that if you do either of the above with systemless SuperSu, or Magisk, with the stock boot.img, that you first flash the UnSu.zip to remove the system installed version of SuperSu, first. Do all of the above before rebooting the device, because the bootloader is unlocked and the device may freeze on booting or give you a warning at boot and also re-encrypt the data partition.

If your data partition is encrypted with the default, you must also factory reset in TWRP, so a fresh, unencrypted partition can be created on first boot after flashing the boot.img and SuperSu or Magisk. I highly recommend Magisk. I have it on all 5 of my tablets.

Here is a link the the Magisk and MagiskHide Installation and Troubleshooting guide:

https://www.didgeridoohan.com/magisk/HomePage#

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

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

I don't check this thread very often anymore, but I will keep an eye on it, if you have any other questions, as what I posted may be a lot to take in, if you have not done any of this before.
[Miscellaneous Android Development] martyfender:
[MENTION=4164606]y0kiua[/MENTION]

UPDATE:

What [MENTION=7933747]shaun279[/MENTION] stated about different audio chipsets now makes some sense to me as my v1.1.1 tablet can use the v1.2.0 rom backup with full sound. After v1.2.0 Nextbook must have changed audio chipset and that is why when I flashed the newer version tablets roms on the older devices, I had no external speaker sound, but bluetooth sound did work. There could possibly be more to it than that, but I am relating my own personal experience with it, only.

All of my 5 devices currently have the version of the rom that came with the tablet, patched with the latest Unofficial and Canary, cutting edge builds of Magisk, as I test and report bugs, frequently, to further Magisk development.
[Miscellaneous Android Development] tcwiv:
Good morning. After reading up extensively here as well as other forums/groups I decided to undertake the rooting of my Nextbook Ares 11A (NX16A11264 - 5.1) and am currently regretting it. Using a version of Ares8A_twrp_recovery...img through (fastboot flash boot Ares8A_twrp....img) I am now at least able to access TWRP although attempts to flash a .img beyond twrp have proven unsuccessful. The most recent attempt was to install from TWRP a downloaded version of '2017-07-01--01-36-33_V1.1.1.1.....zip' from the OP. It has yielded the the following errors - 'Invalid zip file format!' - 'Error installing zip file /usbotg/2017-07-01.......zip' - 'failed to mount '/data' (Invalid argument)'

Although not bricked (yet) I'm hoping its an easy fix to an overlooked mistake - any help would be rejoicingly appreciated.
[Miscellaneous Android Development] shaun279:
Did you follow instructions to root for Nextbook 11A?

According to that thread you don't need to flash the TWRP recovery, only the SuperSU zip
[Miscellaneous Android Development] martyfender:
If the 11A 5.1 is anything like the Ares 8 5.1 that I had before it died, it has a totally different partition scheme than the newer devices and an older, Intel processor and other hardware. I am surprised that the the TWRP for the 8A even boots on it at all. I also am almost certain that flashing roms for the newer Android 6 devices would brick the device, because of the different partition schemes, a different processor and most of the hardware.

Other than those experiences, I have not experience with any of those other devices. I've seen quite a few posts over the past few years where users, for example, tried to flash roms made for a different device with very bad results.

The 5.1 devices used Intel Baytrail processors and the newer 6.01 devices use Intel Cherrytrail processors, from everything I know about them.

You might have better luck with the TWRP from the Ares 8, 5.+ and the 5.1 roms [MENTION=2472806]vampirefo[/MENTION] created for the device. In one of his threads he also has a repartition tool. I have not visited the Ares 8 threads since mine died, but there are about 5 threads concerning that device. [MENTION=2472806]vampirefo[/MENTION]'s lastest 5.1 rom ported to the 5.0 devices, which I had before it died, was working very, very well.

I'm not sure how similar the partition schemes and hardware are compared to the Ares 8, though.

If my memory serves me correctly: failed to mount '/data' (Invalid argument) can mean that the data partition is still encrypted, which would mean you would need to factory reset it or wipe userdata in fastboot so a new, unencrypted data partition can be created. That is assuming the new boot.img has been modified with either Android Image Kitchen or patched by SuperSu systemless to remove encryption and dm_verity.

These older versions of TWRP can't mount encrypted partitions, as far as I know. Newer versions, on some newer devices, can. [MENTION=2472806]vampirefo[/MENTION] made 2 versions of TWRP for the 5.+ devices and both worked very well.
[Miscellaneous Android Development] tcwiv:
[SOLVED]

[SOLVED] Thanks for the input - I thought I would follow up in the event someone else has faces the same challenge. I had inadvertantly flashed a recovery.img to my boot partition instead of the recovery rendering my 11A soft bricked. The following is how I managed too resurrect the device.

1) Flash Ares8A_twrp_recovery.img to recovery (fastboot flash recovery ares8A.......img)

2) Open twrp

3) Wipe all partitions

4) Repair all partitions

5) Clear cache

6) Download update.zip firmware (for your device) at Nextbookusa.com/downloads

7) Download the latest SuperSu.zip

8) NOTE: My install kept failing with 'Error 7 - Can't install this package over a newer build' as I was confident this was not the case I had to edit the updater script.* Open update.zip in winrar or 7zip and navigate to META-INF and find updater-script, change it to a .txt doc, open it in Notepad++ and remove the following line;

(!less_than_int(1477099312, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Oct 21 21:21:52 EDT 2016) over newer build (" + getprop("ro.build.date") + ").");

getprop("ro.product.device") == "NX16A11264" || abort("This package is for "NX16A11264" devices; this is a "" + getprop("ro.product.device") + "".");

9) Save the file, remove .txt and save the file back in the archive directory.

10) In twrp install update.zip

11) Install superSu.zip

12) Clear cache and reboot normally - it may take some time to boot the first time.

Hope that helps!
[Miscellaneous Android Development] martyfender:
I'm glad to see That you got it working. For your tablet and a few other older ones, Nextbook released updates. They did not for newer versions of the tablets. That is why I depend on my TWRP backed up roms to use as my stock, if I need to start fresh.
[Miscellaneous Android Development] JAGMAD_:
After getting this far and trying to flash the edited update.zip(removing: '(!less_than_int(1477099312, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Oct 21 21:21:52 EDT 2016) over newer build (" + getprop("ro.build.date") + ").");

getprop("ro.product.device") == "NX16A11264" || abort("This package is for "NX16A11264" devices; this is a "" + getprop("ro.product.device") + "".");'), The error code 7 was gone but I was getting a different variation of the error code? It still said 7 but got past 'can't install over newer build'. A fix would be appreciated, I'm super close to fixing my device besides this.
[Miscellaneous Android Development] tcwiv:
All of my issues went back to wiping and repairing all partitions in twrp.....I found myself having to do this multiple times to wipe out previous failed attempts. Do you have the actual error code?
[Miscellaneous Android Development] MerlinStWahgwaan:
Anyone have any ideas on how too fix a stock NX16A8A116K that wont boot?

I get bootloader error code 01 when trying too boot, and recovery mode wont load either... DNX fastboot does work, but developer options and usb debugging was never turned on so i cant seem too boot the TWRP.img in this thread....

Any ideas? Anyone have the .flash file to use the Intel Phone Flash tool too fix the stock OS?
[Miscellaneous Android Development] martyfender:
[MENTION=6741001]MerlinStWahgwaan[/MENTION] What did you do to the device to get to this state? Have you tried a forced shutdown and booting again to bootloader mode and with fastboot, flashing your stock boot.img? I have had something similar happen when trying to use the direct install method in Magisk. I alway use TWRP to flash it for that reason. However, I was still able to reboot to TWRP so something else may be going on. I rarely check this thread now so sorry for taking so long to reply.
[Miscellaneous Android Development] MerlinStWahgwaan:
I did not do anything particular... it worked fine for a while, wasnt used for about 3 months, and when i went to turn it back on, it started doing this EFI loader failed error.....

I have the intel flash software, and can get into fastboot, where both adb and the software recognize the device, but usb debugging was never on and it was never rooted, so I need to flash STOCK STOCK ROM onto it before I can do anything with it, but I cant sem too find the stock ROM for this particualr device ANYWHERE.... it should contain a flash.json file or flash.xml file, for intel phone flash tool to be able to use it too correctly to repair the damage.....

ANY IDEAS?? I cant find squat about where too get the stock ROM, the intel site eveyone send me too doesnt have it, only the owners manual, no other downloads....
[Miscellaneous Android Development] martyfender:
Nextbook never saw fit to release a stock rom so I have had to depend on my TWRP backups posted on androidfilehost as "stock roms". I believe I had, or still have the Intel Phone Flash installed on my Windows drive, but was never able to use it. I have not booted into Windows 7 in over 6 months or more. I always Run Linux Mint Mate as it boots and is much faster than Windows. I have access to the Windows drive in Linux, though.

Most of the time, a problem like yours is caused by something that the user did, for example, tried to flash a rom that was not compatible with our device, such as roms for the original Ares 8, which had Android 5 or 5.11, or other. I have that older device, but unfortunately, it died.

Can you boot into bootloader mode where you see the little green Android robot on his side? If so, you should be able to:

fastboot boot Ares8A_recovery_twrp.img

and be able to flash a twrp backup on your internal SD or external SD.

You may already have this setup correctly on your Windows system but it never hurts to check:

Both Intel Windows drivers and Adb and fastboot have to be installed properly. If they are not setup systemwide then you must run a command prompt from the adb/fastboot folder, where you also have vampirefo's Ares8A_recovery_twrp.img copied. In fastboot/bootloader mode, issue:

fastboot devices

hit the enter key and you should see the fastboot serial number if it is connected.

If you don't get this result, then there is a good chance that the Windows fastboot drivers are not installed properly. Sometimes, while booted into fastboot/bootloader mode, you have to go into the Windows device manager and select the Intel fastboot drivers, if they are not showing up there, I forget the exact name seen. I may have that info in the OP on how to set them up.

https://www.xda-developers.com/install-adb-windows-macos-linux/

https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
[Miscellaneous Android Development] N01F3AR:
So which files would I need to unlock the 8a 6.0.1 marshmallow with a 3.0.4 build number? I get the basic process just not understanding which files I'll need?? TIA
[Miscellaneous Android Development] Vijaypavi:
Can you please give me the link for of this Nextbook 8a tab it's v1.0.8

Can you please give me the link for the stock rom of this Nextbook 8a tab it's v1.0.8

---------- Post added at 11:41 AM ---------- Previous post was at 11:12 AM ----------

Can you please give me the link for the unrooted stock rom from Nextbook ares 8a v1.0.8.
[Miscellaneous Android Development] EL_FINO:
hello I have a table Nextbook 8a v1.0.8 .... the fact is that I also look for the rom stock ... I wonder if someone can provide me with the link ... greetings beforehand
[Miscellaneous Android Development] Online Gravy:
im currently trying to get root on my ares 8 tablet, it's a v3.0.4 running android 6.0.1. i followed the steps to get twrp running but twrp can't mount storage. i can't flash anything because of this. any advice on how to get twrp to work correctly?
[Miscellaneous Android Development] martyfender:
twrp can't mount storage, or can't mount data? Did you factory reset or delete the data partition, so a new, unencrypted data partition can be created. This version of twrp can't mount the original, encrypted data partition. That is why when you first root it, you have to do this. If there is important data there, you should have backed it up first. Twrp will not, however, delete your internal storage (internal sd card, unless you specifically choose that option.

Don't do that.

UPDATE:

It may give you a somewhat deceiving message of "can't mount storage when the data partition is still encrypted. I can't remember for sure, because that was a couple of years ago when I did the inital rooting of the devices.

On 4 out of the five devices I own, the external SD card reader has failed. My first v1.1.1 device just recently, totally died.

Because the external has failed, I now keep a twrp stock backup on the intenal SD. It does consume valuable space, but since Nextbook never released any roms, including fastboot flashable ones, the twrp backup is the only way to restore on 3 out of my 4 tablets.

I forgot to mention, please give me a response if this helps you or not. I hate spending time helping people and getting no feedback.

I don't check this thread very often, since this device is no longer made.

I am considering getting an 8" Onn tablet, since there is now a root solution for it, just not twrp, yet.

Thanks
[Miscellaneous Android Development] Online Gravy:
the data partition has been wiped multiple times but twrp just keeps saying "unable to mount storage" and "failed to mount /data". everything i flash errors out because it cant access storage, the /sdcard directory is empty in twrp. i left the system partition untouched. i was going to try flashing one of the roms with encryption disabled but the device stopped turning on after i left it to charge. it was fine when i shut it down but now it doesnt have any signs of life. the charging led doesnt light up anymore either. i wont be surprised if it died. also, i cant factory reset from within twrp because of the unable to mount storage error
[Miscellaneous Android Development] CrazyBugMJ:
Hello All,

I have the Ares 8A and it comes up with boot failed messages. Below is what I have done so far. Any help is appreciated.

*When I power on it fails with Boot failed message.

* The reset factory option itself is not there. When I hold UP & Power it does nothing. But when I hit DOWN and Power for 7 secs or more it comes with boot up screen and then shows me to select Android and only leads Boot failed message.

* I proceed with boot failed (hit OK) and it shows once more and I OK again and it allows me to select 2 options with icons. Continue and Boot From File. The other options Boot Manager, Device Management, Secure Boot Option, SCU are all not enabled or not able to navigate there.

* When I select boot From file, it allows me to navigate to my internal storage but <EFI> <Capsules> Loader.efi and this file selection fails.

* Going to EFI--> BOOT--> bootx64.efi fails too.

* I loaded the default 2017-07-01--01-36-33_V1.1.1.MMB29M.20161203.041025.zip into my SD card and placed inside the recommend foder structure in SD card and i can navigate in the table to this folder structure. But no files show up. I renamed this file to boot.img and renamed the file name above to .img or filename above.img and none of them shows the files.

*Extracted the zip contents and loaded into SD card with the same folder structure and still no files show up.

This has manufac date of Mar,2017 and running Android 6.0. It was brand new unit booted up with this error message.

All I need is to get to a running android version. Thanks in advance.
[Miscellaneous Android Development] martyfender:
[MENTION=10185833]CrazyBugMJ[/MENTION] It sounds like you have a newer version of the tablet than the v1.1.1 TWRP backup you are trying to load. You did unzip the twrp backup to /TWRP/BACKUPS/NX16A8116K/2017-07-01--01-36-33_V1.1.1.MMB29M.20161203.041025/All twrp files in here.

So a folder, within a folder, within a folder, with the files, four layers deep.

I believe you need one of my newer backups, though.. Volume down, power button should take you to bootloader/fastboot mode, with the green Android guy on his side. If you do boot to that mode you can see the bootloader version and IFWI version to post here. The IFWI version will give a clues as to the version you have. You boot to this mode from complete power off. From bootloader mode you can toggle the volume rocker to choose where to boot and to choose to boot to recovery. You then hit the power button to boot to the toggled mode shown.

Have you flashed or temp booted the TWRP recovery image from your PC connected in bootloader mode? You need TWRP to flash one of my backups and of course you need the proper Intel drivers installed and working on your PC to do this. If you did not, the stock recovery should still be there. These instructions are documented in the OP of this thread.

The mode you were in sounds like the boot manager efi mode which can only be used if you have a usbotg cable connected to a mouse and a keyboard, but that mode is not usually useful to most of us. You can boot to it from power off with the volume up and the power button.There is also another mode, FTM mode which I don't know much about, so it seems to be useless for us.

So the 2 modes you need to try to fix this are bootloader mode and recovery mode. And you need the twrp for recovery, as the stock one will not do what we want to do, except factory reset and a few others.

My v1.2.0 tablet was manufactured in March of 2017, with an IFWI version of M882_JJ.019.

My v4.0.3 tablet was Manufactured in May of 2017, IFWI version of M882_JJ.021_JJ . I posted the numbers of the most likely tablets you could have, but there are others which I do not have, or have not been made aware of.

All of them Have Android version 6.0.1.

Every brand new one I have had, booted to the DISA activation screen first, except for v1.1.1, before they added the activation code entry requirement. Yours appears to be v1.2.0 but there could have been some of the v1.2.0 tablets without DISA activation or one in between those 2 tablet versions, without it. The ones needing activation have a padlock symbol on the box. Where did you buy this?
[Miscellaneous Android Development] martyfender:
I just love spending time trying to help someone out here and getting no feedback whatsoever. It just makes me not want to help.
[Miscellaneous Android Development] Online Gravy:
I feel your pain, tried helping so many people that just disappear
[Miscellaneous Android Development] martyfender:
Exactly, and I responded the day after, not even: " I found another solution" etc. Oh well, this tablet is dead, anyway. I have moved on to the Onn 8 with Android 9 and it is so, so, much better.

I may eventually close this thread.
[Miscellaneous Android Development] Vortell:
Not sure why b you would close it. There are areas 8s for less then $20 on eBay right now. I appreciate the work that has been done do far since I bought one of those tablets.

Need to research it overheating though. All it does is turn down screen brightness though. :silly:

---------- Post added at 06:29 PM ---------- Previous post was at 06:02 PM ----------

My build is v1.0.1! What do I need to look for to get compatible TWRP or are I all v1 based use same TWRP image? And have you tried magisk for root ever? I will try to read more version numbers just confused me. Are you collecting system images for these somewhere? This is marked as a "live demo" and model #NX16A811DEMO. I assume sound loss it's based on chipsets it's there a list to reference for that info?