English

TWRP installable stock firmware packages for Fairphone 3

Installed Fairphone_FP3_8901.2.A.0110.20200109_01092024_user_release-key.zip with twrp-3.3.1-0_k4y0z-20200131-01-fp3.img.

Same result, installs fine but still freezes at “Fairphone” when booting.

Rebooted into stock recovery and did “Wipe data/factory reset”.
Wanted to “Reboot to System” from the recovery … got Fastboot Mode instead, and:

fastboot getvar current-slot
current-slot: INVALID
Finished. Total time: 0.007s

That’s when fastboot booting TWRP doesn’t work anymore, which even makes sense to me …

fastboot boot twrp-3.3.1-0_k4y0z-20200131-01-fp3.img
Sending 'boot.img' (28570 KB)                      OKAY [  0.771s]
Booting                                            FAILED (remote: 'unknown reason')
fastboot: error: Command failed

At which point I’m wondering … How can I determine afterwards to which slot I installed the ZIP?

Edit:
I had a look beforehand now and installed to slot a.
I rebooted into Fastboot Mode and

fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.001s

So it seems it’s not the installing that makes the slot invalid.
Tried to boot the OS … freezes at “Fairphone”.
Rebooted into Fastboot Mode … slot is still a.

Is there anything I could check with fastboot or TWRP now?

Thank you, @k4y0z that worked!
But now when I try to flash a gsi again with fastboot flash system <system-image> I get the following error:

Invalid sparse file format at header magic error: write_sparse_skip_chunk: don't care size 183539441 is not a multiple of the block size 4096 fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertionpad >= 0’ failed.`

Can you confirm you used the new file I uploaded today?
md5sum: 428bdfe207aab70fad51fe4da33e8d6c

In my opinion that doesn’t make sense at all, fastboot boot should work regardless of the current slot being bootable or not.

However the workaround for this is to set the slot active using fastboot, which will reset the retry-counts:
fastboot -set_active=<slot>

The ZIP will be installed to the current slot.
You can see in the TWRP reboot page which slot is currently active (and switch slots)

I am unsure, what could now be the issue.
Please make sure you used the new upload from today.
Also @corvuscorax If you could also double-check again, that the new version has the correct images?

I have also reuploaded the 105, because it wasn’t finding mirrors:
https://androidfilehost.com/?fid=4349826312261714314

1 Like

Yes. I checked the MD5 … and the new file is *key.zip instead of *keys.zip.

Yes, but that doesn’t help much afterwards, or does it? Couldn’t the phone have changed slots because booting didn’t work out? (I noticed an automatic rapid reboot or two yesterday from the “Fairphone” screen when stuff didn’t work.) (Edit: Ok, such a reboot doesn’t seem to change the slot. At least not now when I had one and checked the slot.)

That’s why I made sure I knew the active slot with the second try.

Thanks, I will try that one, too.

I installed the new Fairphone_FP3_8901.2.A.0105.20191217_12171325_user_release-keys.zip (checked the MD5) with twrp-3.3.1-0_k4y0z-20200131-01-fp3.img on slot a.

The phone shows the “Fairphone” screen and then reboots … shows the “Fairphone” screen again, and then reboots into the recovery with the “Can’t load Android system. Your data may be corrupt. […] Try again / Factory data reset” screen.
The active slot is still a.

Once I “Factory data reset” there, the phone reboots straight into Fastboot Mode, and the slot is invalid.

By the way … that the TWRP script supposedly should install all the partitions, but only ever mentions system, vendor and product is ok?

1 Like

That’s strange, when it showed that “Try again” message, Factory reset has always worked in my tests to bring it back.

The other partitions are flashed in a different format, and there is just no output in the script.
You can check META-INF/com/google/android/updater-script in the ZIP-file.

I’m not sure what is going on at this point, maybe @corvuscorax has an idea.
It should restore all the partitions to the original ones and boot without issues.

EDIT:
OK, I have another idea what might be going on, can you please go into adb shell in TWRP and do
ls -l /dev/block/bootdevice/by-name

send me the output please?

1 Like

Ok, I got a booting A.0105 back somehow again.

I installed the new A.0105 ZIP with the old TWRP, immediately formatted data before rebooting because the old TWRP complained about FBE (the new TWRP didn’t), which is strange because I formatted data long ago and had no working OS in the meantime to encrypt it again.

The phone rebooted into the “Fairphone” screen, then into the “Try again / Factory data reset” screen again.
Instead of choosing anything there, I booted the old TWRP again and restored my A.0105 backup … and A.0105 boots again!

Man, am I not understanding any of this :slight_smile: .

This would kind of correlate, with what I am currently thinking.
Please go into TWRP adb and get me the output of
ls -l /dev/block/bootdevice/by-name/
I might have to build a new TWRP to get this fixed once and for all.
You probably won’t be able to update to 110 when you installed 105 with the old TWRP.

Old TWRP …

fp3:/ # ls -l /dev/block/bootdevice/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 aboot_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 aboot_b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 apdp -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 36 2020-02-01 20:51 boot -> /dev/block/bootdevice/by-name/boot_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 boot_a -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 boot_b -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 cmnlib64_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 cmnlib64_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 cmnlib_a -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 cmnlib_b -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 config -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 devcfg_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 devcfg_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 devinfo -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dpo -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 35 2020-02-01 20:51 dsp -> /dev/block/bootdevice/by-name/dsp_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dsp_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dsp_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dtbo_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 dtbo_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 frp -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 fsc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 keymaster_a -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 keymaster_b -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 keystore -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 lksecapp_a -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 lksecapp_b -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 logdump -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 mcfg -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 mdtp_a -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 mdtp_b -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 misc -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 37 2020-02-01 20:51 modem -> /dev/block/bootdevice/by-name/modem_a
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 modem_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 modem_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 msadp -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 persist -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 prodinfo -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 39 2020-02-01 20:51 product -> /dev/block/bootdevice/by-name/product_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 product_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 product_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 rpm_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 rpm_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 sbl1_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 sbl1_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 sec -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 splash -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 ssd -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 syscfg -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 38 2020-02-01 20:51 system -> /dev/block/bootdevice/by-name/system_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 system_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 system_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-03-27 00:08 tz_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 tz_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 userdata -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 vbmeta_a -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 vbmeta_b -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 38 2020-02-01 20:51 vendor -> /dev/block/bootdevice/by-name/vendor_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 vendor_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-03-27 00:08 vendor_b -> /dev/block/mmcblk0p33

New TWRP …

FP3:/ # ls -l /dev/block/bootdevice/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 aboot_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 aboot_b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 apdp -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 36 1970-03-27 00:16 boot -> /dev/block/bootdevice/by-name/boot_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 boot_a -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 boot_b -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 cmnlib64_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 cmnlib64_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 cmnlib_a -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 cmnlib_b -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 config -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 devcfg_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 devcfg_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 devinfo -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dip -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dpo -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 35 1970-03-27 00:17 dsp -> /dev/block/bootdevice/by-name/dsp_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dsp_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dsp_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 36 1970-03-27 00:16 dtbo -> /dev/block/bootdevice/by-name/dtbo_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dtbo_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 dtbo_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 frp -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 fsc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 keymaster_a -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 keymaster_b -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 keystore -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 lksecapp_a -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 lksecapp_b -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 logdump -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 mcfg -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 mdtp_a -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 mdtp_b -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 misc -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 37 1970-03-27 00:17 modem -> /dev/block/bootdevice/by-name/modem_a
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 modem_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 modem_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 mota -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 msadp -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 persist -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 prodinfo -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 39 1970-03-27 00:16 product -> /dev/block/bootdevice/by-name/product_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 product_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 product_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 rpm_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 rpm_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 sbl1_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 sbl1_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 sec -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 splash -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 ssd -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 syscfg -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 38 1970-03-27 00:17 system -> /dev/block/bootdevice/by-name/system_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 system_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 system_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-03-27 00:16 tz_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 tz_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 userdata -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 vbmeta_a -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 vbmeta_b -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 38 1970-03-27 00:16 vendor -> /dev/block/bootdevice/by-name/vendor_a
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 vendor_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-03-27 00:16 vendor_b -> /dev/block/mmcblk0p33
1 Like

