Bug two sim cards only one is working perfect

UniSuperBox

I edited your posts to place the command output into code blocks. You can do this yourself in the future by surrounding your text with three backticks:

```
this is a code block
```

this is a code block

FP2andFP3-User

@unisuperbox thanks.

Luksus

@fp2andfp3-user

So I can't see anything obvious... except from, that system image seems to be the problem.

Did you already try to do a fastboot flash system_a system.img without the -S 300?
From my experience it is not needed, when you specify the slot system_a instead of system.

FP2andFP3-User

@luksus crazy without -S 300M I could flash with system_a, but the same result...no booting take the last image 13.02.2021

fastboot flash boot_a boot.img

target reported max download size of 534773760 bytes
sending 'boot_a' (30064 KB)...
OKAY [ 0.793s]
writing 'boot_a'...
OKAY [ 0.310s]
finished. total time: 1.103s

fastboot flash system_a system.img

target reported max download size of 534773760 bytes
sending sparse 'system_a' 1/5 (511226 KB)...
OKAY [ 13.513s]
writing 'system_a' 1/5...
OKAY [ 13.557s]
sending sparse 'system_a' 2/5 (492340 KB)...
OKAY [ 12.896s]
writing 'system_a' 2/5...
OKAY [ 5.422s]
sending sparse 'system_a' 3/5 (477789 KB)...
OKAY [ 11.594s]
writing 'system_a' 3/5...
OKAY [ 5.717s]
sending sparse 'system_a' 4/5 (522237 KB)...
OKAY [ 13.094s]
writing 'system_a' 4/5...
OKAY [ 17.960s]
sending sparse 'system_a' 5/5 (369029 KB)...
OKAY [ 9.411s]
writing 'system_a' 5/5...
OKAY [ 30.732s]
finished. total time: 133.896s

FP2andFP3-User

@luksus and when I flash the old one which is booting the result from

fastboot flash system_a system.img is

target reported max download size of 534773760 bytes
sending sparse 'system_a' 1/5 (510162 KB)...
OKAY [ 13.714s]
writing 'system_a' 1/5...
OKAY [ 13.524s]
sending sparse 'system_a' 2/5 (522239 KB)...
FAILED (remote: data too large)
finished. total time: 27.255s

so i flashed again with -S 300M the old one and it works

weiti

Hi,
i made the same tests... same result.
boot.img and system.img from 24.1. works.
never boot.img with system.img from 24.1. works.
never system.img never works.

Luksus

@FP2andFP3-User @weiti

Another try: I reverted the changes that I have added after the 24.01.:
https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/jobs/1031622918/artifacts/download

FP2andFP3-User

@luksus thanks for the try.....the new image will not boot!

Luksus

@fp2andfp3-user ha, so I also installed this image on my slot b and it does also not boot, that is a progress

So this one works for me here:
https://drive.google.com/file/d/1SwAhywG4ahMiulUTg873Jg-n495FwCrQ/view?usp=sharing

What about you?

FP2andFP3-User

@luksus installed googledrive on slot b it will not Boot.....sorry

FP2andFP3-User

@luksus you know the last build 15 minutes ago will not Boot....

weiti

Hi,
Today i tried again some new builds, same result (also the last build from yesterday does not work).

What is also tried is to connect per ssh to 10.15.19.82 after booting the phone, but fails with:

Connection refused

Output of lsusb contains the line where the ssh connection should work:

  iSerial                 3 GNU/Linux Device on rndis0 10.15.19.82

Any (new) ideas for debugging?

FP2andFP3-User

@weiti hello, no New ideas....i will wait for the ubport installer....this will be a New Option....At the Moment i take the old image From Januar...and test the New images like you and have also no luck.sorry.....hope for @Luksus and the ubport installer

weiti

good news from my side. after a lot of trials (go back to android, wiping data partition, changing active slots... ) after some time the newest build is working. don´t know what it solved. thanks.

FP2andFP3-User

@weiti okay perfect.....so you did everything again and then it runs? Wiping data how? Twrp or Android or over fastboot?

FP2andFP3-User

@Luksus when i do fastboot -w this is the result:
wiping userdata...
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.45.6 (20-Mar-2020)
/tmp/TemporaryFile-ydrusO: Nicht implementierte Ext2-Bibliotheksfunktion beim Erstellen des Superblocks
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

FP2andFP3-User

@weiti I tried also many times now, but no chance to boot the new image. I think, the problem is maybe the data wiping.....
@Luksus
Now E foundation is flashed, because after testing no Android and no old Image was running....e foundation is running now with android 10....Do you have an idea?

Luksus

@weiti interesting. I am happy that you could solve the problem.

@FP2andFP3-User not surewhy it does not work with fastboot.
Did you try it with twrp already?

FP2andFP3-User

@luksus yes with twrp Android and
Fastboot -w and fastboot erase userdata

weiti

i did it with Twrp, for me also with fastboot its not working (same error message as you wrote).