yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] martyfender:
Which branch of the kernel source should I choose? Just curious why 5.1 and not 6.0.1 to build the bootable kernel. Once I have the correct source what would be the full make command to run to build it? Then I would run fastboot commands to boot the ramdisk?

Is the purpose of this root access to pull the boot.img and recovery.img?

I think I figured out why my local directory was empty. I need to run the terminal command from the folder where I want to download the source.

Is this the kernel I should choose, or is there a different one I should choose?

https://android.googlesource.com/kernel/x86_64/+/android-x86_64-fugu-3.10-lollipop-release

Thanks
[Miscellaneous Android Development] vampirefo:
Yes, the purpose is to pull the stock recovery.img, from that you build TWRP.

I don't know what kernel source you need, you will need to try several until you find one that boots.

I don't keep this information stored away in my head somewhere, it's simply trial and error til you find the right combo.

Took me two days, many different kernel sources and many different builds to build a kernel that would boot into recovery so I could pull stock recovery.img.
[Miscellaneous Android Development] martyfender:
[MENTION=2472806]vampirefo[/MENTION] I am hoping to get at least one other to commit to giving you a donation to buy a new tablet so you can release. I can donate $35 which is about half of the cost of the tablet. So far, no one else has replied to my request. I see you have have a place to donate in your signature. IF we get a tablet for you, how long would it take to have it built and release it-just a rough estimate. It seems like you did it pretty quick with your son's tablet, back in the spring.

I still would like to learn how to do it though, even if you release it.

Thanks again
[Miscellaneous Android Development] vampirefo:
I just checked my local Walmart no longer carries this tablet.
[Miscellaneous Android Development] martyfender:
I get paid thursday. I will be checking my finances over the next few days to see if i can handle it. I am a walmart receiving associate so i get a 10% discount. Free shipping for orders over $35. It could be sent to your home. Stay tuned to see if i can afford it. It may being phased out?

Regards
[Miscellaneous Android Development] vampirefo:
Don't put yourself out like that, to be honest if only you paid for it, I wouldn't release it to the public, I would just send you TWRP and modified boot.img.

If it's not worth it to anyone else, I would recommend to just let it go, or continue working on it yourself.
[Miscellaneous Android Development] martyfender:
If that does happen to be the case i could always pm you. Shipping is free, but what state are in? I am in Indiana.

I want to continue myself, but it is very very hard to find info how to do it i have spent hours searching.

You have never uploaded a device tree to the twrp repository have you? Did you use cm or omni sources? I am assuming you prefer to keep your sources closed? I can't find a similar device in the repository. Since my original ares 8 is running great with the tunings I have done with lspeed and Kernel Aduitor, I don't really need the ares 8A. It is more of a hobby with me to learn about computers and oses. I have the tablet to use at work because Just turning 59 Thu., my eyes aren't what they used to be. The unrooted device is somewhat useless, to me.

I also suspect there aren't many with this device, or we would be seeing more posts like in your ares 8 thread.

I will think about it and let you know, either way. I really thought that there would be a few others who would be willing to do a small donation, though. Maybe I could find a newer samsung device with a root solution for it, but I am not a fan of the touch wiz interface and all of the other incompatibilites it brings, not to mention the greater cost of those devices. The very first android device I touched was a samsung s3, which I reflashed a rom for someone who had messed it up.
[Miscellaneous Android Development] SageForce:
Thanks for the info. I picked up 1 at Walmart for 35! I needed a tablet with HDMI out for my Mavic to use my FPV glasses with. I'd definitely like to see it rooted.
[Miscellaneous Android Development] martyfender:
Just curious, what area do you live in? The store I work in on the south side of Indianapolis, IN has them still at full price and they don't appear to be selling. Walmarts web site still lists them at full price: $68.
[Miscellaneous Android Development] martyfender:
[MENTION=2472806]vampirefo[/MENTION] I noticed a sticker on the boxes in my store today that is different than the current model I own. "Power up will demand the Activation Code from your receipt" These have a manufacturing date sticker of 2017, I forget what months. Mine was December 2016. Will this have any effect on rooting it and the twrp build and boot.img compatibility with my older device? Or would you need it to determine this? Is this something new for android devices. I assume it is for theft deterrence.

The quote was from a review of the tablet when I changed my store zip code to one where I use to live on the northside of Indy. The review reminded me of seeing it today when I was at work.
[Miscellaneous Android Development] vampirefo:
I have no idea, if the kernel is different then I would have to have both tablets, if the kernel is the same, it wouldn't make any difference.

I have no way of knowing the difference between the tablets, what works on what, without having it in my hands.

This activation code seems nasty, right after rooting, I would find a way to remove it.

Anytime tablet was reset the code would be needed.

https://www.ifixit.com/Answers/View/400956/Need+activation+code+without+receipt
[Miscellaneous Android Development] martyfender:
[MENTION=2472806]vampirefo[/MENTION] walmart has a 15 day return policy on electronics. If I buy one, would I be able to pull the necessary info you need without root to decide if the new and older are compatible. The kernel Info is easy to find if Boot it up in about tablet and other info can be gotten with a utility like aida64. If you think it will work from this info, I could send it to you. If not, I could return it.

I think doing the steps you outlined to root it is beyond me at this point in my learning.

When I try to git clone a kernel dir, it appears to download, creates a dir, the disk space diminishes, but the folder appears to be empty. Do you know what I am doing wrong? I was able to directly download a kernel source through the web browser, but I don't know the proper make commands to use. One I tried: make menuconfig, brought up a configuration window where I can choose options. I also saw in a google search where I need to download pre-compiled toolchains, not sure how to get x86-64 ones?

Time to go to bed. i am very frustrated about trying to do this my self. It is the learning how that is hard.

Thanks, once again. I give up for tonight!
[Miscellaneous Android Development] vampirefo:
I don't know what info you could get that would show that one TWRP would work on both versions.

You can compare build.prop check kernel version in about and unlock bootloader.

Those give a good idea, but aren't 100%, to get 100% you would need to pull recovery.img from both, then boot recovery.img on the other tablet, if it booted then they are 100% the same.

The problem is you buy a tablet, send it to me, I root it, build TWRP, send you TWRP and modified boot.img and they don't work on your current tablet then what?

You would then have to buy another tablet that the TWRP and boot.img worked on.

The 15 day policy would be your ideal window to work on rooting it, if you fail you could return it.

As you can see there is zero interest in rooting this tablet other than yourself, Others want you to bare the cost and me to do the work, at no cost of time or expense to themselves.

I encourage you to let it go, but if you send me the tablet I will do the work for you and only you, meaning I will send you the TWRP and modified boot.img.

You of course can do as you like with it, share it or not share it, as you paid for the work it would be yours.

You can use your money to buy yourself a different device, Nextbook might even release Android 7 soon, for about the same cost as this tablet.
[Miscellaneous Android Development] martyfender:
Thanks, this is great advice. I am off today, but tomorrow at work, I will buy one, pull the build pro, compare and then decide if I want to send it to you, or return it. My guess would be that a activation code is generated based on the serial number scan when it is rung up at the register. Do you think activation is built into the boot.img? If I decide to send it to you, should I pm you? What state are you in? Of course sending it to you will increase the cost, vs the free shipping from walmart.com, if it was sent directly to you. I haven't shipped anything in years to know how expensive it is . Base on zip code, I guess. And could keep using my old ares 8. I even have better connectivity with it now. I found info somewhere googleing I changed vm properties overcommit_ratio to 87, min_free_kbytes to 5780. Don't remember where I found the info. It was min free they recommended changing. I had posted about connectivity problems in the past in the thread where you released the 5.1.1 rom. Seems to be better now.

Do you have any advice concerning my adventures with git and make?

Thanks

walmart.com reviewer of nextbook ares 8a:

"Power up will demand the Activation Code from your receipt then start the NextBook Setup Wizard." Reminded me that I saw those new stickers on the boxes when at work yesterday. that also explains why they are not in electronic lockup now.
[Miscellaneous Android Development] billybleu97:
martyfender nextbook ares 8A manf Nov 2016 BN v1.0.8.MMB29M.20161107.053713 nextbook

