yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
I have uploaded a 1.2.0 version of a twrp backup with userdata deleted, so it should boot to the android setup screen. It contains Supersu, Greenify and yds Busybox 1.27.0. I had Greenify installed as a privileged, system app. Greenify can be un-installed, though. The latest Busybox, was flashed yesterday. If you want to use another Busybox, yds has a Busybox cleaner that can be flashed in twrp to remove it. You need to go into Supersu settings and set it up again.

I have it on my 1.1.1 version of the tablet. There is no apparent difference between it and the 1.1.1 version. It has the same kernel and android version. The newer tablet requires activation, but there is no sign of it when flashed the the older tablet, which leads me the believe the the activation is hardware base.

There is no apparent benefit to flashing this to the older tablet. But if you are having issues with either version of the tablet, this may be of benefit to you.

Use at your own risk. It works great on my device.

Unzip and copy the folder: 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208, to your: external sd card/TWRP/BACKUPS/NX16A8116K/ It needs to be in the original order and naming to be recognized in twrp.

Please let me know how it works and if you have any issues.

I would especially like feedback if you flash it on a newer, 1.2.0 tablet.

Thanks.

get it on Android file host:

https://www.androidfilehost.com/?fid=673368273298970542
[Miscellaneous Android Development] therune:
The build number is V1.1.0 MMB29M.20161121.041731

I did go in to TWRP to clear both the cache and Dalvik cache, didn't solve the issue. I do have a backup, I'll test that after work today. I have two of these that are the same model, the first one was locked (didn't know what version of android it had) so I tried rooting it with the 5.1.1 method and it soft bricked it. I used my backups from the new tablet (the one with these wifi issues) and now both have the wifi issue. I can compare the build numbers later, but it must be an issue with these models?

Thanks!
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Well, we have twrp, modified boot.img, supersu, and BusyBox. Now all we need is Xposed module, unencrypted room, and possibly in the future, a 7.0 rom.
[Miscellaneous Android Development] martyfender:
This rom is unencrypted, if you mean rom instead of room. You can tell by going to settings, security. It should say: Encrypt tablet, if it is decrypted.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] After the rooting and flashing process, my tablet still says it's encrypted. Maybe I did something wrong? Also, if I was unencrypted, could I mount /data and backup my data?
[Miscellaneous Android Development] martyfender:
I am not surprised that you bricked it with the 5.1.1 method, if it is an 8A and not an 8.

By locked, do you mean you had to enter an activation code? If yes, then it should be version 1.2.0. Another thing you can try, after trying your own backups, of course, is the twrp backup I posted, a few posts back. In fastboot I formatted userdata and cache so it will boot to the setup screen again. Can you access your wifi router with other devices ok?
[Miscellaneous Android Development] martyfender:
It doesn't say in settings security: Encrypt tablet? That is strange, did you format userdata and cache from fastboot and reboot to decrypt? You have to do this from bootloader mode.

Also, did you fastboot flash boot your boot.img version? for both procedures it should show successful completion on both the computer and tablet screens.

Again, you have to do both from bootloader mode.

the first procedure will delete all of your data (userdata).
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Oh shoot, I may have forgotten that
[Miscellaneous Android Development] martyfender:
Which one, or both? format userdata and cache means erase them and write new, empty files in their place. It will take a longer time to boot, also, the first time.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Dang, I didn't read the op correctly.
[Miscellaneous Android Development] martyfender:
Was it format userdata and cache, you didn't do?
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] I didn't wipe anything, all I did was backup the partitions I could and flash supersu and twrp
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Now I see what I did wrong, I didn't use the adb commands to format userdata and cache, that's why tablet it still encrypted. I'll factory data reset my tablet and try again, and give you results when I'm done.
[Miscellaneous Android Development] martyfender:
I suspected you used adb. Format userdata does the factory reset and maybe more.

You need to reboot the tablet into bootloader mode and use fastboot commands, not adb commands.

Adb commands are used when the tablet is normally booted.

Fastboot commands are used in bootloader mode.

fastboot format user data push enter, wait to complete, then:

