Messed up, PBP does not start after write_spi_flash
04-05-2020, 12:23 PM
You're outside my expertise now. Some thoughts, in case they're helpful:
The instructions say you can `rkdeveloptool ld` to confirm your pinebook pro is connected and in maskrom mode. Did you ever get that to work?
In my experience flashing phones, low-level firmware writes are often very flaky. It's not unusual to have to try the whole dance several times to get it to work. Try connecting usb before or after pressing the reset button, varying the rhythm of the steps, that sort of thing.
The instructions say to remove all bootable devices. Did you take out the sdcard, and the eMMC module?
I don't understand what you mean by "the boot volume" being "automatically mounted". Do you mean the Pinebook Pro presented a USB mass storage device? What filesystem type? (e.g reported by typing `mount | grep media`) how big was it? (`df -h`) Some boards do allow firmware update this way, but most present a custom usb device, which is what I expected from rkdeveloptool needing libusb installed.
The instructions say you can `rkdeveloptool ld` to confirm your pinebook pro is connected and in maskrom mode. Did you ever get that to work?
In my experience flashing phones, low-level firmware writes are often very flaky. It's not unusual to have to try the whole dance several times to get it to work. Try connecting usb before or after pressing the reset button, varying the rhythm of the steps, that sort of thing.
The instructions say to remove all bootable devices. Did you take out the sdcard, and the eMMC module?
I don't understand what you mean by "the boot volume" being "automatically mounted". Do you mean the Pinebook Pro presented a USB mass storage device? What filesystem type? (e.g reported by typing `mount | grep media`) how big was it? (`df -h`) Some boards do allow firmware update this way, but most present a custom usb device, which is what I expected from rkdeveloptool needing libusb installed.