cmdlieao Posted March 13, 2020 Posted March 13, 2020 I'm at my wit's end here, I've tried all I can think of. I have this Mecool M8S Pro, I've been trying to root it, flash twrp, and install armbian. There is no way to access bootloader, or maybe it's the same as recovery. When I put armbian on an sdcard and made an armbian_first_run.txt file, I first tried using the update app. I picked the aml_autoscript.zip, and confirmed the update, then a message pops up and says "shutting down", then nothing I've left this for a long time and the box never comes back on. Basically, the box won't turn on if there is an sdcard in the slot. I've looked at all the logs available from the recovery screen and after I try this it says something like this: "failed to mount /dev/block/mmcblk0 (device or resource busy)". Even if I hold the reset button, the box turn on if there is an sdcard in the slot. I have also tried flashing twrp, it doesn't work if I have it on an sdcard and boot to recovery because the box won't turn on if there is an sdcard in the slot while powering up, and if I plug it in after I boot to recovery the box won't see it when searching for files in update from EXT. The update also didn't work when I had it on a USB and tried to update from EXT. The message I saw on the log after trying this said something regarding cryptfs driver not working. There was an earlier error in the log, but it seemed to make it past this error. I can't install TWRP at least the two versions I have tried. I have yet to try to put SuperSU zip on the box using update, or an apk using app installer. Would that help? The main reason I mentioned no bootloader in the title is because, when I broke down and tried to use adb over Ethernet, I would run adb reboot bootloader, the box just turns off, regardless of whether there is an sdcard in the slot. I had to use Ethernet to debug, because when I plug in USB to the box there is a CD image that appears on my PC and I can't use adb over USB. So, I got adb to work with tcpip, but adb reboot bootloader does nothing. I got to a bootloader looking screen with adb reboot recovery, it gives me options like 'Update from ADB', 'Update from EXT', 'Wipe data', 'Wipe cache', 'Mount /system', 'Reboot system', 'Reboot bootloader' (just turns the box off), and more. Once I have reached this screen, adb devices lists the device as offline and I can't run fastboot commands such as 'flash recovery' or 'oem unlock'. I'm at my wit's end.
cmdlieao Posted March 13, 2020 Author Posted March 13, 2020 Armbian_20.02.0-rc1.037_Aml-s9xxx_buster_current_5.5.0-rc6_desktop_20200205.img
cmdlieao Posted March 13, 2020 Author Posted March 13, 2020 Here's some more info on the recovery/last_log I see after trying to boot armbian: W: instaboot: cannot open devicecharge 1, charged 1, status -2, capacity. -2147483649 Finding update package I: update location /sdcard/aml_autoscript.zip Opening update package... W: try mount /dev/block/mmcblk0 ... E: failed to mount /dev/block/mmcblk0 on /sdcard (Device or resource busy). try read only ... E: failed to mount /dev/block/mmcblk0 on /sdcard by read-only (Device or resource busy) . . . sysutil. Unable to open '/sdcard/aml_autoscript.zip': No such file or directory E: failed to map file E: failed to read uncrypt status: No such file or directory I: /sdcard/aml_autoscript.zip 0 time_total: 4 retry: 0 Installation aborted. I: saving locale 'en_US' I: saving locale 'en_US' -------------------------------------------- If there is something I can tweak in the image so that my sdcard is remounted properly, I'll do that. If rather not have to open up the case to fiddle with any hardware. Would it be better if I tried a different image? I had assumed it was just the box being difficult with the bootloader, as all I have access to is the factory recovery image. I don't know how to oem unlock the box right now either.
balbes150 Posted March 14, 2020 Posted March 14, 2020 On 3/13/2020 at 6:22 AM, cmdlieao said: When I put armbian on an sdcard and made an armbian_first_run.txt file, You do not configure the system correctly, you need to configure the dtb in the file (uEnv.txt). This file armbian_first_run.txt is not used and can be deleted .
cmdlieao Posted March 14, 2020 Author Posted March 14, 2020 Ok, ty. Working now. Following a newer install guide, but I don't see /boot/extlinux for installing to internal memory. Is this still going to work?
cmdlieao Posted March 14, 2020 Author Posted March 14, 2020 And I can't find nand-sata-install. What is the new method for installing to internal storage?
SteeMan Posted March 14, 2020 Posted March 14, 2020 31 minutes ago, cmdlieao said: And I can't find nand-sata-install. What is the new method for installing to internal storage? There are scripts in /root for installing to internal storage
balbes150 Posted March 15, 2020 Posted March 15, 2020 This topic is outdated , all relevant information in this topic.
Recommended Posts