fastboot format cache push enter, wait to complete, then reboot to normal android mode setup screen.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Okay, I'm trying to factory data reset my tablet from the settings, and after I did the rooting process, it just bits me into twrp, give a bunch of /data errors and just boot me back to the startup with no changes, and the reset didn't happen. I'm gonna used the fastboot userdata command to force a factory data reset, if it doesn't work, then I'm stumped
[Miscellaneous Android Development] martyfender:
When I was researching editing the bootloader to remove encryption and dm_verity, I recall reading that a factory reset is not enough. That is why I asked you to format user data and cache. So you didn't do that yet? That is probably why you are having problems. Your data partition is still encrypted.
[Miscellaneous Android Development] TurnaboutSavage:
I made a video showing that I have achieved root access, BusyBox, and my tablet is unencrypted.

I'll upload it to YouTube to show it's been made.

---------- Post added at 12:20 AM ---------- Previous post was at 12:12 AM ----------

@martyfender I did the root process over again and now my tablet is unencrypted and I can backup ALL of my tablets partitions in twrp.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] [youtube]7x_zT0CLRuQ[/youtube] Now YouTube knows and root for this device will be more well-known.
[Miscellaneous Android Development] therune:
Your backup fixed the issue! Thanks, I really appreciate it.
[Miscellaneous Android Development] martyfender:
You are welcome. In the process of doing this, it fixed and issue for me also. Last week I had done the fastboot format userdata and cache, then downloaded apps etc.

On my ares 8 5.1.1 I use and app, called apps2sd, where you re-partition you ext sd card with two partition and this allow you to move apps to your sd card. It has worked very well on my old tablet, to move the one, big app I have, GT Racing 2, to my sd card.

On the new tablet, despite being a new setup, the partitions were not remounting after a period of doze when the charger was unplugged and the app was becoming partially linked.

After I setup the tablet again after all userdata was deleted, the partition are staying mounted. Not sure what is different, this time around. I would recommend doing this over a factory reset to fix problems.

Out of curiosity, did you try the fastboot commands to delete userdata first, before trying my backup, with success, or did you jump straight to my backup?

If you didn't try that first, that may have solved it for you. Apparently this does more than a factory reset does. I'm not sure what, though.
[Miscellaneous Android Development] martyfender:
I have been using j rummy's root check app for sometime because in addition to a root check, to will give good info about selinux status and the busybox version installed. The lastest version, targeted for android 7.0, has caused issues on my tablet, in churning forever trying to get root access and eventually causing the system ui to crash, requiring a reboot.

I downloaded an older version from apkmirror.com, v3.4.3.0 and it works on this device, just fine. Your mileage may vary, though.
[Miscellaneous Android Development] therune:
I actually did not delete the userdata, I just restored using your backup. Strangely enough, restoring with your backup brought back the activation screen on the older tablet I had. It was a used tablet that someone couldn't unlock so I figured I'd give it a try (which is how I ended up bricking it :D), when I used the restore with the broken WiFi the activation screen didn't come up. Very strange.
[Miscellaneous Android Development] martyfender:
If you or anybody has unexplainable issues, a clean start is recommended. You can do this with my backup, or faster, by using fastboot to format userdata , cache and reboot to android setup.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Now all we need is the xposed installer that works, then the future is what holds new things for this tablet.
[Miscellaneous Android Development] martyfender:
I'm not sure if it will work with marshmallow

https://xdaforums.com/xposed/xposed-intel-atom-x5-z8300-x8664-solved-t3585087

I tried that version on my ares 8 with 5.1.1 and I found it slowed down the tablet and reduced battery life.

Here is a link on my experiences with it on the ares 8:

https://xdaforums.com/showpost.php?p=72303130&postcount=96

Maybe if I had used other, or not all of the supposed battery saving modules, I would have been ok. I won't try xposed again unless I see it could be beneficial, not detrimental.

I don't see it as being as beneficial on marshmallow as it was on the original ares 8 when I had android 5.0.

5.0 had a major memory leak and an xposed module was made to address that. in addition, I used gravitybox to improve the UI and youtube adaway to remove ads in youtube. 6.0.1 has a much improved UI and no memory leak.

