Open main menu


The device is only flashable using the rkusb bootloader mode. This can be done with the opensource rkdeveloptool utility.
To trigger the bootloader hold a magnet on the backcover of the pinenote while powering it on.  When it's booted correctly into bootloader mode it should show up in the device list of rkdeveloptool: <source lang="shell-session">$ rkdeveloptool ldDevNo=1 Vid=0x2207,Pid=0x350a,LocationID=100 Loader</source> It's possible to overwrite the eMMC with the LBA write command: <source lang="shell-session">$ rkdeveloptool wl 0 rootfs.imgThe 0 is the offset in blocks from the start of the eMMC, can be used to flash a partition if you know the offset</source> == Recover from a broken bootloader == If uboot image is overwritten the rockusb mode won't work anymore. The device might boot into maskrom mode in which case it should show up in `rkdeveloptool list` as maskrom. If the uboot image is partially overwritten but still recognized by the maskrom it won't stay in maskrom mode and you'd have to open the back of the device and short TP1301 and TP1302 while powering up. This will make eMMC reads fail so maskrom always runs. Once the device is in maskrom mode the only thing you can do is push a new loader into ram and start that. <source lang="shell-session">$ rkdeveloptool listhere it lists maskrom now The .bin file is build by u-boot and might have a slightly different version$ rkdeveloptool db rk356x_spl_loader_v1.04.108.bin$ rkdeveloptool pttnow it's able to read flash and list the partitions</source>
== Installation ==
== See also ==
* [ PINE64 wiki page]
* [ fork of rkdeveloptool with many improvements] this will be the version supported on the pinenote.