[SuperSU] SugarSweetStarr:
Lollipop PC Box

Hi, sorry I'm a noob but I can follow instructions.

I have a Rupa M8S Pro 4k box which came with Lollipop, SuperSU 2.46 and stock recovery:

DevCheck Report

amlogic
Amlogic M8S Pro

Jan 15, 2017 5:57
Uptime: 48m 43s
Deep sleep: 0s (0%)

HARDWARE
Amlogic
null
null
Cores: 4
Frequencies: NA MHz - NA MHz
Governor: hotplug

GRAPHICS
Vendor: ARM
GPU: Mali-450 MP
OpenGL: OpenGL ES 2.0
Resolution: 1920x1080
Screen density: 240 dpi
Screen size: 13.77 in / 350 mm

RAM
RAM size: 2.0 GB

DEVICE
Model: M8S Pro
Codename: p201
Manufacturer: amlogic
Serial Number: unknown

SYSTEM
Android Version: 5.1.1 (Lollipop)
Build: p201-userdebug 5.1.1 LMY47V 20160816 test-keys
Architecture: aarch64 (64-bit)
Kernel: Linux version 3.14.29 (foxluo@skykirin2) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #4 SMP PREEMPT Tue Jul 12 10:35:24 CST 2016

BATTERY
Technology:
Health: Unknown
Capacity: NA

Amlogic

Dump 1632476 [mamhde] - Submitted by M8S Pro - 2017-01-17 18:44:00

Device Manufacturer
Amlogic

Model ID
M8S Pro

Android Version
5.1.1

Kernel Version
3.14.29

Battery Capacity
1000 mAh

SoC (Processor) Architecture
ARM (aarch64)

SoC Model
ARM Cortex-A53

SoC Family
4x ARM Cortex-A53 @2.02 GHz

Frequency
2016 MHz / Min: 100 MHz - Max: 2016 MHz

Main CPU Cores
4 Cores / 4 Threads

CPUID
41.0.8.D03.4

Revision
R0P4

Features
FP ASIMD CRC32 WP HALF THUMB FASTMULT VFP EDSP NEON VFPV3 TLSI VFPV4 IDIVA IDIVT

Display (GPU / LCD)

SoC Manufacturer
ARM

SoC Model
Mali-450 MP

OpenGL Ver.
2.0

LCD Size
13.8 inches / 35.1 cm

LCD Resolution
1920 x 1080 pixels

LCD Definition
240 DPI

Memory RAM
1779 MB (2 GB)

Flash
12010 MB

Embedded Sensor

CPU-Z SCREENSHOT

￼

Sorry that I don't yet have a USB cable running to the box, but I do have Ethernet, keyboard, mouse, USB stick and HDMI plugged in so perhaps an SSH session would help. I have mostly Windows but can run Linux on a virtual machine.

As noted, when I open SuperSU it asks to update the binary. In-app normal does nothing at all, while in-app TWRP/CWM reboot my box, show me the droid with his guts open and then reboot without giving me any options.

I've installed CWM Rom Manager, which can reboot my box into a stable recovery and I can choose what to do. I've then used the update file for v2.46 and it said it succeeded and only complained about not being able to mount /misc. However, after I rebooted it and opened the SuperSU app it asked again to update the binary.

I've also tried updating the app to 2.79 but although it installs from Google Play it fails to update, saying "bad recovery detected, no unzip, abort install".

Rom Manager also offers to install roms for me, but doesn't recognise my model so doesn't show me any roms to download. If I tick the box to show other devices none of them appear to be like mine.

- Exact device model

The firmware says RUPA on boot and M8S Pro 4k is emblazoned on the outside.

- Exact firmware version

I hope that the logs above give this. If it doesn't I'll need to use an app or command to find it.

- Exact Android version

Android 5.1.1 Lollipop

- Exact SuperSU version

2.46 out of the box, 2.79 offered by Play Store.

- Interfering apps

Not aware of any other rooting apps being installed. Definitely no Busybox or Xposed.

- Update methods tried

In-app normal = fail to reboot; in-app TWRP/CWM = the progress bar underneath the droid seems to get halfway and then reboot; other options not offered by SuperSU.

Stock rom, never updated.

- What kind of root are you left with?

After a failed binary update, multiple outcomes are possible:

- Root seems to mostly still work. Most apps still work.

- Nothing has changed at all. Binary version remains at 2.45.

- Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app

After pressing the TWRP/CWM button, the device should reboot into TWRP, do it's thing for a few seconds, then reboot into Android. If SuperSU still complains about the binary, please retrieve the TWRP log file. You can retrieve it via

adb pull /cache/recovery/last_log

, which should produce the last_log file in your current directory. You still need at least partial root from booted Android to retrieve this log. Sadly it is wiped and replaced with a new file when you boot into recovery a second time, so you cannot retrieve it that way. Note that this log will always contain a number of errors, as the installer tries several things in several ways, that work differently on different firmwares. Attach this log file.

I'd like to, but I haven't managed to retrieve the log files yet. Is there an app or a command from within Android that can get these logs?