yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Iwantroot:
Ok, sorry felt like an idiot when I read what you said about the boot.img and realized what was going on.

Kernel version : 3.14.64-x86_64 (warrior@warrior-11) (gcc version 4.9.2 (GCC)) #1 SMP PREEMPT Thursday Feb 16 21:25:00 EST 2017.

Build ID : V2.1.5.MMB29M.20170327.212634

OK now at the risk of looking like an idiot again... In my twrp backup folder, the only files I see pertaining to boot are boot.emmc.win and boot.emmc.win.md5... How exactly do I go about getting the boot.img file?
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] The boot.emmc.win is the twrp boot image backup. The boot.emmc.win.md5 is not the boot image but an md5 verification checksum, which I don't need.

I only need: boot.emmc.win, which I will rename: boot.img so I can unpack it and edit it. You only need to send that file: boot.emmc.win . If you have google drive, which you should have if you setup a google account, you can upload it to there and create a sharable link to give to me. Or you can upload it somewhere else where files are shared. It is too big to attach here on xda.

You have the same kernel version, but the build ID is definitely a newer model. I'm not sure what was changed other than a later build date of March 27th. The build date may be the only thing that changed and the build ID.

Thanks
[Miscellaneous Android Development] Iwantroot:
Ok thanks for the explanation.

https://www.mediafire.com/file/n1waq1fn14zin5d/boot.emmc.win

Thank you for all your patience and help on this martyfender, it is truly appreciated
[Miscellaneous Android Development] martyfender:
I am having trouble with this, it appears to be much different than the older ares 8a models. When I repack it, it creates two boot images, smaller than the original.

Don't flash them in fastboot yet, unless they boot ok. The boot.img is your original you uploaded and renamed.

Boot to bootloader mode then issue fastboot boot image-new.img enter to boot it only.

Then try the other: fastboot boot unsigned-new.img

On my system I get into a continuous boot animation bootloop, where I have to shut down by holding the power button. See if you get a bootloop, also.

I am going to have to check into this further. It could be a bug in the tool I am using, not sure. Some of the files in the boot.img are named differently than the older builds of the tablet> that may or may not be the reason. Based on the file names outputted for the boot images it may be signed. So I am going to have to do some digging to hopefully find a solution. What I thought would take ten minutes may now take days. I work the next few days so it may be a while, unfortuately.

This appears to be a signed boot image and I have posted it on another forum to try to get answers, so be patient. Please report back to me the result asap.

Thanks

UPDATE: I uploaded a newer version to test after I redid it with java jdk installed on my machine.

https://www.androidfilehost.com/?fid=673368273298974572
[Miscellaneous Android Development] TriggerWarning:
I just got this tablet from Wal Mart for about 18 bucks on clearance, and what I could gather from the thread was that some versions of this tablet are rootable while others are not. Mine is the Ares 8a with marshallow 6.0. Is it possible for that version, and is it even worth jumping through all the hoops to get it rooted?
[Miscellaneous Android Development] martyfender:
Go to settings, about tablet and scroll all the way to the bottom to find the build number. this root solution is for v1.1.1 and v1.2.0. They both have Android 6.0.1.

If it is an older build, temp twrp may boot on it so you can backup and pull the original boot.img named: boot.emmc.win from it to upload to me to modify.

A newer version of the tablet I am having troubles modifying it but I don't think it will be a problem if it is an older version than the above two versions.
[Miscellaneous Android Development] martyfender:
There is a newer version v2.1.5 of the Ares 8A and I have a boot.img from it but am having trouble modifying it as it creates two boot images when I repack it, not sure why. It appears to be much different than from the older versions of the tablet. I am investigating as to the cause.
[Miscellaneous Android Development] Iwantroot:
martyfender, while I was on my lunch break I was able to try the image-new.img before I went back in to work. It booted perfectly, had sound, wifi, bluetooth, cameras etc. Everything worked perfect did not get a chance to try the unsigned.img or flash the image-new.img and try root yet but so far looks promising. When I get off work and get to work on it more I'll let you know how it goes. Once again many thanks for all your work on this I really appreciate it.
[Miscellaneous Android Development] martyfender:
Thanks for the response, I was worried because it would not boot on my older device. I updated it twice and updated the google drive link. If you downloaded it recently you got my latest build. If you could though please check and also report on flashing. i want to get any bugs out before I release it to the public.

Signed images need java installed for my app I use to sign boot image files.

That is what I had to install to get it to work.

Thanks
[Miscellaneous Android Development] Iwantroot:
Martyfender it was the updated files, I just saw the post while I was on lunch and downloaded them. I didn't even see it when you posted the first set. I'll be sure to let you know how it goes.
[Miscellaneous Android Development] martyfender:
I am at work now and don't get off until 11pm edt, but will check at my dinner and breaks.
[Miscellaneous Android Development] TurnaboutSavage:
Well, it took a while, but now the WiFi on my tablet is extremely slow. I've factory data reset my tablet, removed supersu, and did everything I could, but now I think my tablets WiFi is permanently slow. Is there a way to fix this?
[Miscellaneous Android Development] porkenhimer:
I rooted this tablet and everything is fine, except one thing. I keep keep getting a popup about the temperature of my device being warm so it dims the screen. I realize this is just a safety measure, but my device is not even warm when this happens. I know about editing the two thermal XML files in the ETC folder, but I do not really understand how to and do not wanna mess anything up. Has anyone else had this problem? Is there a solution besides editing the two thermal XML files in the ETC folder?

I know editing the two XML files is to raise the temperature for when the warnings popup and the screen dims. I have had several android devices and they have gotten extremely hot to the touch and the warning and screen dimming would not happen, but with this device it seems a bit extreme to dim the screen when the device is not even remotely warm. I need a way to either stop this from happening, or to stop it from happening so often. I am not worried about the device getting warm or hot, cause as I said I have had several devices get hot and never had a problem. Can someone please help me?
[Miscellaneous Android Development] martyfender:
I noticed that sometimes, before I rooted and removed the overhead of encryption, only when doing several playstore updates. I've only occasionally noticed it since I started fresh again by deleting userdata and cache in fastboot, which I think is better than a factory reset, despite it appearing to be the same thing. You might try that, or at the very least, delete the dalvik cache and cache in twrp advanced wipe.
[Miscellaneous Android Development] Iwantroot:
Ok tried flashing both the image-new.img and the unsigned-new.img, both flashed fine with everything working. But after installing root they both go into a constant bootloop.
[Miscellaneous Android Development] martyfender:
Did you install root by flashing SR1-SuperSU-v2.82-SYSTEMMODE.zip in twrp?

This may be a long shot, but you could try this after flashing supersu again. In twrp hit wipe, advanced wipe, check delete dalvik cache and cache. then reboot. A more drastic measure which will wipe all of your data is: boot to bootloader, then: fastboot format userdata hit enter, wait to finish, fastboot format cache wait to complete. Then fastboot reboot recovery to boot into twrp, then hit install to pick and flash the supersu.zip, then reboot to the android setup screen to start fresh. Let me know how it goes, as I don't yet have access to the newer tablet to test it.

I don't think this will make a difference, but there is an older version of supersu in systerm mode at:

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

SR3-supersu-2.79-SYSTEMMODE.zip , you could try, also. That is the one vampirefo originally supplied to me.

Please let me know your progress, so I can decide if the modified boot images are ready to be released to the public.

Thanks
[Miscellaneous Android Development] martyfender:
This could be one of the side effect of trying to flash several xposed versions, I'm not sure. You could start fresh again by booting into the bootloader, then fastboot format userdata enter, wait, fastboot format cache, then reboot and setup the tablet again. Or-- flash my twrp v1.2 backup. I think I have only had one user report wifi problems that were solved by doing one of the above. my experience with flashing the xposed uninstaller on the original ares 8 with 5.1.1 was that it didn't remove all of the changes to the system, so I had to revert to a good twrp backup to fix the problems I experienced.

That is only one of the reasons I won't try xposed again, at least not until I know there is a version that is compatible and doesn't cause any of the side effects that I experienced on the ares 8 5.1.1.
[Miscellaneous Android Development] TurnaboutSavage:
[MENTION=8126387]martyfender[/MENTION] Question, could I flash the modified v1.2 boot.img in twrp, or do I have to do it in adb?
[Miscellaneous Android Development] martyfender:
I am not 100% certain as I have never done it that way. and you can't in adb as adb works when you are booted into android normally. You would have to reboot to the bootloader:

