soft brick with ayufan
07-15-2021, 03:11 AM
(This post was last modified: 07-17-2021, 02:31 AM by DimHummingbird.)
Hi everyone -
I wanted to install the ayufan buster-containers release onto my PineBook Pro, but now my machine won't boot. The boot LED doesn't even come on.
Here's what I did. Connected to USB-C power the whole time.
1) Use etcher on another machine to flash buster-containers-rock64-0.11.0-1185-arm64.img from https://github.com/ayufan-rock64/linux-b...tag/0.11.0 onto a microSD card. (I previously tried, and couldn't boot with, the "stable" version 0.9.14).
2) Successfully booted from the sdcard on my pinebook pro and logged in.
3) Connected my USB ethernet adapter, and scp'ed over the same image file. Used md5sum to validate the transfer was OK.
4) Checked which device was mounted as root (emmc 1).
5) `dd if=buster-containers-rock64-0.11.0-1185-arm64.img of=/dev/emmc2 bs=64M status=progress`. (I don't remember the exact device naming convention, but it was the tab completed root device of whichever "mmc" was NOT mounted).
6) `sudo reboot now`
7) The machine hung at a blank screen with a single blinking cursor in the top left, so after a couple of minutes I powered off with a long-press of the power key.
Now I can't turn it back on again! I get a charging LED when I plug in USBC power, but no boot LED when I press the power button.From reading other threads and the doco, I have tried:
* an "extra sure hard power off" by holding power for >30 secs (once even > 1min) before trying to power on again
* validating the sd card contents. `p3` does contain what looks like a normal `/boot`. `p2` is an empty vfat. `p1` contains nilfs, fdisk output:
* flipping the hardware switch to disable the internal emmc
I can't get it to show any sign of life, with or without the sd card. I'm stuck! What can I do next?
I wanted to install the ayufan buster-containers release onto my PineBook Pro, but now my machine won't boot. The boot LED doesn't even come on.
Here's what I did. Connected to USB-C power the whole time.
1) Use etcher on another machine to flash buster-containers-rock64-0.11.0-1185-arm64.img from https://github.com/ayufan-rock64/linux-b...tag/0.11.0 onto a microSD card. (I previously tried, and couldn't boot with, the "stable" version 0.9.14).
2) Successfully booted from the sdcard on my pinebook pro and logged in.
3) Connected my USB ethernet adapter, and scp'ed over the same image file. Used md5sum to validate the transfer was OK.
4) Checked which device was mounted as root (emmc 1).
5) `dd if=buster-containers-rock64-0.11.0-1185-arm64.img of=/dev/emmc2 bs=64M status=progress`. (I don't remember the exact device naming convention, but it was the tab completed root device of whichever "mmc" was NOT mounted).
6) `sudo reboot now`
7) The machine hung at a blank screen with a single blinking cursor in the top left, so after a couple of minutes I powered off with a long-press of the power key.
Now I can't turn it back on again! I get a charging LED when I plug in USBC power, but no boot LED when I press the power button.From reading other threads and the doco, I have tried:
* an "extra sure hard power off" by holding power for >30 secs (once even > 1min) before trying to power on again
* validating the sd card contents. `p3` does contain what looks like a normal `/boot`. `p2` is an empty vfat. `p1` contains nilfs, fdisk output:
Code:
Disk /dev/mmcblk0: 116,16 GiB, 124721823744 bytes, 243597312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E96A8F3C-0431-4043-8BFE-2D57A1A4CE67
Device Start End Sectors Size Type
/dev/mmcblk0p1 64 8191 8128 4M Linux filesystem
/dev/mmcblk0p2 8192 32767 24576 12M Microsoft basic data
/dev/mmcblk0p3 32768 524287 491520 240M Linux filesystem
/dev/mmcblk0p4 524288 243597278 243072991 115,9G Linux filesystemI can't get it to show any sign of life, with or without the sd card. I'm stuck! What can I do next?