yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
Here is the link to download the boot.img :

https://drive.google.com/open?id=0By0mLSbF9jhcRHpXdk0tSjZMVzg

unzip it to your computer where you put the twrp recovery files to fastboot.

Have the supersu.zip I linked to you on your external sd card also.

boot into bootloader mode and from the windows command line:

fastboot devices

then hit enter and your device # should be listed. Then:

fastboot flash boot unsigned-new.img

Hit enter to boot and test. don't reset up if you boot to the setup screen reboot to bootloader mode and

fastboot boot Ares8A_recovery_twrp.img

enter, or if you already flashed it permanently:

fastboot reboot recovery

and hit enter.

Once booted into twrp hit install, choose micro sd card, ok select the SuperSU-v2.82-201705271822.zip then swipe to flash it. Read the messages carefully to confirm it patched the boot.img sucessfully. now hit the twrp home button, hit wipe, advanced wipe and choose dalvik cache, cache and data only. you need the userdata deleted so android can create a new unencrypted data partition.

Do not select the system or you will wipe it.

Now choose reboot in twrp to reboot and setup android. Please report to me asap if it was successful or not or if you have and question. I work tomorrow afternoon 2 PM to 11 PM EDT so I am available only at breaks and dinner hour and of course, before and after work.

Good luck

Update: [MENTION=4798480]thejunkie[/MENTION] I backed up my current system and flashed your 2.1.1 version to my tablet. I am setting up android as I type. Be very patient the first time it boots It can take several minutes the first time. I thought it was stuck in a bootanimation bootloop, but it eventually booted to the android setup screen. that is result of supesu patching the boot.img and userdata being deleted.

The next reboot should be fast and thereafter.

I just realized that I have no sound on my device, so it may not be compatible after all. I don't see why yours wouldn't work, but please let me know. I guess I'll have to reflash my backup.
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] I have found out that I didn't modify the sepolicy file in the boot.images I provided and do not have the necessary skills to do so. That, so I am told is why it bootlooped for you with the system mode supersu.

Apparently the systemless install of supersu modifys that in the boot.img that it recreates to avoid that issue. So I was told to have you redo a twrp backup of just the new, now, supersu modified boot.img and it will solve the issue in the future.

Do you have enough data to backup the new boot.img only in twrp and post it as soon as possible so I can replace it with the one I uploaded yesterday?

Let me know, either way. I would like to get my hands on one of the newer versions of the tablet, but I don't think we have any yet in the Indianapolis store, where I work.

I have just found out today that there may be 4 or 5 different versions of this tablet, so as I receive the boot.img from users, I will have to modify each one.

This is becoming a real challenge now.

Thanks for all of you help

Thanks again
[Miscellaneous Android Development] martyfender:
"I have found out that I didn't modify the sepolicy file in the boot.images I provided and do not have the necessary skills to do so. That, so I am told is why it bootlooped for you with the system mode supersu.

Apparently the systemless install of supersu modifys that in the boot.img that it recreates to avoid that issue. So I was told to have you redo a twrp backup of just the new, now, supersu modified boot.img and it will solve the issue in the future.

Do you have enough data to backup the new boot.img only in twrp and post it as soon as possible so I can replace it with the one I uploaded yesterday?

Let me know, either way. I would like to get my hands on one of the newer versions of the tablet, but I don't think we have any yet in the Indianapolis store, where I work.

I have just found out today that there may be 4 or 5 different versions of this tablet, so as I receive the boot.img from users, I will have to modify each one.

This is becoming a real challenge now.

Thanks for all of you help

Thanks again"

This message was intended for another user as he has the original 2.1.5, sorry

Thanks for sending the 2.1.1 system files to me. I will backup and flash it on my device to see if it works on my older tablet and eventually upload it to my android file host site to provide a backup for others, especially those who have made stupid mistakes in trying to do this procedure. in the future, I would recommend you zip those files before upload to save bandwidth and space, or, at least it didn't appear you did that because g drive zipped it before it was sent to me.

