04-17-2016, 03:28 PM
(This post was last modified: 04-17-2016, 03:31 PM by yourhighpriestess.)
(04-17-2016, 12:37 PM)Ghost Wrote:(04-17-2016, 11:30 AM)yourhighpriestess Wrote:(04-16-2016, 01:19 PM)yourhighpriestess Wrote:(04-15-2016, 05:28 PM)quintonc Wrote: Your experience mirrors my own... I flashed the android image to my SD card with the win32 disk imager method which I have used to great success on several raspberry pis. I tried 2 different micro USB power supplies, a LiPo battery, a PC power supply with an adapter to connect to pin 2 and 6 on the e bus. All to no avail. I was about to give up but after reading dozens of threads I went back to the SD card. Verified my SD card with H2testw which it passed. Re-flashed using the phoenix utility. The flashing failed two times but was successful on the third. At least then I got the Pine64 Logo. Still working on it but I am now at least confident that I can get it to boot.
Try the Phoenix Card burn method...
Used Phoenix to write it and nothing. I'm thinking about Win32 Imager now.
This is new..
When I wrote Android back on it and plugged it in, the screen is black and the power light on the monitor flashes.
can't get it to burn
Is this the same 512GB microSD you mention trying to use in this thread?
I haven't use the 512 yet.. I have like a dozen of these cards. So far I have used my 32 and 16 cards and they are not working well. I doubt best buy would sell me fakes.
(04-17-2016, 02:13 PM)tkaiser Wrote:(04-17-2016, 01:56 PM)MasterHyjinx Wrote: *Shrug - Tosses it into the tech recycling bin*
So you did a lot of things without a real concept mainly because the Pine64 folks refuse to provide a clear quickstart guide how to get the stuff up and running.
Using dd with the 'official' Android/RemixOS images won't work. Using Phoenix Card with Linux images won't also work.
When you see the Pine64 screen when trying to boot an Android or Remix OS image then this means that you successfully burnt the image to TF card using Phoenix Card. When you don't see the floating RemixOS logo after some seconds then this means most probably that Ethernet was connected in this stage. Might this be possible? At least it's a well known problem that is 100% reproducible (and not mentioned by the Pine64 guys). With connected Ethernet both Android and RemixOS will not get past the very first boot stage. You can wait 5 minutes, 10 hours or 2 weeks. It won't work since Ethernet has to be disconnected on 1st boot when trying out any Android bases OS image.
So in case you want to give it a try again...
there's a pine screen?