PINE64
The 6 most common reasons why Pine64 won't boot - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: General (https://forum.pine64.org/forumdisplay.php?fid=1)
+--- Forum: Getting Started (https://forum.pine64.org/forumdisplay.php?fid=21)
+--- Thread: The 6 most common reasons why Pine64 won't boot (/showthread.php?tid=514)

Pages: 1 2 3 4 5 6 7 8 9 10 11

RE: The 5 most common reasons why Pine64 won't boot - Ghost - 05-27-2016

(05-27-2016, 12:00 AM)eddyp Wrote:
(03-31-2016, 11:15 AM)Andrew2 Wrote: I explained the reason several times in the forums why Android images 'need' Phoenix card (the data partition somewhere inside will be resized to the medium's maximum capacity) and also how the Pine64 folks could deal with: prepare a bunch of dd-able Android images with fixed sizes: 7.5, 15.5, 31.5 and 63.5 GB. Or by expanding the partition on first boot -- that's easy with Linux but maybe not with Android. No idea since I'm not interested in Android at all Smile

It sounds like depending on a Windows host could be easily eliminated. It shouldn't be hard enough to make a shell script that could do the writing of the small image then increase the FS to the needed capacity (or simply make the FS big from the start and loopback mount the partition from the image and rsync the contents from the image to the big FS).

I see you said you're not interested in this, but hasn't anybody tried this yet?


On a related topic, is the format of the Pine64 compatible images documented somewhere? I am thinking of trying other OSes than Linux or Android, so this information would be crucial to be able to do this.

Fixed-sized dd-able Android images are already available via the Pine64 wiki.

RE: The 6 most common reasons why Pine64 won't boot - pcfr33k - 06-06-2016

Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

RE: The 6 most common reasons why Pine64 won't boot - Luke - 06-07-2016

(06-06-2016, 10:45 PM)pcfr33k Wrote: Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

1) Burn a linux image 
2) disconnect everything except for ethernet // power the Pine on
3) watch for LED activity on ethernet ports / see if the red power LED stays solid 
4) see if you can ssh into the Pine 

You can always swing by the chat - someone will help you troubleshoot.

RE: The 6 most common reasons why Pine64 won't boot - pcfr33k - 06-07-2016

(06-07-2016, 04:24 AM)Luke Wrote:
(06-06-2016, 10:45 PM)pcfr33k Wrote: Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

1) Burn a linux image 
2) disconnect everything except for ethernet // power the Pine on
3) watch for LED activity on ethernet ports / see if the red power LED stays solid 
4) see if you can ssh into the Pine 

You can always swing by the chat - someone will help you troubleshoot.


Got it to work with a linux image burned on Windows 10 Pro using Win32DiskManager.  That needs to go on Wiki BTW.  Some people may not want to burn a Linux image in Linux!!

Now we need to know why RemixOS and Android 5.1.1 burned in Phoenix will not work.  Can I use Win32DIskManager to burn those images as well?

Thanks

RE: The 6 most common reasons why Pine64 won't boot - Ghost - 06-07-2016

(06-07-2016, 09:18 AM)pcfr33k Wrote:
(06-07-2016, 04:24 AM)Luke Wrote:
(06-06-2016, 10:45 PM)pcfr33k Wrote: Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

1) Burn a linux image 
2) disconnect everything except for ethernet // power the Pine on
3) watch for LED activity on ethernet ports / see if the red power LED stays solid 
4) see if you can ssh into the Pine 

You can always swing by the chat - someone will help you troubleshoot.


Got it to work with a linux image burned on Windows 10 Pro using Win32DiskManager.  That needs to go on Wiki BTW.  Some people may not want to burn a Linux image in Linux!!

Now we need to know why RemixOS and Android 5.1.1 burned in Phoenix will not work.  Can I use Win32DIskManager to burn those images as well?

Thanks

On the Pine64 Software Release part of the wiki, DD images are for Win32DiskImager and there are also images labelled as being for PhoenixCard.

RemixOS for PhoenixCard:
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-phoenixCard.zip

RemixOS for Win32DiskImager (8GB image):
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-8GB.zip

Android for PhoenixCard:
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-phoenixCard.zip

Android for Win32DiskImager (8GB image):
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-8GB.zip

RE: The 6 most common reasons why Pine64 won't boot - pcfr33k - 06-07-2016

(06-07-2016, 09:23 AM)Ghost Wrote:
(06-07-2016, 09:18 AM)pcfr33k Wrote:
(06-07-2016, 04:24 AM)Luke Wrote:
(06-06-2016, 10:45 PM)pcfr33k Wrote: Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

1) Burn a linux image 
2) disconnect everything except for ethernet // power the Pine on
3) watch for LED activity on ethernet ports / see if the red power LED stays solid 
4) see if you can ssh into the Pine 

You can always swing by the chat - someone will help you troubleshoot.


Got it to work with a linux image burned on Windows 10 Pro using Win32DiskManager.  That needs to go on Wiki BTW.  Some people may not want to burn a Linux image in Linux!!

Now we need to know why RemixOS and Android 5.1.1 burned in Phoenix will not work.  Can I use Win32DIskManager to burn those images as well?

