yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] MatterHatter:
I think my tablet is just bricked now and I'm just getting more confused. Nothing seems to be going right and the tablet still says No OS installed.

Edit: To answer a question for you from a bit ago about the IFWI ver. This isn't in the about tablet info since I can't get the tablet to load of course so it's from the bootloader screen. It says it's IFWI ver M882_JJ.016

Edit #2: Woohoo I finally got a system installed using the 1.1.1 folder you had up loaded. Now time to check if I can get WiFi and sound back.

Edit #3: Well the tablet is finally working with sound and WiFi. The build number has also been changed so far it looks like everything was successful.
[Miscellaneous Android Development] martyfender:
Since your original tablet was 1.0.7, that makes sense that any 1. Series should work, in my experience.
[Miscellaneous Android Development] MatterHatter:
Yeah I guess what happened was I thought I was following the steps but maybe my dyslexia was kicking in on some parts or I may have rushed a few. Anyway thank you for all the help you have provided and I'll still keep an eye on this thread as well. On a side note you know of anyways to help improve the tablet. Mine seems to overheat sometimes pretty quickly even from just light internet usage. Or point me towards some forums that may have the information I'm looking for.
[Miscellaneous Android Development] martyfender:
Here is the link to an old post in this thread:

Here is a list of apps I find useful:

https://xdaforums.com/showpost.php?p=72995672&postcount=112

On every tablet that I own, that is rooted, I install most of the apps I mention in that post.

Kernel Aduitor and L Speed are great. with L Speed I recommend you sign up for the beta on the play store and use it. The beta has most of the latest fixes and new features.

A couple of alphas were released in the last couple of days but alpha builds are only available on the L Speed alpha thread. Alphas are very early builds which often test new feature. The current alpha is causing more battery drain on the 8A, so, in general I recommend staying on the beta or stable version.

In recent weeks I have either bought or donated, in the case of L Speed to help these hard working developers continue development.

In recent months, my finances have been in much better shape than they were in the past. The developers really deserve something for their hard work and to continue future development.

If setup and used correctly, Greenify is a good app.

The only game I currently have installed on some of my Ares 8A's is GT Racing 2 Real racing. I have the Drastic DS Emulator installed on on older Ares 8 5.1.1 tablet, also.

I just re-read what you posted and I have noticed that more frequently where you get the message where the display is dimmed because of over heating.

I'm not sure how to solve that although tuning properly with Kernel Aduitor and L Speed can help in that regard.
[Miscellaneous Android Development] martyfender:
I'm glad that it has worked out for you with my V1.1.1 backup ROM. I may be wrong, but I feel that the previous versions you tried would have worked. I am thinking that due to inexperience or maybe dyslexia, maybe there was some user error in the previous attempts. I could very well be wrong, though.

The bottom line is that you have learned from your experiences an hopefully the current version will work for you.

In the recent weeks, I have purchased both a V2.1.5 tablet and a V3.0.4 tablet and they seem to work and perform much better and have much fewer issues than the older, V1.1.1 and V1.2.0 tablets.

The only real issues I have with the older versions of the tablets is with the Micro SD card mounting. The V1.1.1 in particular is troublesome in this regard, where as when it was newer it never has such issues.

Multiple reflashing of V1.1.1, V1.2.0, V2.1.5 or V3.0.4 ROMS has not solved the problem.

It may be due to an obscure hardware issue in that particular tablet. it works great in every respect, other than that.
[Miscellaneous Android Development] icyicy ice:
i have seemed to have soft bricked my tablet, is there any way i can fix this?
[Miscellaneous Android Development] martyfender:
Maybe, I need more details as to the version of the tablet you have, what you did to brick it etc.

[MENTION=8804681]icyicy ice[/MENTION] were you able to solve your issue? I haven't heard back from you?
[Miscellaneous Android Development] icyicy ice:
bricked

i bricked my device by accidentally formatting the device

so... i am running android 6.0 with the 1.2.2 update, and i have a backup of my tablet. but i dont have the /data files in the backup put the backup on my device it still did not turn on. i got all of the files back but do i need the /data for my tablet to work is there anything i can do to fix this?
[Miscellaneous Android Development] martyfender:
Where did you get the 1.2.2 update? I did see one other user mention a V1.2.2 tablet, if I remember correctly. On Android File Host I have V1.1.1 and V1.2.0. Every version of the tablet I have seen has Android 6.0.1 on them.

