Bug two sim cards only one is working perfect

Luksus

@fp2andfp3-user hm, then I have currently no idea...

FP2andFP3-User

@luksus I will wait for the next image and try again. No problem. Thanks

FP2andFP3-User

@fp2andfp3-user I don't understand, your new images is also not flashable for me....all older images are okay... I tried with ubuntu and with windows 10 no chance...damm

weiti

Hi, first thanks for the FP3 port, really nice to have it since a long time.

i have exactly the same Problem. The last build which is working is the one from 24.01. Newer Builds do not boot any more (no access with adb/ssh). Any information i can provide to find the root case?

Luksus

@weiti @FP2andFP3-User
I also don't know whats going on... for me it is still working.
Can you please try this artifacts, which I build on my homeserver: https://drive.google.com/file/d/1Rua6Soc2OyHh5HibaFz1lYS-tBoRtpx3/view?usp=sharing

If this also does not work, I can only suggest you to flash the stock android rom A.0111 with this tool: https://github.com/p1gp1g/fp3_flash_stock.
Your data partition should be stay untouched in this case, so you don't have to be worry about loosing data (normally).

After flashing the stock rom, you don't need to boot android.
Just flash again the ubports images.

FP2andFP3-User

@luksus you have to give US access in googledrive, then we can test it. Thanks

FP2andFP3-User

@luksus shall we flash on both slots or only on one?

Luksus

@fp2andfp3-user Does the link work now?
To be safe you could flash both slots. But this is not needed.
So if you can keep the overview on which slot you are operating, it is up to you ...

FP2andFP3-User

@luksus link is running......thanks

FP2andFP3-User

@luksus googledrive is not booting....I will check flash.all tommorrow or on saturday.....

Luksus

@fp2andfp3-user regarding flashing both slots:

What I do is, I flashed initially both slots.
Since then I only flash slot A with newer images. This way, I have a working backup slot (B) in case slot A does not boot anymore.
So if it is that case I can just boot to fastboot, switch active slot and boot to the working one.

FP2andFP3-User

@luksus

1: I flashed both slots with ./flash
2: I flashed boot image and system image from yesterday
3: It will not boot!

1:./flash.sh
2:./flash.sh
3:fastboot flash boot boot.img
4:fastboot flash system system.img
--> error flashing
5:fastboot -S 300M flash system system.img
--> okay
6: Reboot
7: It hangs on Fairphone Logo as lasttime

damm Whats the problem?

Luksus

@fp2andfp3-user Do you have still no access over ssh via usb connection?
Do you have 2 simcards? Maybe try with only one inserted.

FP2andFP3-User

@luksus I tried it serveral times and also again your googledriveimage. I tried Windows, Ubuntu and also Manjaro....no chance to boot.

the last bootable for me is from 03.02.2021

FP2andFP3-User

@luksus with flashing or with booting? I tried it with both simcards everything booting and flashing

Luksus

@fp2andfp3-user booting.

FP2andFP3-User

@luksus ok. nothing happened also with one simcard on slot 2

Luksus

@fp2andfp3-user can you get a telnet connection to 192.168.2.15 (also with usb connected)?

Did you try, to only flash the boot.img which was working for you, together with the current system build, or the other way around?

I just rebuild the system from the commit which was working for you:
https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/jobs/1027345380/artifacts/download?file_type=archive

So in it, there is the old working boot.img, and an up to date system.img (with old and working overlays).

FP2andFP3-User

@luksus it will not boot....I have tried the old boot image and the new system image and both new.
Maybe I am wrong and the image which is runnning much older like @weiti told us from 24.01.

telnet is not running
I have flashed so much....
Maybe we need a data reset?

Luksus

@fp2andfp3-user if the old images are working, I don't think that a data reset would be useful...

Perhaps you could try one last thing:
Starting with a working system (some older images):

flash new boot only -> try to boot
if this is not working go to start
flash new system only ->try to boot

If we don't can identify the culprit image, then I don't know how to proceed.

I would try to start with the android stock images again. But this time boot it once on every slot, so that you have a successful boot on both slots. You probably need to wipe the data.

Then try again with latest images...

But when I think about it... the whole issue makes no sense at all.

Perhaps you should document exactly, what you are doing in the terminal, so that I can analize and compare your process against mine. Including:

which slot you are on: fastboot getvar slot-active:a
perhaps a fastboot getvar all would be useful
which slot you may have set to active: fastboot --set-active=a
what checksum does your flashed images have: sha256sum boot.img
what commands did you use to flash the images:
- fastboot flash boot_a boot.img
- fastboot flash system_a system.img
what is the complete output of the flash command

Can you boot to recovery btw.?