Thanks

On the Pine64 Software Release part of the wiki, DD images are for Win32DiskImager and there are also images labelled as being for PhoenixCard.

RemixOS for PhoenixCard:
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-phoenixCard.zip

RemixOS for Win32DiskImager (8GB image):
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-8GB.zip

Android for PhoenixCard:
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-phoenixCard.zip

Android for Win32DiskImager (8GB image):
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-8GB.zip


Thanks.  I have the 32gb card so will any of those links work?  They all say 8gb?
My mistake I see 8 to 64gb in the links sorry about that.

RE: The 6 most common reasons why Pine64 won't boot - aegrotatio - 06-07-2016

My PINE64 boots fine but outputs a video signal on the HDMI port that won't let DVI and DisplayPort monitors work. I can ssh to it and it works fine, just no video.

I do not want to go out and buy a cheap HDMI television just to use my PINE64, but I'm certain there is a kernel setting that needs to change.

All the other Allwinner boards work fine with HDMI-to-DVI cables after changing a few settings.

Now that everyone is finally receiving their boards we'll get more and more reports of nonworking video which will force a solution.

RE: The 6 most common reasons why Pine64 won't boot - pcfr33k - 06-08-2016

(06-07-2016, 08:24 PM)pcfr33k Wrote:
(06-07-2016, 09:23 AM)Ghost Wrote:
(06-07-2016, 09:18 AM)pcfr33k Wrote:
(06-07-2016, 04:24 AM)Luke Wrote:
(06-06-2016, 10:45 PM)pcfr33k Wrote: Tried different images, none boot.  Windows 10 Pro using Phoenix Card 3.1.0.  I chose startup option on the Phoenix Card software.  Allwinner processor starts to get hot and I have to remove power.   Is my board defective?  I just received it a couple days ago.  A64-DB -2G -Rev B dated 2106-03-21.

I am using HDMI so I burned the HDMI Android 5.1.1 release.  Also tried Remix OS same issue won't boot.

1) Burn a linux image 
2) disconnect everything except for ethernet // power the Pine on
3) watch for LED activity on ethernet ports / see if the red power LED stays solid 
4) see if you can ssh into the Pine 

You can always swing by the chat - someone will help you troubleshoot.


Got it to work with a linux image burned on Windows 10 Pro using Win32DiskManager.  That needs to go on Wiki BTW.  Some people may not want to burn a Linux image in Linux!!

Now we need to know why RemixOS and Android 5.1.1 burned in Phoenix will not work.  Can I use Win32DIskManager to burn those images as well?

Thanks

On the Pine64 Software Release part of the wiki, DD images are for Win32DiskImager and there are also images labelled as being for PhoenixCard.

RemixOS for PhoenixCard:
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-phoenixCard.zip

RemixOS for Win32DiskImager (8GB image):
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-8GB.zip

Android for PhoenixCard:
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-phoenixCard.zip

Android for Win32DiskImager (8GB image):
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-8GB.zip


Thanks.  I have the 32gb card so will any of those links work?  They all say 8gb?
My mistake I see 8 to 64gb in the links sorry about that.

Nope none work with 32Gb card.  Only ones that work are linux since they work on a range of the size of the card.  The links you listed are for the 8gb sdcard.  Do you have images of all those links for the 32gb card to burn with Win32DiskManager?

RE: The 6 most common reasons why Pine64 won't boot - Ghost - 06-08-2016

RemixOS for Win32DiskImager (32GB):
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-32GB.zip

Android for Win32DiskImager (32GB):
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-32GB.zip

Android for Win32DiskImager (32GB, ROOTED):
http://files.pine64.org/os/android/android-rooted-ver5.1.1-20160505-pine64-32GB.zip

Android for Win32DiskImager (LCD Touchscreen version, 32GB):
http://files.pine64.org/os/android/android-ver5.1.1-lcd-version-20160603-pine64-32GB.zip

Android for Win32DiskImager: (LCD Touchscreen version, 32GB, ROOTED):
http://files.pine64.org/os/android/android-rooted-ver5.1.1-lcd-version-20160603-pine64-32GB.zip

RE: The 6 most common reasons why Pine64 won't boot - pcfr33k - 06-09-2016

(06-08-2016, 01:05 AM)Ghost Wrote: RemixOS for Win32DiskImager (32GB):
http://files.pine64.org/os/remix/remix-v2.0-20160415-pine64-32GB.zip

Android for Win32DiskImager (32GB):
http://files.pine64.org/os/android/android-ver5.1.1-20160505-pine64-32GB.zip

Android for Win32DiskImager (32GB, ROOTED):
http://files.pine64.org/os/android/android-rooted-ver5.1.1-20160505-pine64-32GB.zip

Android for Win32DiskImager (LCD Touchscreen version, 32GB):
http://files.pine64.org/os/android/android-ver5.1.1-lcd-version-20160603-pine64-32GB.zip

Android for Win32DiskImager: (LCD Touchscreen version, 32GB, ROOTED):
http://files.pine64.org/os/android/android-rooted-ver5.1.1-lcd-version-20160603-pine64-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?