AMLogic S912 & S905 FAQ ✰ Fix Root, Hide SU, Backup/Restore... ✩ Media Player TV Box!

[flipmode_11]

AMLogic S912 & S905 FAQ ✰ Fix Root, Hide SU, Backup/Restore... ✩ Media Player TV Box!

AMLogic S905 & S912 FAQ, Resources, Hints & Tips ✩ Fixing Root, Masking SU, Switch SuperUser (SU), Backup & Restore!
~ Android Media Centres, Streaming Players, Smart TV's & Multimedia TV Boxes ~​

SUMMARY:
This topic provides help and assistance to users of all levels, giving access to resources for all AMLogic S905 and S912 media centers and TV boxes (and any other compatible devices), and provides detailed steps and examples - all fully-tested. I have writen my own documentation for myself and friends, so decided to simply cleaned it all up and pasted it here to share.
There is limited support for these Chinese no-name clones, so I hope this is helpful to others, and others will share their knowledge too!
Warning! Beware of S905W devices (e.g. X96 Mini). The "S905W" has inferior specifications, a crippled CPU (1.5GHz), has no 3D support (among other limitations and missing features). Always buy a S905x or S912 CPU device.

Tested on the following hardware specs: ($40-50 & $80-$120 AUD from Ebay/GearBest)

- CPU: Amlogic S905x Cortex-A53 Quad-Core 1.5GHz -&- AML S912 Cortex-A53 Octo-Core 2.0GHz.
- GPU: ARM Mail-450MP5 Penta-Core 750MHz -&- Mali-T820MP3 Tri-Core 750MHz. [I question these Chinese Specs!]
- RAM: 1GB, 2GB, 3GB or 4GB (DDR3\DDR4); FLASH 'ROM': 16GB, 32GB+ (EMMC).
- OS: Android 6.0.x Marshmallow.​

Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -​

FAQ, HINTS & TIPS ARTICLE INDEX

» How to Backup your Device & Data (w/o Modifying Stock Recovery/Boot).
» Magisk SU & Magisk Manager Root (w/o Modifying Stock Recovery).
» Replacing BusyBox & Optimal Systemless BusyBox Installation.
» Handy Resources & Useful Download Tools.
» Anti-Detection Methods: Masking Magisk SU Root & Renaming Magisk Manager.
» Magisk Hide Settings Lost & Not Saving (Re-Opening App / Reboot) - Troubleshooting Magisk Hide.
» Corrupt or Problematic Root? Re-Rooting!
» Backup Important System, Boot, Recovery & Data Partitions.
» How to Access TWRP Recovery W/O Modifying Recovery/Boot.
» Find & Locate your Stock Boot Image Backup Created by Magisk.
» BusyBox App or BusyBox Applets Installed on your Device.
» Masking BusyBox Modules and Applets.
» Google Play Store & Play Services - Old Versions, APK Backups & Archives.
» Google Play Store & Play Services - Errors, Issues, Fixes & Troubleshooting.​

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -​

HOW TO BACKUP YOUR DEVICE & DATA (W/O MODIFYING STOCK RECOVERY/BOOT)
I recommend backing up the partitions before making any changes to your default box. In fact, whenever you buy *anything*, always take a full backup before doing anything - yes, before connecting it to the Internet! Regardless if there is no important data there, ALWAYS make a backup!

Requirements:

• Download Optimised AML S905 & S912 Media Player Bootable TWRP Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached at bottom of post)
• Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
• USB Storage (memory stick, external USB drive) - optional;
• USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy! Get a Logitech K/B & Mouse w/ unifying dongle); and
• Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip);

Backup Procedure w/o Modifying Stock Recovery/Boot:

• Stage 1. Access recovery w/o modifying stock device status.
  • 1.1. Extract the Media Player compatible TWRP 'recovery.img' image from ZIP file (DO NOT RENAME FILE!).
  • 1.2a. Insert a 2GB+ Micro SD card (Class [4] or higher) to Windows computer.
  • 1.2b. Format Micro SD card on PC: untick "Quick Format" and select 'FAT32' (not 'FAT', not 'NTFS', not 'exFAT').
  • 1.3a. Copy only the 'recovery.img' to the root of the Micro SD card (excluding any other files and folders).
  • 1.3b. Safely eject the Micro SD card from computer and insert upside-down in the TV box.
  • 1.4. Unplug the "AV" port cable (3.5mm audio socket) and A/C power from TV box. NOTE: May reset system date/time! TWRP Backups then have wrong time stamps!
  • 1.5a. Carefully insert the long plastic ink ball-point pen nib/tip into the "AV" port and you will feel a button depress.
  • 1.5b. Connect the A/C power cable to the TV box, while holding the button inside the "AV" port.
  • 1.5c. Wait while device initialises and displays TWRP screen (Black & Blue TWRP interface).
  • 1.5d. Release the pen ink nib NOW and reconnect the "AV" audio cable, if in use.
    .
• Stage 2. Perform a device partition backup.
  • 2.1. From the on-screen TWRP menu, select "Backup" menu option.
  • 2.2a. Select three most important partitions: "/boot", "/system", "/data" (untick "/cache").
  • 2.2b. Check the required backup space "Total Size of All Data 3100MB" against the available space on selected backup volume (enable compression if req'd).
  • 2.3. Click the GREY button at the bottom-left to specify backup location. Choose your USB stick (or Micro SD if sufficient free space).
  • 2.4. Backup will now run. Do not walk away - watch the process for any errors. It will only take 3-8 mins (depending on amount of data and apps on the device). N.B. Check system temperature at top-left corner before executing backup. If you are concerned about heat you should monitor this (mine was really bad - floating around 69-72'c during backup).
    
    Once complete it will be display in Blue text: "Backup Completed in 485 Seconds". Remove the Micro SD and reboot!

** Don't forget to install a better or light-weight Launcher! Try "Nova" or even "Microsoft" Launcher - both feature rich and easy-to-use!
** Don't forget to copy/move TWRP backups from SD card to PC, to restore any partitions in future!
** Don't forget to install "BK Disabler" to disable/remove all useless system packages plus disable their services to save memory and resources!

- - - - - - - - - - - - - - - - - - - - -​

MAGISK SU & MAGISK MANAGER ROOT (W/O MODIFYING STOCK RECOVERY)
Connect your WiFi so that any auxillary files and updates can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free space. Allow for 1-3 hours to perform these steps. Do not rush!

1. Identify your device and save the essential details - see the tabs with most important information. Search for words like Build ID, Device, Model, Fingerprint, Baseband, Modem, Bootloader, CSC, etc. as these will give you most of the information you are seeking.
   Download two of these "System Info" apps (unfortunately no one app covers all the information in one!) to perform a hardware and software audit of your device - personally, I use all three:
   • AIDA64 ("System", "CPU" & "Android" tabs.),
   • DevCheck ("Hardware" & "System" tabs. Has nice 'Charger Connect' counter and UI),
   • Device Info HW ("General" & "System" tabs.), and
   • SamMobile Device Info (General, Firmware & Android tabs)
2. Search DuckDuckGo/Google for a backup of your exact Bootloader and Build ID. This signifies a version that matches the OS and hardware variant. For example the 1st box I tested was a 1GB/8GB X96 Amlogic P212 ($40). All your finite and detailed specs are available within the System Info apps mentioned above (#1 A, B, C). Write down, export and screen shot your device's specs and details somewhere for quick reference.
   For example, System Info output for my device:
   • Build: '20170622.19:55' in one app, but 'MHC19J' in another app (often letters & numbers and not a date w/ other hardware);
   • Fingerprint: 'Amlogic/P212/P212 6.0.1/MHC19J/20170622:userdebug/test-keys' (inc. make, model, device, OS, etc.);
3. Due to many of these Android media centres coming with a Faulty or Corrupt bundled Root, unknown SuperUser and an unlocked Bootloader - I highly recommend you either:
   • Flash the Magisk Combined Installer .ZIP through recovery;
   • backup the boot partition, extract (or download) the boot.img image, patch, then flash modified boot image .IMG through recovery; or
   • Install Magisk Mananger then click "Install" and select "Direct Method".
   
   I had nothing but problems with Magisk Manager trying to take ownership and replace the corrupt SuperUser SU and SUD files (bundled with the device on delivery). For this reason, due to the boot and system partitions already being modified, I chose option "#3 A." - to flash the Magisk Flashable ZIP through recovery. However if you do have working root and an operational SuperUser, you may choose the fastest option of "#3 C.". Or if you can obtain a stock Boot image, then use option "#3 B.". The choice is yours and it really depends how messed up your device is!
   
   Note: As many of these devices either come already rooted or are unstable, perform a full backup before installing or doing anything, so that if you make a mistake you can always revert back to that original state! e.g. An on-device backup, or backup via a PC with Google's SDK Tools (ADB) . Follow the steps above under "BACKUP YOUR DEVICE & DATA" from #1.1 to #1.5 for on-device backup instructions.

Scenario A) Stock ROM W/ Root Access

• Download Magisk Flashable ZIP, Magisk Manager APK, and Magisk Uninstall ZIP onto your external storage.
• Install Magisk Manager and launch the app.
• Within the Manager UI, click "Install" button on screen and choose "Direct Install" method. Magisk will now attempt to install SuperUser and confirm root status.
• No Errors? You are finished. Done.
• Errors? Failed? If this fails, as it did for me, you need to follow the instructions above under "BACKUP YOUR DEVICE & DATA" from #1.1 to #1.5. to reboot into Recovery and perform a backup (w/o modifying Stock recovery/boot etc).
• Follow steps to download the S905/S912 Backup & Recovery ZIP file (attached to bottom of topic) and prepare the Micro SD or SD Card or USB drive.
• From the Recovery interface, where you performed your backup, return to the main menu and choose Install (Flash).
• Now browse and select the previously downloaded Magisk ZIP file. Slide the right-hand-side button to proceed.
  NOTE: If prompted whether you want to keep System partition "Ready Only", select "Keep Read Only" button to allow future OTA device updates.

. . . Trying to find MORE time to re-type & clean up notes . . .

Scenario B) Stock ROM W/O Root Access (or if Scenario A. fails)

• Download Magisk Flashable ZIP, Magisk Manager APK, and Magisk Uninstall.
• If your bootloader is locked (To-Do: reference process to check), you will need to first unlock it. Download the original boot image or backup your device, should you
• need to undo your changes. Follow steps above to backup the device (selecting Boot or all partitions) and then extract the boot image once complete -or- download the original boot image and keep it handy.
• Install Magisk Manager and launch the app (green mask icon with bits of white and blue).
• Select Install from middle of screen, then from the pop-up click Install on the right-hand-side.
• Choose "Patch Boot Image File" and you will be asked to navigate and browse to where you downloaded the original boot image (or performed the backup). Be very careful as you will not be prompted to confirm your selection!!!
• Wait for the process to complete. Now reboot into the recovery on your Micro SD card.
• From here you can choose Flash to flash the previously patched boot image from within the /MagiskManager/ directory.
• Once complete, reboot the device and launch Magisk Manager. At the top of the screen it will verify the Magisk SU is install and up-to-date.
• If you have any doubts, you may click "Install" again and verify the process completes successfully.

. . . Trying to find MORE time to re-type & clean up notes . . .

** Don't forget to install a better or light-weight Launcher! Try "Nova" or even "Microsoft" Launcher - both feature rich and easy-to-use!
** Don't forget to copy/move TWRP backups from SD card to PC, to restore any partitions in future!
** Don't forget to install "BK Disabler" to disable/remove all useless system packages plus disable their services to save memory and resources!

- - - - - - - - - - - - - - - - - - - - -​

REPLACING BUSYBOX & OPTIMAL SYSTEMLESS BUSYBOX INSTALLATION
What exactly is this whole Busy Box thing? Well ... BusyBox is this unified bundle of over 300 common Unix commands (as applets) forming an 'Android Swiss Army Knife' (as it is commonly referred as) that replaces and adds standard Linux functions on your device, so that you can have greater control over your device - just like a PC with Linux OS. This 'toolkit' was specifically built to accommodate embedded OS devices with limited resources to work with the Linux Kernel. It is FREE software under the GNU, however various developers create easy-to-use BusyBox installers which are available both free or paid online.

Due to many of these devices coming pre-installed with BusyBox and old/outdated bundled Applets, there can be confusion with what does or does not work. Therefore it is very important to determine what state your device is in (again writing down what works or does not) and take a backup before making changes. In recent years, developers have added code to their programs to detect BusyBox and 3rd party apps, just like other root methods. Therefore it is *highly* recommended you migrate away from the standard/bundled BusyBox and move to the Magisk 'Systemless' version of BusyBox that makes no changes to your /System partition and does not mount it 'RW'.
Please direct your thanks to @osm0sis - a truly valuable community member.

Requirements:

• Download Stericson's BusyBox installer 'Free/Pro' (or reputable alternative) [https://play.google.com/store/apps/details?id=stericson.busybox].
• Have already flashed 'Magisk Flashable ZIP' to gain Root; or installed 'Magisk Manager' v12+ (replaces BusyBox App & SuperUser Manager) and flashed 'Magisk' SU v5.6+).
• Install two or more of these excellent system info apps from the Android "Play Store" to audit and display system info (OMG! I am over calling it Google "Play"! It's the Android Market!):
  • AIDA64 (System, CPU & Android tabs);
  • DevCheck (Hardware & System tabs);
  • Device Info HW (General & System tabs); and
  • SamMobile Device Info (General, Firmware & Android tabs).

BusyBox Procedure:

1. To begin, download and install Stericson's BusyBox installer (link above).
2. Launch the BusyBox app, click "Grant" to the root request, and wait for 2-3 minutes while the app initialises for the first time.
3. At the top of the screen it will show your current BusyBox version and details. At the bottom-left of the screen, click "Install" to update. It will automatically update and perform maintenance on SymLinks, fixing any issues for you.
4. Exit BusyBox and re-open. Now click "Uninstall" at the bottom-right and click "Uninstall" again saying yes you understand.
5. Now your system has no BusyBox! Some background services may complain but this will only be for a few minutes.
6. Open Magisk Manager and swipe open the left-hand side-menu and click Modules.
7. You will now see your currently installed (active/disabled) modules plus the latest versions of other Magisk-compatible modules below.
8. Click the Search icon at the top-right and search for 'busybox'. You should find "Busybox for Android NDK" (ignore the "NDK" part).
9. This is the Magisk recommended Systemless BusyBox module managed by XDA member 'Osmosis' @osm0sis. Click the Row for more information or click the Download icon then "Install" on the right-hand-side to begin. Once complete, without any errors, click "Reboot". If you experience any errors just reboot and try again or click save and examine the logs.
10. Now open one of the three 'System Info' apps (listed above) -OR- re-open the BusyBox installer app again. This will allow you to determine your BusyBox name and version! If everything was successful, you should see something like "BusyBox v1.23.4-OsMoSiS" with path "/system/xbin/".
    All Done!
    
    When an app requests SU and BusyBox access, Magisk SuperUser will prompt to grant or deny this request, then if accepted, automatically serves the Systemless BusyBox environment to the requesting app. Amazing!
    If you have any issues, please use the Magisk Manager support topic and attach all related logs.

- - - - - - - - - - - - - - - - - - - - -​

HANDY RESOURCES & USEFUL DOWNLOAD TOOLS
Below are some handy tools you should download and have ready on the external Micro SD Card and your PC's HDD. This list is far from complete and will be updated by member suggestions! The list includes a short description plus links to further details, support, downloads and dates they were last updated. If you know an Android or Windows app that is *essential* for use, please feel to post it here, and I will add it to the list. Thanks!!

Where is the AMLogic Website? Site shows compatible OS versions, hardware specifications w/ chipset, memory RAM, CPU & frequencies, etc. Click around and you will find all sorts of info, e.g. Email address mbox-android[@]amlogic.com
» http://openlinux.amlogic.com/Android/Mbox (Strange 'S905x' is planned for OS v8 but the 'S912' is not planned beyond OS v7??)

AMLogic S912 & S905 Toolkit [Bundled Fastboot, Flash, Burn, Port, Backup] (Tool & Drivers) - IMPORTANT! Combined toolkit to flash, backup, convert recovery images and restore ALL AMLogic AML S912 & S905 TV Boxes remotely from your PC. Read more...

AMLogic Network Flash Tool [Bundled ADB & FastBoot] (Tool & Drivers) - IMPORTANT! Ability to flash, backup, convert recovery and restore AMLogic Media Player TV Boxes remotely over the network (LAN Cable or Wireless/Wi-Fi). Always backup prior to upgrading/downgrading! Capable of backing up, restoring and converting any other device's TWRP Recovery. Read more...
» https://mega.nz/#!AII2TB6R!Tk8SS9RUZbFHF9Nwl2H27fD_z54o6Ph2nSlK-JdlZDc [2018.02.24 v1]

AMLogic USB Burning Tool v2.1.6 [Device Re-Imaging] (Tools) - IMPORTANT! This tool allows you to Flash (or "Burn") an update to AMLogic Media Player / TV Boxes using a USB Type-A to Type-A cable. Ability to "Burn" (Flash) and upgrade your device. Please always backup prior to updating!
*Warning!* Wipes ALL device data!!! Use *.img files only, not *.zip files!
» https://mega.nz/#!8ZJTETzL!cdPql9YqK0GGT-xhCfplCVI7b-d0xR-nH5tDIhdeZEg [2018.03.07 v2.1.6]
» https://mega.nz/#!RcglgLrK!0rLQQP_kWCQsLbyAoBBvxFpPsy47A2KP0ycLX1FzgPI [2017.08.14 v2.1.2]

TeamWin TWRP S905 S912 Recovery (Bootable) - IMPORTANT! [Micro SD Boot 100% Guaranteed!] Use to access TWRP recovery without modifying your recovery partition. Frequently updated alternate recovery project. The most suitable recovery will depend on your device! If you cannot boot into TWRP recovery, you will need to learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Check the XDA Forums relevant for your device and custom Recovery solutions listed. Flashing will modify your Stock Recovery - this is not recommended should you wish to perform OTA firmware updates and use 3rd party apps that circumvent modified/rooted device detection (Spotify, Netflix, Stan, etc.). Be sure to take a backup of ALL IMPORTANT partitions, plus separate backups of EVERY partition too.
» https://mega.nz/#!4Mx2wSbQ!G-Vws-Xv1KfKLMg2MytoroMik_5MBVc4IZ4c7SfCpZE [AmLogic-specific S905 & S912, TWRP v3.0.2]

Odin3 for Windows - Flash various types of firmware for your device - e.g. modem, boot, system, etc. Odin can push OTA manufacturer and third-party signed/unsigned software updates / patches to devices via USB. e.g. Flash Radio to resolve various issues, or flash and restore the original to resolve custom ROM issues. Please visit the Odin3 thread by ChainFire for support. Read more...
» Odin3 v3.09.0 [2013.06.21] | Odin3 v3.09.5 [2014.03.12] | Odin3 v3.11.1 [2016.05.13] | [url=https://mega.nz/#!NJxxCbAS!EE1zGsa200NiR5RaPlAV7e4ac8YCslgELZAfxepNRJo]Odin3 v3.12.7 [2017.05.06] | Odin3 v3.12.10 [2017.11.01]

Fix Permissions v2018.04.15 by Osm0sis [Repair Micro SD & TF] Flashable - Repair and fix both file and directory errors/corruptions with ownership and permissions. Flash the signed package to execute. [URL=https://forum.xda-developers.com/showthread.php?t=2239421]Read more...
» https://mega.nz/#!wRYiSZ6K!8DVVq5v9KFsu0kkciqtla156l7nlYFCVy0QssuE8Qvw [2018.04.15]

ADB & FastBoot Drivers [Windows Mac Linux] (Drivers) - Essential if pushing, pulling and backing up device content & partitions. Familiarise yourself and bookmark the command examples on ADB + Fastboot. You will need to verify your Device's Model/Fingerprint/Bootloader/Modem/CSC BEFORE flashing. Enter commands via command prompt - for example, to push new recovery image: "fastboot boot xyz-recovery.img". Read more...
» OS Selection: Windows | Linux | MacOS
» https://mega.nz/#!EB4C3bwR!d7jO4ngpCxSsDc21ZA5l2dhDNbXnXTKFVspA8uCmUs0 [2017.12.13 Win v27.0.1]

Root SU Uninstaller by Magisk - Un-Root & Clean-up (Flashable) - IMPORTANT! UnRoot / DeRoot and reverse system modifications from Magisk SU, SuperSU and other 3rd party rooting tools. Excellent tool for removing corrupt Chinese root to install Magisk SuperUser and Magisk Manager or SuperSU. Read more...
» http://bit.do/magisk-uninstaller-flashable-zip-20180429 [Latest! Dev Link]
» https://mega.nz/#!xZInDJSQ!l_Kl-NcHvwAUEu9kC8UbH9sm14EcAzMrHFutREl4BVs [v20180429]
» https://mega.nz/#!ABJU1Jza!6xYhQn_RGJGCpQRTzX4CvDqli351p-uc28KXCX5SSkA [v20180222]
» https://mega.nz/#!4Bwn0azK!fc9roBz32eTkbJ1POy5OcsHOGTKkFShQz515PlQ4KXY [v20180113]

Osm0sis UnSU Un-Root & Clean-up (Flashable) - UnRoot and restore modified system files correctly from half a dozen 3rd party root methods. See also the Magisk Uninstaller above for more up-to-date solution should this not work. Read more...
» https://mega.nz/#!gUZhXbTD!bUGGnnDuqCRPhYoYsTOZJBWlP9B3MbroCc3vUxOgGiE [2018.02.06]

CleanupSU (Flashable) - Cleans up all leftover SuperUser files that might be laying around. Perform every time you need to re-root. See also the Magisk Uninstaller above for more up-to-date cleanup solution.
» https://mega.nz/#!MNpUjaTZ!VYBOQRfelzrFVSWdxGZdMKgY6pTa-kgJJPdfygmjblw [2016.11.03]

SUMount (Flashable) - For use with either 'Systemless' root options: @topjohnwu's Magisk SU -or- Chainfire's SuperSU. Toggles mounting of 'magisk.img' & 'magisk_merge.img' or 'su.img' to access their file systems for manipulation (ADB Shell, Aroma File Manager, TWRP Terminal or TWRP File Manager, etc.). Read more...
» https://mega.nz/#!lYZmhIga!TSE-l519X2-AUNbdPnfpzGI244TJRYGpWM9IG4HoPhE [2008.02.28]

TeamWin TWRP Recovery (Flashable & Bootable?) - NOT TESTED!! UNTESTED!!! You can always try booting (not flashing) from this recovery image if the AML S905/S912 Recovery above does not work. I recommend you learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Be sure to take a backup of ALL Important partitions. Read more...

Philz Touch Recovery [Database of Devices] (Flashable & Bootable?) - NOT TESTED!! UNTESTED!!! You can always try booting (not flashing) from this recovery image if the AML S905/S912 Recovery above does not work. I recommend you learn your Device's Model/Fingerprint/Bootloader/Modem/CSC. Be sure to take a backup of ALL Important partitions. Read more...
» https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw

Want to backup your device's Recovery? Want to restore another device's Recovery? Want to use it for another Media Box? Try the nifty little tool called: AMLogic Network Flash Tool! (see above) Note: I have not tested with RockChip media boxes (RK3328 RK3368 RK3399).

- - - - - - - - - - - - - - - - - - - - -​

More hints and tips to come as I find time to document them:

» SafetyNet issues...
» Google Play Store & Play Services - Errors, Issues, Fixes & Troubleshooting.​

Found this useful? Click the [:good: Thanks!] button below!
Cheers!

.​

 

[flipmode_11]

General Support - TV & Media Boxes, Magisk Root, Backup, Restore, Play Services, etc.

Continued.....

- - - - - - - - - - - - - - - - - - - - -​

ANTI-DETECTION METHODS: MASKING MAGISK SU ROOT & RENAMING MAGISK MANAGER
Two features 'Magisk SU Root Masking' labeled as "Magisk Hide" -and- 'Magisk Manager Rename' labeled as "Hide Magisk Manager". This can be confusing and the sequence of these options are in reverse order, than what I would have thought. Enabling 'Magisk Hide' detection system is *usually* sufficient for most scenarios with problematic Catch-up TV apps, Banking apps, Google apps, Music services (Spotify, etc), Anti-tamper Game hacks, and so on. A better word to describe what Magisk Hide does would be 'masking' or 'cloaking' its presence from other apps.
For further assistance, access the Magisk Hide FAQ: https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

» Activate Magisk SU ROOT Masking (i.e. Magisk Hide)
What does it do? It masks detection of the presence of SU from selected apps. This feature will activate a hidden option in the left menu. When opened it allows you to select various applications to BLOCK detection from these apps from recognising system has been compromised and has SuperUser + ROOT.

Magisk SU ROOT Masking Steps:

1. Always Backup! Take a full backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).
2. Launch Magisk Manager (round green mask icon).
3. Slide open the left menu by swiping left-to-right. Click Settings.
4. Scroll down to yellow 'MAGISK' section.
5. Enable "Magisk Hide".
6. Close Magisk Manager. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
7. Select 3rd option "Magisk Hide" and begin selecting which apps to "Cloak" or "Mask" Root to prevent detection.

NOTE: Do you find after closing Magisk Manager or rebooting, that "Magisk Hide" disappears from the left menu and is disabled in settings? See Magisk Hide Troubleshooting steps below to resolve!!

» Activate Magisk Manager Package Rename (i.e. Hide Magisk Manager)
What does it do? Should you have issues where an app is circumventing the Magisk Hide feature (above), you can use the Magisk Manager Package Rename feature (ironically named "Hide Magisk" just to confuse you!). The feature creates a cloned APK file of Magisk Manager but with a random package name ('com.XxXxXxXxXx' instead of 'com.topjohnwu.magisk') and installs it, then automatically removes the original Magisk Manager app to avoid detection.

If you proceed with Hide Magisk Manager (Rename) there are a number of inherent limitations. Research on the forums first to fully understand the consequences of this feature. For example, Magisk Manager check for updates fail, automatic update notification is unavailable, re-install Magisk Manager unavailable, plus numerous other restrictions.

Magisk Rename Steps:

1. Always Backup! Take a full backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).
2. Launch Magisk Manager (round green mask icon).
3. Slide open the left menu by swiping left-to-right. Click Settings.
4. Under the yellow 'GENERAL' section.
5. Click "Hide Magisk". *NOTE* There is NO CONFIRMATION prompt!
6. Wait 1-2 mins and Magisk Manager will close automatically.
7. Open Magisk Manager (same round green mask icon). You can now check the new package name.
8. Under settings where you selected "Hide Magisk" is now a "Restore Magisk Manager" option to restore the original package (e.g. for Magisk updates or modules).

What does the Uninstall button do?
When removing Magisk & Magisk Manager there are three options:

• Remove the "Manager" app only = "Uninstall App";
• Restore stock/original Boot image for OTA Updates = "Restore Images";
• Clean-up & removes Magisk SuperUser, Modules & Manager = "Complete Uninstall".

Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues

- - - - - - - - - - - - - - - - - - - - -​

MAGISK HIDE SETTINGS LOST - TROUBLESHOOTING MAGISK HIDE
Magisk Hide (Masking Magisk SuperUser) - 2 Solutions w/ Magisk Hide being disabled after reboot or closing and re-opening Magisk Manager.
If you are using Magisk Manager and Magisk Root and are experiencing difficulty with Magisk Hide (Masking Magisk's SU) not showing in the Manager's side-menu or remembering its status in settings, it occurs when a file is not automatically deleted and removed.

PROBLEM:
Open Magisk Manager, Settings >> Enable Magisk Hide, close Manager, re-open and Magisk Hide is disabled and not visible (hidden) in the left side-menu. i.e. Exit, Close, Stop, Re-Open & Reboot Reset's Magisk Hide's State to Disabled.

SOLUTION 1.

1. Force stopped Magisk Manager.
2. Backup then Delete file /data/property/persist.magisk.hide (0600).
3. Launch Magisk Manager.
4. Go to Settings >> Enable Magisk Hide.
5. Go back to Manager home screen. Swipe to reveal side-menu and check Magisk Hide menu is visible.
6. Close Magisk Manager or Force stop.
7. Reopen and Swipe side-menu and confirm Magisk Hide is still visible!

I hope this helps others also experiencing issues with Hiding Super User SU. Thanks Shak!

SOLUTION 2.
Another fix @dunderball posted Dec 2017 was in regards to an error "fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory"
The issue is due to Magisk Manager being unable to save the list of ticked Apps to hide from SU to /magisk/.core/magiskhide/hidelist.

1. Check the existence of the "/magisk/.core/magiskhide/hidelist" path.
2. Create the "/hidelist" directory.
3. CHMOD "/magisk/.core/magiskhide/hidelist" to 0644.

Thanks go to @dunderball. :highfive:

SOLUTION 3.
If you are using an old device or perhaps an old ROM with custom Kernel, you may find Magisk does not work. Magisk Manager & Magisk SuperUser requires a Kernel with version v3.8.x or newer.
Check your device forums on XDA for assistance.

SOLUTION 4.
Magisk Hide will not function if you have disabled your 'logd' service, or your have set your log threshold to 0 bytes. Magisk requires to examine the logs in order to hide the selected apps from root status. Enable and start the 'logd' service and try again! Solution 5 also discusses the importance of the Logging service.

SOLUTION 5.
Magisk anomalies, problems with diagnostic logs and non-functioning Magisk Hide.
ATTENTION: If you are experiencing diagnostic and logging issues (e.g. blank or no debug logs created in "/data/adb/Magisk/") or you are experiencing some anomalies after enabling Magisk Hide, please be aware v15.4+ of Magisk Manager checks and verifies if the "LOGD" diagnostic logging service is running. Devices NOT using the 'logd' service for logging will therefore NOT be able to successfully have "Magisk Hide" enabled and functioning.
If you really wish to use this feature, then I recommend:

1. Performing a backup of your data, important partitions and system state;
2. Flash Magisk Uninstall ZIP (link available above & on Magisk topic); and
3. Flash Magisk v15.31 ZIP to allow enabling the Magisk Hide feature.

Disable the check for updates option within Magisk Manager settings to prevent accidental upgrade until the issue is fixed by @topjohnwu.

Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Requirements Magisk uses logging ('logd' service) to hide/mask root. Magisk Hide needs Kernel v3.8+ or newer (e.g. My Galaxy S5 uses v3.10.40 & X96 TV box has v3.14.29).
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues

- - - - - - - - - - - - - - - - - - - - -​

CORRUPT OR PROBLEMATIC ROOT? RE-ROOTING!
Restore to factory defaults does *not* work on these devices. It will NOT restore root or any 'destructive' actions made on the OS and to any apps. The great thing about MagiskManager is that it can co-exist with SuperSU, however it will not truly be hidden and invisible. If you do mix-and-match SuperUser's then make sure you use their method for hiding, e.g. search for Hide SuperSU by ChainFire.

Depending on how 'destructive' your previous actions were on the device, you should have a 'close to original' stock System partition and a copy/backup of the *Original* device's Boot Image. There are two things you can try when either root, SU, permissions or something else is corrupt:

• flashing the Magisk Uninstall ZIP to un-root your device to perform a clean-up and proper removal; or
• try restoring (flashing) the stock/original untouched device Boot Image via TWRP.

Once you confirm things are stable and working, you can then either:

• Launch MagiskManager and click Install and choose 3rd option, Direct Method;
• flash Magisk via TWRP again; or
• Launch MagiskManager, click Install and choose 2nd option, browse for your stock Boot image and then flash the updated image via TWRP.

Requirements:
With either the Stock Standard or a Custom Recovery:

• Download the S905 & S912 Media Player Bootable TWRP Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached to above post)
• Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
• USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy!);
• Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip); and
• Attempt to fix and repair all file, directory and application permissions by booting into TWRP and selecting "Fix Permissions".