nextbook NX16A8116K ANDROID 6.0.1

KERNAL VER 3.14.64-X86_64

SECURITY PATCH AUG 16 2016

manf Nov 2016

BN v1.0.8.MMB29M.20161107.053713

Can you tell me which version of twrp to use wiht 1.0.8 build so i can get you a orig boot.img so ican use your method to root my tablet please
[Miscellaneous Android Development] martyfender:
use the version of twrp I provided. It was built from a V1.0.8 tablet by vampirefo. Please provide a link to your original boot.img, once you back it up in twrp and I can modify it, when I have time. Off to work, now. the twrp backed up boot.img is named: boot.emmc.img
[Miscellaneous Android Development] billybleu97:
i temped twrp and did backups but those files are names with .emmc.win extention did i do sumthing wrong

---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------

i dont know where i can post those files for you ca i just email them they are on;y like 30 Mb ive tried putten stuff on mt google drive but it just takes sooooooo long for it to upload but ill try these files and send you link
[Miscellaneous Android Development] martyfender:
gmails maximum file size is 25mbs, so that is out. It never takes me long to upload to my google drive, but I have always done it from my desktop computer through a wired connection and not from my tablet through a wireless connection. I also have a 15 mbps, spectrum internet account, with upload speeds of ~2.5 mbps. there are many other file sharing sites you can use, but if your internet speed is limited, you may run into the same problem. the boot.emmc.win is the correct file. it has to be renamed to boot.img for me to unpack it to edit it. I just got off work, so it took a while to respond to your message.
[Miscellaneous Android Development] martyfender:
[MENTION=8479770]billybleu97[/MENTION]

I sent you a pm with the link to to the modified boot.img for the V1.0.8 version of the ares 8a.

I also responded here concerning the ares 10a:

https://xdaforums.com/android/help/loss-nextbook-nx16a10132s-ares-10a-t3654507/post74200840#post74200840

Please let me know how it works and if you encounter any problems. The pm also outlines the feeback that I need concerning it also. Be sure to test wifi, sound and bluetooth, as that is the the problem that a few users of newer versions of the tablet have encountered, when they presumably matched the correct version of the modified boot.img, with the corresponding system version.

Thanks

UPDATE:

I will eventually release this if I get good feedback from you, as there have been a few others with your version of the tablet who have posted on this thread, but never provided me with the original boot.img for me to modify. I also have some more info for you, once you provide feedback, that may be useful in the future, with your device.
[Miscellaneous Android Development] thew-tab:
[MENTION=8126387]martyfender[/MENTION], I just got the ares 8A with v1.22. I used the files for v. 1.20. Everything went well, with the unlocking and getting TWRP installed, but when I rebooted, I couldn't get connected to the wifi or bluetooth, I am downlading the TWRP back-up of 1.20 to see if that will fix it, do you have any ideas, if that doesnt work?

---------- Post added at 06:58 PM ---------- Previous post was at 06:44 PM ----------

the back-up seemed to work
[Miscellaneous Android Development] ericzollman:
Sorry bro, i don't have the tablet any more... I sold it to a buddy.
[Miscellaneous Android Development] martyfender:
That is a new version I was unaware of. If that is the case, that is why you lost wifi, bluetooth and sound. the same version boot.image must be used for it. I don't have that version of the boot.img to modify it.

I need to update the op and the files on android file host concerning systemless supersu.

I am currently recommending the official, systemless supersu, as it will patch the boot.img for you to disable encryption and dm-verity. It does not however, patch, by default, for selinux permissive. there is a supersu commandline option to do this, however, when I tried it I couldn't get it to work in permissive mode. Maybe I did it wrong. I tried it in the twrp terminal and also the in adb from linux. Currently, I am running both of my tablets with selinux in enforcing mode. Apparently I have no root apps that have problems with it. your results may differ, depending on which root apps you will be using. I can patch your original boot.img if you upload it to me, if you want selinux permissive.

The supersu config thread lists some of the command line options and inside the supersu.zip installer they can be found. Unfortunately, the supersu config is arm only, there is no x86 version of it.

https://xdaforums.com/apps/supersu/2017-08-13-supersu-config-t3655754

Here are the overidable variables:

Overridable variables (shell, /system/.supersu, /cache/.supersu, /data/.supersu):

# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)

# PATCHBOOTIMAGE - Automatically patch boot image? (true/false, SYSTEMLESS only)

# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)

# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)

# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false, SYSTEMLESS only)

# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE only)

# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)

# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/false, PATCHBOOTIMAGE only)

# Shell overrides all, /data/.supersu overrides /cache/.supersu overrides /system/.supersu

The 1.2.0 should work. if you want to use your backup of version 1.2.2, reflash it. It should include your original boot.img.

Reboot to fastboot mode and issue:

fastboot format userdata

hit return, wait to complete.

fastboot format cache

hit return, wait to complete.

Reboot to twrp and flash the systemless supersu, which must be on internal sd or external sd, first.

https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1

Reboot, which will take sometime, the first time, up to 5-6 minutes.

approve the android usb debugging security prompt. you should now be at the android setup screen to setup as new again.
[Miscellaneous Android Development] martyfender:
Thanks for your reply.

UPDATE: supersu systemless, only patches to disable encryption and dm-verity, by default. It does not patch selinux to be permissive.
[Miscellaneous Android Development] martyfender:
Thanks to @ billybleu97 , I have now uploaded a V1.0.8 modified boot.img to Android file host, linked here and in the op:

https://www.androidfilehost.com/?fid=962021903579487577

Included is the latest SR5-SuperSU-v2.82-SR5-20171001224502.zip, SYSTEMLESS VERSION, TWRP, an older version of jrummy's root check app and the original boot.img.

Flash this boot.img on the V1.0.8 tablet only, paired with it's V1.0.8 rom, only.

It is modifed to remove encryption, dm_verity and selinux permissive.

If you want selinux enforcing, flash the original boot.img, followed by Supersu systemless and it will patch your boot.img to remove encryption and dm_verity, only.

I'm not sure what is going on at android file host lately, but in the last few days, when I have tried accessing my files, I have had intermittent problems loading the page. I notice they have made some major interface changes. Hopefully they get the problems ironed out.

UPDATE: uploaded a new file to correct an error.
[Miscellaneous Android Development] leveck:
8A 1.22 Issues

I have a 1.22 device. So, installed TWRP, flashed the 1.20 image as described in this thread, got Super SU installed, unit is rooted. Of course I do not have wifi, et al. Interesting twist: TWRP will not restore the 1.20 backup image linked to in this thread.

Caveat: I am trying to restore the image from a USB-OTG + thumbdrive (formatted as FAT). Do I need a microSD? Is there another culprit?:confused:

Sorry to have bothered you guys... figured it out - user error
[Miscellaneous Android Development] martyfender:
I have not purchased the special, USB-OTG cable to try it, although there have been a couple of instances where it would be useful. Just for clarification, did you get USB-OTG to work on your device and have the drive show up in twrp?

If your tablet, truly is a 1.2.2 device, as would have been shown in settings: about tablet: build number: V1.2.2 and you flashed my V1.2.0 boot.img, that is one reason you lost wifi, et al.

Of course, if you have successfully flashed my V1.2.0 backup, it will now show as V1.2.0. Out of curiosity, what is your IFWI version, also shown listed in settings: about tablet?

Personally, I have not lost wifi, et al, when the same boot.img version is paired with the same system version. Some others have and I wonder if my tutorial needs to be modified in some way to change the order that the steps are done?

The current way that I do it is:

1. Unlock bootloader

2. Boot into temp TWRP and backup boot, system and recovery and data.

3. Immediately boot into fastboot and delete userdata and cache.

4. Reboot to bootloader and fastboot flash the boot.img and TWRP.

5. Reboot to TWRP and flash SuperSu and YDS BusyBox.

7. Reboot to the new, Android setup screen and setup the device.

