Buy new sdcard, do this:
https://talk.maemo.org/showpost.php?...13&postcount=3
and come then then tell is do you have some problem.
Then I can help you.

Despite my abandonment of the Leste for now I'll post my experience the I can remember. After flashing "The Modem Distro" then going back using "flash_stock" I flashed the latest Leste image to the eMMC without a SIM installed. I upgraded all and immediately went through the process of going devel and building the latest ofono pkg. All went well having figured out the process but when inserting the SIM and reboot, the SIM was never acknowledged and no backend showed up on the dialer. So I thought ****! I hosed my modem firmware with my Modem Distro screwing around so I followed the steps to install the firmware I think I had before (V0708_30.006.30.006) and then repeated the entire process with a fresh install thinking the modem condition even the lack of SIM had an effect on the ofono pkg building. I actually repeated the process 2 or 3 times because once I did a make then install rather than make then make install. Ultimately the SIM was recognized but the ofono backend still wasn't on the dialer. Calling didn't work. I decided to do an /etc/init.d/ofono restart for the hell of it then the stinking phone stopped recognizing the SIM again even after a reboot.

I've had a working PostMarketOS on a microSDHC that I fall back to sometimes and so that's where I went. It was way out of date so I did the big upgrade and it works well. I also set up my WxPython project on it and it works well too unlike on Leste where the screen never clears when the app starts and all the widgets stay on the screen when switching from one tab to another within my multi-tabbed app

So I'm hanging with PMOS for now despite "systemd" and let Leste mature for awhile before trying again

On a side note I had one of those Emergency Broadcast System tests that played on my android phone that had no SIM in it but the EBS test didn't play on the Pinephone that had the SIM in place Hmmm!?.

Yes, you have a newer modem then. The stock flash will do nothing to help you but this will work.
https://themodemdistro.com/efs_recovery

Remember to use root(sudo su) not sudo to do your modem flashing commands.
If you cant get back into flashing mode do a full sutdown without charging cable in and then boot up.

This takes about 10-15 min and you will have fixed the modem and it will always be safe to flash.

This is well documented on https://forum.pine64.org/

The Modem Distro site docs seem to have changed since I last used them. And I'm not convinced that the level of recovery that I performed was necessary because I didn't confirm that the modem wasn't booting, I just ASSumed, but I used the "qfirehose" app including opening up the phone and shorting two connection points while booting. Considering the fact that the phone works fine with PMOS I have to conclude that the phone and modem are in good working order.

I had the situation on a Pinephone Pro from this year where after doing the modemdistro upgrade I was getting up to to a slash through the telephone signal symbol on the GUI; it was still accepting the command to enter flash though.
I was not able to use ADB flashing nor some script flashing tools though because of permissions problems, while sudo ,command. or chmod'ing or chown'ing the script should work making myself root on the phone(mobian) was the only way to get them to run. I just started by creating a root shell, sudo su, and everything worked as advertised even if it didn't at first fix the modem function,
I was getting close to trying the pin-short option, which I dont think wouldhave done anything more than I already had, when I found the solution.
It still took scrolling in the git issues to discover someone linking the dev had a website with everything, even though it is not mentioned in the git anywhere.

To confuse issues further I had previously went through a round of trying to flash new ADSBs and themodemdistro firmware after the PPp arrived then tried flashing back to 'stock' when I had gotten the dysfunction issue, instead of trying toshort pads I left the phone overnight with no battery, and regained functionality when I booted in the morning.