Using one of my modified boot.imgs or Using the official SuperSu systemless, instead of the unofficial SuperSu in systemmode patches the boot.img to remove encryption and remove dm_verity.

Once encryption is removed the original userdata must be deleted in order for a new, clean, unencrypted data partition to be created.

In the two backups I mentioned earlier, userdata has been removed.

I currently recommend using SR5-SuperSU-v2.82-SR5-20171001224502.zip, the official systemless version, with your original boot.img.

flashing this .zip in TWRP will patch your original boot.img so you don't have to use mine.

If your tablet truely is on V1.2.2 and you used either of my modified V1.1.1 or V1.2.0 boot.imgs, you could loose sound and possibly wifi and bluetooth.

In TWRP, temp booted or if permanently installed:

restore backup, uncheck data partition.

In bootloader (fastboot) mode did you:

fastboot format userdata

hit return, wait for sucessful completion message.

fastboot format cache

hit return, wait for sucessful completion message.

Booted into TWRP again, click install:

install: SR5-SuperSU-v2.82-SR5-20171001224502.zip

read to see that it successsfully backed up and patched your boot.img

click install again: install: Busybox-1.27.2-YDS-X86.zip. The above 2 must have been previously copied to either your external MicroSD card or to your tablets internal storage. Of course, it appears that you can't access the internal storage yet, as you can't boot to Android, so you have to use external SD card.

You must also select choose storage and select the external SD card in TWRP also.

If you can't do this then something is wrong and I will need much more detail info in all of the various steps you did to get where you are with it bricked.

I just re-read what you wrote and

Hold the power button for some time to force shutdown

hold the volume down and power button for some time:

does it boot into bootloader (fastboot) mode with the green Android robot?

Can you also boot into either temp TWRP or permanently installed TWRP?

When trying to boot up normally do you see the Nextbook boot animation?

if so is it continuous or does it eventually go to a black screen?

After formatting userdata and cache, first boot can take up to 5 minutes: you will see the boot animation for some time.

The first time patching the boot.img with SuperSu systemless will take a little longer time also and it will appear to reboot once in the process.
[Miscellaneous Android Development] icyicy ice:
ok i'll try that, and i read the bottom, it does load the animation and after that it does go to a black screen, but i'll try the top steps

and i guess i got the 1.2.2 update out of the box.
[Miscellaneous Android Development] martyfender:
[MENTION=8804681]icyicy ice[/MENTION] I have seen that black screen when the original boot.img was not patched or the system partition is erased. I'm sure there are other causes, also.

Did you install TWRP permanently or did you temp boot it?

I also saw the black screen on the first V1.2.0 I bought and returned. After testing it and rooting it I tried to restore the stock boot.img, the stock recovery and the stock system and it booted to a black screen. to get it to boot with the original stock I had to use my modifed boot.img to disable dm_verity. Apparenly it was detected as modified and therefore would not boot without Android Verified Boot disabled.

Since you system is already modified, I think it is best to have TWRP permanently flashed to replace the stock recovery, if you haven't already. Once flashed permanently be sure to go in to it's settings again and set your time Zone and language.

If you get it up and running again please go into: settings: about tablet: scroll to the bottom and give me the whole build number to confirm it is 1.2.2.

Also the listed Android version, IFWI version and the Kernel version.

As I stated earlier, If it truly is V1.2.2 you should definitely use the newer, SuperSu.zip systemless as it will patch the boot.img. My V1.1.1 and V1.2.0 patched boot.imgs will not work entirely with V1.2.2.

Your other option is to flash my TWRP backed up V1.2.0 userdata deleted version.

It is pre-rooted with older system mode SuperSU and has Greenify also installed as a system app, if my memory serves me correctly.

You then could use UnSu to remove the system mode SuperSu then flash SR5-SuperSU-v2.82-SR5-20171001224502.zip. and Busybox-1.27.2-YDS-X86.zip:

UnSU:

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

SuperSU:

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

This BusyBox I recommend over the popular, Play Store, Steven Stericson version, as it has no ads, is open sourced and is updated soon after a new Busybox source is released. If you ever get an error when flashing in TWRP, go back and hit mount and mount the system first then reflash it:

https://xdaforums.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

Once you get to the Android setup screen, set it up including Google account info, enable developer options again, enable USB debugging and enable su during boot, trust system user, enable pro features, go back and enable full logging, prompt, all in the SuperSu app.

UPDATE: I just did a restore and flashed SuperSu systemless and the first boot took 7 1/2 minutes to reach the Android setup screen.
[Miscellaneous Android Development] rafade31:
Hi , i have rootes my ares8a with magisk & it was fine just after update of magisk 15.0.zip it gone bootloop i reflash magisk 14.0 in twrp & dont fix it , so i reflash unmagisk.zip & restore /system stock but also nothing , i make a Factory reset it show red ligne in twrp failed to mount /data invalide argument ...i fix that by formating data with EXT2 then EXT4 as original FS was in , but now it not bootup with message (your device may not work proprly ...) with ⚠️ red ...so i restore /boot, /system, /recovery & reboot ...

but i have the same message ⚠️ can you halp me to fix it or send me link for stock rom please .
[Miscellaneous Android Development] martyfender:
First of all, do you know which version of the tablet you have? It is important that you flash a version in the same series. I have V1.1.1 and V1.2.0, so they are both from the V1.0 series. I have one tablet that is V2.1.5, so it is from the 2.0 series. The most recent version I purchased is V3.0.4, so it is from the V3.0 series

If you flash the wrong version on it you will loose sound and possibly wifi and bluetooth.

On my V1.1.1 tablet I now have the V3.0.4 rom on it but I lost sound from the external speaker and head phones. However, blutooth audio does work on it.

Also today I made the mistake, like you of testing Magisk V15.0 on it and it froze at the splash screen, just like yours.

I solved it by using the Magisk uninstaller.zip in twrp and then reflashing my stock boot.img followed by supersu.zip official, systemless version and it re-patched my boot.img and is working great again.

SR5-SuperSU-v2.82-SR5-20171001224502.zip

I have twrp rom backups of V1.1.1, V1.2.0 and V2.1.5. I have not uploaded the V3.0.4 because, as of yet, no one else has stated that they Have this version, or requested it.

If you never looked at the build number when your tablet was operational. one may be able to get some idea from the manufacturing date sticker on the box.

If you reflashed your original boot.img without letting supersu or a working version of Magisk, patch it, you are getting the Android verified boot failed message, it sounds like. dm_verity and encryption needs to be disabled.

You and I are not the only one who are having problem with Magisk V15.0. Many users are having the same issue as us on the Magisk forums.

I haven't tried Magisk since the summer and in both versions I tested, I would always loose root before 24hrs. passed.

I have not tested V14. Was V14 working for you on this tablet? I believe I tested V13.2 and V13.3 back in the summer, where root failed.
[Miscellaneous Android Development] rafade31:
I dont remember witch version is it (think is v1.1.1 ) i have the same tab ...& the files needed when i unlock/unencrypt/rooted first time it was whith SR1-superSU-V2.82...

For magisk it was fine rooted i just unrooted (i gues it was with supersu but it take lot time so i install other app to unroot it ) it & flashed magisk-14.0.zip in twrp +install manager & voila ...

In Fastboot screen it show me :

SECURE BOOT - DISABLED

LOCK STATE - UNLOCKED !!

it is normal !?

Mybe it help

Prod name : NXM882CAP

VARIANT : N/A

HW_ver-type1 - TBD BY OEM

BOITLOADER VER - Kernelflinger-02.20

IFWI VER - M882_JJ.018

SERIAL NUMBER - CHTT000158E1

#So doing the same steps i used in first time will fix [ADB,Flashing unlock,...Flash oldboot(8,87 Mo) ...!!??

Ps: i lose twrp coz try restoring recovery .

Thkx for replay
[Miscellaneous Android Development] NyTR0S:
I am having the same issue as he is I flashed the wrong version and had no sound so I tried to flush another image and now it is only bootlooping is it possible to find the version if I go to the backup where sound does not work at all if so if we have the same version is there any way you can send me the default image so I can try again with routing?
[Miscellaneous Android Development] martyfender:
I am at. Work, but I believe the V1. 1.1 tablet has the IFWI version. 018. You could flash my 1.1.1 backup on android file host.
[Miscellaneous Android Development] martyfender:
There are v1. 1.1, v1. 2.0, maybe v1. 2.2 v2. 1.1, v2. 1.5 and v3. 0.4, maybe more?

