I don't know if the other two might work, and I'd rather get an answer on this rather than just randomly trying things and repeatedly rebooting my computer. This got rid of the "!" - but it didn't solve my "device not found" when trying to run adb commands. There were three drivers to choose from, and I just picked the first one, as the guy that wrote the superuser post didn't run into that (apparently). I tried to manually assign this driver to the MTP item, and I overrode the compatibility warning. I also have Portable Devices: NXA8QC116 (no "!"). When Googling for help I found a superuser post about an "!" in the device manager. I thought I had adb for Windows installed correctly. I was able to drag and drop SuperSU246.zip to the SD card on the tablet. I have the developer options and USB debugging enabled on my tablet. I am getting "device not found" errors when I try to run the adb commands (such as "adb reboot bootloader"). (I would have to buy another hard drive or laptop to install Linux, and I would have to learn Linux). I am trying to use this guide to get root access to my Nextbook Ares 8, NXA8QC116, Android Version : 5.1.1 NOTE: the TWRP backup already has the modified boot.img, so you don't have to install the Ares8_5.1_modified_.greatbal.zipĬredit goes to vampirefo for his work in bringing TWRP and root to Nextbook Ares 8. Wipe dalvik-cache, cache, data, system.Ħ) In TWRP: Restore>Choose "Ares8_Stock_5.1_rooted_unencrypted.-TWRPbackup" Mine it's TWRP/BACKUPS/NXA8QC116/ folder.ĥ) In TWRP: Wipe>Advanced Wipe. Place it inside the TWRP/Backups/ folder. You could try it on your Ares 8 version.ġ) Download Ares8_Stock_5.1_rooted_ģ) Transfer the Ares8_Stock_5.1_rooted_unencrypted.-TWRPbackup folder you extracted to your sd card. It's pre-rooted and removed force encryption. This is the TWRP backup of the stock Ares 8 5.1.1 rom. Install SuperSU via TWRP for a better Android experience. Making a system backup is highly recommended (but not necessary).ĥ) Download, place on your sd card and install via TWRP the attached file Ares8_5.1_modified_.greatbal.zip (just like a normal zip file flashable via TWRP)Ħ) Reboot your device after successful installation. Root Nextbook Ares 8, TWRP Recovery, Disable encryptionģ) Don't reboot your device as the unmodified stock boot.img wouldn't work with unlocked bootloader and vampirefo's modified boot.img will not work with our stock 5.1.1 rom.Ĥ) Boot to TWRP. Else, leave this thread, and go elsewhere.Ģ) Head over to vampirefo's thread to install TWRP. Unencrypting your device will wipe your data partition.ġ) Read disclaimer above. IMPORTANT NOTE: Make a backup of all your important data. If you don't have a backup, you could try the TWRP 5.1.1 backup posted below.Ģ) TWRP installed (using vampirefo's method) If you are using a custom rom at the moment, go back to your TWRP backup of stock 5.1.1. NOTE: The modified boot.img attached is for the stock 5.1.1 It won't work properly with other roms. I am posting here the modified boot.img (with encryption removed) and a TWRP backup of the Rooted and Unencrypted Stock 5.1 rom so others may try (at their own risk).ġ) Nextbook Ares 8 with 5.1.1 stock rom. So i am happy with TWRP installed and a rooted Stock Ares 8 5.1.1 rom. I flashed my modified boot.img and my Ares 8 booted normally. I also modified it to remove the force encryption. So I edited the original 5.1 boot.img so it works on unlocked bootloader/custom recovery. Unfortunately too, the stock boot.img won't work with unlocked bootloader. Good thing is I made a TWRP backup of my stock 5.1 rom, including the original boot.img. My tablet was stuck in the Nextbook logo. But, unfortunately, his modified boot.img did not work with my Ares 8 5.1.1 stock rom. But, despite his warning, as I really needed TWRP and root, I went ahead and did his steps. His thread is specifically for the Nextbook Ares 8 with stock Android 5.0. I came across vampirefo's Root Nextbook Ares 8, TWRP Recovery, Disable encryption I bought a Nextbook Ares 8 whose stock rom is:Īs with all of my Android devices, I always have to have a custom recovery and device must be rooted.Īnd upon googling around, there's not much discussions/forums in installing custom recovery and root for this device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |