yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
I only used it for about 24 hrs. so maybe I didn't give it a fair shot. However, it seemed good at first, then I lost root, which was solved by rebooting. In the 1 1/2 years I have been on android, I never once had that happen with supersu. All I can say is try it and see for yourself. See a previous commenter on his experiences with it on a different device, in the past, also. Please let us all know your experiences with it and if xposed works with it on this device.

Thanks
[Miscellaneous Android Development] dorpmuller:
I lost root at random times over a period of ~1 month. That's why I quit it. JMHO: I wouldn't bother.

Rich
[Miscellaneous Android Development] TurnaboutSavage:
Well, I'm back from trying to see if xposed worked with magisk. From my experience, it works exactly the same as when I tried the first time, with that being said, it doesn't work sadly. Since we can't get it naturally, it'll just have to be custom made for this tablet, the the xposed installer apk and the framework zip file most likely.
[Miscellaneous Android Development] choose27:
That's weird. Magisk has worked like a champ for me. I installed it immediately. I'm on the old model using the 1.20 stock from the original post. Haven't lost root and I set up several Magisk Modules like the sony framework for remote play and folder bind. Xposed definitly does NOT work it actually bootloops the device. Just wanted to post this in case anyone wanted to install magisk and was afraid to after reading what you guys posted.
[Miscellaneous Android Development] martyfender:
Maybe I jumped ship to quick, but as I had never once had this happen with supersu, whether installed in system mode or systemless, I reverted. Also There weren't any features that the modules provide that I really need for my use.

Sometime in the future I may try it again when it is improved, though. Please keep us up to date in the future, if it continues to work for you. Maybe I had remanents left over from supersu. I believe I used the unroot option in supersu and flashed unSU also. From what I've read I probably should have started clean and reflashed the original, modified boot image, before flashing Magisk.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Sorry for only noticing this now, but you have the 1.20 boot.img running on a 1.1.1 ROM, does it work correctly, no lost WiFi or sound loss? Is it safe to flash 1.20 on 1.1.1?
[Miscellaneous Android Development] martyfender:
No, I have the 1.2.0 boot.img paired with the 1.2.0 ROM running on a 1.1.1 tablet. You have to use the same boot.img as the ROM. It will boot with that boot.img but you will loose sound, wifi, etc. There is a link for the 1.2.0 factory reset image in the OP. It should run fine on your 1.1.1 tablet. I tried the 2.1.1 ROM on my 1.1.1 tablet, but in that case, despite pairing its modified boot.img and ROM it looses sound, so I reverted to 1.2.0. The only thing I could see different with the 2.1.1 tablet is that it has a newer IFWI (Intel Firmware Interface) version, from the info that the owner sent me. I have V M882_JJ018 and his has V M882_JJ019. There could be hardware revision differences, but I doubt it. My guess is that the newer, 2.1.5 tablet version also has that IFWI version, or newer.

If you flash the TWRP backup img I provided for 1.2.0 you will loose any data you have created. It contains supersu SR1 2.82 in system mode and Greenify in privileged mode (system private app),

As I lost the original, untouched system version from a corrupted Microsd card, caused by using Easy Reboot (ROOT), by Simone Luconi which apparently isn't updated to work correct with Marshmallow. I now use Simple Reboot.
[Miscellaneous Android Development] flyboynm:
After trying this twice, I cannot get it to see any wi-fi networks. I verified I have the v1.1.1 version. I have rolled everything back to the backup image and tried it again but no wifi networks are seen. When I turn on wifi, nothing ever shows up. It just says "Turning Wi-Fi on..." and nothing comes up.

Any suggestions? It was working in the original version of Android.

Edit: I bricked it. When I try to boot into recovery, I get the dreaded Android with a red exclamation point and "your device has failed validation and may not work properly" message. I am out of the country until October sometime and can't do a RMA until I get back to the US.

Any of you got some ideas here? I can get it to the bootloader screen without problem.
[Miscellaneous Android Development] martyfender:
After you flashed my modified boot.img for the 1.1.1 tablet: Ares8A_Old_boot.img,

Did you boot into bootloader mode and issue:

fastboot format userdata

hit enter, wait to complete.

then:

fastboot format cache

hit enter, wait to complete.

Then:

fastboot reboot

hit enter, to reboot to the android setup screen to start fresh.

The data partition needs to be wiped to create a new, unencrypted data partition, at boot.

If that doesn't work then there is a factory reset 1.2.0 twrp backup ROM linked in the OP, that you can try.

Both will wipe your userdata which is what is needed to create a clean, unencrypted data partition. They boot to the Android setup screen, to start fresh.

Please let me know your result.
[Miscellaneous Android Development] martyfender:
[MENTION=5074186]flyboynm[/MENTION] You got that message because you flashed the original boot.img with a modifed system image.

try to flash my modified boot.img first in bootloader mode:

fastboot flash boot Ares8A_Old_boot.img

then:

fastboot format userdata

hit enter, wait to complete.

then:

fastboot format cache

hit enter, wait to complete.

then;

fastboot reboot

hit enter, to reboot to the android setup screen.

Or try the newer 1.2.0 twrp backup I posted in the OP (Opening Page).

The twrp backup must be placed in your twrp backup folder, on your ext sd card, in the proper hierarchy, to be recognized in twrp:

/TWRP/BACKUPS/NX16A8116K/2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208/

My suspicion is that you didn't format userdata and cache after flashing my modified boot.img the first time, to create a new, unencrypted data partition. Deleting data is a necessary evil of this procedure.
[Miscellaneous Android Development] flyboynm:
I did the commands both times. I am working on downloading that ISO. I have Fiber Internet but it still says 3 hours to download. :(
[Miscellaneous Android Development] martyfender:
Wow, that is hard to believe on a fiber connection. I have a 15mbs Spectrum cable connection and it usually only takes a few minutes to download. It could be a problem at android file host, also. If you are using wifi, that could be another potential bottleneck. I have a direct connection on my Windows/Linux Mint Mate desktop.
[Miscellaneous Android Development] flyboynm:
Sad but true:

http://www.speedtest.net/my-result/6512804038
[Miscellaneous Android Development] martyfender:
You didn't, by chance flash the version for the 1.2.0 tablet: Ares8A_Newer_boot.img did you?

Time to leave for work.
[Miscellaneous Android Development] flyboynm:
No, I didn't.
[Miscellaneous Android Development] martyfender:
Another user had the same issue and it was resolved with the 1.2.0 backup you are downloading.
[Miscellaneous Android Development] nphektor:
i have this tablet, and was in process of installing TWRP & SU when something went wrong. It now boots to the "failed verification" message, and I can get it into the EFI bootup mode but after that it goes to the "fail to verify" and then blackscreen.

how do i get it into fastboot or other mode necessary to "unbrick" and try again?

i DID get a full backup made of the original partitions, and I assume they are good backups.
[Miscellaneous Android Development] martyfender:
From complete power off, hold volume down and the power button to boot into bootloader mode.

Also did you flash my modified boot.img, (using the correct version for your tablet version)? Failing verification sounds like you still have the original boot..img on the tablet. The modified boot.img removes encryption, makes the kernel permissive and removes dm_verity or the verification you are experiencing. [MENTION=8459971]nphektor[/MENTION]
[Miscellaneous Android Development] martyfender:
What version of the tablet do you have?
[Miscellaneous Android Development] flyboynm:
Marty - the long download file worked. Thank you again!
[Miscellaneous Android Development] martyfender:
I'm glad to hear that! So the 1.2.0 backup was what you had success with? As I stated earlier, you are the 2nd person with no wifi that was fixed with the 1.2.0 backup. By chance, did you check sound when you had no wifi? Did you have no sound? If so I may need to re-examine the boot.img for the 1.1.1 tablet version for any mistakes that could cause this. Let me know. Thanks.

I just checked the 1.1.1 boot.img and I can't find any obvious errors in the edits I did.

I am now wondering If one boots to recovery after deleting userdata and cache in fastboot and flashing supersu first, would make a difference on the 1.1.1 tablet, instead of boot to unrooted android first. I'm not sure, but I have done that before and it has worked for me.

However, I have been on the 1.2.0 rom for sometime and reflashed it several times with no wifi issues, so maybe that is the solution. When I was still on 1.1.1 my instructions worked fine for me as long as I formatted userdata and cache in fastboot, first. I did get errors when I didn't do that the first time, because the data partition was still encrypted.

If anybody has any other thoughts about this, please let us know.

Thanks
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] [MENTION=4798480]thejunkie[/MENTION] I am still appealing to the 2.1.1 and 2.1.5 tablet owners I have asked, to upload the supersu systemless, modified boot.imgs to me, backup boot only in TWRP.They are very small files so they shouldn't use much bandwidth. Just zip them first, upload them to google drive or other file sharing site and provide a link for me to download. Please label them clearly as to version such as: supersu211bootimg.zip, for example.

