[Android Stick & Console AMLogic based Computers] 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 S905

x

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://xdaforums.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! :P

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)

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.);

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! :P

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 [MENTION=4544860]osm0sis[/MENTION] - 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:

To begin, download and install Stericson's BusyBox installer (link above).

Launch the BusyBox app, click "Grant" to the root request, and wait for 2-3 minutes while the app initialises for the first time.

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.

Exit BusyBox and re-open. Now click "Uninstall" at the bottom-right and click "Uninstall" again saying yes you understand.

Now your system has no BusyBox! Some background services may complain but this will only be for a few minutes.

Open Magisk Manager and swipe open the left-hand side-menu and click Modules.

You will now see your currently installed (active/disabled) modules plus the latest versions of other Magisk-compatible modules below.

Click the Search icon at the top-right and search for 'busybox'. You should find "Busybox for Android NDK" (ignore the "NDK" part).

This is the Magisk recommended Systemless BusyBox module managed by XDA member 'Osmosis' [MENTION=4544860]osm0sis[/MENTION]. 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.

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://xdaforums.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: [MENTION=4470081]topjohnwu[/MENTION]'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!

.​