I need to know your version. IFWI version in bootloader mode will give a clue.

I'm home from work. The versions of the tablets IFWI are as follows:

V1.0.8 has IFWI MM882_JJ.016 I don't own this one.

V1.1.1 has IFWI MM882_JJ.018

V1.2.0 has IFWI MM882_JJ.019

V2.1.1 has IFWI MM882_????? I don't own this version. That owner may have possibly listed it in this thread with their post> my guess would be IFWI MM882_JJ.020

V2.1.5 has IFWI MM882_JJ.021_JJ

V3.0.4 has IFWI MM882_JJ.023_JJ

If what I stated earlier was not clear, the IFWI version is shown if you can boot into fastboot (bootloader) mode. Unless your device is really messed up, you should be able to boot to that mode, even if it won't boot into Android.

I recommend permanently flashing TWRP. I do recall having problems with the stock recovery when I restored it on a tablet that I returned.

reviewing what you wrote, once you unlock your bootloader, you don't have to unlock it again, unless you used the fastboot command to lock it again.

With the newest tablet I purchased, I realized that you only have to enable oem unlock in developer options, to unlock the bootloader.

Thanks to info that [MENTION=8479770]billybleu97[/MENTION] sent me in the recent past.

If both of you flash one of my backups in the same series as your tablet, ie V1.0 series or V2.0 series, I believe it will work for you. I have not, as of yet, uploaded my backup of my newest, v3.0.4 tablet, as no one else has posted that they have that version of the tablet.

If anyone has this newest version of the tablet and needs this V3.0.4, let me know and I will upload it.

I have never lost root on this tablet with supersu. The only reason I have tried Magisk again is that supersu was sold to a company that has not updated it in some time and I was willing to risk using my original, V1.1.1, to test it. I would stick with supersu until Magisk is fixed. So to be clear, for you, Magisk V14.0 was working fine, on this device?
[Miscellaneous Android Development] rafade31:
Yes magisk 14.0 was fine but first you should Unroot your tab then flash magisk_14.0.zip in twrp then install magisk manager for get module ..ect

I try [ xposed fwork x86 ] from magisk manager but nothing just going into bootloop

Just in case i have the same tab coz i purchased two so in that tab it is

1.1.0 MMB29M 2016.....

& IFW are the same M882.JJ.018

Thank you
[Miscellaneous Android Development] BigM69:
Just got my son the nextbook ares 8 for Christmas and it's so slow he can't really do anything with it. I need instructions on how to install twrp and root so I can speed it up using kernel auditor.. My tablet version is 2.1.1 I'm not sure which zip I need to download there's more than one. If anyone could help me pick the right files I would really appreciate it.

My IFWI version is M882-JJ.019

BUILD v2. 1.1 my IFWI matches v1. 2.0 So how is my build v2. 1.1 doesn't make sense to me..
[Miscellaneous Android Development] martyfender:
A quick update was released today for Magisk for apparent problems patching the boot.img on some device. This may solve it for our device. It is V 15.1. I will be reading the magisk threads before I even attempt it again on my older V1.1.1 tablet that I have relegated to testing new things. I have already installed roms three times this week, two times because of Magisk failure of unofficial builds and yesterday the official, version 15.

As far as xposed, there is, as of yet, no known version that will work on these devices because of a non standard implementation of ART. The author will not make special version for such non standard devices. I posted info and links previously somewhere in this thread.

Unknown versions of this tablet keep popping up. Since it has the same IFWI version, my backup V1.1.1 should be ok on it. I wouldn't put it on there unless you have problems later. Due to a corrupted Micro SD card back in July, I lost my first, virgin back up of my V1.1.1 device. The backup I have on AFH Is a system mode, pre rooted version with greenify installed as a privileged, system app.
[Miscellaneous Android Development] BigM69:
[MENTION=8126387]martyfender[/MENTION] i have adb fastboot/platform tools setup from when I flashed another device. I'll be using windows 10 on a hp laptop. Since I already have adb setup I don't have to worry about it right? I mean is there any difference in adb zips?
[Miscellaneous Android Development] NyTR0S:
Here ill just send you what my fastboot sais. (sorry for late reply i threw my mouse out of frustration and broke it.)

