yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
I

I have never had those wifi issues. The only time I have personally seen it is if the wrong boot. Img was paired with a different rom. For example with the 1.1.0 rom one must use the 1.1.0 boot.img not the 1.2.0 boot.img. Others who had this problem solved it by flashing my twrp 1.2.0 tablet backup.
[Miscellaneous Android Development] dednotebook:
Will I have to redo all the steps to reflash 1.1.0? such a weird config, mac address is showing 02:00:00:00:00, is it safe to flash to 1.2 if I am 1.1.0? These will be the last questions, I am stuck right now on the mac
[Miscellaneous Android Development] martyfender:
Yes, you choose restore in twrp. Read back about where I wrote you about the proper folder structure to copy my 1.2.0 backup for it to show up in twrp. Be aware it is a fresh, data deleted version that will boot to the android setup screen.

What is confusing me is that you are about the 4th person to have wifi problems aftef following tbis procedure. Maybe some things need to be done in a different order? I have not been back on 1.1.0, almost from the get go to know. I have had no problems with 1.2.0 in several restores since my release in July.
[Miscellaneous Android Development] dednotebook:
Ok now I am confused, I thought if I was on version 1.1.0 I couldn't flash the 1.2.0? I did every step, step by step, and made sure everything was good before proceeding to the next steps. Sorry for soo many question, I really appreciate all the help you have given me so far. What would be the procedure for reflashing? Just reflash it on top of each other? I was going to try and reflash 1.1.0 again to see if anything fixes this issue., is it safe to go to 1.2.0 without bricking it? This is so frustrating! Even bluetooth is broken on it too now.. the thing is I don't want to go back to a stock image because I hated the encrypted storage and how slow it is. Thanks again for all your help.. ok maybe this will be my last questions.

Update: No camera's work

Wifi is broken

Bluetooth is broken

Sound is broken
[Miscellaneous Android Development] martyfender:
Those sure sound like the symtoms of flashing the wrong boot.img for your tablet. Is this the boot.img you flashed: Ares8A_111_boot.img? That is for the 1.1.1 tablet version. Do you have a 1.1.0 tablet version like you originally stated? go to settings, about tablet and give me the full build number, for example, mine was originally: V1.1.1.MMB29M.20161203.041025. Now it is:

V1.2.0.MMB29M.20170216.211208, with the 1.2.0 rom.

The simplest thing for you to do is flash my whole twrp backup rom for V1.2.0 here:

https://www.androidfilehost.com/?fid=673368273298970542
[Miscellaneous Android Development] dednotebook:
When I go to settings about it sill shows build version 1.1.0.MMB29.20161121.041731 - I am not sure why it's different than yours, so frustrating, I guess I probably shouldn't have flashed anything now
[Miscellaneous Android Development] martyfender:
So yours was built in Nov 2016 and mine in Dec 2016. Sorry, that was my mistake in rememembering my old build number. I am on linux now, but I had backed up 1.1.1 to my windows drive back in July, so I got the correct build number looking at the twrp backups from then.

I still believe the simplest thing for you to do is to flash my 1.2.0 backup. Otherwise I would need you to send me your original 1.1.0 twrp backed up boot.img to modify for your 1.1.0 tablet.

The files must be unzipped in the proper twrp folder structure: TWRP/BACKUPS/NX16A116K/2017-07-10-23-29-03_V1.2.0MMB29M20170216.211208/ to your external sd card or internal (where ever you save your original backups).
[Miscellaneous Android Development] martyfender:
I do not understand why Nextbook released so many different versions of this tablet in a short time period. The jump to 1.2.0 made sense since they added the anti-theft activation, but after that I am not sure what the reasons were?

Versions so far that I am aware of:

1.0.8

1.1.0

1.1.1

2.1.1

2.1.5

~Nov 2016 to March 2017
[Miscellaneous Android Development] dednotebook:
My backup doesn't have all the files like yours, ya it doesn't make sense why the short time between different version. I am copying your 1.20 to the external, how do I flash it properly? TWRP - restore option?

---------- Post added at 05:21 AM ---------- Previous post was at 05:15 AM ----------