What features, are you wanting that xposed modules would give you?

I see more problems that xposed creates than it solves. It creates lots of incompatibilies with other apps.
[Miscellaneous Android Development] gabe.ulrickson:
I almost want to just buy an older Samsung Tab or an LG tab running Android 4.4 or 5 and root it

Anybody have any insight on Lgs line of tab
[Miscellaneous Android Development] martyfender:
I would like to encourage all of you who have used this to donate to [MENTION=2472806]vampirefo[/MENTION] Here is the link:

https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=KS22ZQGZWA3KQ&lc=US&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted

Please do not contact him for any support, he will not respond. I, and others here will provide support.

Without his release of TWRP and his original boot.imgs, none of this would have happened. I donated to him before he released it to me. Donate to him, even if it is a small amount.

Reply here if you have donated.

Thanks
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] That Xposed tutorial you gave me was for lollipop lol. Do you have one for marshmallow?
[Miscellaneous Android Development] martyfender:
No, as I stated in this thread. The rom of the official one on xda, may work, but my guess is it won't if it is like on the ares 8 with 5.1.1. You can flash it in twrp and if it boot loops, force a hard shutdown flash the official xposed uninstaller in twrp and reboot. At least it worked to remove it like this in 5.1.1.

http://dl-xda.xposed.info/framework/sdk23/x86/xposed-v87-sdk23-x86.zip

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

Get the xposed app, which you need and the twrp flashable uninstaller.
[Miscellaneous Android Development] orion214:
i wanted to get remix o this nextbook model please could you help me
[Miscellaneous Android Development] gabe.ulrickson:
Good luck
[Miscellaneous Android Development] orion214:
is it possible ? somebody ever tried it ?
[Miscellaneous Android Development] gabe.ulrickson:
I've tried with no luck

---------- Post added at 04:23 AM ---------- Previous post was at 04:21 AM ----------

Ended up getting my tab to a state where if it's turned off for extended period it bricks itself and you have to do a factory reset before it will work again
[Miscellaneous Android Development] orion214:
So what did you do at the end

like what rom are you running now
[Miscellaneous Android Development] gabe.ulrickson:
It didn't work. Failed root. Couldn't even get it to work.
[Miscellaneous Android Development] orion214:
oooh sorry but did you ask anybody on the forum for help ?
[Miscellaneous Android Development] gabe.ulrickson:
I didn't use this method to try and root, I was going to until I figured out my device was soft bricking itself, I will be returning it and picking up an LG g pad x 10.1 later down the road

---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------

I didn't use this method. I tried normal routes and then went towards this one when I realized mine was soft bricking itself, decided to return it and will pick up a LG g pad x 10.1 later
[Miscellaneous Android Development] martyfender:
Did you try flashing my backup rom in the OP? If you try it and it doesn't work, my guess is you have messed up the bootloader partitions or others. I know how to fix that on the original ares 8, but I have not clue on the ares 8a. The 8a has a totally different partition scheme than the ares 8. I flashed these files:

efilinux.efi

droidboot.img

I don't think this uses droidboot but my guess is it uses some kind of efilinux.efi

You can get to the uefi bootmanager by holding volume up and power at boot where a usb otg cable can be used to connect a keyboard. I do know this device has two bootloader partitions, most likely to support duel booting as many of these devices include android and windows. This is not of much help, but it is all I have at this point.
[Miscellaneous Android Development] gabe.ulrickson:
No I didn't, my only plan was to use a go of internal storage as virtual ram and maybe some other stuff, don't see the point in spending a ton of time trying to figure it all out for so few things
[Miscellaneous Android Development] orion214:
Could somebody help me with remix for this model please
[Miscellaneous Android Development] martyfender:
[MENTION=8413126]orion214[/MENTION] I see that a version released for the original ares 8 but I wouldn't try on the 8a because it has an entirely different partition scheme, so will probably brick the device trying.

The best place to ask is in the xda remix os device forums.

I think someone would need to port it to this device. You can view this devices partition details in an app like Diskinfo. I have compared my original ares 8 vs the 8a and they are dramatically different from each other.

Here it is for the Ares 8A:

﻿--------------------------