Options and Procedure:

# Magisk

• Flash Magisk ZIP installation script.
  1. Boot into TWRP recovery via 'recovery.img' on Micro SD card.
  2. Take a full device backup.
  3. Flash Magisk latest stable or beta ZIP.
  4. Magisk Manager will be re-installed automatically.
  Alternatively,
• Open Magisk Manager and click "Install" at the bottom of the screen.

# SuperSU

• Flash SuperSU ZIP installation script.
  1. Boot into TWRP recovery via 'recovery.img' on Micro SD card.
  2. Take a full device backup.
  3. Flash SuperSU latest stable or beta ZIP.

# ChainFire

• Flash ChainFire ZIP installation script.
  1. Boot into TWRP recovery via 'recovery.img' on Micro SD card.
  2. Take a full device backup.
  3. Flash CF Root ZIP.

NOTE: Cannot flash via ODIN w/ standard Micro USB cable due to Media TV Boxes not having USB peripheral 'host' ports. You will need to buy a USB type-A to type-A cable for this to work - compatibility will be device dependant ($5 investment on Ebay). If you are more comfortable with Odin, you can flash either a 3rd Party Recovery (temporarily) or Stock Recovery in the "AP" slot (*.tar or *.tar.md5) - always backup first! I have not tested any WiFi ADB tools or flashing with "FlashFire", "Rashr" or "Flashify" (Odin update) - should essentially work once you have root access...

The process is essentially the same as the process to root. However you simply select a different SU ZIP to flash. There is ample documentation available for using TWRP. Please DuckDuckGo/Google your specific root method and TWRP if you are unsure.
If you do receive an error and the process does not complete, copy the log to your card and try again. Fails again? Examine the logs and look for any errors.

WHAT IF? If this all fails, try using ChainFire's "UnSU ZIP script" -or- Magisk's "Uninstaller ZIP script" and flash either via TWRP to clean-up the system. Alternatively, you could use TWRP to flash the stock boot/recovery/system partitions -OR- use TWRP to Factory Reset (after backing up all data!!), and then begin the Magisk Root steps from scratch!

Magisk Topics » Magisk Stable | Magisk Beta | Support Q&A
Downloads » Magisk Manager | Magisk Flashable | Magisk Clean-up v20180429 | v20180328
Troubleshooting Documentation, Wiki & FAQ | Magisk Hide Help | Diagnosing Magisk Issues

- - - - - - - - - - - - - - - - - - - - -​

BACKUP IMPORTANT SYSTEM DATA & PARTITIONS
Prior to installing lots of apps or making any system changes, it is *always* advised to take regular full backups, plus backup of your Boot and Recovery. If you cannot find the original ROM images easily online (e.g. obscure media player device, non-existent version numbers) then perform a backup within TWRP app or boot into recovery. It is *highly* recommended you have Stock backups prior to performing any actions that may affect the boot partition (inadvertently).

Backup Boot & Recovery Partitions:

• If you DO NOT have Root, follow the Backup instructions above under "HOW TO ACCESS TWRP RECOVERY W/O MODIFYING RECOVERY/BOOT" (below) to access the backup recovery environment.
• If you DO have Root access - download, install and open TWRP (has a stupid name "Official TWRP App"), click 2nd option "Backup Existing Recovery".
• Perform two backups: first enter a meaningful "Device Recovery Backup" file name and click "Backup Recovery"; then repeat for the "Device Boot Backup" and update the backup file name.
• The backup should complete within a few seconds, depending on its size and destination.

To restore, follow the same steps via TWRP app, or alternatively boot to the 'recovery.img' (attached & discussed above) and choose TWRP Flash restore, browse and select the backup, then select which partitions you wish to recover.

- - - - - - - - - - - - - - - - - - - - -​

HOW TO ACCESS TWRP RECOVERY W/O MODIFYING RECOVERY/BOOT
Requirements:

• Download the AMLogic S905/S912 TWRP Bootable Recovery image (13.3MB): https://forum.xda-developers.com/attachment.php?attachmentid=4426811&d=1519210044 (attached to above post)
• Reasonable quality Micro SD Card (Class '4' or higher) w/ 2GB+ size formatted in FAT32 - run a disk check if any doubts or issues w/ card;
• USB Input (cordless mouse & keyboard, as the "air mouse" remote sends you crazy! Get a Logitech K/B & Mouse w/ unifying dongle); and
• Dismantle a ball-point pen and remove the long plastic ink nib section (or a kebab stick, tooth pick, paper clip);

TWRP Procedure:

• 1. Extract the Media Player compatible TWRP 'recovery.img' image from ZIP file (DO NOT RENAME FILE!).
• 2a. Insert Micro SD card (Class [4] or higher) to Windows computer.
• 2b. Format Micro SD card on PC: untick "Quick Format" and select 'FAT32' (not 'FAT', not 'NTFS', not 'exFAT').
• 3a. Copy only the 'recovery.img' to the root of the Micro SD card (excluding any other files and folders, unless flashing the firmware).
• 3b. Safely eject the Micro SD card from computer and insert into TV box.
• 4. Unplug the "AV" port cable (3.5mm audio socket) and A/C power from TV box. NOTE: May reset system date/time! TWRP Backups then have wrong time stamps!
• 5a. Carefully insert the long plastic ink ball-point pen nib/tip into the "AV" port and you will feel a button depress - don't let go!
• 5b. Connect the A/C power cable to the TV box, while holding the button inside the "AV" port.
• 5c. Wait while device initialises and displays TWRP screen (Black & Blue interface).
• 5d. Release the pen ink nib NOW and reconnect the "AV" audio cable, if in use.
  Done. Rock and roll!
  Now perform any TWRP functions - backup, restore, fix permissions, flash, etc.

NOTE: If you wish to install vendor OTA updates, I recommended you continue using TWRP (or other solution) via Micro SD Recovery and the TWRP Android app. Otherwise, if you flash TWRP (or other recovery) you will need to take extra steps to re-flash your Bootloader prior to any updates, then flash again, and again afterwards.

- - - - - - - - - - - - - - - - - - - - -​

FIND & LOCATE YOUR STOCK BOOT IMAGE BACKUP CREATED BY MAGISK
Whether you initially used the Magisk Manager app -or- TWRP Recovery \ ADB FastBoot \ Odin3 to flash the Magisk patched boot image, a backup copy of the existing stock boot image is stored in "./data/" as "stock_boot.img".

However, if you flash an already Magisk patched "boot.img" through ADB FastBoot (Download Mode), then neither a "stock_boot.img" backup will be created or existing backup overwritten. Magisk detects the active boot image as already patched, therefore you must manually create a backup if you wish to retain the existing boot image.

Note: When patching a stock boot.img and flashing via Magisk Manager, the backup of the stock boot image is temporarily held until the next reboot in: "./data/user/0/com.topjohnwu.magisk/install/stock_boot.img".
If you are struggling to locate the file, access an on-device terminal emulator, type "SU" and enter: "find -name 'stock_boot*'".

- - - - - - - - - - - - - - - - - - - - -​

BUSYBOX APP OR BUSYBOX APPLETS INSTALLED ON YOUR DEVICE?

1. Download, install and open your Busybox app. We will only use the "Uninstall" component of this app to clean-up any Busybox applets and remnants left behind.
2. If you have any corruptions in BusyBox preventing removal, first click "Install" to update, and then click "Uninstall".
3. Once complete, you may uninstall your Busybox app as is no longer required!

MASKING BUSYBOX MODULES AND APPLETS

1. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
2. Click the "Downloads" menu item.
3. Scroll down the list and looks for something like "Busybox NDK" or similar.
4. Read the module description. Click Install and follow the steps.
5. Slide open the left menu, select the "Modules" menu item to see the list of (active/inactive) installed modules (you may tick/untick a module to temporarily disable it, or click the trash icon to remove and uninstall it completely).
   You should now see the 'BusyBox NDK' systemless module installed.

- - - - - - - - - - - - - - - - - - - - -​