Again, good luck.
[Miscellaneous Android Development] TurnaboutSavage:
So I uploaded a YouTube tutorial for how to root this tablet for v1.1.1 + v1.2.0, and for the most part I've gotten positive reception. Except that somebody else is wondering if Xposed can be made/used on this tablet, this is what I said back to him. Hope fully we can get one made soon, but as of right now, nope.
[Miscellaneous Android Development] dorpmuller:
I'll have to check today. Fastboot is working fine on Windows 10. Had no trouble unlocking the bootloader.

None of the files will load in fastboot. Can't load the twrp either. Hear's the dope:

Kernel is what you posted. Security is 8/16. Model is nx16a8116k. Build # is v1.08mmb29m.20161107.053713 . IFWI version m882_jj015 . I repeat, fastboot, adb are all verified working.

Thanks for the help!
[Miscellaneous Android Development] thejunkie:
Yeah sorry heh.. ill keep following this, hopefully you find the solution quickly
[Miscellaneous Android Development] martyfender:
Apparently it is incompatible with my version of the tablet. Everything is working on my device except sound. So I am at a standstill until you flash the boot image, flash systemless root to patch the boot image and set it up to confirm that sound is working, which it should since you provided me with the original boot image that came on the device originally. I assume you didn't try to flash one of my other versions of the boot image and send that one instead of the original that came on the device correct?

[MENTION=4798480]thejunkie[/MENTION] Here is a slightly updated boot.img to use instead of the first one I linked:

https://drive.google.com/file/d/0By0mLSbF9jhcZDd3TklIV3pvMVk/view?usp=sharing

Thanks
[Miscellaneous Android Development] martyfender:
I'm not sure why fastboot is not working then. You were in bootloader mode where you see the green android guy against a black background?

If so what is the result of typing fastboot devices? did you unlock your bootloader by going into developer options enable it then reboot into fastboot and issue:

fastboot flashing unlock

hit enter

you should get successful prompt of some kind.

You will know it is unlocked by message and when you reboot you should get the android setup screen, again.

Some devices use:

fastboot oem unlock

hit enter

but I don't think your slightly older version than mine would fall into that catagory. When you just type fastboot, you should see a list of available fastboot commands.

Did you setup adb and fastboot with this system wide installer?

https://xdaforums.com/showthread.php?t=2588979

Did you open the adb folder, right click to open a command prompt here?

And finally, are the files you are flashing in that same adb folder?

If none of this works then I am at a loss as to what is wrong.

when you are booted normally and issue:

adb devices

you are seeing the device serial number listed?

Is usb debugging enabled in developer options on the tablet?

and when you plug into the computer and issue adb commands, you should see a security prompt popup on the tablet to approve to allow adb and fastboot to work with it. Did you see that and did you check the box to always allow?

I have been using Windows for years and have worked on a few Windows 10 machines my self.

Over the 1 1/2 I have been on Android I have seen more users having problems getting adb and fastboot working correctly. Did you allow it to use unsigned drivers?

When you go into device manager do you see Intel adb and fastboot listed there?

I believe, if my memory serves me correctly fastboot will only show in the device manager when the tablet is booted into bootloader mode.

My machine is Windows 7, but for the last month I have been using Linux mint mate, running on a persistent, bootable, 64gb, usb key to test.

I may eventually install it to my hard drive and duel boot it.

I am loving it. It boots and runs much, much faster than Windows 7 and that is from a slower usb key. There is a learning curve but Mint is pretty user friendly with a great gui. I have full access to my windows drives from it also.

Looking at a twrp recover log, apparently that is the version of the tablet that the author [MENTION=2472806]vampirefo[/MENTION] , who ported twrp to these devices had to build it with.
[Miscellaneous Android Development] thejunkie:
I sent you the original, one that was on my tablet. Is the one you provided the one i should flash on my new tablet? And see if everything works?
[Miscellaneous Android Development] martyfender:
Yes, the newer one I linked today: unsigned-211.img.zip and you must also flash SuperSU-v2.82-201705271822.zip to patch the boot.img also. Let me know how it goes. test sound, wifi, bluetooth, if you can, etc.