device-mapper

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

* zram0 [zram0] Not mounted

Total space: 400 MB

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

Internal Storage (MMC)

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

* android_bootloader [mmcblk0p1] Not mounted

Total space: 60 MB

* android_bootloader2 [mmcblk0p2] Not mounted

Total space: 60 MB

* android_boot [mmcblk0p3] Not mounted

Total space: 30 MB

* android_recovery [mmcblk0p4] Not mounted

Total space: 30 MB

* android_misc [mmcblk0p5] Not mounted

Total space: 1 MB

* android_metadata [mmcblk0p6] Not mounted

Total space: 16 MB

* android_system [mmcblk0p7] Not mounted

Total space: 3 GB

* Cache (android_cache) [mmcblk0p8] (/cache) [ext4]

Used: 31.5 MB, Free: 568 MB, Total space: 600 MB

* Data (android_data) [mmcblk0p9] (/data) [ext4]

Used: 6 GB, Free: 4.7 GB, Total space: 10.6 GB

* android_persistent [mmcblk0p10] Not mounted

Total space: 1 MB

* android_config [mmcblk0p11] (/config) [ext4]

Used: 4.3 MB, Free: 3.7 MB, Total space: 8 MB

* mmcblk0rpmb [mmcblk0rpmb] Not mounted

Total space: 512 KB

* mmcblk0boot1 [mmcblk0boot1] Not mounted

Total space: 4 MB

* mmcblk0boot0 [mmcblk0boot0] Not mounted

Total space: 4 MB

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

SD Card

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

* SD card [mmcblk1p1] (/mnt/media_rw/8233-19F2, /storage/8233-19F2) [vfat]

Used: 1.2 GB, Free: 13.5 GB, Total space: 14.7 GB

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

Internal Storage

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

* System [dm-0] (/system) [ext4]

Used: 2.6 GB, Free: 364 MB, Total space: 3 GB

* dm-1 [dm-1] Not mounted

Total space: 10.6 GB

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

tmpfs mount points

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

* /dev [tmpfs]

Used: 40 KB, Free: 447 MB, Total space: 447 MB

* /mnt [tmpfs]

Used: 0 B, Free: 447 MB, Total space: 447 MB

* /storage [tmpfs]

Used: 0 B, Free: 447 MB, Total space: 447 MB

* /storage/self [tmpfs]

Used: 0 B, Free: 447 MB, Total space: 447 MB

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

Memory

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

* RAM

Used: 493 MB, Free: 400 MB, Total space: 894 MB

* Swap

Used: 119 MB, Free: 280 MB, Total space: 399 MB

This was from the 8A before it was rooted.
[Miscellaneous Android Development] TurnaboutSavage:
I'm currently attempting to find out which version of xposed will work on this tablet. Wish me luck, I'm probably going to backup and restore my twrp saves so much, but its worth it to help this rooting community. Wish me luck! :laugh: :laugh:
[Miscellaneous Android Development] martyfender:
Good luck, you'll need it. I didn't have good luck when I used it on my older, are 8 with Android 5.1.1. I ended up getting rid of as it slowed down my device and caused poor battery life. That could have been caused by the combination of modules I was using though. Here is my post about it:

https://xdaforums.com/showpost.php?p=72303130&postcount=96
[Miscellaneous Android Development] Iwantroot:
Bought one yesterday, new version, V2.1.5. Tried with newer 1.2 boot.img and was successful gaining root, but wifi and Bluetooth would not turn on. Also tried martyfender's 1.2 twrp backup, this was successful also, wifi and Bluetooth work, but sound no longer works. If anyone has any ideas or suggestions it would be greatly appreciated.
[Miscellaneous Android Development] martyfender:
Gg

If you can upload a copy of your original boot.Img, I can modify it and it should work. Can you provide kernel version, build date, build ID etc to compare. Aida64 is good for this. I noticed no sound when the wrong boot.img is paired with it. Boot. Img and system build need to match. Did you buy this newer version at walmart? What city?
[Miscellaneous Android Development] Iwantroot:
Yes it was Walmart, small town in Alabama. When I make it back home this evening I'll try to get all the info you requested and upload a copy of the original boot.img, thanks for your help.
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] You can upload it to g drive and share a link or other file sharing site. I work at a Walmart and I believe we don't have the newer version, the last time I checked, but I don't work in electronics and any newer ones are in lockup. I had purchased the 1.20 version and pulled the rom from it before I returned it. I don't believe we have got any new ones because they are not selling well as the reviews on the Walmart site are not positive. It has been good for me though. Did you have to activate yours with a code from the receipt? Your boot.img will have to be modified to remove encryption, make the kernel permissive and dm_verity removed.

I'm not sure why you had a difference between what you originally flashed and my backup version they both should have been v1.2.0: Ares8A_Newer_boot.img if that is the version you flashed originally vs. Ares8A_Old_boot.img for the 1.1.1 version of the tablet. It will be interesting to see what differences there are in the V2.1.5 tablet version Later, .if that truly is the version you say, it would be nice if you could upload the system.img (~2.6GB) and the boot.img and I could share it on android file host. If not, I will modify the boot.img which is the most important, right now.

For now, just upload the original boot.img that came with the device.

Thanks
[Miscellaneous Android Development] Luvkraft:
I finally rooted mine 3 days ago with the 1.2. Wi-Fi and Bluetooth are working fine, I did however notice the Bluetooth Icon, doesn't always show up and seems to show OFF on the pulldown. If you actually go in to settings it shows as ON
[Miscellaneous Android Development] martyfender:
I'm not sure as mine shows up fine in both places. You could boot into twrp recovery, choose the wipe button, then advanced wipe and check dalvik cache and cache, swipe to confirm delete, then reboot the system. It will take some extra time as you will see android optimizing apps message. Did you delete userdata and cache in fastboot when you set it up originally? If the above doesn't work you could boot to bootloader mode then: fastboot format userdata, hit enter, wait to complete, then fastboot format cache, hit enter, wait to complete, then reboot to the android setup screen to setup as new. All of your data is deleted, of course, with this method. If the above solutions don't work, then I'm not sure.

You could try my twrp backup files also. However, it was created after I deleted userdata and cache also, to start fresh. It contains supersu and greenify, so you'll need to set them up again. You can delete greenify if you don't want it. The link to it is in the OP.
[Miscellaneous Android Development] TurnaboutSavage:
OK, I'm back from my Xposed framework project. I have made a small amount of progress. Anytime I tried to flash the Xposed framework via twrp recovery (had a backup of course) and all of those failed to work. I tried to install the lastest xposed framework (v87) via the xposed installer. It actually booted back up and was very excited, but when I went into Xposed, it said the framework was installed but not active. I haven't been able to get that result again since. I'll try again, but I might need some help in doing so.
[Miscellaneous Android Development] martyfender:
I was just wondering what the status is. Did you work something else out? I thought I could edit that boot.img tonight since it is my day off.
[Miscellaneous Android Development] Iwantroot:
Sorry I haven't posted back sooner, having issues with the original backup I made with twrp. Everytime I try to flash it back the tablet starts to boot then says, "your device has failed verification and may not work properly." then moves to a black screen and goes no further from there. Not sure what the problem is, I've wiped userdata and cache after flashing Also. It did have the activation code on the receipt too BTW.
[Miscellaneous Android Development] martyfender:
The original boot.img will fail verification because your system has been modified and it detects that without dm_verity removed from the boot.img. You need to flash the one I modified originally to at least boot properly. you will have no sound, of course since it is not a match for your 2.1.5 device.

If you can get that far then if you upload your original twrp backup of the boot.img , I can modify it tonight and repost the new version.

I had the same issue when I reflashed the original boot.img on the 1.20 version I returned. Since it was rooted, the system was modified, therefore it fails verification. Even when I flashed unsu, supersu uninstaller, it failed verification.

Unfortunately I lost my original, unmodified system.img because of a corrupted sdcard issue, which was apparently caused by an app I had used for sometime under lollipop: Easy Reboot [ROOT] by Simone Luconi, but apparently is not compatible with Marshmallow. I now use Simple Reboot by Francisco Franco, famous here on xda.