GOOGLE PLAY STORE & PLAY SERVICES - OLD VERSIONS, APK BACKUPS & ARCHIVES
Normally most Android devices have a "Vending.apk" as their Google Play Market package. However some devices use a different package name for Play Market and Play Services packages e.g. "Phonesky.apk" or "Velvet.apk".
In order to upgrade Play will depend on your system. Installing an updated Phonesky.apk will work. e.g. I updated my unstable Google play from v6.0.1 and Play Services with the following packages:
- Play Store v6.0.5 as 'com.android.vending' in "./system/priv-app/Phonesky/Phonesky.apk"
- Play Services v8.4.89 as 'com.google.android.gms' in "./system/priv-app/PreBuiltGMSCore/PreBuiltGMSCore.apk"

Updating Google Play and Play Services options:

#1. use any root explorer (Solid Explorer, FX Explorer, ES Explorer, Root Explorer) to rename (backup) and replace the "Phonesky.apk" and "PreBuiltGMSCore.apk" packages;
#2. flash the updated Play Market or Play Services ZIP package via Magisk Manager;
#3. flash the updated Play Market or Play Services APK package via Recovery; or
#4. flash via ADB FastBoot (please search the XDA forums for examples [ADB, FastBoot, Push/Pull]).​

IMPORTANT! Always backup your existing APK files (both system and manufacturer apps!).
If you wish to Disable Apps do not use a Root App Uninstaller. Instead, use a systemless application disabler with your systemless root - e.g. Magisk Manager + App Systemizer module. This will allow you to achieve the temporary removal of system apps without modifying the /system/ partition. Why is keeping the System image original and stock important? If you modify the system partition (mount RW, delete an app, or make any changes) it will cause future issues and prevent updates when you wish to upgrade your OS or perform an OTA update.

» Google Play Services APK
Before installing any random version of Google Play Services, you must first make sure it matches a number of variables to prevent conflict on your device (Android TV, Mobile Device, TV Box, etc) and the corresponding OS etc. To do this, expand the box below but clicking "Un Hide".
To determine the suitable version of Google Play services for your Android device, go to Settings » Apps » Google Play Services (or Play Services). Here you will see the size, memory use and the version. Observe the three digit 'xyz' sequence 'v##.#.# (xyz-#########)'.

For example: Play Services v11.0.45 (430-155874144)
The 'xyz' here shows '430' which will represent which 'variants' of Google Play services that are compatible with your device. Therefore "430" represents:
X = "4" = if OS 5.0, 5.1 = Play Services v7.9 and older -OR- if OS 6.0+ = Play Services v8.0 and onwards.
Y = "3" = armeabi-v7a ARM CPU.
Z = "0" = Universal and can be used on any device with high or low DPI.

Example 3 Digit Prefixes:

430 = Android >=6.0; armeabi-v7a; NoDPI/Universal device;
046 = Android <5.0; arm64-v8a CPU; Max 320dpi device;
876 = Android TV; x86 CPU; Max 320dpi device;
940 = Android >8.0; arm64-v8a CPU; NoDPI/Universal device;
438 = Android >=6.0; armeabi-v7a CPU; Max 480dpi device;​

Download All Versions of Play Services:
- TV Versions: https://www.apkmirror.com/apk/google-inc/google-play-services-android-tv/
- Standard: https://www.apkmirror.com/apk/google-inc/google-play-services/

View further information on these 3-digit prefixes:
STATUS: Work In Progress!

ANDROID TV & GENERAL GOOGLE PLAY SERVICES COMPATIBILITY FINDER
X represents the Android OS version:
	'0' = Android <5.0 (pre OS 5.0.x. e.g. OS 4.3)
	'2' = Android 5.0 and 5.1 starting with Play Services v8+
	'4' = Android 5.0 and 5.1 before Play Services v8, Android >= 6.0 after
	'5' = Android Wear OS
	'7' = Android 5.0
	'8' = Android TV
	'9' = Android 8.0+

Y represents the CPU Architecture:
	'1' = armeabi
	'3' = armeabi-v7a
	'4' = arm64-v8a
	'5' = mips
	'7' = x86
	'8' = x86_64

Z represents the Screen 'dots per inch' (DPI):
	'0' = Universal or "NoDPI" restrictions.
	'2' = Max 160 dpi
	'4' = Max 240 dpi
	'6' = Max 320 dpi
	'8' = Max 480 dpi

OS Changes & Play Services Notes (exclusions):
 - With Google Play services v6.5+, builds migrated from '7yz' to '4yz'. Therefore, if you were on '7yz' with Play Services 6.4.x AND now have Play Services v6.5+, then the prefix changes to '4yz'.
 - With Google Play services v8.0+, '4yz' builds were split into '2yz' for Lollipop OS, and '4yz' for Marshmallow OS. Therefore, if OS is Lollipop v5.x AND Play Services v8.0+ used, then the prefix changes to '2yz'.
 - Please be aware the "Android TV" does not refer to ALL Android TV's or TV Boxes, but refers to light-weight bundled compatible Android enabled TVs. Double-check your television!

NOTE: This list is not fully complete and is only a guide.

Variant	Arch		O/S			Screen DPI
(000) 	arm		OS 4.0+		nodpi
(001) 	arm		OS 4.0+		160dpi
(002) 	arm		OS 4.0+		240dpi
(003) 	arm		OS 4.0+		320dpi
(004) 	arm		OS 4.0+		480dpi
(005) 	x86		OS 4.0+		nodpi
(006) 	arm		OS 5.0+		nodpi
(007)	arm		OS 5.0+		240dpi
(008) 	arm		OS 5.0+		320dpi
(009) 	arm		OS 5.0+		480dpi
(010) 	arm64/arm	OS 5.0+		nodpi
(011) 	arm64/arm	OS 5.0+		320dpi
(012) 	arm64/arm	OS 5.0+		480dpi
(013) 	x86		OS 5.0+		nodpi
(014) 	x86/x86_64	OS 5.0+		nodpi
(017) 	arm		OS 6.0+		nodpi
(018) 	arm		OS 6.0+		240dpi
(019) 	arm		OS 6.0+		nodpi
(020) 	arm		OS 6.0+		240dpi
(021) 	arm		OS 6.0+		320dpi
(022) 	arm		OS 6.0+		480dpi
(023) 	arm64/arm	OS 6.0+		nodpi
(024) 	arm64/arm	OS 6.0+		320dpi
(025) 	arm64/arm	OS 6.0+		480dpi
(026) 	x86		OS 6.0+		nodpi
(027) 	x86/x86_64	OS 6.0+		nodpi
(030) 	arm		OS 4.0+		nodpi
(032) 	arm		OS 4.0+		160dpi
(034) 	arm		OS 4.0+		240dpi
(036) 	arm		OS 4.0+		320dpi
(038) 	arm		OS 4.0+		480dpi
(046) 	arm		OS 8.0+		nodpi
(047) 	arm		OS 8.0+		240dpi
(048) 	arm		OS 8.0+		nodpi
(049) 	arm		OS 8.0+		240dpi
(050) 	arm64/arm	OS 8.0+		nodpi
(051) 	arm		OS 8.0+		480dpi
(052) 	arm64/arm	OS 8.0+		nodpi
(053) 	arm64/arm	OS 8.0+		320dpi
(054) 	arm64/arm	OS 8.0+		480dpi
(055) 	x86		OS 8.0+		nodpi
(056) 	x86/x86_64	OS 8.0+		nodpi
(070) 	x86		OS 4.0+		nodpi
(230) 	arm		OS 5.0+		nodpi
(234) 	arm		OS 5.0+		240dpi
(236) 	arm		OS 5.0+		320dpi
(238) 	arm		OS 5.0+		480dpi
(240) 	arm64/arm	OS 5.0+		nodpi
(246) 	arm64/arm	OS 5.0+		320dpi
(248) 	arm64/arm	OS 5.0+		480dpi
(270) 	x86		OS 5.0+		nodpi
(280) 	x86/x86_64	OS 5.0+		nodpi
(430) 	arm		OS 6.0+		nodpi
(434) 	arm		OS 6.0+		240dpi
(436) 	arm		OS 6.0+		320dpi
(438) 	arm		OS 6.0+		480dpi
(440) 	arm64/arm	OS 6.0+		nodpi
(446) 	arm64/arm	OS 6.0+		320dpi
(448) 	arm64/arm	OS 6.0+		480dpi
(470) 	x86		OS 6.0+		nodpi
(480) 	x86/x86_64	OS 6.0+		nodpi
(736) 	arm		OS 5.0+		320dpi
(738) 	arm		OS 5.0+		480dpi
(746) 	arm64/arm	OS 5.0+		320dpi
(930) 	arm		OS 8.0+		nodpi
(934) 	arm		OS 8.0+		240dpi
(936) 	arm		OS 8.0+		320dpi
(938) 	arm		OS 8.0+		480dpi
(940) 	arm64/arm	OS 8.0+		nodpi
(946) 	arm64/arm	OS 8.0+		320dpi
(948) 	arm64/arm	OS 8.0+		480dpi
(970) 	x86		OS 8.0+		nodpi
(980) 	x86/x86_64	OS 8.0+		nodpi

» Google Market Play Store APK
Should you require any older versions of Google Play / Market either to resolve instability, require less memory, or for use on a low-end/budget device, you can easily downgrade without issues. There are multiple methods of installation here, and it depends on your device type. If one method does not work, then simply try the next available.

Download All Versions of Play / Market:
- Standard: https://www.apkmirror.com/apk/google-inc/google-play-store/

Amalgamating and collating resources...

- - - - - - - - - - - - - - - - - - - - -​

» GOOGLE PLAY STORE & PLAY SERVICES - ERRORS, ISSUES, FIXES & TROUBLESHOOTING
STATUS: Work In Progress!

Be aware you do *not* need the latest version of every Google app to use your device. Updating often introduces issues and more resource intensive apps and services. May of 2018 and I am still using Google Play v6 without any issues on my TV Box.

More information will be updated soon...


Found this useful? Click the [:good: Thanks!] button below!
Cheers!

.​

 

[black-hook]

i have KI plus Amlogic S905D and 7.1.1 android version
can't find stock Rom download link (to use it in case of failure)

i tried to boot to recovery to install TWRP, but the device not accepting to boot to recovery

only showing Mecool Logo

 

[Ricky Divjakovski]

.
.

For hiding magisk you need to edit the APK file, as for safety net I believe @whiteak has passed safety net

As for the playstore fix, simply replace vending.apk

As for the crashes(not only Firefox) I believe it's got something to do with Amlogic-res or some other frameworks and libs

The recovery varies on Android version, I know you cannot load a fresh kernel from a different version and my best bet is either due to the bootloader or dtb, I cannot successfully flash either without USB burning tool, so if you find a way let me know so when can implement this fix in future roms removing the need to flash the same stock firmware as the target android version prior to flashing a rom

 

[Ricky Divjakovski]

i have KI plus Amlogic S905D and 7.1.1 android version
can't find stock Rom download link (to use it in case of failure)

i tried to boot to recovery to install TWRP, but the device not accepting to boot to recovery

only showing Mecool Logo

Pm me, I'll fix it for you

 

[black-hook]

Pm me, I'll fix it for you

i sent pm to you yesterday

 

[flipmode_11]

Blackhook, you are very lucky!
All us Aussie's are top blokes! Ricky especially!

Pm me, I'll fix it for you

i sent pm to you yesterday

 

[flipmode_11]

Thank you Ricky for taking the time to respond in the topic. Much appreciated!

Okay, so I don't understand "Edit APK file"? Can you please be more specific?

I cannot get Play/Play Services to work in anymore (15.3 to 16). Currently Play says "Certified" under settings. I've no idea how to replace Play, as it uses a different APK file name.

'WhiteAK'? has passed SafetyNet? I don't know what you mean... Whiteak has the same device and managed to update Play/Play services and get it working??

Crashes are "Amlogic-res" and/or lib \ framwork related. Okay I get System, Settings, plus any app I'm in... So perhaps some file/library can be updated to resolve this instability?

Strange as it doesn't appear as "Vending.apk" within BK Disabler, Titanium and other apps.
It is listed as
* Play Store v6.0.5 'com.android.vending' /system/priv-app/Phoneysky/Phonysky.apk
* Play Services v8.4.89 'com.google.android.gms' /system/priv-app/PreBuiltGMSCore/PreBuiltGMSCore.apk

So backup Vending.apk; download new Vending.apk (any original version?); overwrite old with new Vending.apk from (Link ???); that should take care of Play Store AND Play Services?
How do you prevent updates for Play + Play Services, like it is currently?
Will this solve the download/install issue?

Oh, so if reflashing, Slot 1 = current ROM version/variant (from backup I assume) and Slot 2 = new ROM to install?
I don't know what a "USB burning tool" is. Link to dev/site?

Thanks for sharing your knowledge.
Cheers mate!

For hiding magisk you need to edit the APK file, as for safety net I believe @whiteak has passed safety net

As for the playstore fix, simply replace vending.apk

As for the crashes(not only Firefox) I believe it's got something to do with Amlogic-res or some other frameworks and libs

The recovery varies on Android version, I know you cannot load a fresh kernel from a different version and my best bet is either due to the BOOTLOADER or DTB, I cannot successfully flash either without USB BURNING TOOL, so if you find a way let me know so when can implement this fix in future ROMs removing the need to flash the SAME stock firmware as the target android version prior to flashing a ROM

 

[flipmode_11]

Updated first two posts above.
If you notice any mistakes or typos, let me know.

Please share your knowledforfor anything Media Centre / TV BOX related!!
Cheers!

 

[ItsSunnyB]

will this only work for the t95z plus, i have a m9x 3 that has the amlogic 3912 with 3/32gb, the stock rom on it is really buggy would like something that works well. I have this installed on my t95z plus and works well.

 

[flipmode_11]

will this only work for the t95z plus, i have a m9x 3 that has the amlogic 3912 with 3/32gb, the stock rom on it is really buggy would like something that works well. I have this installed on my t95z plus and works well.

This will work as you have the same S912 standard chip and hardware.
Devices like the $$$ Nvidia Shield are very different units with very different hardware.
Booting to the recovery image and backing up WILL NOT make any modifications, unless you wipe, install or repair, etc...
Perform a (NANDroid) Backup of your device with above steps before attempting [*anything*].

 

[luffy_senpai]

good info

Thanks a lot for the useful info you posted here. I have kiii pro with amlogic 912, but the stock kernel doesn't include all device modules from source. I have some joysticks and they never work since no drivers are loaded for them. I would be grateful if you could help me with kernel source and a way to compile it with modules i need

 

[flipmode_11]

G'day Luffy,
I think the issues you've highlighted with the missing framework and modules is something you should post separately as this topic is for rooting, backing up, flashing, etc.

Create a new topic with subject: Kiii K3 Pro S912, Missing Modules / Drivers in Stock Kernel

Something like that in the subject, to describe the issue. Is it a Mecool? I nearly bought the Kiii/K3 but keep seeing people have issues on the forums!

I suggest you follow the Backup instructions above before you do anything else.....
P.s. Replace "xxGB" with model's RAM you have below.
Goods luck mate!

Thanks a lot for the useful info you posted here.

Hello, I have a Kiii Pro TV box w/ xxGB RAM, Amlogic S912 & DVB T2/S2.
I am experiencing issues with the stock kernel as it does not include all standard peripheral device modules. For example: I have some joysticks and they are neither recognised nor work, since no drivers are available to be loaded.

I would be grateful if you could help me with Kernel source and a way to compile it with all standard driver modules or those module drivers I need
Thank you.

 

[Ricky Divjakovski]

Thanks for sharing your knowledge.
Cheers mate!

Download the latest 7.1.2 gapps, get the vending file from within it.
On your device, playstore is either stored as vending, phonesky or velvet, so whatever one it's stored as delete the folder, make a new folder called vending and add the vending.apk inside it, set permissions to rw-r-r(644) , that's your playstore issues fixed(all of them)
You don't need to prevent updates, updates are distributed for a reason
Gms core is the core of all Google's services and does not need to be touched

Yes Whiteak has a t95z plus and managed to pass safety net, im unknown how though

For recoveries, I made a great tool to port recoveries to any device, removing the need to find a specific recovery for the variant, check this forum for my Amlogic flash tool and recovery porter

The random crashes I still haven't figured what fixes them but in my PoisonRom, none of those issues appear
And with next release, it compiles the kernel on the device so it will be compatible with every single Amlogic device.

 

[flipmode_11]

Champion mate! Really appreciate it.
Yes, PhoneSky. But Play Services is updated, and I updated Play from 6.0x to 6.0.5.
I downgraded from 12 to 11 on GMS (Play Services) and stopped getting the new crashes within apps. However it just auto-updates itself again and starts crashing again...

So flash Poison on to this X96 1GB (800MB) device? Already deciding on my next Media Box! (Shortlist: H96 Pro, X99 Max RKM MK39, R-TV K99 / CSA96, R99, CloudNetgo CD19, and......?). Any recommendations
They're all 4GB DDR3 RK3399 T860 models. I assumed the RAM capacity was more important than DDR4 speed....
Cheers!

p.s. downloaded your tool some time ago but now I understand what it does, given your explanation - Port a 3rd Party Recovery to be Generic Recovery supporting any AML S905/S912 media centre? Does that include RK33xx RockChip too?

@ricky Your name has a space so cannot write @ and mention you
Did you see I included your tool above? This was all I could interpret from descriptions and forum messages:

AMLogic Network Flash Tool [Bundled ADB & FastBoot (Tool & Drivers) - Ability to flash AMLogic Media Player TV Boxes remotely over the network (LAN Cable or Wireless/Wi-Fi). Always backup prior to upgrading/downgrading! Read more...

Will need to fix it up.
Thanks again for your information. I will add it to the top articles.

EDIT: p.s. Play Services has crashed 3 times on my phone today. So it is definitely the most latest version that is causing it to crash *more* than usual.

Download the latest 7.1.2 gapps, get the vending file from within it.
On your device, Play Store is either stored as "vending", "phonesky" or "velvet", so whatever one it's stored as delete the folder, make a new folder called vending and add the vending.apk inside it, set permissions to rw-r-r(644) , that's your playstore issues fixed(all of them)

For recoveries, I made a great tool to port recoveries to any device, removing the need to find a specific recovery for the variant, check this forum for my Amlogic flash tool and recovery porter

The random crashes I still haven't figured what fixes them but in my PoisonRom, none of those issues appear
And with next release, it compiles the kernel on the device so it will be compatible with every single Amlogic device.

 

[MKUltraBlack]

This worked for me on Bqeel k12 (amlogic s912) octacore running stock 7.1.2 ? thank you very much to OP ? booted into twrp first time from fat32 formatted sd card so I restarted, downloaded supersu zip, back to recovery, flash su.zip (via nice shiny new twrp?) root check and all is 100%
I see the twrp is 3.1? Will the theme zip work on it that was for 3.1 twrp ?

 

[flipmode_11]

Updated Support Downloads and Links.
+ Included AMLogic "USB Burning" Firmware Update/Imaging Tool v2.1.6 2018.03 Update..
+ Included Magisk Flashable Multi-Root Uninstaller ZIP latest update.


@Kurtlestat Thanks for the feedback.
I've not tried any theme.zip's so cannot comment. But trying standard Philz or TWRP do not work. This is a specially modified version to be compatible with all AML devices.
I'm actually looking for a RockChip compatible TWRP image but so far have not been successful!
If I were you, check out Magisk instead. It is systemless too. I switched as seems to be more actively maintained and organised.

 

[MKUltraBlack]

I tried the theme zip but it's only for twrp 3.1.0 This version is 3.1.1 so it was no dice, but still gave it a try ?

Now the sad news ? I tried flashing the poison rom and it failed with error 7. I went to restore my backup and musta wiped it lol can't even say I've got an expensive paperweight cos the things so light ?

Anyways does anyone know of stock firmware or custom rom for bqeel k12 amlogic s912 octacore 2/16gb it came with nougat 7.1.2 stock. Going to try download poison rom in mean while as I think error 7 is corrupt file. But..... to OP ...... the twrp still works ?

 

[flipmode_11]

New article added to 2nd post.

FIND & LOCATE YOUR STOCK BOOT IMAGE BACKUP CREATED BY MAGISK
Whether you initially used the Magisk Manager app -or- TWRP Recovery \ ADB FastBoot \ Odin3 to flash the Magisk patched boot image, a backup copy of the existing stock boot image is stored in "./data/" as "stock_boot.img".

However, if you flash an already Magisk patched "boot.img" through ADB FastBoot (Download Mode), then neither a "stock_boot.img" backup will be created or existing backup overwritten. Magisk detects the active boot image as already patched, therefore you must manually create a backup if you wish to retain the existing boot image.

Note: When patching a stock boot.img and flashing via Magisk Manager, the backup of the stock boot image is temporarily held in a directory until the next reboot: "./data/user/0/com.topjohnwu.magisk/install/stock_boot.img".
If you are struggling to locate the file, access an on-device terminal emulator, type "SU" and enter: "find -name 'stock_boot*'".

*Magisk Topic* » https://forum.xda-developers.com/showthread.php?t=3473445 (Features, Functionality, Q&A, Discussions)
*Troubleshooting* » https://www.didgeridoohan.com/magisk/HomePage (FAQ & Detailed Solutions & Examples)


Masking and Cloaking Root Access & SuperUser

1. Open Magisk Manager, open Settings. Scroll down to the yellow heading "MAGISK" and enable "Magisk Hide" (Note: do NOT enable "Hide Magisk"!!!)
2. Close Magisk Manager. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
3. Click the 3rd item down - "Magisk Hide".
4. Scroll down and tick the box on "Spotify" or any other item you want to "Cloak" or "Mask" Root to prevent detection.

BusyBox App or BusyBox Applets installed on your device?

1. Download, install and open your Busybox app. We will only use the "Uninstall" component of this app to cleanup any Busybox applets and remnants left behind..
2. If you have any corruptions in BusyBox preventing removal, first click "Install" to update, and then click "Uninstall".
3. Once complete, you may uninstall the Busybox app. It will not be required from now on.

Masking BusyBox Modules and Applets

1. Open Magisk Manager. Slide open the left menu by swiping left-to-right.
2. Click the "Downloads" menu item.
3. Scroll down the list and looks for something like "Busybox NDK" or similar.
4. Read the module description. Click Install and follow the steps.
5. Slide open the "Modules" menu item to see the list of (active/inactive) installed modules (You may tick/untick a module to disable it temporarily, or click the trash icon to remove and uninstall it completely).
   You should now see the BusyBox NDK systemless edition installed.

Found this useful? Please click "Thanks". :good:
Cheers!

 

[flipmode_11]

Mate I would literally post that in the Poison ROM topic as they will know the best thing to do.
Didn't you save the TWRP backup on your SD Card or PC? Always save to a PC! Read all my posts! I'm obsessed with backups! Hah

Bqeel K12... Find their web site and use the contact form if you cannot find the support downloads. I had a quick google and struggled. However many sellers now have "Support" tabs, with links to firmware.
Don't stress mate, you'll be right. They're fairly indestructable as all unlocked and fairly flexible boxes.

p.s. From your experience, would you get an S912 or RK3399 or RK3368? and 4GB DDR3 or 3GB DDR4?
Trying to get a more reliable box, that can handle the power. I have seen no bootable SD recovery.img for RockChip. Bit of a concern I can't get to TWRP on this $50 RK3328. Next box: RKM MK39 or CloudNetGo CR19 (RockChip) - and - Any 3GB DDR4 or Any 4GB DDR3 (S912) - and- Meecool KIII DVB-T2 or ....

I tried the theme zip but it's only for twrp 3.1.0 This version is 3.1.1 so it was no dice, but still gave it a try
Now the sad news I tried flashing the poison rom and it failed with error 7. I went to restore my backup and musta wiped it lol can't even say I've got an expensive paperweight cos the things so light
Anyways does anyone know of stock firmware or custom rom for bqeel k12 amlogic s912 octacore 2/16gb it came with nougat 7.1.2 stock. Going to try download poison rom in mean while as I think error 7 is corrupt file. But..... to OP ...... the twrp still works