yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Jimmy2526:
So I need to make a folder on an sdcard that's named twrp/backups......etc and insert into the tablet then try to boot it into temp twrp

---------- Post added at 08:01 AM ---------- Previous post was at 07:44 AM ----------

I can't open cmd by right click+shift.. my system always wants to open Windows power shell so I always just open cmd and then (cd to the dir where my files are..) I was just trying to show that I do indeed have and and fastboot installed system wide
[Miscellaneous Android Development] martyfender:
You could try creating a short cut for the command prompt in the minimal adb folder. On Windows, the cmd.exe is in System/System32. There is also one in System/SysWOW64. Create a short cut for the one in System32 in the minimal adb folder. I have done that before when I was using minimal adb, which I still have on my Windows partition.

I am currently booted into Linux Mint most of the time and I forgot about the shift, right click in Windows. In Linux I just right click and choose open in terminal. My Windows is 7 so I only have the "open a command prompt here" and not the powershell option. Have you tried the commands in powershell? I am not very familiar with it, but know of it.
[Miscellaneous Android Development] Jimmy2526:
I'm not very familar with it at all myself.. I've been thinking about going to Linux. In reality it seems and looks like an easy to use self explanatory variable and powerful in the programming aspect. But you know it's the nervousness of looking my cherry and still failing at the same time that's making me apprehensive about it
[Miscellaneous Android Development] martyfender:
I would tell most to stick with Window because it is easier to find support for it.

Any luck getting temp TWRP to boot?

This is a long shot, but I wonder if he unlocked the bootloader before he did what ever he did that bricked it. The fastboot command to unlock it is:

fastboot flashing unlock

what happens when you enter the above command? If that succeeds, try again to temp boot TWRP.

I neither of the above works then my original thought that the bootloader/fastboot partition is messed up, since you state that you can't boot the tablet into that mode with the little green Android guy on his side.
[Miscellaneous Android Development] Jimmy2526:
I'm just now getting the file copied to a sd card so I need to extract it there then rename it correct
[Miscellaneous Android Development] martyfender:
None of the above will work if you first can't get TWRP to temp boot, or did you?
[Miscellaneous Android Development] Jimmy2526:
I haven't tried waiting to get my files in order and in correct format on sd card
[Miscellaneous Android Development] martyfender:
Like I stated, that is wasted effort if you can't boot into or install TWRP.
[Miscellaneous Android Development] Jimmy2526:
This is what fastboot returns with all the things you've questioned.. when I tell it to boot twrp it says it did but the tablet will sit there for like 20-30 sec then reboots to the same DNX FASTBOOT MODE screen
[Miscellaneous Android Development] martyfender:
This probably won't work in your case, but you can also try to install TWRP:

fastboot flash recovery Ares8A_recovery_twrp.img

I you can find out if there is a way to pull the files and restore the bootloader/fastboot mode, I could do that.

I'm not sure where you can ask, though. One possibility is the TWRP build forums, although they may consider this off topic, even if it is to get TWRP to boot.

You can use this info in my signature to post:

Nextbook Ares 8A

Processor: Intel x86 Cherry Trail Atom x5-Z8350 @1.92 GHz, 1gb RAM, 16gb internal storage

Model number: NX16A8116K

Android version: 6.0.1 Marshmallow

Kernel version: 3.14.64-x86_64
[Miscellaneous Android Development] vampirefo:
You could buy this tablet from eBay, and save yourself a lot of stress. The tablet is requesting bootable media, without knowing what was done to tablet, you may be wasting your time.

Boot a boot.img for that tablet instead of twrp.
[Miscellaneous Android Development] martyfender:
The ones I have seen people post here did not provide the activation code or disa code which means they may have been aquired illegally by the ebay seller.
[Miscellaneous Android Development] martyfender:
Hello [MENTION=2472806]vampirefo[/MENTION], great to hear from you. Thinking about it, booting from a boot.img does make sense, I guess there has always been a boot.img on a device when I booted twrp.

I do not know how to defeat that activation, nor do I know the sellers on ebay that are doing that. If you know of a way to defeat it I have had a few people ask how too.
[Miscellaneous Android Development] Jimmy2526:
I've tried all that already. I've tried to boot into the system,bootloader,recovery,the boot image twrp nothing works at this point
[Miscellaneous Android Development] vampirefo:
I wouldn't post how to by pass a security measure, that only increases stealing.

Anyway I don't use these tablets, Was just suggesting the user buy another tablet, rather than stress himself out on the one he has.
[Miscellaneous Android Development] JAGMAD_:
Hello. I have the Ares 10a tablet, but I assumed these would work on it as well because they should technically use the same system files. But I'm at a hault right now, I have a bricked system that is stuck on the nextbook logo when activated. Luckily, I have TWRP on it before hand but I don't have a backup of the system files nor do I know how to put the files back onto it. If anyone is able to help me figure out how to put the files from this forum onto my tablet in order to restore it to a working state it would be greatly appreciated.

Thanks,

-JAGMAD.
[Miscellaneous Android Development] TJMartin55:
Tablet wont boot

Unfortunately I followed some other instructions prior to finding these and have totally screwed up my grandsons new Tablet. It's a Nextbook Ares 8 A 16G. So here's what I did and why, I only wanted to get rid of the encryption so I downloaded ADP and the drivers and installed them on PC. I was able to access the tablet and Below are the steps I followed. Now the Tablet wont boot is does go to what I guess is TWRP but I only have the option to continue or select a file to boot from, I can't figure out how to get it to boot manager or any of the other options in TWRP that show on the screen. I cannot access the tablet any more from PC to use adp again and even though the tablet does see a thumb drive when I insert it into the usb it will not boot from the Boot.img file I downloaded from your links that match my version. (2.11) Have I bricked this thing? Is there any hope of recovery? It will read for thumb drive in USB , does that leave any type of hope for recovery? Thank you for any and all assistance. This thing was literally brand new and my grandson is not to happy with Grandpa today.

(Droid School Instructions)

Next connect your device to PC & write the below command and press enter

adb reboot bootloader

5. Switch off your device & turn on into fastboot mode

Write the below command you can flash the TWRP recovery of your device

fastboot flash recovery twrp_recovery.img

To disable Encryption type In TWRP Flash The Boot you can use the bellow command

fastboot flash boot boot.img

Reboot your device with below commend

fastboot reboot
[Miscellaneous Android Development] TJMartin55:
Reply

Thank you for your quick reply, Although adb would not see the device fastboot actually would so I followed your instructions accurately and BAM it's fixed. I now have your 211 image, TWRP and supersu installed and the machine seems to be running well. After getting it running correctly I also went into TWRP and have done a complete backup of the Tablet with the NOW correct Stuff on it. Appreciate you assistance and patience in helping me get this straightened out. Grandson will be very happy... :)
[Miscellaneous Android Development] martyfender:
[MENTION=8203588]TJMartin55[/MENTION] I'm glad I could help. Now that you have the device booting into Android normally, you should also be able to see it again in adb. My suspicion is that boot verification was failing at boot, until dm_verity was disabled or the data partition was newly created again to disable encryption. In other words, it could have failed because encryption was disabled in the boot.img and it could not boot because of the still existing, encrypted, old, data partition.

I wish I could still purchase more of the older, Intel, Android 6.0.1 tablets in the store I work in, but we only have the newer, slower, Arm based ones, with Android 7.0.1 Nougat, that can't easily be rooted.
[Miscellaneous Android Development] mohsin-*:
can i able Root This one ? which boot will work

(bootloader) unlocked: no

(bootloader) secure: yes

(bootloader) serialno: CHTT000128C5

(bootloader) board: Insyde Cherry Trail CR Type2 - Board V

(bootloader) device-state: locked

(bootloader) boot-state: ORANGE

(bootloader) firmware: INSYDE Corp. M882_JJ.019

(bootloader) product-name: CherryTrail

(bootloader) secureboot: no

(bootloader) off-mode-charge: 1

(bootloader) has-slot:config: no

(bootloader) partition-type:config: ext4

(bootloader) partition-size:config: 0x0000000000800000

(bootloader) has-slot:persistent: no

(bootloader) partition-type:persistent: ext4

(bootloader) partition-size:persistent: 0x0000000000100000

(bootloader) has-slot:userdata: no

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:userdata: 0x00000002A7800000

(bootloader) has-slot:data: no

(bootloader) partition-type:data: ext4

(bootloader) partition-size:data: 0x00000002A7800000

(bootloader) has-slot:cache: no

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:cache: 0x0000000025800000

(bootloader) has-slot:system: no

(bootloader) partition-type:system: ext4

(bootloader) partition-size:system: 0x00000000C0000000

(bootloader) has-slot:metadata: no

(bootloader) partition-type:metadata: none

(bootloader) partition-size:metadata: 0x0000000001000000

(bootloader) has-slot:misc: no

(bootloader) partition-type:misc: none

(bootloader) partition-size:misc: 0x0000000000100000

(bootloader) has-slot:recovery: no

(bootloader) partition-type:recovery: none

(bootloader) partition-size:recovery: 0x0000000001E00000

(bootloader) has-slot:boot: no

(bootloader) partition-type:boot: none

(bootloader) partition-size:boot: 0x0000000001E00000

(bootloader) has-slot:bootloader2: no

(bootloader) partition-type:bootloader2: none

(bootloader) partition-size:bootloader2: 0x0000000003C0000

(bootloader) has-slot:bootloader: no

(bootloader) partition-type:bootloader: vfat

(bootloader) partition-size:bootloader: 0x0000000003C00000

(bootloader) max-download-size: 0x0000000010000000

(bootloader) battery-voltage: 3766mV

(bootloader) version-bootloader: kernelflinger-02.20

(bootloader) product: NXM882CAP
[Miscellaneous Android Development] kazooguyz2:
Help!!

Purchased 2 of the Nextbook Ares 8a in August of 2017. (They were discount priced at $35 each) Opened 1 of them and use it regularly. Decided to open the other one to do all the updates and keep it "fresh". Pressed the power button, saw the Nextbook logo for about a second and then got the message Android Boot Failed. Made contact with Nextbook customer service and explained situation. They refuse to help me since I no longer have the original receipt. Looked at the manufacture date on the box, Jan 2017. No longer in warranty anyways so I gave up trying to get help from them. I would like to use it as a backup. The one that works has Android Marshmallow 6.0.1 Is there anything I can do to get it working?
[Miscellaneous Android Development] martyfender:
The info you provide does not state the version of the tablet you have, found in settings, about tablet, but it appears you have a V1.2.0 tablet. My current recommendations are

not

to use my modified boot.img and supersu in systemmode, but to flash the latest, beta version of supersu, which is systemless and will patch your original boot.img. or the other option is to use Magisk for root and let Magisk patch your original boot.img.

I currently use Magisk Unofficial builds with the latest fixes in it, on these tablets, as noted in my signature.

https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

https://github.com/kantjer/MagiskFiles

Or you can use the latest, stable version, 16.0 found in one of the links listed on this page:

https://xdaforums.com/apps/magisk

If you choose Magisk to root, sometimes the Magisk Manager does not install when flashing through TWRP and you may have to install it separately. If this happens, you can download it and install it, or extract it from the Magisk.zip, of the current version you are using. The one in the stable, 16.0 zip may be an older version than the v5.7.0 that they link on the stable page, though and has some fixes for crashes, etc..

However, the lastest, unofficial version as of this writing, works great on all 4 of my Ares 8A's.

You can flash them through TWRP. The TWRP is the same for all versions of my hosted files on Android File Host.

the other way to do it is through the magisk manager direct install method. I have the unofficial set in the Magisk Manager settings, custom channel:

https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json

With the above option, you install the Manager only and it will download the Magisk.zip and patch your boot.img, then you reboot to finish.
[Miscellaneous Android Development] KiLL3Rw0lF:
Does anyone happen to have a modded boot image for Ares 8 version 1.1.0? It boots on 1.1.1 and 1.2.0, however I have lost wifi ability.:eek:
[Miscellaneous Android Development] martyfender:
[MENTION=9275375]KiLL3Rw0lF[/MENTION] Do you really mean the Ares 8A? If it is an 8A that is a version I was not aware of.

If it is an 8A and you still have a copy of the original boot.img, I recommend that you flash your stock boot.img, followed by the SuperSU systemless version linked here and it will patch your boot.img to remove encryption and dm_verity, by default, so you don't need a pre-patched image. Somewhere, I posted these updated recommendations, but it may have been missed by you.

https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

If you do not have your stock boot.img, flashing my twrp backed up rom, v 1.1.1 or v1.2.0 fully, which includes the boot.img and system, should allow you to have wifi and sound, I believe. I think that should work on your v1.1.0 tablet. I believe for it to work correctly you need to delete userdata, unfortunately.

You can delete userdata 2 ways:

1: Boot to TWRP and choose wipe, factory reset.

2: boot into fastboot/bootloader mode and issue from the command prompt on your attached computer:

fastboot format userdata

then hit the enter key then:

fastboot format cache

then hit the enter key and watch for messages in the above 2 commands for successful completion.

Please post here if you are successful and if you have any other questions.
[Miscellaneous Android Development] martyfender:
You lost wifi because the boot image version must be paired with the same version of the rom, ie. v1.1.0 boot image with v1.1.0 system or v1.1.1 boot image with the v1.1.1 system, etc.

Any v1.0 rom works correctly with both my v1.1.1 tablets and my v1.2.0 tablets.

V3.0.4 rom works on my v1.1.1 and v1.2.0 tablets, but I loose sound.on the internal speaker but keep bluetooth sound. So you must stay within the same version series, 1.0+. I am not sure if there are hardware differences, but more than likely it is because of the different IFWI (Intel Firmware Interface Version).
[Miscellaneous Android Development] KiLL3Rw0lF:
Yep. It's an Ares8A. I also have a version 4.0.0 Ares 8 as well. The boot I'm got corrupted on that before I did anything to it, so I'll try to flash your twrp backup on to that one as well. Right now I'm finishing installing Windows onto the version 1.1.0 Ares 8. I am pretty positive that I have figured out a way to install Windows 10 32-bit. It has to be a 32-but system due to the RAM limitations. Unfortunately I can't find my OTG cable to hook up a keyboard. I can get it to the W10 installation loading screens but there is no touch feature until later on in the installation so I need a OTG until then.:D

---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------

My guess would be a difference in hardware. The wifi modules are probably different so the drivers won't 'line up'. Probably just a small change between models to save a small amount of money where they can.
[Miscellaneous Android Development] KiLL3Rw0lF:
[MENTION=8126387]martyfender[/MENTION] Would you happen to come across a backup of V4.0.0 as well for the Ares 8? That's the one that I got with the corrupt boot image. I cannot seem to get it to boot off any of your backups or boot images and I need Wi-Fi on it. Right now I'm trying to reinstall TWRP onto it. I forgot how I got it on there in first place. I have a backup of this one, however I need to get TWRP back installed in order to recover it and the boot and system images are off. Although the backup booted there was no Wi-Fi. I got TWRP on it somehow, however I have missplaced my link on how to do that. This one had to have a different file.
[Miscellaneous Android Development] martyfender:
I have never come across a v4.0.0 tablet. The newest one I have is V3.0.4.

Usually you flash twrp through fastboot or temp boot it, Without installing it. See op.

The newer ares 8a tablets in my store are arm based and have android 7.0.1 which i don,'t know how to root as no twrp is made for it.
[Miscellaneous Android Development] KiLL3Rw0lF:
[MENTION=8126387]martyfender[/MENTION] I did get TWRP back on it and reflashed my backup. For some reason it is sensitive to which TWRP is installed so I had to go through my list of TWRP images and I eventually found one for Ares 8 on Android 5.1.1 that worked. The 4.0.0 is a Intel tablet running Android 5.0 or 5.1. The weird thing is that the 4.0.0 looks like the oldest out of all of them. I have a ARM one as well, however that one I believe to be bricked.

---------- Post added at 02:41 PM ---------- Previous post was at 02:41 PM ----------

[MENTION=8126387]martyfender[/MENTION] I did get TWRP back on it and reflashed my backup. For some reason it is sensitive to which TWRP is installed so I had to go through my list of TWRP images and I eventually found one for Ares 8 on Android 5.1.1 that worked. The 4.0.0 is a Intel tablet running Android 5.0 or 5.1. The weird thing is that the 4.0.0 looks like the oldest out of all of them. I have a ARM one as well, however that one I believe to be bricked.

---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------

[MENTION=8126387]martyfender[/MENTION] I did get TWRP back on it and reflashed my backup. For some reason it is sensitive to which TWRP is installed so I had to go through my list of TWRP images and I eventually found one for Ares 8 on Android 5.1.1 that worked. The 4.0.0 is a Intel tablet running Android 5.0 or 5.1. The weird thing is that the 4.0.0 looks like the oldest out of all of them. I have a ARM one as well, however that one I believe to be bricked.

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

[MENTION=8126387]martyfender[/MENTION] I did get TWRP back on it and reflashed my backup. For some reason it is sensitive to which TWRP is installed so I had to go through my list of TWRP images and I eventually found one for Ares 8 on Android 5.1.1 that worked. The 4.0.0 is a Intel tablet running Android 5.0 or 5.1. The weird thing is that the 4.0.0 looks like the oldest out of all of them. I have a ARM one as well, however that one I believe to be bricked.
[Miscellaneous Android Development] martyfender:
So that tablet is an Ares 8 and not an Ares 8A and that would use a different TWRP, to be found somewhere in vampirefo's threads concerning the Ares 8.

My original Ares 8 which I had last updated to 5.1.1 unfortunately has died.

He also has a rom to update the original 5.0 tablet to 5.1.1 That is what mine was, it originally had 5.0 on it.
[Miscellaneous Android Development] KiLL3Rw0lF:
[MENTION=8126387]martyfender[/MENTION] Ah, that stinks. You wouldn't happen to have made a TWRP backup of the 8 would you? I got it to 5.1 using his instructions, however that still did not enable Wi-Fi. I'm just messing around right now trying to see if I can get any of your 8A backups to boot on the 8. XD

Sorry about the multiple post. I have no clue as to what happened there. Lol
[Miscellaneous Android Development] martyfender:
The Ares 8 and the Ares 8A have entirely different partition schemes and completely different hardware, so I think it is impossible to get the 8a rom to work on it.
[Miscellaneous Android Development] codyw1996:
When attempting to decrypt my Ares8 v2.1.5 I found that "fastboot format userdata" returns an error "CreateProcess failed: The system cannot find the file specified. (2) error: Cannot generate image for userdata"

"fastboot erase userdata" does work, and it is sufficient to decrypt the tablet and allow access to internal storage in TWRP. I couldn't flash SU or Busybox until after decrypting the tablet.
[Miscellaneous Android Development] martyfender:
Are you sure it is not an Ares 8A? The Ares 8 is an older version with a baytrail processor and Android 5, with a completely different partitioning scheme.

I have an Ares 8A v2.1.5, but have never used the fastboot commands with it to format or erase userdata. It very well may be different, as it is slighly newer hardware than v1+ series.

Are you doing this from Windows or Linux? In Linux there are different versions of the fastboot binaries that have slightly different command sets.

The first one I tried was missing the fastboot flashing unlock command, for example. I'm not sure if there are different ones in Windows binaries with different command sets. I have had no reason to test it recently on my Ares 8A v2.1.5. I may have only done a factory reset on it originally, before flashing Magisk on it. I can't remember.
[Miscellaneous Android Development] KiLL3Rw0lF:
Your v1.1.1 backup 'worked', however the Wi-Fi was still dead. The weirdest thing though. The v1.1.1 backup flashed and showed up as v1.0.1, or something like that in the Android settings details. I'm working on buying another Ares 8 tablet to make repairs and get a flashable backup file off of.

Unfortunately I believe I had bricked the tablet that I was installing Windows on. I was messing with a boot image that allowed me to enter a device BIOS. I believe I accidentally changed the boot display so now there is no picture. I'm guessing it's trying to boot off of the micro HDMI so I'm going to grab one of those cables eventually and try and reset it. I can still enter the bootloader through the buttons, however there is no display. The only reason that I know it is in the bootloader is through 'fastboot devices', to which it shows up. I have the battery disconnected currently and it's setting on my desk.