| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,110
» Latest member: Gudila
» Forum threads: 16,362
» Forum posts: 117,533
Full Statistics
|
| Latest Threads |
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
9 hours ago
» Replies: 2
» Views: 139
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 74
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,031
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 235
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 129
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,597
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,209
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 276
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 195
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,669
|
|
|
| Fanless daily driver? |
|
Posted by: donblanco - 04-22-2019, 08:23 AM - Forum: Linux on RockPro64
- Replies (2)
|
 |
What I am trying to replace: mini-itx I LINUX Mint, 3 drives and a noisy fan.
Typical usage:
- Music/video streaming (youtube/SomaFM, etc)
- Browsing
- Darktable (photo editing)
- ebook server
- Libre Office
- email (Mailspring)
- watching video downloads
- Transmission torrent client
- VS Code (web sites)
Occasional/optional usage:
- video editing
Need to be able to:
- connect to 3 drives (USB?)
- connect to VT KEYBOARD
- do HDMI
Questions:
1 - is this possible with the RockPro64 in a small fanless case?
2 - is Linux Mint 19 running on this yet?
|
|
|
|
Video and Guide to install Android to emmc no emmc to usb adapter |
|
Posted by: NightCrawler504 - 04-21-2019, 07:19 PM - Forum: RockPro64 Projects, Ideas and Tutorials
- No Replies
|
 |
First get your hardware:
1) Usb to type c cable, if you don’t have a usb to type c you can use an adapter
*usb 3 to usb 3 cable should work but I tried with mine and did not work
Cables are not created equal if procedure does not work after following instructions try with another one, I’ve got plenty of cables and procedure only worked with 2, if you can adb to your phone it should also work for this.
2) A jumper to short out pins, if you do not have one you can use 2 sided female gpio cable to jump pins anything that can short the pins should work just be careful.
Software:
1) Download Android Flash Tool:
files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip
2) Download Drivers:
files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip
3) Download Image for android I recommend this one it’s the one that has worked best for me:
files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz
--Unzip to get image you will burn, download comes zipped you need to unzip, remember where you put the image file and the name so you don’t get confused selecting unzipped download… better yet once unzipped just delete the zip file.
While you are at it might as well download Domos platform tools from here:
https://drive.google.com/file/d/1YAMZF0J...mDRpP/view
You can use minimal adb or any already installed adb, but Domo download has a set of packages we will need later to install google store, so might as well use this one.
Would recommend you keep all your downloads in a single separate folder for easier location of files.
Ok let’s Start!
1) Install drivers from driver download, it’s an exe file that’s called DriverInstall
2) Go to your downloads and run the exe file called AndroidTool from the file you downloaded
3) Unplug your rp64 from power source and leave it like that, take out your microsd if you have one, make sure your emmc is plugged in correctly
4) Short the pins with jumper (pins that need to be shorted are right next to the emmc)
5) Open your Android Tool (yes this is step 2 repeated) make sure its open
6) Connect your usb cable to computer and type C to rp64 (flashing only works on type c to my experience if you have found differently please comment bellow)
On Android Tool you should get Found One MASKROM Device
7) Connect power again, wait for device description on android tool to recognize device
8) Disconnect jumper, wait for device description on android tool to flicker
9) Go to Android tool and Go to Upgrade Firmware on the top menu (flash will only work on MASKROM)
10) Select firmware and select your unzipped image, be sure to have it unzipped and selected the right image burning the wrong image or burning an unzipped image can really be a headache to troubleshoot cause you might not know what went wrong.
If Flash doesn’t start then:
Unplug power, make sure there is no microsd card, put jumper back, make sure emmc is connected, take type c out wait for light to disappear and connect type c again, put power back in wait to see message in android tool flicker, take of pin once device has been recognized and wait for android tool device flicker, take off jumper pin and try again. If after a few tries still not working try changing your cable.
If your issue is device not found this is most likely a driver issue, go to device manager find what rp64 appears as in device tree and try to add driver manually from the drivers folder you download, if this doesn’t work just delete the driver, after that device should pop out again, driver issues can be very frustrating it might be reading as and adb device from a previous install or a manufacturer brand you made or as a phone (like sony, huawei piking it up) even then just delete driver from the device on device manager or add correct one, if this doesn’t work there are many videos on the internet explaining how to fix these kinds of issues they can be very particular so maybe post bellow and some can help you.
11) If flash did not finish or gave an error flash again, its happened to me before eventually it will flash correctly. With any luck you got it right on the first time. Sometimes it even finished and didn’t work in my case, had to reflash.
12) Finally connect as you normally would, without jumper…
13) Wait a good 5 minutes and voila, Android at your service.
Once you get the hang of it process to flash should take around 5 to 10 min first time is the hardest because of trouble shooting and forgetfulness but after that it’s a breeze.
For Visual aid you can see video at the link bellow:
https://youtu.be/JBjWyajeZPw
If something remains unclear leave a comment to see if I can help you and further explain.
|
|
|
|
| Connecting external monitor to the Pinebook |
|
Posted by: Fox7799 - 04-21-2019, 01:14 PM - Forum: Ubuntu
- No Replies
|
 |
Hi: My Pineboard connects to an external monitor but my Pinebook which has the Pineboard as its motherboard does not. I'm using an adapter to connect the micro hdmi on the Pinebook to a standard hdmi cable that goes to the monitors. I read somewhere that a special cable from Pine64 is needed. Is this true and if so what is different? How much do one of these proprietary cables from Pine64 cost? Thanks
|
|
|
|
| RockPro64 not booting |
|
Posted by: jekohk - 04-20-2019, 03:01 PM - Forum: General Discussion on ROCKPRO64
- Replies (10)
|
 |
Hey all,
Posting here in hopes that I can get some guidance on where to turn next. Wanted a second opinion before I go ahead and attempt to get a replacement board, since the last one took close to a month to ship.
Essentially, my RockPro64 just refuses to boot. I'm using the 64GB SD Card purchased from the Pine store, and have tried burning multiple distros to the card using multiple devices (a mac, PC, and linux machine) but no dice. When I plug in power, the lights on the Ethernet port light up, as well as the power light next to the DC input, but it looks like the USB ports get no power as my KB and mouse do not light up and I get no signal from HDMI.
I then purchased a serial adapter CH340G to attempt to check the boot process of the board, however I can't seem to get any serial output from the board either (My steps for that detailed in a post here)
Apparently it is common that the SD Card slot on the boards ships broken, does it sound like that is the case? It looks like the board itself is getting power according to the lights on the ethernet port.
Additionally, does it make sense that I would get no serial output even if the SD Card slot was broken? Will the board only begin outputting to the serial terminal if it has a functioning boot device? I was hoping even if the sd card slot was bad, I would at least see some errors in the serial console as it tried to boot.
Just looking for advice on what to do next/if it's worth debugging further or if I should begin the returns process?
|
|
|
|
|