If you’re restoring via TWRP, you can connect via ADB while it’s doing that.
But no hurries, I won’t be able to build the new TWRP for another few hours.
BTW, if you want to be able to update from your 105 now after restoring data, you probably have to flash the product partition from the original stock dump with fastboot.

1 Like

Thanks, this worked.

Ok, I did that.
The updater (according to logcat) then complained about other partitions, which I flashed with fastboot then from the stock dump:

  • sbl1
  • system

… and apparently now it updates to A.0110 … and now it successfully booted A.0110 :+1: .

Never give up, never surrender! :slight_smile:

I also faced similar issues as @AnotherElk updating from 105 to 110. Fairphone logo kept showing up, deployed 110 with different TWRP versions, 105 with both versions.
This is what I did:

  • on a stock 105 I installed the old TWRP.
  • installed magisk over TWRP
  • OTA 110 failed -> restored boot.img from magisk -> to no avail
  • I flashed the @k4y0z 105 dump using adb fastboot flash -> again the OTA fails (due to dsp.img?)
  • sideloaded the 110 version with the new TWRP -> did not get beyond the FAIRPHONE greeting. Factory reset in stock firmware not possible. This is also the point where the corruption message started to show up.
  • flashed the 105 dump again with adb fastboot, this time replacing the dsp.img.
  • now I got the screen with the four rotating dots, but nothing happens.
  • tried to restore a backup via TWRP, failed with E:extractTarFork() process ended with ERROR=255 -> now I get only to the bootloader.

Finally I flashed the 101 dump from here:
https://androidfilehost.com/?fid=4349826312261713361
using adb fastboot as described here, restored factory defaults and installed 110 OTA.

2 Likes

did you find out what was the cause? is there a partition naming mismatch?

confirmed, unpacked images from zip with md5sum 428bdfe207aab70fad51fe4da33e8d6c are identical to OTA images fresh of the phone in size and content.

1 Like

Thanks for your output, it confirms what I was suspecting, though it doesn’t explain why the old TWRP worked for you.
About sbl1 not matching that would also be explained by what I was thinking.
System could only be mismatched if it was mounted RW in TWRP.

@corvuscorax I have a very good idea now, what was wrong, though it will need to be tested, once I have built a new TWRP.
When you look at @AnotherElk’s ls output, you will see, that some partitions are missing a symlink to the current slot (i.e. sbl1 and vbmeta).
This would mean, these partitions with missing slots where not flashed during the TWRP install.
Which would also explain the corrupted system message.

1 Like

Woah, I got the update finally working, too.
I flashed the TWRP flashable A.0105 -> ota update error
Then I flashed from the Stock dump with fastboot the dsp.img, system.img, boot.img, product.img and sbl1.img -> ota update error
And finally, I flashed the above image to the other slot (B) -> update to A.0110 worked!

1 Like

I had this, too.
Before I could restore the data partition from my backup I had to set up my screenlock access method (PIN in my case) again in Android, only then was TWRP able to access the data partition again, and only then I was able to restore the data partition from my backup again.

To avoid confusion for people perhaps reading along never having used these … this flashing is done with fastboot.
adb and fastboot are different tools for different tasks in different situations.

fastboot is being used in Fastboot Mode (in this topic here e.g. to flash partition images to the phone, to boot TWRP without installing it, to check or activate the A/B partition slots of the phone), adb will not work in Fastboot Mode.

adb can be used for some other tasks when TWRP is running, or for even more other tasks when Android is running with USB debugging enabled. In these situations fastboot will not work.

how did you get the 110 update?

i only get 105 ota and then nothing

Nevermind i have made it!

flashed the 0110 with twrp to slot b, kicked it back in fastboot
flashed the vbmeta.img and sbl1.img to slot b from the 0110.

reboot

sucesess!!!

1 Like

Indeed. I’m sorry I’m new to this environment and toolchains. I’ll fix the error above.

1 Like

New TWRP release is up.
This one finally fixes installing the full stock ZIPs.
Make sure you have the option “Mount system partition read-only” checked in TWRP if you want to be able to OTA.

Thanks to @pigpig for testing!

7 Likes