--------------------------------------------------------------------------

PRODUCT NAME - NXM882CAP_ES

VERIANT - N/A

HW_VERSION - Type1 - TBD by OEM

BOOTLOADER VERSION - kernelflinger-02.20

IFWI VERSION - M882_JJ.023_JJ

SERIAL NUMBER - CHTTBB398F59

===============================================

SECURE BOOT - DISABLED

LOCK STATE - unlocked

----------------------------------------------------------------------------

Hope that helps.

UPDATE: I managed to find a backup (the same backup where sound does not work but for bluetooth. Is there any backup for a moded system+root for the v1.2.0 version of the tablet? if so can you send me like a link or a pack with the steps of completely wiping the tablet and re adding the following:

Rooted+Unlocked Android 6.0.1

TWRP

SuperSU flash.

UPDATE2: So i got the right version this time (v1.2.0) and there is still no sound from speaker and headphones. What do i do in this case? I dont have a bluetooth speaker/headphones to use with this device. and i do not have a clean system image to work with.
[Miscellaneous Android Development] BigM69:
Ok, I have the SUPERSU zip downloaded. Where is the busy box zip I need? I'm also trying to figure out which TWRP I need. My build is v2. 1.1 and IFWI Is M882_JJ019
[Miscellaneous Android Development] martyfender:
You need the Intel drivers I linked in the OP. When the tablet is booted normally, Under Windows, go to the device manager. I believe it will show up as Intel Android Device:

Intel Android composite adb Interface.

When the tablet is booted into fastboot/bootloader mode It will show up as: Intel Android Device:

Intel Android Bootloader Interface.

If those two don't show up, select it update driver, browse my computer, let me pick, select.

I boot most of the time to Linux Mint, but my primary drive is still Windows 7.

I believe under Windows 10 you may have to disable unsigned driver for these to install.
[Miscellaneous Android Development] BigM69:
Thank you for your help I really do appreciate it!
[Miscellaneous Android Development] martyfender:
If you have IFWI VERSION - M882_JJ.023_JJ, then you almost certainly have a version 3 tablet such as my newest, V3.0.4 tablet.

You flashed a V2 rom on it so that is why you have now sound from the ext. speakers/headphones. Does wifi work?

I will prepare my V3.0.4 backup and upload it to Android File Host (AFH).

This may take some time because I have to zip it first and lately, sometimes AFH is down.

I will post a link when it is up.

I am uploading now it is usually slow, will post if there are no upload errors.

[MENTION=8813896]NyTR0S[/MENTION] Here is the AFH link for the V3.0.4 rom, unrooted. Flash it in TWRP:

https://www.androidfilehost.com/?w=files&flid=237933
[Miscellaneous Android Development] martyfender:
https://xdaforums.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

Choose this one from the download page: Busybox-1.27.2-YDS-X86.zip

There is only one TWRP ported to this device by [MENTION=2472806]vampirefo[/MENTION] and is included in my boot.img downloads and others.
[Miscellaneous Android Development] BigM69:
What if I don't have a SD card? Can I just put both the twrp and su in platform tools and flash twrp and then flash su?

---------- Post added at 04:33 PM ---------- Previous post was at 04:26 PM ----------

When I type in adb devices it shows my device is attached but out from it it says unauthorized

---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------

But when I click on command shell in startup menu it doesn't say unauthorized it says device beside the string of numbers. I'm assuming that I can flash twrp in c drive as long as the image file is in that drive correct?
[Miscellaneous Android Development] NyTR0S:
Yes I am getting wifi just not Sound through the internal speaker or the headphones.

Thanks man I really appreciate the help im getting here. see I JUST got this for Christmas and the same day i tried rooting it cus it was slow as S#)@*T I bricked the system.
[Miscellaneous Android Development] BigM69:
I have all 3 zips placed in downloads, since I do not have an SD card I hope I don't lose the zips when I start. First thing is unlocking the bootloader, then flash twrp then root. Well here goes I hope I get this right the 1st time[emoji16]