This is a cross post from Manjaro Forum (by request)

https://forum.manjaro.org/t/wip-pinephon...aned/39655

---

## Be cautious
* The nano-to-micro sim adapter in the package is not a superfluous accessory.
* The sim reader is for micro sim - so if you have a nano sim - you will need it.
* The sim reader is the lower of the two slot - the upper slot is SD-card reader.

The pictograms showing sim/sd-card can be misunderstood - this will short you sim and cause irreparable damage to it. Because the nano sim is smaller than an SD card you will most likely bend the third leg in the reader - with a high probability of causing damage to the PCB and subsequently your SD-card.

So be sure to insert the cards in their appropriate slots.

So by now you will all know that I melted my sim and learned to take apart the pinephone and replace the pcb with a new undamaged counterpart.

## Pinephone boot order
Pinephone boots from USB or SD if present - otherwise the eMMC. Due to the high number of writes rumors are SD-cards don't last very long.

That means you can try out other images without actually flashing your phone

## Testing images
Download the xz compressed image to your computer and unpack the image

    [fh@a116h Downloads]$ ls
    Manjaro-ARM-plasma-mobile-dev-pinephone-201124.img.xz
    [fh@a116h Downloads]$ unxz Manjaro-ARM-plasma-mobile-dev-pinephone-201124.img.xz
    [fh@a116h Downloads]$ ls
    Manjaro-ARM-plasma-mobile-dev-pinephone-201124.img


Then use your favorite image writing tool - mine is **mintstick** - to write the image to the SD-card. You can also use **dd** but you **must** ensure all data is written before removing the card from your computer.

## Using jumpdrive
Depending on the sequence when connect your device - you may experience weird behavior of your network connection.

I have not been able to nail it completely but it seems be act like this

**Connect to computer after loading jumpdrive**
Your system will create a new route leading nowhere because 172.16.42.1 is broadcasted as router but has no internet connection.

**Connecting before loading jumpdriver**
Your network connection works as expected.

## Flashing your pinephone
Flashing from an SD-card is prone to failure. The only viable way is to get the jumpdrive image. Read more at Pine64 wiki by following [this link][1]. Download is found following [this link][2].

System used for this excercise is a cheap yepo laptop

    [fh@a116h ~]$ inxi -Sxxx
    System:
      Host: a116h Kernel: 5.9.11-2-MANJARO x86_64 bits: 64 compiler: gcc
      v: 10.2.0 Desktop: Xfce 4.14.3 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm4
      dm: LightDM 1.30.0 Distro: Manjaro Linux

I have no idea if it was/is my sd-card(s) or a limitation of the jumpdrive but I was only able to make it work using a smaller SD-card than the 8GB cards used to test images.

So if you cannot get jumpdrive to work - use a small card -  64MB is enough - I got a 2GB card to work. Remove the back cover and the battery and insert the jumpdrive in the ***upper*** slot. Attach the battery - and the phone starts - immediately displaying the jumpdrive.

[details="jumpdrive screen"]
[/details]

Attach your device to your computer using the red cable. After a few seconds your system will display two new block devices - it could look like this

[details="jumpdrive devices"]
[/details]


and you can verify using the terminal

    [fh@a116h ~]$ lsblk
    NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 238,5G  0 disk
    ├─sda1  8:1    0  100M  0 part /boot/efi
    └─sda2  8:2    0    16G  0 part /
    sdb    8:16  1  29,1G  0 disk
    ├─sdb1  8:17  1 213,6M  0 part
    └─sdb2  8:18  1  28,9G  0 part
    sdc      8:32  1  1,8G  0 disk
    └─sdc1  8:33  1    49M  0 part

In the example sdb is the eMMC of the device and sdc is the jumpdrive.

Open your image writer application select the unpacked image you want to write and write it to the device eMMC as shown below.


When flashing is done - ensure the data is synced - use the eject button of the file manager.


Remove the cable, battery and jumpdrive. Attach battery and the device starts using the new system.