Thanks
[Miscellaneous Android Development] TAcrolimus005:
Is there a way to speed up the tablet or make it capable of handling more than 1 app at a time? Your install instructions worked flawlessly, THANK YOU! I have a v1.1.1
[Miscellaneous Android Development] martyfender:
Use lspeed govtuner performance profile, for one. kernel aduitor for vm tuning, IO scheduler tuning, Androids low memory killer (LMK) etc.

Use Greenify to hibernate apps that run in the background. Don't hibernate apps such as lspeed or kernel aduitor, as they have services that need to run regularly. Don't go crazy hibernating every app though. I keep standard doze as aggressive doze is controversial as it's benefits may be negated upon wake with more sluggishness after wakeup as services that usually run during standard doze will wake up and try to catch up, so to speak.

The lspeed xda forums have a lot of info on the use of the program, for various use scenarios. Battery v.s performance, multitasking etc.

https://xdaforums.com/apps/l-speed

Here is a link to my post on programs I have found useful:

https://xdaforums.com/showpost.php?p=72995672&postcount=112
[Miscellaneous Android Development] martyfender:
SuperSU v2.82-SR2 released

SuperSU v2.82-SR2 released. This is the systemless version:

https://xdaforums.com/showpost.php?p=73327315&postcount=10762

Here is a link for the systemmode version:

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

Release notes

https://plus.google.com/+Chainfire/posts/YCoHDpNaY38

There is a new, optional install mode: SBIN mode. This mode is for the systemless Supersu version.

If any of you decide to test SBIN mode, please report how it works.

Thanks
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] I'm gonna see how all these SuperSU files work on v1.1.1 and report back!
[Miscellaneous Android Development] martyfender:
I've used the previous version both in system mode and systemless with great results. So far, as always with SuperSu for me, the new version is working great in system mode. The thing I am curious about is the new option, SBIN mode. You either have to enter a command in adb before you flash it or you can open the terminal app in twrp, enter the command, then flash it, to get SBIN mode.

"To enable it on N and M, you need to execute the following command in ADB shell before (re-)flashing the SuperSU ZIP:

echo "BINDSBIN=true">/data/.supersu
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] K, I'm on it
[Miscellaneous Android Development] martyfender:
"To enable it on N and M, you need to execute the following command in ADB shell before (re-)flashing the SuperSU ZIP:

echo "BINDSBIN=true">/data/.supersu

Type adb shell before executing it, if you do it from your computer and adb.

I believe if you do it in twrp you just need to enter the command in it's terminal.

If you test SBIN mode, let me know how it works. There may be some apps that don't work properly with it. I am curious which ones, besides the one [MENTION=631273]Chainfire[/MENTION] mentioned in his release notes: FlashFire, one of his apps.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] OK, I'm back from enabling sbin mode in supersu. I'm on my 6th reboot. While my tablet isn't rebooting, I've tried to give apps root access, but my phone keeps rebooting, while I'm typing this my tablet keeps rebooting, I might have messed it up XD
[Miscellaneous Android Development] martyfender:
Hopefully, you did a twrp backup before doing this. I should have mentioned that as I can't always assume the obvious. If not, have you tried reflashing supersu systemless without the command options? And also, wipe, advanced wipe, check dalvik cache and cache boxes, only, before you reboot after flashing supersu systemless. then reboot. You did use the supersu systemless or this, right and not supersu system mode?
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] OK, I've made the horrible decision and force made supersu a system app, when by default it can't be, I've made a backup and I'm fixing this. Before I made that mistake, the sbin mode was working very well.
[Miscellaneous Android Development] martyfender:
How did you make it a system app? The system mode supersu, makes it a system app, but I don't believe you should use supersu system mode with the command line options, as I believe they were intended for supersu systemless installer and SBIN mode is a systemless install in data. [MENTION=631273]Chainfire[/MENTION] installer installs in systemless mode, by default on Android 6.0 and newer.

The system mode supersu is an unofficial installer created by a user to force system mode on Marshmallow. It usually doesn't work for newer, Android N or O, in general.
[Miscellaneous Android Development] TurnaboutSavage:
I used lucky patcher to make it a system app, I'm regretting that XD
[Miscellaneous Android Development] martyfender:
What was the reasoning behind that? Some apps don't benefit by being a system app. One example is Greenify, but there is a specific way to do it for that app which involves copying it's app data folder to system/priv-app/ and changing folder and file permissions to match the permissions of what they are in the /data/app/com.oasisfeng.greenify-1/. That is also the manual way to make an app a system app. That is the only app I have made a system app, myself, with the exception of supersu in system mode, but it has a special, install location, in system/xbin/. It can be risky making an app a system app with out evidence from others, to it being beneficial for that app. Many apps don't benefit by being a system app, on a rooted device, as they can already have su privileges.
[Miscellaneous Android Development] TurnaboutSavage:
Idk, I just want to see what happened.
[Miscellaneous Android Development] martyfender:
If you have a good backup, you can do that, but even twrp backup restores can have their problems. I had that happen after I reverted from a magisk install. I had to to reflash my deleted, userdata version backup and start over, as I had a system error at boot. It booted to android ok but had this error message about problems with the system. I might have been ok if I had just reflashed my modified boot.img after running the magisk uninstaller, who knows? Somehow, something was modified, that wasn't reverted by the backup flash. The failed backup restore, had supersu systemless, which had worked quite, well, before the backup.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] I just restored, all is well again.
[Miscellaneous Android Development] martyfender:
That is good to hear, I have to work tomorrow at 2:00PM, so it is time to hit the hay. Good night.
[Miscellaneous Android Development] HERPDERP202:
Need help

does anyone have the stock rom and how do you view the version of what you're on i bricked my device but i got twrp working :eek:
[Miscellaneous Android Development] martyfender:
Do you have the box the ares 8A came in? If so, there is as manufacturing date on it. That might give some clue. Linked in the op is a twrp backup of the 1.2.0 tablet version. It will work on the 1.1.1 tablet also as I have the 1.1.1 tablet and am running the 1.2.0 rom on it.

The twrp backup must be placed in your twrp backup folder, on your ext sd card, in the proper hierarchy, to be recognized in twrp:

/TWRP/BACKUPS/NX16A8116K/2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208/

Since your tablet is bricked you would need to place the external micro sd card in a card reader in a computer and create a folder called TWRP. Inside it another folder called BACKUPS and inside that, yet another folder called NX16A8116K.

The folder inside the zip archive: 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208, which contains the backup files themselves, must be inside that last folder. So the full path is:

External SD card//TWRP/BACKUPS/NX16A8116K/2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208/ all files inside that last folder. Place it back into the tablet, boot the tablet to twrp and click the restore button. make sure the external sd card is selected and find your 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208 backup and restore.

What were you doing to cause it to be bricked? Do you get the Nextbook boot animation screen when you try to start it? choosing the factory reset in twrp, could solve your problem,how ever that may depend on how you bricked it?

I really need more info Though.
[Miscellaneous Android Development] HERPDERP202:
Will try

I Will try it thanks :)
[Miscellaneous Android Development] martyfender:
If you have a tablet version 2.1.1, or 2.1.5, that backup will probably leave you with no sound, so try the other thing I mentioned first. also flashing the proper version of my modified boot.img may solve it also. However, if you don't know your tablet version, how can you select the proper one. And you didn't answer my question: how did you brick it? If you downloaded my files you surely checked your tablet version and downloaded the one for it's version, didn't you? My original archive has boot.imgs for both the 1.1.1 and 1.2.0 tablets, labeled: Ares8A_Old_boot.img for the 1.1.1 tablet and Ares8A_Newer_boot.img for the 1.2.0 Tablet. Later I released one for the 2.1.1 tablet and the 2.1.5 table.
[Miscellaneous Android Development] HERPDERP202:
i need an activation code?

