Any luck on getting your desktop back?
I am trying to get the dongle working...to get to rkdeveloptool...to reflash to stock.
From linux minicom dongle works...if the PN boots (not to desktop but acts like it's going there). I can get a login and use it.
The dongle has yet to show me any of the u-boot console except garbage characters.
Still fighting it.
To expand on my boot issues:
- apt-get update, install, ... to attempt to get X11 going
- switched off autologin in wayland/gnome/settings
- lost wayland ie no desktop
- would boot show some text, flash the squares Pine 64 background
- tried dongle
- had dongle working for a bit for the OS ie I got on, found I had wifi, and scp'd some stuff off. (linux debian 12 desktop, minicom)
- never saw u-boot stuff in minicom. When it was supposed to show...got corrupted characters
- Followed the instructions and ran bash install_stable_1056mhz_uboot.sh
- I think this is what killed the dongle from working
- now no matter what I boot how, I just get to the u-boot selection screen, end up on a Pine64 squares but nothing shows up on the serial console.
$400 is a lot to shell out for this. We must have a method to reset back to zero. Possibly a fixed rom and a reset button. Perhaps a SD card?
Should not be able to brick a device given the steps above.
Help?
I am trying to get the dongle working...to get to rkdeveloptool...to reflash to stock.
From linux minicom dongle works...if the PN boots (not to desktop but acts like it's going there). I can get a login and use it.
The dongle has yet to show me any of the u-boot console except garbage characters.
Still fighting it.
To expand on my boot issues:
- apt-get update, install, ... to attempt to get X11 going
- switched off autologin in wayland/gnome/settings
- lost wayland ie no desktop
- would boot show some text, flash the squares Pine 64 background
- tried dongle
- had dongle working for a bit for the OS ie I got on, found I had wifi, and scp'd some stuff off. (linux debian 12 desktop, minicom)
- never saw u-boot stuff in minicom. When it was supposed to show...got corrupted characters
- Followed the instructions and ran bash install_stable_1056mhz_uboot.sh
- I think this is what killed the dongle from working
- now no matter what I boot how, I just get to the u-boot selection screen, end up on a Pine64 squares but nothing shows up on the serial console.
$400 is a lot to shell out for this. We must have a method to reset back to zero. Possibly a fixed rom and a reset button. Perhaps a SD card?
Should not be able to brick a device given the steps above.
Help?