[Miscellaneous Android Development] martyfender:
I didn't use a tethered recovery, I used the twrp recovery posted at the start of this thread. It is in the ares8_5.0_upgrade_5.1.zip.

When I had similar problems, I found a post by [MENTION=5368024 [MENTION=4821597]social-design-concepts[/MENTION] https://xdaforums.com/showpost.php?p=65435780&postcount=409 in the original ares 8 thread to fix the problem:

"

Member

94 posts

Thanks: 30

Quote:

Originally Posted by social-design-concepts

"thats the uefi / bios access menu you'll need an usb otg adapter and most devices ( not all ) require use of a powered usb hub ( which i personally recommend regardless as devices that use more power can short out the port ) and keyboard and mouse to navigate it. but it looks as if you esp is corrupt if you have the efiloader and droidboot.img you can try.

Code:

fastboot flash osloader efilinux.efi

fastboot boot droidboot.img

this should get you back into droidboot / fastboot where you can then partition your device and reflash the esp and the reset of android.

[MENTION=4821597]social-design-concepts[/MENTION], thanks for this post. When I tried to reinstall vampirefo's latest 5.1.1 rom, ported to work on the 5.0 device, it failed and Could only get into dnx mode. I used your instruction to fix the ESP partition, then reinstalled the rom, with no problems. It is running great now.

Thanks, again."

I used the above commands and files within the rom posted above, so I didn't even need a usb otg adapter to do it. I believe I used the droidboot.img and efilinux.efi. The efilinux.efi is in the esp.zip. unzip to the root of your folder where you have adb and fastboot installed. The rom files must also be unzipped to that location.

The above commands are run through an adb and fastboot command prompt, from your computer. Those are the windows commands. they would be slightly different if you are on linux. Then I rebooted the tablet back into fastboot mode: fastboot reboot bootloader, which worked again, ran the fastboot_cmd.bat to reflash the rom again. This was all done from the computer with an adb and command prompt, using fastboot commands, of course. Type fastboot devices, to make sure your device is showing up, before proceeding

I never figured out the cause of the problem when I reflashed this rom the second time, but I suspect I should have done a factory reset before doing it. It was flashing the above files that gave me the ability to get into fastboot bootloader again, then I reflashed the whole rom the third time and it worked as it did the first time I did it.

Currently I am using the newer, twrp 3.1 recovery he posted in the ares 8 5.1 problems thread.

UPDATE: if you don't have a permanent recovery installed, this may or may not work in the tethered, temp, twrp recovery. I don't know as I have never used the tethered, temp, recovery.

Actually, I think I used the fastboot commands in dnx mode to flash the droidboot.img and efilinux.efi, rebooted into the bootloader: fastboot reboot bootloader and then ran the fastboot_cmd.bat to reflash the rom.

And of course, you have to make sure adb and fastboot drivers are setup correctly and recognizing your device, for all of the above to work. I tried to retrace my steps. I hope I didn't forget any of them!

Good Luck!