Also before I proceed, will I have follow all the instructions to get root again? and busybox?
[Miscellaneous Android Development] martyfender:
Yes, boot into twrp, hit the restore button and choose the 1.2.0 version you copied to your twrp backup folder. If you don't see it in twrp, that means you didn't place it correctly in the directory structure. swipe to flash. Once you see a successful message, go to the main menu, click on the reboot button and choose system to reboot to the android setup screen. boot should take a long time, so be patient. Mine usually takes ~5-6 minutes the first time only. It takes some time to recreate files and the unencrypted, new data partition. This backup already contains supersu and greenify. Open supersu to set it up and setup greenify. Greenify is an app I find useful. It can be uninstalled also, If you like.

Here is a list of apps I find useful in my situation:

https://xdaforums.com/showpost.php?p=72995672&postcount=112
[Miscellaneous Android Development] dednotebook:
Ok I got the folder structure correct but I still see nothing -- I am not sure why
[Miscellaneous Android Development] martyfender:
I can't recall the busybox version it has. Install this jrummy root check app to see the installed busybox version. I had problems with the latest version from the play store so I used this version from apkmirror:

https://www.apkmirror.com/apk/jrummy-apps-inc/root-check/root-check-3-4-3-0-release/root-check-3-4-3-0-android-apk-download/

Make sure that you go to settings, security and check unknown sources to be able to install from apkmirror. It is a reliable, trusted source, that checks it's sources before they upload to their server.
[Miscellaneous Android Development] dednotebook:
can I just not flash 1.2.0 to my tablet? or will that break it? I added yours to internal and external, verified the directory structure but still don't see any options in restore
[Miscellaneous Android Development] martyfender:
In restore, Did you select storage: internal or Micro sd card?

At the root of either external sd or internal sd create a folder, TWRP, in it another folder, BACKUPS, in it another folder, NX16A8116K, in it, 2017-07-10-23-29-03_V1.2.0MMB29M20170216.211208, in that last folder all of the twrp backup files boot.emmc.win, boot.emmc.win.md5, recovery.log, system.ext4.win000, system.ext4.win000.md5, system.ext4.win001.md5, system.ext4.win001, system.info.

A folder, within a folder, within a folder, within a folder with the twrp files

If that doesn't work, look at the folder structure of your original twrp backup to see if it is some how different than the one I outlined for my device. I have seen the backups not show in twrp when they are not in the correct structure. They are unzipped, correct?
[Miscellaneous Android Development] dednotebook:
I copied it both ways and tried it, it didn't work shows up blank in restore either way I do it. I think I am running out of options
[Miscellaneous Android Development] martyfender:
Although something else could be wrong, that is not my experience. I believe you are not creating the folders within folders, files in the final folder, or your backup folder structure is named differently, which is possible. Is your native language English?

I had this problem of old backup not showing up on my original ares 5.0, when I updated to 5.1.1. the folder names were different. The NX16A8116K folder could possibly have a different name.
[Miscellaneous Android Development] dednotebook:
You might be on to something here, the folders are different -- tried it again with the updated paths and still don't see anything , i really screwed up I think. Yes my native language is English.
[Miscellaneous Android Development] martyfender:
That is it, as I suspected. name them the same as your original with the exception of: 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208, for the last folder. Was the: NX16A8116K folder a different name?

Here are the backup folder names for twrp backups saved to my Windows drive"

/TWRP/BACKUPS/NX16A8116K/2017-07-01--01-36-33_V1.1.1.MMB29M.20161203.041025

/TWRP/BACKUPS/NX16A8116K/2017-07-01--03-50-20_V1.2.0.MMB29M.20170216.211208

/TWRP/BACKUPS/NX16A8116K/2017-07-02--02-31-35_V1.2.0.MMB29M.20170216.211208

/TWRP/BACKUPS/NX16A8116K/2017-07-02--16-09-14_V1.1.1.MMB29M.20161203.041025

/TWRP/BACKUPS/NX16A8116K/2017-07-02--17-05-46_V1.2.0.MMB29M.20170216.211208

/TWRP/BACKUPS/NX16A8116K/2017-07-02--19-15-50_V1.1.1.MMB29M.20161203.041025

/TWRP/BACKUPS/NX16A8116K/2017-07-04--04-33-03_V1.2.0.MMB29M.20170216.211208

/TWRP/BACKUPS/NX16A8116K/2017-07-05--01-46-50_V1.1.1.MMB29M.20161203.041025

The actual twrp backup files are within each of those folders, for example one is boot.emmc.win, the backed up boot.img.

Each new backup within my /TWRP/BACKUPS/NX16A8116K/ will have a different name with rom version number, backup date and additional, different numbers, for example: 2017-07-04--04-33-03_V1.2.0.MMB29M.20170216.211208.
[Miscellaneous Android Development] dednotebook:
the only difference was the last folder, I tried to copy your files to my directory structure but my trick didn't work... Can I just flash the 1.2.0 using adb? or will it make things worse? I mean flashing with adb to flash 1.2.0, can I even go from 1.1.0 to 1.2.0?
[Miscellaneous Android Development] martyfender:
the last folder was the unique name for that particular backups folder, such as: 2017-07-04--04-33-03_V1.2.0.MMB29M.20170216.211208.

This is getting very frustrating for me as well as you.

On your external sdcard or internal sd card, you have a folder named TWRP. You open it and within it you have a folder named BACKUPS. You open the backup folder and within it you have one named NX16A8116K or slightly different. You open it and have one named: 2017-07-10--23-29-03_V1.2.0.MMB29M.20170216.211208.

Within it you have all of the loose twrp backup files starting with the name boot.emmc.win, system.ext4.win00, system.ext4.win01.

Those are the backup files, the others are checksum files, recovery log and system info.

As far as I know you can't do that in adb. In fastboot you could with file renaming, but since the system images are split into two files, I'm not sure how they would be combined.

File permission could also be an issue, but I have not experienced that or know what would cause it. A google search revealed this.

You didn't, by chance, choose read only for the system in twrp? there is a box that shows up when you launch twrp, if I am not mistaken. In twrp click the mount button. In twrp setting, general, none of the options are checked, by default.
[Miscellaneous Android Development] dednotebook:
I am sorry you are getting frustrated as well, I have done all of what you said in the previous comment.

so the command fastboot flash boot Ares8A_120_boot.img , can I flash it like that? or does it need to be done with

---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------

I did all of the above already, sorry you're frustrated as well. can I not just flash using fastboot flash boot Ares8A_120_boot.img? Never did read only. either, nothing shows up in restore still. I am not sure what to do now
[Miscellaneous Android Development] martyfender:
That will only flash the boot.img not the system. That boot.img with your 1.1.0 system would produce no sound, wifi bluetooth. Twrp has the ability to produce a system.img, but I have never created one.

You could save your original, first backed up, boot.img named: boot.emmc.win, zip it and share it to me on google drive or other file sharing site by creating a shareble link and I could modify it to remove encryption and dm_verity and share it back to you once done. Sending the boot.emmc.win.md5, though not necessary, might be a good idea, also. It is just a checksum file to verify that the file has not changed. Then you could keep your original version 1.1.0 .You can create a shareable link in your google drive, for example.

I am off work tommorrow so I could modify it then. You would then just have to flash it only, in fastboot, and flash a different, systemless version of supersu for it to work. Systemless supersu is the official version for android 6.0+ I can't patch selinux to make it permissive as I don't have the tools or skills to do it, like vampirefo did for my original two images. Systemless supersu patches this in the boot.img for us. Let me know.

I still feel that the naming or folder structure wasn't right, somehow, though in your attempts.
[Miscellaneous Android Development] dednotebook:
That isn't going to work, I did the backup earlier and it only backed up two files, system.ext4.win000 and system.ext4.win001 - so I think that won't work now
[Miscellaneous Android Development] martyfender:
Did you check each box in twrp that you wanted to back up? boot, system etc? If you had only system checked, that would explain that. you mean to say you don't have a backup of your original boot.img? before you flashed any files? The more you tell me the more it leads me to believe it is user errors.

Have you searched google or youtube, for a good, twrp tutorial?
[Miscellaneous Android Development] dednotebook:
Yes IIt worked -- you are right, user error. now that I have it in TWRP what are the next steps? It has Boot and System selected.. do I need to mount the System partition before I restore this version?
[Miscellaneous Android Development] martyfender:
Do you mean my 1.2.0 backup? If so hit restore, choose the proper twrp backup folder and swipe to flash it. If not, I'm not sure what you mean. you shouldn't have to mount it, but it can't be read only to restore. You are talking about my 1.2.0 backup?
[Miscellaneous Android Development] dednotebook:
yes your 1.2.0 version, it's restoring now

---------- Post added at 09:46 AM ---------- Previous post was at 09:41 AM ----------
[Miscellaneous Android Development] martyfender:
That is great to hear. Was it the folder naming structure or the loose files placed in the wrong one? Please let me know how it works.

Don't forget that it takes a good amount of time to boot the first time. It will appear to be in a bootloop. 5-6 minutes. The next boot after you set it up should be much faster. After setup, test, sound, wifi and bluetooth.
[Miscellaneous Android Development] dednotebook:
I noticed a difference in the name NX16A8116K - one has a 8 and one doesn't.. I restored 1.2.0 and everything works, mic, camera, wifi, bluetooth. There is no telling how many hours I looked at the folder names and didn't notice a difference. User Error :good:

Thanks again Marty, you saved my tablet! :highfive:
[Miscellaneous Android Development] martyfender:
So is yours named: NX16A116K instead of NX16A8116K? Can you install Aida64 from the play store? Under the system tab model what does it show? On the android tab fingerprint, what does it show?

Thanks

This could either be due to slight hardware differences or a different Intel firmware version.

Under settings about tablet what IFWI (Intel Firmware Interface) does it report? My 1.1.1 tablet is:M882_JJ.018.

A 2.1.1 tablet owner reported to me that his has M882_JJ.019.

Thanks
[Miscellaneous Android Development] dednotebook:
Well I did the restore - I am not sure how to answer your questions because I restored to your 1.20 version, which was the fix for me.. Let me know if I am wrong, and if aid64 will show me the information you requested. Thanks again for all the help last night, I thought for sure I screwed up
[Miscellaneous Android Development] dednotebook:
Marty,

I think I have found an issue with the 1.2.0 FW, I can no longer get it to ask me if I want to charge or do files transfers when I plug in the usb to a computer, can you check and see if you get similar behaviors? It looks like there is no connecting back to adp, seems to be broken now

---------- Post added at 05:14 AM ---------- Previous post was at 05:12 AM ----------

it is no longer recognized by windows since the restore of 1.2.0
[Miscellaneous Android Development] martyfender:
I've never seen that kind of behavior. Did you approve the security prompt that pops up on the tablet to allow usb debugging? After flashing the rom again that always comes up on my tablet before I can get to the first setup screen.

Is developer options enabled? settings, about tablet, tap 7 times on the build number to enable it. It should say something like: you are now a developer.

I'm on Linux now, but from what I recall, go to device manager in windows. When plugged in you should see Intel adb interface or device. Is USB debugging enabled in developer options? Look at developer options: Select USB Configuration.

Have you tested with a real charger such as the one that came with the tablet?

You might also try booting into twrp recovery and choose wipe, advanced wipe and check cache and dalvik cache and swipe to delete, then reboot. Upon reboot, you should see android is optimizing apps 1 of (the number of apps) etc. before it boots to the desktop.
[Miscellaneous Android Development] dednotebook:
I have done everything you said to do but file transfer over usb still does not work, it will only let me select charging and nothing else. You are on 1.2.0 right? Does it do the same for you?
[Miscellaneous Android Development] martyfender:
File transfer and charging works for me. In Linux, I am currently transferring a twrp backup to my external sdcard from my Windows drive.
[Miscellaneous Android Development] dednotebook:
soo weird, I will try linux later, for now I have found a program called airdroid that allows file transfer via wifi
[Miscellaneous Android Development] dednotebook:
Update: Used another usb cable (one that didn't come with my tablet) and all the options are there now.... I can't explain at all why that works and gives me all the file transfer option.s.
[Miscellaneous Android Development] martyfender:
I now own a 1.20 version of the Nextbook Ares 8A which required activation. I am using the standard, systemless root, recommended for Android 6.0+: SR3-SuperSU-v2.82-SR3-20170813133244.zip, instead of the unofficial, system mode version.

I noticed a new version of magisk root has been released, but I am hesitant to try it considering the problems of loosing root that I had with previous version. I am tempted to test it again, with a good twrp backup, but I really don't have any good reason to do this myself, as I don't use apps that detect root and fail to run, or use things such as android pay that require hiding root. SuperSU has been very, very dependable for me.

My older, 1.1.1 version apparently has an unresolvable hardware issue that has not been solved by multiple flashes of the 1.1.1 rom, or my 1.2.0 rom. The external SD card is not mounted at boot or appears as corrupt. ejecting it and reinserting it 1-3 times and it appears as normal and appears as uncorrupted. I have also tried a new card and one other existing card to confirm this. Also, sometimes after wakeup it is unmounted and appears corrupted and is once again solved by ejecting and reinserting it. I do believe it is a hardware issue because it shows this same behavior when booted into twrp, also, even with a fresh twrp re-flash. It may have had this issue partially since new, but was not as severe to notice. My apps2sd would always loose it's 2nd ext4 partition mount after doze. The app author thought it was my rom.

The new tablet has none of these issues and and the apps2sd 2nd partition is always mounted, just like normal, as it is on my Ares 8 5.1.1 tablet.

If anyone has any thoughts on this and or has seen this kind of issue before, let me know. Everything else appears normal on the tablet.
[Miscellaneous Android Development] billybleu97:
martyfender nextbook ares 8A manf Nov 2016 BN v1.0.8.MMB29M.20161107.053713

nextbook NX16A8116K ANDROID 6.0.1

KERNAL VER 3.14.64-X86_64

SECURITY PATCH AUG 16 2016

---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------

I JUST BAUGHT AN ARES 8A 16g ROM qUAD

---------- Post added at 01:27 PM ---------- Previous post was at 01:16 PM ----------

My collleges are shocked Im one of those guys that comnines 4 diff "computer Formats" to get diff models and versions of a total pakage piecednilles hopacotch all over the office together to make a workuing machine I need advice as to which ver of twrp and such should i start backing up and how again adb twrp Hit me back when you can I can also supply you personal library with stock images of this device i havent done anythig ut read your thread and turn the tablet on and off hopr to hear from you soon

billybleu97@gmail.ocm
[Miscellaneous Android Development] martyfender:
Can you clarify how one takes advantage of this deal? When I go to the link in my walmart store it shows the full price.
[Miscellaneous Android Development] martyfender:
I certainly haven't made much progress in learning how to do this. When I download sources with git in linux, my drive space decreases, a folder is created in my home directory and it appears to be empty. A search doesn't reveal where all of the disk space is going, either. Does anybody have any ideas. I thought I had drilled down to the proper branch.

I would be willing to give a donation to help purchase a new tablet for him, if others will also. I just can't afford the full cost of a tablet right now. I think there is a link in his signature for donations?
[Miscellaneous Android Development] avgary:
upc for Ares 8A on brickseek 847275001352 blue color

I just picked one up today for $35. I believe here are 4 colors each with a different UPC / SKU

SKU

Red 135510787

Black 122137749

Silver 196308982

Remember that brickseek is not always correct.

These models seem to have been built in Nov 2016.

Newer ones were built in April 2017 and are $68. Couldn't find the difference - front camera still 0.3MP? I think the boxes were exactly the same.

A month ago I found a 10" android nextbook for $25!
[Miscellaneous Android Development] martyfender:
No one replied to my previous post how brickseeker works?

Is there a promo code one has to give to walmart, or does one have to register with brickseeker?

I work at a southside Indianapolis walmart and I suspect we only have to newer ones. all of ours are priced at $68.

Do the older ones also have android 6.0.1 on them also? The current one I have has a manufacturing date sticker of December 2016.

It is strange, they put the new ares 8A display model in late winter to early spring. A few weeks ago they removed it. and put all of the inventory on an end cap display, instead of being locked up. That usually means new models are coming out or walmart is discontinue them (at least according to an electronics associate)

Despite poor reviews on their website, mine works and runs great.

I would love to get one for $35 to send to [MENTION=2472806]vampirefo[/MENTION] so he can root it and build the twrp for it.
[Miscellaneous Android Development] avgary:
Brickseek.com is just a website that tracks inventory at stores like Walmart and target.

All it does is give you an idea if a clearance item may be located near your zip code using an SKU or upc code.

You have to go to the store and see if the item is actually there and is listed with the clearance price. As I said earlier - there are no guarantees.

It Is not a code or coupon site. Hope I have made it clearer.
[Miscellaneous Android Development] martyfender:
Thank You