[1]: https://wiki.pine64.org/wiki/PinePhone#F..._Jumpdrive
[2]: https://github.com/dreemurrs-embedded/Ju.../releases/

I just received the Pinephone today.
It seems like Phosh has no support for Japanese language interface, which was disappointing.
Probably I can opt in for localization, so not a big deal.
If there's no way, make your own way I'd say.

But this is not necessarily the reason to install another OS on it, the main reason is because I just prefer KDE over Gnome.
I flashed the micro SD card like this:

Hello,

I'm selling PinePhone pmOS to anyone based in Japan.
It's in perfect new condition. Only used for a day, been left inside the box ever since because I couldn't find a way to incorporate it into my current workflow. Everything included with the official pmOS box.

I'm selling it for 1,4000円

If you're interested leave a comment below or pm me.

Best regards,
Carl

Hey good people.

Has anyone managed to get networkmanager-l2tp to establish a connection on Manjaro 20.04 for the Pinebook Pro?  On mine, xl2tpd keeps quitting with a signal 15 as soon as it tries to establish a connection, and frustratingly does not provide any details as to why.  I'm not sure if it supports any sort of verbose logging, and I'm still fuzzy as to where networkmanager-l2tp stashes the configs it passes to strongswan and xl2tpd where I might turn such logging on or at least double-check the config.  The connection establishes fine on Debian using the unofficial installer, as well as other clients I've connected previously, so I know my general setup is fine.  I just can't figure out why Manjaro won't connect.

Anyone have any pitfalls they've encountered getting it working, something I might check for?  I really want to give Manjaro a fair shot if at all possible, but not being able to use my home VPN is a bit of an issue.  

I'd love to know what people are doing as far as security tweaks for the pinephone. Not that I need anything like CalyxOS or Graphene type of phone, but I'd like to put a little VPN on it as it can only be used for a pocket linux. I don't have the skill set to really work on the phone like others, but maybe one day I will.

I was looking at the schematic for the Pinecil, and it seems like the way the GPIO pins are broken out through the USB port might be a little strange.  I'm seeing SPI and UART broken out on the SSTX pins.  Is this thing likely to fry a regular USB port should someone absentmindedly try to use one?

UBPorts running on PinePhone and Cosmo, how cool is that?

Attached Files

Thumbnail(s)
   

After today's update

Continued Issues
Settings: date/time issue continues - now you cant change the date/time from Jan 10, 2116 20:34
Lolly Pop:head phone issue continues - still doesnt play through the head phone but through the speakers
Software: continues not to display available software and it was not aware of today's update until sudo pacman -Syyu was ran

New issue
Global issue:The X in an minimized app upper right hand corner is missing and there is no intuitive way close an opened app

New app
Disks: - displays partition info although it report SD 32GB and I dont have one present (Maybe I am reading it wrong)

Image Viewer: First impression is it that is working a little more "smoother"

Still well done and I am looking forward to contribute one day!!

I booted into a microSD-borne Manjaro on my PinebookPro and used Manjaro's `manjaro-arm-flasher` to permanentize that distribution. In that process, however, I chose the wrong image `rock64` rather than `pbpro` and as a result ended up with a PinebookPro that is not even able to boot from the microSD any longer.

In a first attemtp at remediing this situation I have switched off the eMMC on the main bord - now booting from the microSD is possible. The wiki says the eMMC is hot-pluggable, so I hoped when switching it back on when the system is up and running, I could just reflash it and be fine.

BUT: when toggling the eMMC's hardware switch on the running system, the blockdevice does NOT (re)appear accessible for the `manjaro-arm-flasher` utility.
My next step is trying to have journalctl -f running while toggling the eMMC to have a better feedback of what may be going wrong ...

Can anyone help me out with this situation?

Hello,

I'd like to contribute to https://wiki.pine64.org/wiki/PinePhone_APN_Settings (or ask someone to do it if that is not possible). Should I just register or what the process is?

I've contacted @Luke via PM but I think he's too busy or receives too many PMs.

Also I'd like to encourage everyone to do the same as well, we all will benefit from this.