I believe that is how I did it when I got my newer, V1.2.0, tablet.
[Miscellaneous Android Development] DME44:
HELPP! i have version 1.2.2 Which one would be compatible? Thanks

I have version 1.2.2 Which one is compatible? Thanks
[Miscellaneous Android Development] dorpmuller:
None of this works for me. I have the 1.08 version. I have followed the instructions to the letter, even to the point of installing adb\fastboot to another windows machine. All I get when trying to flash the images is that windows spits out a line that says it cannot determine a filename and that it is an unknown image. I downloaded it 3X from the horrible android file host and still no joy. This might have worked for youall but I'm SOL. Thoughts?

Thanks, Rich
[Miscellaneous Android Development] martyfender:
See my previous post concerning this version of the tablet which I have never seen for instructions.

download the official, SR5-SuperSU-v2.82-SR5-20171001224502.zip from the supersu beta xda thread,

boot to temp twrp and backup your system, then in twrp flash the SR5-SuperSU-v2.82-SR5-20171001224502.zip. it will patch your boot.img to disable encryption and dm-verity..

reboot to bootloader mode and delete userdata and cache see my instructions to do this.

All data will be deleted including any pictures and files in the internal sd so have a backup before hand.

reboot to android to setup.

For a selinux disable version I would need your original, backedup boot.img named boot.emmc.win to modify to remove selinux enforced. I now use mine in enforcing mode.

You only need permissive in some unusual circumstances, such as certain programs etc.

The twrp included in any of my file downloads are all the same.

Just don't use my included unoffical supersu system mode zip. You can only use it it you have your original boot.img patched by me or others, in Android Image Kitchen.
[Miscellaneous Android Development] philcurious:
i was one of the lucky individuals who didn't bother making a backup of their original boot.img. i installed the 1.2.0 backup and everything works except for the internal speaker, neither of the 2.1.5 boot.img in the OP do anything other than boot loop, and i left unsigned_new.img try overnight, so i was wondering if anyone has a full backup of the 2.1.5 version or if anyone had any other ideas
[Miscellaneous Android Development] martyfender:
I wish I could buy a newer version of the tablet such as 2.1.5, but the store I work at in Indianapolis only has a few of the V1.2.0 left. Walmart.com shows out of stock, so it may be discontinued, I have no idea. My suspicion is that Walmart may be discontinuing this tablet. Reviewers gave it a bad rap, mostly based on ignorance and inexperience, I believe.

If you installed my V1.2.0 backup, you need to use the boot.img provided with it to get sound. If a different version boot.img is paired with it, you will potentially loose wifi, sound and bluetooth. I don't recall if the V1.2.0 rom works, or not, with the newer version of the tablet without re-reading my thread for owner's reports of the V2.1.5 version.

The bootloop was probably cause by not flashing the supersu

systemless

version in twrp, before rebooting in standard mode.

I currently recommend the lastest beta version, from the supersu beta, xda thread: SR5-SuperSU-v2.82-SR5-20171001224502.zip. This info is based on a user report with the V2.1.5 tablet and what [MENTION=2472806]vampirefo[/MENTION] told me concerning the reason for the bootloop.

Read back in the thread for further info.

I would appreciate any feedback you give me, since I don't own a V2.1.5 tablet.

Also, I don't check this thread, very often, anymore, since there are very few new posts. If I can help in any way, I will give it my best.
[Miscellaneous Android Development] philcurious:
i am using the boot.img from your backup, it works best out of all of them, which i've tried due to (why not) but 1.2.0 boot.img has everything but the internal speaker working. like, sound works over bluetooth, i haven't tried wired headphones, i'll get back to you on if those work, but any kernel other than 1.2.0 either bootloops or doesn't get wifi or bluetooth.

update: regular wired headphones don't get sound either.
[Miscellaneous Android Development] philcurious:
i also haven't even tried to root it yet, it's just the internal speakers don't work straight from the backup, but none of the apps seem to be aware of this, and i'm currently using a bluetooth speaker that's playing fine

if any of that is helpful or if you have any other questions i'm happy to help