adb reboot bootloader

and use fastboot:

fastboot flash boot boot.img

substituting the actual name of the boot.img at the end, for example:

fastboot flash boot Ares8A_Old_boot.img

then hit the enter key.

I tried it on my tablet and the boot.img doesn't show up in twrp on my external sd card under install, but does if I go to advanced, file manager external _sd/download . So twrp must be able to detect when a flashable zip it there, or not. I only see the two flashable zip files I have there: busybox and supersu.

UPDATE: hit the install button, hit the install image and it shows up. Then select the partition: Boot, swipe to confirm. I did it and it is booting as we speak.

Your question caused me to think a little and I learned something new today!

Thanks
[Miscellaneous Android Development] TurnaboutSavage:
Oh, I meant to say fastboot, not adb. So, is it safe to flash the newer boot.img if I used the old boot.img? Is that safe to do?
[Miscellaneous Android Development] martyfender:
The old boot image needs to be paired with the 1.1.1 rom. The newer boot image needs to be paired with the 1.2.0 rom. They both will boot on the device if they are not paired, but you will loose sound and maybe wifi and bluetooth. The first, I have confirmed, but the last two are speculation.

I updated my last post: you can flash the boot.img in twrp. See my updated instructions, as I flashed it to test, just a minute, or two ago.
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] [MENTION=1143630]osmosis[/MENTION] asked why I was not using the official supersu, which should install systemless on Marshmallow and above. The one I provided flashes in system mode. If my above suggestions don't work, you could try flashing that at:

https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip

I would recommend flashing unSU first to remove any remnants left over from previous versions and wipe the dalvik cache and cache first, in twrp, wipe, advanced wipe, before flashing the above, newer version.

https://xdaforums.com/showpost.php?p=63615067

I followed the directions I gave you to remove older supersu with unSU and have successful flashed it in systemless mode, to my device. So far, so good.

Be sure to read all of the info in twrp after it patches your boot image, it may take extra time to boot and could loop once or twice. I think it looped once on me, as I saw the boot animation start over once. Let me know how it goes.

Thanks
[Miscellaneous Android Development] Iwantroot:
Update, I tried all of your suggestions with the same results. Out of curiosity I tried the latest

.Zip from the supersu website and and it was successful, have verified root and also installed busybox using the latest .apk. Sound, wifi, bluetooth, cameras etc. All working correctly as well. This is using the unsigned-new.img, I have not attempted to try the same procedure with the image-new.img yet, but I will let you know how this turns out as well. Once again thank you martyfender for all your time and help
[Miscellaneous Android Development] Quentin Ferrel:
Tried on Build 2.1.5, not only ended up with no sound, i also ended up with no wifi, and bluetooth!

Also the battery numbers don't look like they're going up.
[Miscellaneous Android Development] martyfender:
So did you flash this one in systemless mode and it worked or did you get the lastest stable release from their website?

SR1-SuperSU-v2.82-SR1-20170608224931.zip This is the one I had suggested to try. SR stands for service release and is the current beta version. I just flashed that today and am having no issues in systemless mode. It fixed some issues in the released, stable version:

SuperSU-v2.82-201705271822.zip

So let me know which you used.

you can test boot the signed image in bootloader mode: fastboot boot image-new.img enter key and check if everything is fuctioning as well, without flashing it, but supersu in systemless mode would have patched your existing boot.img so supersu may not function and could even bootloop you unless you flash the signed boot image and reflash supersu again to patch the newer boot.img

Thanks
[Miscellaneous Android Development] Iwantroot:
SuperSU-v2.82-201705271822.zip this is the one I used
[Miscellaneous Android Development] martyfender:
So you had previously tried this one and it bootlooped also:

SR1-SuperSU-v2.82-SR1-20170608224931.zip ?
[Miscellaneous Android Development] martyfender:
here is a link to updated bootimages for your device. Don't use the one named boot.img as it is the original unmodified version. I got a report that the unsigned one works and he had to use supersu Stable which flashes in systemless mode, by default. see posts above use unsu first.

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

https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
[Miscellaneous Android Development] Iwantroot:
Martyfender I have not tried that one yet I did not see that post before trying the SuperSU-v2.82-201705271822.zip
[Miscellaneous Android Development] Quentin Ferrel:
Wow, i am not the brightest. Just figured out before installing the unsigned boot.img file,that

