![]() (Don't use this if you have already unlocked your bootloader: if you want just stock FireOS flash it through TWRP, and if complete stock follow the guide in the unlock thread) To return to stock or recover from a soft brick:.Probably using pm uninstall on some system apps would work. Flashing GApps works well with TWRP, but the 16GB version doesn't have enough space in the system for even the pico version.Refer to this StackExchange post for a guide on how to install apps as system. You can install apps as system apps just as on any other device, and you can use the app Link2SD for converting user apps to system apps. ![]() A debloating guide made for HD 10, but works fine on the HD 8.Removing accounts and viewing Usage Access settings which are hidden.Amazon Fire Toolbox, I have never tried this but it looks awesome!.The first (and currently only) ROM for this device and it works great! Lineage-12.1 for Amazon Fire HD8 2017 (douglas).This link has a complete step-by-step guide, assuming you have some soldering experience. This is first root method ever discovered for this tablet and is a hardware root. Hardmod Root Your Amazon Fire HD 8 (7th Gen).Refer here for installing SuperSU for permanent root, and here for an automated script for Windows. This is the first software root method discovered for this tablet and is a really easy and quick method of getting a root shell, and the link has a complete guide on it. Using Magisk is recommended because SuperSU is no longer supported, and Magisk has modules, Magisk Hide, and the root prompt is working (In SuperSU it's not working so you have to always grant root permissions which is a major security loophole) You can flash Magisk using TWRP after bootloader unlock.You don't need to downgrade if you are on 5.6.4.0. Requires Linux, so you'll have to either install it as dual-boot or use a live system if you are not using it already. This is an excellent and complete guide which has everything you need for this. It is still possible to unlock by a different method, check the bootloader unlocking thread. The root method was patched in 5.6.4.0 (some versions of 5.6.4.0 still work so you could try) It is advisable to disable OTA updates or unlock the bootloader immediately. The italicized text below are my comments/clarifications.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |