maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Competitors (https://talk.maemo.org/forumdisplay.php?f=4)
-   -   F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch (https://talk.maemo.org/showthread.php?t=101116)

n900user259 2020-11-30 14:11

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
It's here. Ubuntu touch for the Fxtec Pro1: https://devices.ubuntu-touch.io/device/pro1/

n900user259 2020-12-02 09:24

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
So, I'm having a bit of trouble getting ubuntu touch on my phone.
I won't bother you with the entire proces but what it comes down to is that when the flashing is started by the installer the phone prompts the startup screen with a very small message (that starts somewhere offscreen!) to "press any key to shutdown".
I've tried it manually, startup the bootloader and then connect it to USB.
The result is the same. The bootloader is exited and the startup screen is shown with this message.
ADB shows the device is connected.
However when I try adb reboot bootloader the same thing happens.
I've already tried a factory reset but it's still the same.
Has anybody else ever seen a similar problem?

Kabouik 2020-12-02 10:18

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
That's weird, I haven't had such issue. Here's what I did (from the top of my head):

- Download the Appimage installer
- Install fastboot (in the package "android-tools" on my distribution)
- chmod +x the Appimage file, execute it
- In the installer, say yes when prompted for the first time to set udev rules; if not prompted, it's in one of the menus
- Reboot my Pro1 in bootloader mode (Vol Down + Power), plug it to USB
- In the installer, select manually the device I wanted (but automatic detection worked too if I remember correctly, it just took a little bit longer before the device was detected)
- Follow instructions: there are several steps where the installer asks you to reboot in bootloader (already done) and then press a button on the installer to continue, then boot into recovery mode and confirm, something like that

It worked well for me and I did it three times. The only time it didn't was because I had fastboot installed from snap instead of regular package manager, so it was not in my $PATH and udev rules were not set.

Also, I flashed from Sailfish but I recommend you flash from an updated Android reset package instead (the last one is from August 2020, see link in my TWRP guide) because there are some partitions that are not written by the installer and that instead reuse what was written when flashing Android in the first place. It would work still, but some features would be missing depending on how old is the image your flashed into your vendor partition. Normally, it should be enough to just flash vendor.img without reflashing Android (no data loss), this is what I did and I can confirm it fixed the missing features I observed previously. However, I am still having an issue with the fingerprints that looks very similar to one I once had in Sailfish, which suggests again a partition that is not overwritten during the flash and instead reuses what Android flashing procedure wrote in the first place, so maybe there is something else I should flash. That's why, if you're not concerned about data loss, you should avoid these potential issues if you flash Ubuntu onto a recent Android factory package.

Maemish 2020-12-02 10:29

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
Have you informed about these finds?

n900user259 2020-12-02 11:16

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
@Kabouik, Looking at your steps it goes wrong on step 5 when I connect it to USB. I'm on windows by the way. I already flashed Sailfish on it several weeks ago and went back to Android to try out the flashing proces.

Does your bootloader menu show any versions?
Because mine doesn't. It does show the rest. Product_name (msm8998), variant (MSM UFS), serial number, secure boot (no) and device state (unlocked).

Did I mention that the LED is red when connected to USB?

Bundyo 2020-12-02 11:32

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
Make sure you use an USB2 port - USB3 sometimes has problems with flashing. I guess you already have drivers, since you flashed before.

n900user259 2020-12-02 13:15

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
@Bundyo, THANKS!
It was the USB3 port messing with fastboot.

@Kabouik, I want to follow your recommendation in flashing from a more recent Android reset package but looking at your TWRP page it contains 16 files to flash but the .7z archive you linked contains 24.

Also running the fastboot_all.bat is weird.
First the newly added userdata.img failed to flash:
Code:

fastboot flash userdata.img
unknown partition 'userdata.img'
fastboot: error: cannot determine image filename for 'userdata.img'

Second both system.img and vendor.img are commented out:
Code:

rem fastboot flash system_a system.img
rem fastboot flash system_b system.img
rem fastboot flash vendor_a vendor.img
rem fastboot flash vendor_b vendor.img

This is confusing.

netman 2020-12-02 13:19

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
Quote:

Originally Posted by n900user259 (Post 1570360)
First the newly added userdata.img failed to flash:
Code:

fastboot flash userdata.img
unknown partition 'userdata.img'
fastboot: error: cannot determine image filename for 'userdata.img'


The correct command would be
Code:

fastboot flash userdata userdata.img
i think.

n900user259 2020-12-02 13:35

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
Quote:

Originally Posted by netman (Post 1570361)
The correct command would be
Code:

fastboot flash userdata userdata.img
i think.

That would also be my guess.
Also system.img and vendor.img shouldn't commented out because what would be the point?

n900user259 2020-12-02 14:20

Re: F(x)tec announces Pro1 X with Lineage OS and Ubuntu touch
 
I created a post about this on the fxtec community forum.
See: https://community.fxtec.com/topic/24...&comment=54691


All times are GMT. The time now is 15:25.

vBulletin® Version 3.8.8