I know this will work with USA customers, other countries may have similar systems but i'm not sure.

Sign up for a MyUSPS here. If you get past the long (but thorough) signup process, you should be able to get text or email alerts for any package coming to your address, no tracking number required. This way, you won't have to rely on Backerkit or the overloaded Pine64 team to give you your tracking number, you can just get a notification straight from the mail carrier.

I've signed up, and i've got it showing a couple eBay orders i have coming in, but no Pine shipment (yet!) Hope this helps someone. You may see that your Pine is already on its way!

The order of the reasons is not intentional, it's just the order things come to my mind based on Forum posts:

1. The official Android and RemixOS images can't be burned the usual way to an SD card (dd, Rufus, WinDiskimager) but need Phoenix Card instead (Windows only and causing all sorts of troubles for users that do not use this strange operating system). Burning an Android image the wrong way will result in the Pine64 waiting endlessly while showing already a red led lighting. PhoenixCard images can only be burned with the PhoenixCard software. DD images can be burned using the dd command (Linux/Mac) Rufus, Win32DiskImager (Windows), Etcher, ApplePi Baker (Mac). Attempting to burn a DD image in PhoenixCard will result in a 'script not found' error. Likewise attempting to burn a PhoenixCard image with one of the above-named DD processes/applications will not work either.
   
2. Data written to SD card got corrupted either because you unfortunately bought a counterfeit SD card or the card is faulty. Another common problem are SD card readers that start to overheat when used with a fast card and corrupt data 'on the fly'. Checking for both problems is simple: Never use any flash based media without verifying it before.
   
3. Insufficient power supply: unfortunately Pine64 uses Micro USB for DC-IN, many USB cables have a resistance way to high (leading to severe voltage drops) and this combined with crappy PSUs (the old phone charger you found in the drawer) will lead to the Pine64 crashing in early boot stage
   
4. HDMI issues: You connected a screen but Pine64 and display disagree about settings (no idea whether EDID is implemented in Allwinner's 3.10.x Android kernel that is currently also used for all available Linux images)
   
5. The Pine64 boots fine but you don't notice still staring at the red led indicating 'error'
   
6. You use either the RemixOS or an Android image and have Ethernet connected at first boot. This will prevent the board from doing so, so please consider disconnecting Ethernet after burning an Android/RemixOS image and only connect it back when you already see the desktop.
   

• pre-production samples were equipped with a green led, the production batch replaced this with a red led. So red doesn't indicate failure but 'power available' instead. Unfortunately you get no other feedback whether the Pine64 actually boots or not. The red led will light even if the A64 waits patiently for a bootable OS available on a SD card an hour or endlessly.
  
• combining 'smart USB chargers' with devices that are 'dumb' on the other end of the cable might not work: If you use a 'charging hub' to power your Pine64 then chances are pretty high that the charger only provides 500mA (max. current defined by USB2.0 specs) which might be not enough to allow the Pine64 to boot (5.1V/2A!). Most 'smart chargers' will only provide more than 500mA if the device in question implements any of the USB power specifications (Pine64 implements none of them since it's just DC-IN)
  
• 2GB boards suffer from crashing or rebooting loops when Ethernet is connected since there's a integer overflow present in older kernel variants. Fixed by longsleep in early April, so Linux images can be updated using the instructions from "Linux Development" forum an a new RemixOS release should fix this also.
  

Howdy all, 

I just got my Pine A64+ in the mail yesterday and I've been looking around for instructions on how to burn an SD image so that I can boot it.

With other boards (Raspberry Pi, Beaglebone Black, etc.) I'm able to use something like:

So has anyone had any success with getting a 2Gb pine to boot and/or work with the onboard Ethernet either used or not? If so which of the OS's?

any one porting Linuxium to the board ?

Linuxium it is Bootloader software to dualboot Android and Linux

Michael Larson has come out a series of video on the PineA64 Development Board and posted at https://www.youtube.com/playlist?list=PL...fy_I6b5UJW   

The link is also posted on our wiki site under Other Resources in the Net  Section. Feel free to check it out.

Thanks Michael.

I successfully installed Android on my Pine64 (2gb) with a 32gb Sd card. My usb wifi module doesn't seem to be recognized, so i tried using the ethernet port with no luck i know my Computer is setup properly to share internet (Raspi) i just can't seem to get it going, any suggestions?

I just bought a  Samsung UHS-l microSDHC 16GB card.Will  the card work with the Pine64 2GB board?

I can't get past the boot screen (the one that says PINE A64).  I've tried reflashing the SD card from Phoenix with both Android and Remix OS several times, and have waited 30+ minutes; but it does not seem to want to boot.  A LED close to the power supply turns red.  I'm using a power supply that is rated for 2A and a regular USB cord.  I don't have any peripherals connected to the Pine.  Both the power supply and cord work fine with one of my Raspberry Pis.

I have the tricked-out version, the A+ with 2 GB of RAM.

Any ideas on what's going on?

Received my Pine64+ today. Been playing with it for 3hrs now.  All I get is a black screen, tried it on a monitor with HDMI-DVI and a TV. Nothing

Have tried 3 versions of the Android Lollipop and remix os. Been using a class 10 SD card and power cable from my Ras PI. Get the red light, but nothing else..

Think I should have gone with the PI 3, I'm sure I noticed my network cable light flickering earlier but then nothing..

Have left it for 10mins even 30 mins after a clean install..

Any other ideas guys..

BALLLS