PINE64

(06-09-2016, 10:37 AM)pcfr33k Wrote: [ -> ]

(06-08-2016, 01:05 AM)Ghost Wrote: [ -> ]RemixOS for Win32DiskImager (32GB):
http://files.pine64.org/os/remix/remix-v...4-32GB.zip

Android for Win32DiskImager (32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (LCD Touchscreen version, 32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager: (LCD Touchscreen version, 32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

I just don't know why but the RemixOS is not booting and the processor gets too HOT!! If I left it in that state I bet it would burn!!

The only ones that boot so far is  Debian Linux Jessie that is it!!

Something must be happening to the bootloader  or kernel during the burn process to my Scandisk Extreme Pro 32Gb.  That MicroSD works perfectly on all my other devices, Raspberry Pi 3, Pi2, DragonBoard and LinkSPrite PCDuino. I also checked the SD card with the H2testw no problems.

Has anyone tested these 32Gb releases burning with WinDiskManager and to see if Pin64 2GB version boots?  Why would the processor continue to get warmer and even hot when its not booting up correctly?

pcfr33k -   I may have missed it, but have you tried the dedicated PhoenixCard Image burned via PhoenixCard?

Got the 64gb RemixOS image to boot but it crashes with a black screen when applications are opened and im forced to restart.

It's not a power issue as I've checked, it must be an IMG issue... my SD card is legit, but i'm still unable to actually DO anything with my board.

Will the phoenix card images work on a 64gb sd?


______________________________________

Note: The android 64gb version hangs at the pine a64 logo after giving me the verifying apps /2 screen

(06-16-2016, 07:52 AM)BeerSnob Wrote: [ -> ]

(06-09-2016, 10:37 AM)pcfr33k Wrote: [ -> ]

(06-08-2016, 01:05 AM)Ghost Wrote: [ -> ]RemixOS for Win32DiskImager (32GB):
http://files.pine64.org/os/remix/remix-v...4-32GB.zip

Android for Win32DiskImager (32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager (LCD Touchscreen version, 32GB):
http://files.pine64.org/os/android/andro...4-32GB.zip

Android for Win32DiskImager: (LCD Touchscreen version, 32GB, ROOTED):
http://files.pine64.org/os/android/andro...4-32GB.zip

I just don't know why but the RemixOS is not booting and the processor gets too HOT!! If I left it in that state I bet it would burn!!

The only ones that boot so far is  Debian Linux Jessie that is it!!

Something must be happening to the bootloader  or kernel during the burn process to my Scandisk Extreme Pro 32Gb.  That MicroSD works perfectly on all my other devices, Raspberry Pi 3, Pi2, DragonBoard and LinkSPrite PCDuino. I also checked the SD card with the H2testw no problems.

Has anyone tested these 32Gb releases burning with WinDiskManager and to see if Pin64 2GB version boots?  Why would the processor continue to get warmer and even hot when its not booting up correctly?

pcfr33k -   I may have missed it, but have you tried the dedicated PhoenixCard Image burned via PhoenixCard?

Yes,

I have tried Phoenix Card, Win32DiskImager and the dd command in OSX terminal.  Not one single image boots and the CPU gets extremely hot when I continue to wait.  The only one that boots is Debian Jessie. Luke told me after trying many other things such as power supplies etc that it could be a bad CPU or something else hardware wise is bad.  Debian Jessie only runs at half the CPU speed so maybe that is why that image boots, while all the other images require the full CPU speed.  At this point it no longer matters, they are sending me a pine64 2gb plus version replacement

I have tried everything but can't get anything either on external hdmi display or on the 7" touchscreen. I have a solid red light but nothing happens. Can you advise please? I have tried everything in this post without success.

1) which OS are you trying ?
2) how did you make the SD card ?
3) what do you have attached to the board when you try to boot ?
4) have you tried using a serial debug cable (ttl console) to watch the boot process ?
5) have you tried booting it into your network (eth0) (get the ip addy from your router) and then SSH into the board?

marcus

(07-05-2016, 05:54 PM)manthis Wrote: [ -> ]I have tried everything but can't get anything either on external hdmi display or on the 7" touchscreen. I have a solid red light but nothing happens. Can you advise please? I have tried everything in this post without success.

Firstly, respond to Marcus' questions (my guess is something went wrong with burning the img). Secondly, this is one of those instances where it may be better to take it up in the chat (see my sig) so we can help you troubleshoot.

(03-31-2016, 10:03 AM)Andrew2 Wrote: [ -> ]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.
   

Did this used to be true, and is no longer? 

Or was it never true? Since I first got my Pine, I've been using Win32DiskImager (once, I used Rufus), with the wiki images, and I've had nary a problem.

In any case, it ought to be edited to correct the error.

(07-06-2016, 10:44 AM)NexusDude Wrote: [ -> ]

(03-31-2016, 10:03 AM)Andrew2 Wrote: [ -> ]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.
   

Did this used to be true, and is no longer? 

Or was it never true? Since I first got my Pine, I've been using Win32DiskImager (once, I used Rufus), with the wiki images, and I've had nary a problem.

In any case, it ought to be edited to correct the error.

Initially there were no 'DD' images for Android and RemixOS, but they were added pretty soon, so yes, that statement is no longer true.

(07-05-2016, 05:54 PM)manthis Wrote: [ -> ]I have tried everything but can't get anything either on external hdmi display or on the 7" touchscreen. I have a solid red light but nothing happens. Can you advise please? I have tried everything in this post without success.

I'm getting this very same issue, and to answer those additional questions:

1) which OS are you trying ?
I've tried creating bootable SD cards with ALL of the OS options. None work. Multiple SD cards used (from the Pine64 issued one, to Lexar, Sandisk, and others)


2) how did you make the SD card ?
Tried multiple ways, with all the tools suggested

3) what do you have attached to the board when you try to boot ?
Tried both HDMI connection and Touchscreen. Ethernet is NOT plugged in, no external USB devices attached. Tried with the wifi/bluetooth attached and removed as well.

4) have you tried using a serial debug cable (ttl console) to watch the boot process ?
Not yet

5) have you tried booting it into your network (eth0) (get the ip addy from your router) and then SSH into the board?
Not yet

Any thoughts on next steps, aside from 4) and 5)? I'm getting the normal powered red LED, and the processor is heating up, with no activity onscreen. Thanks for any help folks.

Loading a linux image and seeing if you can ssh into the board (suggestion 5, above) would tell you a lot, especially considering display issues are a common start-up issue that users battle. That would definitely be the next step I'd take.