If there are problems, boot into bootloader mode and issue:

fastboot format user data

Hit enter and wait for successful completion, then:

fastboot format cache

enter, wait for successful completion, then reboot to the fresh, android setup screen and setup the tablet, then test the fuctions again. Please let me know asap.

Thanks
[Miscellaneous Android Development] martyfender:
I think I linked you my bad experiences with it on my original ares 8 5.1.1, so I won't try it again on this newer device if one is made for it. The features it allows is just not worth it to me as it can create many incompatiblities.

What features are you wanting from It?

I recommend tuning the device with Kernel Aduitor, lspeed and greenify, for starters.

And the latest dev. version of adaway on xda to block ads primarily in web browsers. It won't block youtube ads though. It will block ads in some apps and games though, but not all.

See my post about adaway on the lspeed xda thread:

https://xdaforums.com/showpost.php?p=73141787&postcount=27740
[Miscellaneous Android Development] thejunkie:
here is what i di, i used the tablet i had from last night, that i originally messed up and couldn't get to work so i wouldnt mess up the new one i bought after, i used for flashing a backup..

i flashed twrp again, i used your new boot image you made, and flashed it, booted into twrp and flashed supersu, and guess what

it works, flawless, thanks

---------- Post added at 10:06 PM ---------- Previous post was at 09:48 PM ----------

just did the same on the new tablet, and its the same, works nicely
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] I'm wanted to be able to use the lucky patcher module, and anything needed to make my device faster. If you can so this, I'll make sure everyone knows
[Miscellaneous Android Development] martyfender:
First of all, I believe that is a forbidden topic on xda because it is used to crack paid programs and games. However, I did try it briefly on the ares 8 with android 5.0. It sometimes worked but it can eventually f up your tablet. If you discuss it on xda mods may ask you to stop.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Nonononono, I'm not trying to crack apps, I'm just using to to delete system apps, and make certain apps /system
[Miscellaneous Android Development] martyfender:
I'm glad to hear that, congratulations. All is working, including sound? Can you once again backup the boot. Img in twrp, zip it, named something like 2.1.1-patched and upload it, as it is the final I should upload for your version of the device. Check boot only, in twrp to back it up. Supersu patched selinux permissive, which is the final piece of the puzzle I need for your device.

Even though I had your matching boot image and system, It was not compatible with my tablet.

Everything worked except sound. I notice yours has a newer IFWI version. (Intel Firmware Interface).

Maybe that is the difference between versions of tablets. I'm not sure as I believe the hardware is the same, uless there are different revisions of the chipsets or other board aspects.

Thanks, again
[Miscellaneous Android Development] martyfender:
I've used several apps for that, so far, is apps2sd by Vicky Bonick. I use it to create a 2nd partition on my sd card to move large apps only, such as games, however, it has many other features such as deleting system apps, converting user apps to system and converting system apps to user apps. Check out its features as there are many more. Search apps2sd xda on google.
[Miscellaneous Android Development] NemoCoOW:
[MENTION=8126387]martyfender[/MENTION] any ideas on how to deodex this device? I've tried several methods and for some reason the deodex checker app says it's deodexed, even though it's not. I looked through the file system, it seems the odex files are located in /system/framework/oat/x86.

I have the old v1.1.1 build, I rooted using magisk and I've used it for a few weeks without any problems, at least not related to magisk, i don't think..

I need deodex for signature spoofing to use microG, etc.

EDIT: The location of the odex files might be the result of an ART optimization module I installed for magisk
[Miscellaneous Android Development] martyfender:
I have no idea as I've never done it. a search brought this link up:

https://xdaforums.com/android/general/guide-deodex-marshmallow-6-0-completely-t3403544

I see the above method uses linux. I have been using linux mint mate for the last month and am loving it.

I used the universal usb installer to create an ntfs formatted, casper-rw, persistent usb key to test linux. So I have full read and write access as if linux was installed to the hard drive

Using ntfs allow file sizes larger than 4gbs and to create a larger persistent partition for linux. I have it on a 64gb key, but a larger one would be better. I probably will eventually install it to my hard drive and duel boot. I rarely use window 7 now that I am using linux. It boots and runs much faster, despite being on a usb key.

I don't know much about what the advantages of using magisk either, as I've never used it either.

Besides the above what are some of the advantages of using it?

I was looking at it's repository, but not sure if any of it is of use to me, so fill me in on it.
[Miscellaneous Android Development] NemoCoOW:
The main advantages of magisk, at least for me, is the ability to disable root and/or hide it for services that require an unmodified system. I've only recently started using it and it works quite well. The developer constantly updates it to make sure it stays on top of Google's various new attempts at detecting it. It also has a module system very much like Xposed framework and also has official support for systemless Xposed

I remember I used to have Linux Manjaro on a USB stick similar to your solution, really useful. I now dual boot my laptop with Windows 10 and Manjaro and run Windows 10 on my desktop for gaming. I also have a USB stick with Tails installed in case I need to use Linux on a different PC. Manjaro, if you are wondering is based on Arch, Mint is based on Ubuntu, correct? I remember trying it out a few years ago, back when it was a lot more closely related to Ubuntu. Does it still use the xfce DE or has it switched over to KDE or cinnamon? I might give it another shot if it still supports xfce, since I'm thinking of switching to a Debian based distro because of the support.
[Miscellaneous Android Development] martyfender:
[MENTION=7117847]NemoCoOW[/MENTION] I see reading about tails that it is for privacy. I would rarely ever use mine on another machine, but what kind of things would be revealed using my version on another machine. I am in the United States so I don't have to worry to much about censorship and I don't do anything that I believe I have to worry much about. I have used Mint with lastpass to pay online rent, electric, internet, auto insurance etc, but that is about it. I rarely ever order anything online.

I'm just curious, what apps require you to hide root with Magisk? I haven't used any, yet and I'm not sure if I will, in the near future. I do read a few xda forums regularly and I am always seeing people who are using Magisk having various problems related to using it, so I had not seen a need to try it. But I do sometimes like to try new things if it doesn't cause the kind of problems I encountered when I tried exposed on my original ares 8 with 5.1.1. It was good when I had 5.0 to fix the lollipop memory leak and to use gravity box to improve the ui and features, but not so useful with 5.1.1 as overall, 5.1.1 is good.
[Miscellaneous Android Development] NemoCoOW:
God dammit I was about to post my reply and I can out of battery, I will get back to you soon, I have to pack as I'm going to London for a week.
[Miscellaneous Android Development] martyfender:
Here is the 2.1.1 tablet version boot.img, Twrp and systemless SuperSU download link:

https://www.androidfilehost.com/?fid=889764386195918830
[Miscellaneous Android Development] martyfender:
[MENTION=2188826]dorpmuller[/MENTION] I was wondering if you were able to solve your adb and fastboot issues you wrote about earlier? If you were and can upload your original boot image backup in twrp, I can modify it for you. If not maybe you know someone who has a windows 7 or linux machine you can try it on. Something was not right, whether it was a problem in windows 10 or one of the steps I outlined earlier not setup correctly. Please let me know, either way.

Thanks
[Miscellaneous Android Development] dorpmuller:
Naw... I mothballed it. I think it is a different model than what your files will work with. I'm not gonna bother with it now. I have much better tabs I can use, but I sure do appreciate your help! Never did like Marshmallow... now you know why!

Rich
[Miscellaneous Android Development] martyfender:
Twrp was built from that version of the tablet based on what i saw in the recovery log.It was built by vampirefo. I don't have his boot image though. It would boot with mine but you would loose sound, more than likely.
[Miscellaneous Android Development] ericzollman:
[MENTION=8126387]martyfender[/MENTION]

So I just use these files and:

1. Unlock my bootloader

2. Flash Recovery img

3. Flash Boot img

4. Install SuperSU using TWRP

???

I have the version 2.1.1 tablet btw.

Thanks for all your work!! I'll let you know how it works for me. after i try it out.
[Miscellaneous Android Development] martyfender:
I recommend you temp boot twrp first so you can backup boot imaage, stock recovery and system image before actually flashing twrp, boot image and rooting.

Also:

fastboot format userdata

enter, wait to complete.

Fastboot format cache

enter, wait to complete.

To have a decrypted data partition, the current one needs to be deleted it creates a new one on boot. The above commands achieves this.
[Miscellaneous Android Development] ericzollman:
Thanks a million bro! Works like a charm.,

:good::good::cool::good::good:
[Miscellaneous Android Development] martyfender:
[MENTION=7248165]ericzollman[/MENTION] If you used the systemless Supersu I provided it should have patched your boot.img. I need the supersu patched boot.img to update the boot.img I provided in the file you downloaded so it has the sepolicy patched correctly. I don't have that yet for the 2.1.1 version of the tablet.

The one in my current zip only works by using systemless supersu, because it patches the sepolicy file. I don't have the expertise to patch the file myself. The original author of the boot.imgs for the v1.1.1 and v1.2.0 patched for them originally. He made the suggestion to get the supersu patched one from a user and use that.

Would you be able to boot into twrp, backup the boot only, zip a copy of it and upload it to me? You can do that in google drive and share a link, or some other file sharing site of your choice. Please let me know if you can, or not.

Thanks
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=7117847]NemoCoOW[/MENTION] So it's like xposed? Can u tell me how to install it. I've been trying to install normal xposed for so long, but I didn't work. Can u help me out?
[Miscellaneous Android Development] martyfender:
Based on positive feedback from another user, I have changed from supesu to Magisk root. So far, so good.

If you decide to try it, first download the Magisk zip, Magisk manager and Magisk uninstaller and copy to your external sd card. Then go into the supersu app settings and choose full unroot from the options. I then booted directly into twrp recovery and flashed the Magisk.zip, then rebooted to android. When I check root in jrummy's root check, I notice selinux is set to enforcing and busybox is 1.23.1-Stericson, instead of the one I had YDS 1.27.1. You can reinstall YDS busybox by going into Magisk Manager, modules, choose YDS busybox from your sd card. It will reflash it and ask you to reboot to update it. I noticed an xposed sdk 23 module in the repository. I will not try it at this time but if anyone does, please let me know if it works or not.

If you disable the suhide in settings and reboot, the root check app will once again show selinux as disabled.

https://xdaforums.com/apps/magisk

I am on a v1.1.1 tablet with rom v1.20. If anybody tries this on either v2.1.1 or 2..15 tablets let me know if it works on them.

Thanks
[Miscellaneous Android Development] martyfender:
After testing Magisk for about a day I may revert to supersu. I've had one incident where I lost root access in evey app that was only solved by rebooting. I've been using supersu for about a year and a half and have never had this happen. Most of that time i was using system mode root.
[Miscellaneous Android Development] dorpmuller:
FYI I had magisk in another device and it was the same thing. I would look at it the wrong way snd it would lose root without me doing anything. Had to reflash magisk twice to get it back. I hated it...got rid of it and went back to Supersu. Trouble over!

Rich
[Miscellaneous Android Development] martyfender:
I have reverted to supersu system mode install after having problems with magisk.

One negative side effect of having magisk installed was when I rebooted into recovery I had no access to my external sd card. I had to copy the magisk uninstaller to my internal sd card along with supersu to flash them.

Once supersu was reflashed and I rebooted, I once again had access to my external sd card in twrp.

Any of you on v2.1.1 and v2.1.5 tablets will have to stay with systemless supersu. Could you send me the supersu systemless, patched boot images, as I so kindly requested, for me to patch the sepolicy on the ones I provided in the downloads. The patched image will allow me to use its sepolicy file to create a boot image which is compatible with system mode supersu.

It is such a small thing to ask considering what was released freely to you.

So, please upload them to me.

Thanks
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Is Magisk really that bad? I'm going to try it to confirm if its that bad. I'm really trying to see if that xposed-like module out to see if it works.