PINE64

Full Version: Cant get anything to work
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey so this is my first post, i have read a handful of threads to try and fix my issue but no luck. first of all, NONE of the wiki download links are working for me, every single one of them say they are corrupted when i try to unzip them. my second problem, when i plug in my pine64 to the charger and the hdmi... nothing, i though i have seen in other videos people plugging them in, and getting the pine64 screen, i dont even get that, i get the red light on indicating there is power, but nothing else. i have a geniune 16gb class 10 sandisk card, and the 1 gb pine64. I am very new to all this so i really need basic tutorial, but even the basic videos i have watched still all direct me to the pine wiki page for download, and none of them work... super frustrated. please help.
Hi

What images have you downloaded / are you trying to burn?
The Pine64 logo only comes on when you have a SD with and OS loaded.

Have you looked in forum for beginners? the http://forum.pine64.org/forumdisplay.php?fid=21
Unless you successfully burned a working OS image on SD card all you get is a red led lighting forever. Without an OS on the card nothing will happen.

To be sure yours is DOA or not:

1) download a good OS image and not the crap from the Wiki: http://forum.pine64.org/showthread.php?tid=376

2) download/upgrade 7-zip (a security issue has been discovered just recently): http://www.7-zip.org

3) uncompress the image and optionally check integrity as outlined in the first link

4) check your SD card and your card reader now. Reasons why and tools you find in issue N°2: http://forum.pine64.org/showthread.php?tid=514

5) Get Rufus and burn the OS image (ending on .asc): https://rufus.akeo.ie (Rufus has a verify function also)

6) Insert SD card, provide stable 5V/2A (not that easy since Micro USB has been used, see forum link above) and start the board

7) be aware that if your display isn't connected directly (HDMI) and capable of 1080p you won't be able to notice any activity. You would need either a connected Ethernet cable (then leds on the Ethernet jack start to blink 20 seconds after boot) or a powermeter (showing 300-400mA and peaks up to 700mA while booting)
(05-12-2016, 08:19 AM)tkaiser Wrote: [ -> ]Unless you successfully burned a working OS image on SD card all you get is a red led lighting forever. Without an OS on the card nothing will happen.

To be sure yours is DOA or not:

1) download a good OS image and not the crap from the Wiki: http://forum.pine64.org/showthread.php?tid=376

2) download/upgrade 7-zip (a security issue has been discovered just recently): http://www.7-zip.org

3) uncompress the image and optionally check integrity as outlined in the first link

4) check your SD card and your card reader now. Reasons why and tools you find in issue N°2: http://forum.pine64.org/showthread.php?tid=514

5) Get Rufus and burn the OS image (ending on .asc): https://rufus.akeo.ie (Rufus has a verify function also)

6) Insert SD card, provide stable 5V/2A (not that easy since Micro USB has been used, see forum link above) and start the board

7) be aware that if your display isn't connected directly (HDMI) and capable of 1080p you won't be able to notice any activity. You would need either a connected Ethernet cable (then leds on the Ethernet jack start to blink 20 seconds after boot) or a powermeter (showing 300-400mA and peaks up to 700mA while booting)
Yes.

Additionally, after you have, say, longsleeps Xenial image... check to see if you get Ethernet activity, or whether it has obtained an IP address from your dhcp server and then attempt to ssh into it with user:pass ubuntu:ubuntu
A good walkthrough by tkaiser.
But I assume that you want Android on you Pine64 - seeing as you posted in the Android section - and that you are a relatively inexperienced user.
So I suggest this simple way of getting Android running:
1) download Phoenix https://drive.google.com/file/d/0B0cEs0l...U1NFk/view
2) download Android img for Phoenix http://files.pine64.org/os/android/andro...ixCard.zip
3) Open Phoenix and point to the correct drive
4) chose the image you've downlaod and make sure Phoenix is set to burn in 'Startup!
5) Burn

Why I suggest this is because Phoenix shows error messages if the burn fails.
You can read all about burning DD images on the forums if you decide to go that route.

Hope this helps
(05-12-2016, 08:56 AM)Luke Wrote: [ -> ]A good walkthrough by tkaiser.
But I assume that you want Android

Even if he wants Android he should follow the steps outlined above. Since with Android he has NO WAY to check whether his board is DOA or not if he runs into the "no display" problem you should be well aware of!

Using the small Linux image and following exactly every step above he will be able to rule out all known issues that prevent burning an OS image successfully. And by using Linux and connected Ethernet the leds on the Ethernet jack can be used as "not DOA" indicator. That's the only known way to really verify if your board is dead or not (if you forget about the crappy Micro USB connector that can also be the reason why Pine64 never successfully boots --> undervoltage/undercurrent as described in the link above)

Choosing Android for DOA detection is impossible since Andoid will refuse the 1st boot with connected Ethernet. So please stop posting recommendations that are already known to NOT work (same here. Why do you tell people an issue that might be related to underpower can be fixed by a kernel update?!)
(05-12-2016, 09:10 AM)tkaiser Wrote: [ -> ]
(05-12-2016, 08:56 AM)Luke Wrote: [ -> ]A good walkthrough by tkaiser.
But I assume that you want Android

Even if he wants Android he should follow the steps outlined above. Since with Android he has NO WAY to check whether his board is DOA or not if he runs into the "no display" problem you should be well aware of!

Using the small Linux image and following exactly every step above he will be able to rule out all known issues that prevent burning an OS image successfully. And by using Linux and connected Ethernet the leds on the Ethernet jack can be used as "not DOA" indicator. That's the only known way to really verify if your board is dead or not (if you forget about the crappy Micro USB connector that can also be the reason why Pine64 never successfully boots --> undervoltage/undercurrent as described in the link above)

Choosing Android for DOA detection is impossible since Andoid will refuse the 1st boot with connected Ethernet. So please stop posting recommendations that are already known to NOT work (same here. Why do you tell people an issue that might be related to underpower can be fixed by a kernel update?!)

tkaiser, 

Quoting the OP "I am very new to all this so i really need basic tutorial, but even the basic videos i have watched still all direct me to the pine wiki page for download, and none of them work... super frustrated. please help." - based on this I feel it is safe to assume that this isn't a case of a DOA board but rather a case of a lack of know-how to install an OS.
In respect to the other post, I have responded to you there. 
Thank you for our input.