ducksoup

If I'm not confused in my own use of terminology, the "dead android" screen reached with volume down+power is recovery. From there, volume up+power will produce a menu, and fastboot can be selected from there. But please do correct me if I'm wrong. Edit: You've added the image. That's not the screen you get on the Pro1-X (release version at least) with volume down+power. Volume down+power (on mine at least) produces this screen: Anyway, not really relevant to this thread. We'll be happy if Spargeltim gets anything at all!

My phone arrived with around 70% battery. It's bad for lithium batteries to leave them empty, so it's very unlikely yours shipped with a dead battery. I know you said you've tried all the buttons, but just to clarify, the power button is on the right side, in between the volume rocker and the fingerprint sensor. Normally you should not need to hold the power button down for very long before you feel a vibration and the screen comes on with the "powered by android" splash. However, under some circumstances, usually related to getting the machine into odd states during flashing proce

Looks good to me, from what I understand on the subject.

Has anyone got the Jolla Mail app working? When I try to set it up, either my own mail server or the one at my ISP, it always times out checking credentials. tcpdump shows no traffic generated on any interface.

Excellent. Thanks. Windows? What's that? 😂

Indeed. While this specific topic isn't something I know a whole lot about, I have seen persist-wiping incidents with other devices, and they've always been recoverable, but have sometimes required some help from the manufacturer.

Agreed, although to be fair, when they posted the factory ROM file, they did specifically say "instructions not ready yet".

Honestly I'm not the right person to do that. I'm very much "learning as I go" here myself. It's a good idea to have such a thread, but I kind of wouldn't know where to start. 😄

Which EDL tool are you using with this phone?

See this post, unfortunately probably too late. Hopefully someone else knows how to fix that problem without a persist backup.

And you still have that option. I also want something other than "full Google" on my device, but I do understand the decision to go ahead and ship rather than shelve their own completed hardware and wait for the software to catch up. I do agree with you that they should update the website so that it isn't promising unavailable software. The headline video on the website in fact is chock-a-block with praise about how great the LineageOS experience will be. Someday! 🙃

boot_a vs boot_b is the easy part. The hard part is creating two separate userdatas, and is alas somewhat more complicated than a mere "set_active". I'm looking forward to multiboot as well. I'd like to use Sailfish as my almost-fulltime OS, with the ability to boot into Android for occasional must-have Android-only apps (e.g. banking).

I certainly didn't do anything that would have changed the system partition, and if I'm not mistaken, system, boot_a, and userdata are the only real parts in play here, and the latter two are overwritten in the Sailfish flashing process. It's curious indeed. Right now I don't really want to undo the work I've put into Sailfish, but it will be interesting to see if anyone else runs into a similar problem. Maybe it's just me, and the warning added to the first post is unnecessary.

Interesting that that worked for you. I have just tested that exact boot.img on my own device and it does not boot. Flashing back the image from last week and I'm back to booting just fine. What is your hardware configuration? I am 8/256 (and the device is black FWIW).

So far this is working pretty well, but I may have run into my first example of "not quite ready for primetime". I'm trying to set up my personal VPN (OpenVPN) and while I can get it to connect just fine if I execute the openvpn client myself from a root shell, it will not connect via the (not especially helpful) UI. journalctl reveals two errors possibly related: Aug 11 11:37:09 Pro1-X connman-vpnd[548]: error setting gid -1 Invalid argument Aug 11 11:37:09 Pro1-X connman-vpnd[548]: error setting gid list Invalid argument This is perhaps beyond the scope of this thread, but just

I don't, and at the moment I'm playing around with Sailfish, so I can't go looking. It should certainly light up, even in default configuration, when you plug in a USB cable to charge.

But is it blue? 😁 By "notification diode", do you mean the general notification LED on the front of the device? There is one, RGB, upper right corner.

Oh of course. My post was intended to be a "helpful hint", not a "waah this doesn't work". 😆

I spent some time today playing with this, and for the longest time was unable to get either Ubuntu Touch or Sailfish OS to boot. Eventually I decided to try out older builds of Ubuntu Touch and discovered that no boot.img newer than the one found in #2807435728 seems to work. After reverting to the boot.img found in that build, both Ubuntu Touch and Sailfish OS boot fine.

I spent some time today playing with this (with the ultimate goal of getting Sailfish OS running), and for the longest time was unable to get either Ubuntu Touch or Sailfish OS to boot. Eventually I decided to try out older builds of Ubuntu Touch and discovered that no boot.img newer than the one found in #2807435728 seems to work. After reverting to the boot.img found in that build, both Ubuntu Touch and Sailfish OS boot fine.

Oh thanks much for that. I admit I had just assumed, based on the design of my current OnePlus cover, that that wasn't an option for the Pro1. Shame on me for not searching the forum first! (I shamefully admit to having completely missed the Pro1 and not discovering F(x)tec until the Pro1-X, so I've got a lot to learn!)

It was a website order, and I ordered blue (IIRC that was the only colour offered). I think I would have preferred blue (every other smartphone I've ever owned has been black, so some variety would be nice!), but it's a mild enough preference that I don't mind.

Pro1-X has arrived in Finland, one day late, but I'll take it. It is definitely not blue, but it is 8/256, and I never had a strong feeling about the colour, so this is fine. I should add that first impressions are very good. The hardware feels excellent, very good build quality. Great screen. I have not tested any connectivity yet. The hinge mechanism feels excellent. Only disappointment is lack of screen protector, as mentioned by others. There is neither a preapplied protector nor an included separate one. I have in the past kept my phone in a flip cover, which obviates

Can't speak for wherever you are, but here in Finland they are very clear about that: "In the case of customs declarations for release for free circulation, the conversion rates applied are those valid on the date when Customs accepts the customs declaration for the goods." So at least here, no, you can't get around that unfortunately.

I self-declared 741€, the amount I paid F(x)tec, ergo 177,84€ VAT.