search

ubports / installer-configs

Install configurations for the UBports Installer
https://github.com/ubports/ubports-installer
GNU General Public License v3.0
57 stars 76 forks source link

devices: Config for the Fairphone 4 #198

Closed z3ntu closed 2 years ago

z3ntu commented 2 years ago

Supercedes #193

maciek134 commented 2 years ago

~After flashing it fails to reboot into fastbootd - blank but turned on screen. UT recovery boots fine, but also can't reboot into fastbootd from there. Any idea what might be wrong? Ofc using the latest installer.~

Disregard, just saw the comment added in the latest commit :sweat_smile:

z3ntu commented 2 years ago

@maciek134 Correct, working on fixing this right now :)

z3ntu commented 2 years ago

Recovery is now built with https://github.com/Halium/android_device_halium_halium_arm64/pull/18

It installs fine now (incl. system image stuff in recovery) but doesn't boot up afterwards. Still need to find out what is happening there and debug.

maciek134 commented 2 years ago

Had the same yesterday, try not removing vendor_b and system_b, it booted for me afterwards.

On Tue, Aug 2, 2022, 5:18 PM Luca Weiss @.***> wrote:

Recovery is now built with Halium/android_device_halium_halium_arm64#18 https://github.com/Halium/android_device_halium_halium_arm64/pull/18

It installs fine now (incl. system image stuff in recovery) but doesn't boot up afterwards. Still need to find out what is happening there and debug.

— Reply to this email directly, view it on GitHub https://github.com/ubports/installer-configs/pull/198#issuecomment-1202800861, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIX3RI5GFNDFZ5LR7F7S6DVXE33XANCNFSM55HRW6IQ . You are receiving this because you were mentioned.Message ID: @.***>

z3ntu commented 2 years ago

Seems odm_a partition is actually required, now it works.

Tested now by flashing FP4-FP3W-factory.zip, then flashing with all checkboxes ticked. Device boots up as expected. Then another flashing round over it with no checkboxes ticked and device still boots up as expected.

(and thanks to whoever for approving CI run!)

Three FIXME remaining, will open discussions on them, feedback welcome!

rubencarneiro commented 2 years ago

Can this be merged?

amartinz commented 2 years ago

Can this be merged?

not yet, see Luca's latest comments.

Needs to be moved to cdimage servers at least. I'll open a ticket for that to happen.

ajsalminen commented 2 years ago

Tested but for some reason I'm not able to get a system booting after installation with this. Starting from a freshly flashed factory image and running UBports installer 0.9.6-beta on Windows with every checkbox checked.

Installer finishes, phone comes up with a message "Installing system update" and after that finishes it won't boot just showing the Fairphone powered by android screen).

No difference if I take out the parts deleting vendor_b and system_b from config and redo as @maciek134 suggested.

Flohack74 commented 2 years ago

@z3ntu whats missing here? More testing only? Our sponsor wants a report when this can be published :P

z3ntu commented 2 years ago

@Flohack74 The open discussions should be resolved, so pushing the current images to cdimage (I think you can do this?) and feedback about the unlock thingy. Then it's ready from my side

Flohack74 commented 2 years ago

please send me all binaries you need to be uploaded on telegram :)

ajsalminen commented 2 years ago

As a followup to my testing:

I was now able to get a bootable install with this for unclear reasons. It could have been because I used TWRP to format userdata and skipped doing that with the installer. Wasn't an isolated test so I did some other things in the interim too like flash a different boot.img before running the installer and the installer downloaded the files again so maybe something changed with those...

Anyway, I do suspect it having something to do with the TWRP format. I think there's a chance that there's either an edge case or even something that affects people with a pristine device that only had the stock install on it previously like I did but of course it could have always been some sort of a fluke too.

edit: To be clear what I'm saying is that using TWRP to format helped and that what the installer did failed to work in my case.

mavaa commented 2 years ago

Hello, I had the exact same issue as @ajsalminen on a fresh out of the box FP4 (yes, I'm very eager to test 😅 )

I used the newest beta of ubports-installer (0.9.6_beta-2), and the FP4.yml from the latest commit of this PR. Got the warning about incorrect checksum, which I ignored like a madman, and experienced the exact same thing as @ajsalminen described above. I haven't tried twrp or upgrading the bootloader yet, but I could try some of it in any order if you would like. I'm in no rush to get this working (except I really dislike my current daily driver phone 🙂 )

Flohack74 commented 2 years ago

Guys please stay patient we are fixing this up now, and it will get merged if it works ;)

Flohack74 commented 2 years ago

Ok latest config should work pretty well, who wants to test it?

mavaa commented 2 years ago

I did, and it worked completely without issue! Tested booting, some fiddling around and sending/receiving sms so far.

z3ntu commented 2 years ago

My test also worked fine now, on top of stock install with FP4-FP3W-factory.zip package.

Electron UI crapped itself as always but install still worked ;)

maciek134 commented 2 years ago

Did anyone test stock + latest updates? Just had an idea that we all flash a pretty old version before trying ;p (I can try in a sec)

On Sat, Aug 13, 2022, 11:51 PM Alexander Martinz @.***> wrote:

@.**** approved this pull request.

— Reply to this email directly, view it on GitHub https://github.com/ubports/installer-configs/pull/198#pullrequestreview-1071999484, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIX3ROFAKZL6VPG4NU2ER3VZAKHRANCNFSM55HRW6IQ . You are receiving this because you were mentioned.Message ID: @.***>

z3ntu commented 2 years ago

It seems there's now FP4-FP40-factory.zip available at https://support.fairphone.com/hc/en-us/articles/4405858261777-FP4-Install-Fairphone-OS-offline which is the A.142 build. The latest is one update later with number A.149.

What's probably also worth mentioning is that e.g. if a user flashes the second to latest one from the factory package (which flashes slot A), then does an OTA update to the latest one, they will have the latest one only in slot B. When we flash Ubuntu Touch over it we only use the _a version, which will then still be the previous version.

Long-term I'm aiming for flashing also a fixed vendor image in the installer but some open points still need to be clarified there. Until then I think the current situation is good enough (and I believe very similar to the other devices with A/B slots)

Flohack74 commented 2 years ago

I think this is a Go! We can finetune it later, but lets get stuff done and integrate it.