---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------

sorry i was in a rush someone gave it to me and it was bricked and i have no clue which version it is
[Miscellaneous Android Development] martyfender:
That activation code was printed on your receipt only for tablet versions 1.2.0, or newer. If you already activated it you have a tablet newer than 1.1.1 and usually doesn't ask for activation a second time.
[Miscellaneous Android Development] martyfender:
Did you look on the box for the build date sticker? Also, a tablet newer than 1.1.1 has a padlock symbol on the box stating it needs to be activated the first time it is run.
[Miscellaneous Android Development] HERPDERP202:
i dont have the box neither do i have anything just the tablet
[Miscellaneous Android Development] martyfender:
Without that info, I believe I have given all of the help I can until you can provide more info.

Boot into twrp and do a factory reset, first. I believe you do that by hitting the wipe button, then swipe to factory reset, then reboot.

Did you install twrp permanently in bootloader mode, by issuing:

fastboot flash recovery Ares8A_recovery_twrp.img

Or have you temp booted it by issuing:

fastboot boot recovery Ares8A_recovery_twrp.img

?

Also, are you certain it is an Ares 8A and not an Ares 8? The Ares 8 uses completely different files, found in another thread. The Ares 8A has Android Marshmallow 6.0.1 and the Ares 8 has Android 5.0 or 5.1.1 lollipop.

The Ares 8A only has a physical power button and volume button. The Ares 8 has a home button, a power button and a volume button.

I own both tablets.
[Miscellaneous Android Development] HERPDERP202:
yes it had android 6.0 and i actually got the activation to go away by uninstalling the setup wizard and oh boy was that a trip trying to do
[Miscellaneous Android Development] martyfender:
Then how do you setup android without the setup wizard? There is actually a website you can go to if you have the disa number from the box of the device to get the activation code. I don't remember what it is as I returned the 1.2.0 tablet after I pulled from it.

I found it with a google search:

http://www.getyourcode.com/

The DiSa Number can be found on the back of the unit.

my guess is that the activation is firmware based, however when I still had the 1.20 tablet, the only time I saw the activation code again was when I restored the stock recovery before returning it. So it may be in the stock recovery.

I run the 1.2.0 rom on my 1.1.1 tablet and have never seen any sign of it on it.

I'm still wondering what negative effect it my have removing that. On mine, under system apps I find startup wizard. Is that what you removed? Did you do that in twrp?
[Miscellaneous Android Development] HERPDERP202:
Ok so i went into recovery and used adb sideload to edit default.prop to enable adb then after that i went into the system and comfirmed the rsa key and adb to launch the settings to log in googleso then i went into play store using adb to uninstall setup wizard which was the cause of everything being lockdown how i noticed is when i forced stop setup wizard i got the navigation bar so i downloaded a root uninstaller and uninstalled setup wizard and boom working tablet and i didnt have to set it up :confused:
[Miscellaneous Android Development] martyfender:
Now that you did that are you able to change settings ok in settings app? Also what version of the tablet shows in setting: about tablet? Scroll to the very bottom, it is listed as the first few numbers of the build number. Mine, for example, is: V1.2.0, since I have the 1.2.0 rom on it.
[Miscellaneous Android Development] HERPDERP202:
I put the 1.2.0 rom so it probably was and yes settings work fine everything does
[Miscellaneous Android Development] martyfender:
So sound, wifi and bluetooth are all working? If that is the case you must have a 1.2.0 tablet, if you were seeing the message to enter the activation code at startup. I believe if you flash the 1.2.0 rom on a 21.1 or 2.1.5 tablet., you would have lost sound and maybe wifi an bluetooth, based on an owner report previously. That is, if I am remembering correctly. Did you remove the setup wizard after you flashed my backup, 1.20 rom?
[Miscellaneous Android Development] SgtWhoop:
Wifi, Sound, and Bluetooth

I have did this and now have no Wifi, sound, or bluetooth. Has anyone found a fix for it? I'm reading through this forum trying to figure it out.