my build is really 1.2.2, and i don't know what to do now.

unsu and installed it again, but to no avail.

Please help me! as im doing this for my brother.
[Miscellaneous Android Development] martyfender:
I'm not familiar 1.2.2, but I have a backup for 1.2.0 linked in the OP. Are you sure it is not 1.2.0? It has all userdata deleted to start fresh with the android setup screen. It is a twrp backup you must place in the correct folder of your external sd card for twrp to recognize it. For example:

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

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

Then booted into twrp, hit restore and choose the correct backup folder, then swipe to restore. If you don't see it in twrp you didn't place it in the correct folder hierarchy.
[Miscellaneous Android Development] martyfender:
[MENTION=8423816]Iwantroot[/MENTION] I am glad to hear that it worked out for you.

Do you have a twrp backup of your system image before you rooted it that you can upload? Even if you only have one after rooting you could upload that if you don't have a backup of the original. I want to test it with my modified boot.img to see if it works on my older tablet and provide a backup of it on android file host as well, for all.

it would be named, for example: system.ext4.win000 and system.ext4.win001. those are the system image split into two parts. There should be two .md5 files of the same name. I should probably provide those as well for people who want to verify the files. It can be zipped to save space and bandwidth.

Thanks
[Miscellaneous Android Development] Quentin Ferrel:
I am restoring the 1.2.0 file like you said, ill report if it works.

---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------

Thank you so much! Just Tested it and the wifi, bluetooth and everything else broken is fixed!

I Really appreciated your help!

Again just thank you so much!
[Miscellaneous Android Development] Iwantroot:
Martyfender, I do have the backup of system before rooting. Unfortunately at this point I'm limited to just the data on my phone. I'm not sure how soon I will have access to a good connection but as soon as I get the opportunity I will upload my system backup for you.
[Miscellaneous Android Development] martyfender:
I updated the OP with the boot images and twrp for the version 2.1.5 of the tablet only.

Do not flash these boot images on the 1.1.1 or the 1.2.0 versions of the tablet,

They will bootloop your device. The twrp is still the same, and only version I have.

You also need supersu systemless for this newer device. That link is also in the Op for the latest, stable version released.

Here is the easiest way to tell what version of the tablet you have:

Go to settings, about tablet and scroll to the very bottom: build number: V1.2.0, for example, the first few numbers of that long, build number.
[Miscellaneous Android Development] martyfender:
Thanks, Just curious, how do you use your phones data with the tablet? Or do you mean you have to put the sd card of the tablet in the phone and upload that way.

I guess I am spoiled and have hispeed internet at home and reasonable wifi at work, so I use wifi at work and home, so even on my phone, I use almost not data.

There is a new link for the 2.1.5 boot images and twrp on android file host. They are the same ones you have, minus the original boot image, as to not confuse people.

Today I changed to the Android norm for 6.0+, systemless root and so far I have encountered no problems. I am about to change my recommendation for that for even older versions of the tablet. [MENTION=1143630]osmosis[/MENTION] a well known Android developer on xda recommended it to me to fix your bootloop problem on your newer device. It does have some disadvantages though, any time you reflash the boot image, you need to reflash supersu so it can repatch the boot image to work. In system mode you can reflash the boot image and supersu will still work without reflashing it. Also, some older apps not updated with systemless root in mind, may not work properly.

Adaway has a setting if you are using systemless root, to also place it's host file where it does not touch the system.

Thanks again
[Galaxy S6 Q&A, Help & Troubleshooting] jp071848:
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.

Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.

Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?

Thanks in advance.
[Galaxy S6 Q&A, Help & Troubleshooting] sofir786:
Just use Samsung smartswitch software to restore firmware.
[Galaxy S6 Q&A, Help & Troubleshooting] forumber2:
Your device's model is SM-G920W8, right?

And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
[Galaxy S6 Q&A, Help & Troubleshooting] sofir786:
He tried to downgrade from marshmallow to lollipop that's why it failed.
[Galaxy S6 Q&A, Help & Troubleshooting] forumber2:
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.

And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
[Galaxy S6 Q&A, Help & Troubleshooting] sofir786:
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing