glodroidcommunity / pine64-pinephonepro Goto Github PK

Issues:

Please ignore the Contact the manufacturer message on the boot. Android shows it because we're using a kernel that Google is not supported officially for Android-13.

Warning. Tow-boot will block any Rockchip native images on the PinePhonePro from booting. Please uninstall towboot before trying GloDroid.

I've been attempting to flash LineageOS for a few hours now with no luck and no real leads so I have opted to open an issue here.

I am attempting to flash LineageOS to EMMC, regardless of the OS or software I use to flash the image to the microSD card the device indicator LED never flashes blue and persistently boots into the stock OS. I ensured I downloaded the latest appropriate release and have attempted everything I can think of to no avail. I have tried multiple cards and I have also ensured that the physical hardware is working and that the disk can be read and written.

I had another regular PinePhone I purchased about a month ago and was able to flash easily, I have followed the official guide as well as the documentation I made for my own use the first time around when flashing this to the previous device. I would like to note that I haven't made any changes to the method or the new device.

I did purchase my device rather recently, so I do not know if Pine64 has perhaps updated something that requires an update on this project in accordance. I really need assistance or some answers as to why I can't seem to flash GloDroid to my new device. I am aware this is likely a hobby project upheld by volunteer work, so while I want some sort of answer or assistance I would like to emphasize that I am making no demands and appreciate everything this project and its contributors are doing.

I am having tremendous trouble flashing GloDroid. I installed rk2aw successfully, but after many attempts and days after trying I was unable to get the image flashed successfully. I did manage to get AOSP flashed, but it had many issues. Upon first boot I was prompted to delete and restore the system data. Doing so led to a successful boot, but the system would always display an ambiguous 'there is a problem with your device' message. This message could be dismissed, but overall performance seemed broken. I managed to flash LineageOS with the same issues as AOSP, but the OS would crash and reboot when the same system message at boot appeared.

I have now attempted flashing with Tow-Boot. I have not managed to get either image flashed, but I am having the same problem I had with rk2aw and is the reason for opening this issue:

If I have a freshly flashed microSD to deploy eMMC, I can easily enter the bootloader mode prior to running the flash-emmc.sh script by holding the RE button before powering the board. However, after the first part of the script completes, I am unable to re-enter bootloader mode again. Holding the RE button and power button causes nothing to happen.

I am unable to enter the second phase of the flashing script, how do I accomplish this?

*I will note that when I managed to flash images under rk2aw, I had to hold Vol Up + Power for the second part of the script, however, the indicator LED was not solid blue but blue & green. I am wondering if this had something to do with the images not working correctly but it was the only way I could fins to proceed in the imaging process for rk2aw.

Though this may be a long ways away as far as the project is concerned adding support for this modem firmware on pinephone and pinephone pro would allow for an easier time debugging certain issues and hopefully an easier time getting mobile data functionality stable.

This is the firmware in question https://github.com/the-modem-distro/pinephone_modem_sdk

As I know, it is currently not possible to boot GloDroid using Tow-Boot..
Why could that be the case? What could be potential hurdles? How could successful boot be achieved?

Thanks for providing a Pinehone Pro and builds of Glodroid!

I have installed GloDroid (AOSP) on my PinePhone Pro. When booting, I am greeted with the following popup:

Android System
There's an internal problem with your device.
Contact your manufacturer for details.

On LineageOS, tapping OK or waiting for it to dismiss it's self causes a crash and reboot cycle. I can safely dismiss this on AOSP, but I am wondering what is causing it and if I can get rid of it?

After update the latest code, I failed to boot into the revovery fastboot mode.

Below is the boot log, hope if you can give some advice.

https://pastebin.com/0yVauNL9

Thanks for your nice job。
I have a rk3399 based board eaidk610，which have a AP6255 wifi + bt module on board，I think it is the same with pinephone pro。
I porting the device configuration from this pine64-pinephonepro project[0]：
But wifi startup failed due to load firmware failed:
[ 5.894232] brcmfmac: brcmf_attach Enter
[ 5.894597] brcmfmac: brcmf_fwvid_attach_ops mod=wcc: enter: dev mmc0:0001:1
[ 5.894849] brcmfmac: brcmf_sdio_readshared sdpcm_shared address 0x00201F18
[ 5.895256] brcmfmac: brcmf_fwvid_request_module: mod=wcc: failed -2
[ 5.896418] brcmfmac: brcmf_sdio_isr Enter
[ 5.896434] ieee80211 phy0: brcmf_attach: brcmf_fwvid_attach failed

The full kernel bootlog is here[1]:
When search online, I find these discuss[2]:

It seems I should change the brcmfmac wifi driver module load order make brcmfmac-wcc insmod before brcmfmac, But I can't find
a proper way to adjust the order.
I also try to setting CONFIG_MODPROBE_PATH="/system/bin/modprobe" , but it also has no luck.
Hope to get some advice from you.

Thanks a lot.

[0]andyshrk@0224c53
[1]https://pastebin.com/H9YDcJNT
[2]https://lore.kernel.org/linux-wireless/CANnVG6=a3etRagG+RaSEH-b4_nfzxpEKffQtuMWrttrbgjunZQ@mail.gmail.com/