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

Always Backup!

Take a

full

backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).

Launch Magisk Manager (round green mask icon).

Slide open the left menu by swiping left-to-right. Click Settings.

Scroll down to yellow 'MAGISK' section.

Enable "Magisk Hide".

Close Magisk Manager. Open Magisk Manager. Slide open the left menu by swiping left-to-right.

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:

Always Backup!

Take a full backup using TWRP app, or alternatively via "recovery.img" (attached & already discussed).

Launch Magisk Manager (round green mask icon).

Slide open the left menu by swiping left-to-right. Click Settings.

Under the yellow 'GENERAL' section.

Click "Hide Magisk". *NOTE* There is NO CONFIRMATION prompt!

Wait 1-2 mins and Magisk Manager will close automatically.

Open Magisk Manager (same round green mask icon). You can now check the new package name.

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.

Force stopped Magisk Manager.

Backup then Delete file /data/property/persist.magisk.hide (0600).

Launch Magisk Manager.

Go to Settings >> Enable Magisk Hide.

Go back to Manager home screen. Swipe to reveal side-menu and check Magisk Hide menu is visible.

Close Magisk Manager or Force stop.

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

SOLUTION 2.

Another fix [MENTION=4725839]dunderball[/MENTION] 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.

Check the existence of the "/magisk/.core/magiskhide/hidelist" path.

Create the "/hidelist" directory.

CHMOD "/magisk/.core/magiskhide/hidelist" to 0644.

Thanks go to [MENTION=4725839]dunderball[/MENTION]. :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:

Performing a backup of your data, important partitions and system state;

Flash Magisk Uninstall ZIP (link available above & on Magisk topic); and

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

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

Boot into TWRP recovery via 'recovery.img' on Micro SD card.

Take a full device backup.

Flash Magisk latest stable or beta ZIP.

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.

Boot into TWRP recovery via 'recovery.img' on Micro SD card.

Take a full device backup.

Flash SuperSU latest stable or beta ZIP.

# ChainFire

Flash ChainFire ZIP installation script.

Boot into TWRP recovery via 'recovery.img' on Micro SD card.

Take a full device backup.

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

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.

If you have any corruptions in BusyBox preventing removal, first click "Install" to update, and then click "Uninstall".

Once complete, you may uninstall your Busybox app as is no longer required!

MASKING BUSYBOX MODULES AND APPLETS

Open Magisk Manager. Slide open the left menu by swiping left-to-right.

Click the "Downloads" menu item.

Scroll down the list and looks for something like "Busybox NDK" or similar.

Read the module description. Click Install and follow the steps.

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!

.​