+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: Issues with "recovery" button (/showthread.php?tid=8927)
Pages:
1
2
RE: Issues with "recovery" button - clover - 01-30-2020
I tried using tux's intructions with a usb-c -> usb-c cable tonight, both pbp's. didn't work.. will try usb-a to usb-c tommrow.
RE: Issues with "recovery" button - clover - 01-30-2020
USB-A to USB-C did work with the ld command, but when i tried to flash the db file, i kept getting "Creating Comm Object failed!" so i decided not to proceed any futher. is this the expected output? i also tried running the command with sudo, but got the same response. tried both tux and as400's files. perhaps the pinebook usb-3 port does not provide enough power to run this command?
RE: Issues with "recovery" button - clover - 01-30-2020
I just tried the spi flash and i think i've really done it this time... lol
~> rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom
~> cd PBPBoot
~/PBPBoot> rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin
Downloading bootloader succeeded.
~/PBPBoot> rkdeveloptool wl 0 spiflash.bin
Write LBA from file (100%)
~/PBPBoot> rkdeveloptool td
Test Device OK.
~/PBPBoot> rkdeveloptool rd
Reset Device OK.
Edit: nvm, it works! it took a while and a few power cycles to figure everything out but i can boot from emmc at least.