Here is a DD image for Remix OS for now.

1. You will need to have a MicroSD card at least 8GB 
2. If you have a larger MicroSD you will need to extend Partition 1 to the rest of your drive size.

If you have any questions let me know. You should be fine to use Win32.
Please let me know if this image fixes the restarting issue I know a lot of you are having. Thanks!

https://drive.google.com/open?id=0BwrRh3...UN2VndCVTQ

Let me first say that I have over 40 years of computer and electronics experience and have worked on many different sizes and types of systems.  I own a number of one-board systems including several other ARM-based projects that I backed on KS. In each case I was able to easily verify within hours of delivery that I had received a working board.

I just received my 2 gig Pine64+ and I'm having the same challenge as other new Pine64 recipients here - I've burned RemixOS to a 16gb Class 10 card using the PhoenixCard tool as shown in the video.  I connect HDMI and Ethernet, insert the MicroSD card, making sure it clicks all the way in, and then plug in my power connection to the MicroUSB connector.  The power light goes on but nothing else happens, even if I leave the board alone for more than 30 minutes.  I am seeing the activity lights on the Ethernet jack flicker, further confirming that the board has power, but absolutely nothing else happens.

1. Is there something else we have to do to force the board to start up and boot?
2. How long is it reasonable to wait before we see some sign of life from the board?
3. Is there any progress indication while the board is performing its initial boot?

It is amazing to me that there is not some sort of OOB write-up or video available for this board, as there has been for every other board I have worked with. If nothing else, this would assure each backer that they had not just bought a brick. I honestly do not believe that the developers of Pine64 have met the minimum standard for releasing a product.  Instead of rushing to get the basic hardware in the mail by the end of March, the right thing to do would have been to delay shipping until a better first experience could be made available. Those of us who have been in the trenches and know how hard it is to bring in a large project on schedule would have understood completely.

I downloaded Android and Linux BSP 1.2 20160113.

How do I build it? Which dev board matches the Pine64?
Are any of those boards an H3 board?

     1. aosp_arm-eng
     2. aosp_arm64-eng
     3. aosp_mips-eng
     4. aosp_mips64-eng
     5. aosp_x86-eng
     6. aosp_x86_64-eng
     7. mini_emulator_arm64-userdebug
     8. mini_emulator_x86_64-userdebug
     9. mini_emulator_mips-userdebug
     10. m_e_arm-userdebug
     11. mini_emulator_x86-userdebug
     12. aosp_flounder-userdebug
     13. aosp_shamu-userdebug
     14. octopus_f1-eng
     15. octopus_f1-user
     16. astar_h7-eng
     17. astar_h7-user
     18. jasmine_perf-eng
     19. jasmine_perf-user
     20. astar_y3-eng
     21. astar_y3-user
     22. octopus_ibt-eng
     23. octopus_ibt-user
     24. octopus_perf-eng
     25. octopus_perf-user
     26. tulip_perf-eng
     27. tulip_perf-user
     28. kylin_p2-eng
     29. kylin_p2-user
     30. octopus_n1-eng
     31. octopus_n1-user
     32. tulip_p1-eng
     33. tulip_p1-user
     34. astar_yh-eng
     35. astar_yh-user
     36. kylin_p1-eng
     37. kylin_p1-user
     38. tulip_t1-eng
     39. tulip_t1-user
     40. aosp_manta-userdebug
     41. aosp_flo-userdebug

I can't seem to get the Phoenix card to burn an image. anyone know where to find a dd image of remix?

I have be able to get lollipop android dd and Arch Linux to work with dd.

I tried to disconnect the mouse and keyboard not nothing is work, I have 2g board and it's only the board.

Got my A64+ 2GB board 2 days ago and so far I'm not that impressed, in fact I actually don't have a usable product right now. My hope with this project was to create a FireTV replacement for our bedroom TV. Right now my FireTV does everything I need it to do. It handles Live TV through the HD Homerun View app and handles all my movies with the Emby app. It also handles all our subscription services like HBO GO, Showtime app and the other various on demand apps. 

I know my hopes were pretty high that a $29 Pine 64 could compete with Amazon's latest offering. But both featured similar quad core CPU's and GPU's, they both offered 2GB onboard memory, both offered gigbit ethernet and both can do 4K & 1080P output. What the heck it's worth a shot. 

Well yesterday I decided to take the plunge and install the Android build first since this would be the obvious intended OS I would be using. Install went fine on my SanDisk Extreme Plus UHS 3 64GB card, inserted it and boom 4 mins later Android was up and running. I played around with the build but it seemed, I don't know, slightly sluggish in appearance and navigation. Button presses seemed slightly delayed and the overall performance seemed sluggish. I though oh well it wasn't that bad, let's try to download some apps and try them out. Fired up Google play and downloaded the HBO GO app. This app did not start off very well, force closed the first 2 times I tried to open it. Once I finally got it open, navigation through this app was painfully slow and glitchy. Once I finally got to a show I wanted to stream I clicked on it and got through the HBO GO splash screen then it hangs for about 15 secs before the stream starts then closes and tells me could not reach the server, please try again later. Ok so I close the program open it back up again and try a different show and episode and same thing, it either tells me "could not play video at this time please try later" or server error.  Strike one. Well, ok so I download the HD Homerun View app, start that up and Video is very choppy and stuttering basically un-watchable, plus navigation through the channel guide was very slow. Strike 2. I was going to try the Emby app but since you have to pay to play videos on every device you install it on I decided to pass and try at a future date. So suffice to say the Android experience was a huge disappointment. 

So today I decided to try the Remix OS build. So I burned that to my Sandisk card and booted it up with only the power and HDMI plugged in for the initial boot. Everything went fine plugged in my mouse and keyboard to complete the sign in, got to the desktop and everything was working. I played around for a few mins with everything then decided to plug the ethernet cable in, 4 secs later it reboots. Ok it gets back to the desktop and I start to explore again then bang reboots again. This time it's just stuck in an endless boot loop all because of the ethernet cable being plugged in. I found a thread that other people were having the same problem with boot loop due to ethernet cable being plugged in. Some were saying it was a Remix OS problem and some were saying it could be a power supply problem but my power supply is a 5V/2A microUSB charger and should work. So I will have to wait until someone clears that up.

So as of right now nothing is really usable for me at the moment. Hopefully the Android and Remix OS builds will get better, I mean I understand most people are just getting their boards so development of the OS builds will take some time and I'm willing to wait it out. Just a little disappointed right now.

Heya, my new pine64 2GB arrived and booted and is stable with Ethernet on Arch Linux (off a powered USB hub). Now I'd just like to get 4K on my el-cheapo Element 4K/30Hz setup.

I've been using OS X and BSD a lot more recently so I'm not as familiar with Linux anymore. I looked for a xorg.conf and didn't find one.

Xdpyinfo is reporting a max resolution of 1920x1080. I will poke around more.

I've flashed and hacked so many roms and images over the years but for the life of me I can't get anything to boot....

I get Allwinner 64 Bit boot screen on one img.  The other img I used that was 7gb just boots to a command prompt. 

alarm:
I type in alarm user and alarm boot and nothing. Used root/root, guest/guess. It just comes back to the next line.

I have yet to see a boot to an OS of any kind.... I really want to use these pine64 for an event coming up in June but it doesnt look good.

Not one of these will boot on my pine64 1GB:

sun50iw1p1_android_db_uart0_1000M_0112
sun50iw1p1_android_db1000_uart0_0216
sun50iw1p1_android_r18_uart0_1210
arch-pine64-bspkernel-20160308-1
android_20160112

Can anyone point me in the direction of how to get 32 bit ARM packages running on Arch Linux aarch64?

My understanding is that armv8 (or aarch64) is backwards compatible, but I have no idea how to enable this.

The software I am trying to run is btsync.

It seems possible on Debian, http://forum.odroid.com/viewtopic.php?f=135&t=18806.  In that forum post, all that was needed was libc6 for armhf.  But specifying the desired alternate architecture in Arch linux does not seem to work when trying to install libc6 with either pacman or yaourt:

$ file btsync
btsync: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=c586701ab44d098336c08f952ac7cdf27373a1be, stripped

Which indicates that ld-linux.so.3 is required (which as I understand is in libc6 package on Debian)

But if I try to install libc6 on Arch:

$ yaourt -S --arch arm libc6
error: target not found: libc6

After investigating further, it seems libc6 is actually called glibc in Arch Linux - but I still cannot figure out how to install it for ARM and not aarch64:

$ pacman -S --arch arm glibc
warning: glibc-2.23-1 is up to date -- reinstalling
error: failed to prepare transaction (package architecture is not valid)
:: package glibc-2.23-1-aarch64 does not have a valid architecture

Does it come with a power switch because I see pictures of them being included and others are not?