Murena Pixel Tablet - Update A14 Official to A15 Community

/e/OS Devices Murena
,
1

Hello everybody,

Currently I use 3.0.4 A14 stable version for my Murena Pixel tablet
A15 is now available for Murena Pixel Tablet and I want to test it.

I tried what seems to be a dirty update with ad sideload e-3.0.4-a15-20250711508347-community-tangorpro.zip serving: 'e-3.0.4-a15-20250711508347-community-tangorpro.zip but at the end I have an error on the tablet:
‘ERROR: recovery: Signature verification failed’
‘ERROR: recovery: error: 21’

So I guess I need to update the recovery to update OS from a14 to a15
So I went here: Install /e/OS on a Google Pixel Tablet - “tangorpro” (or can I use another method?)
I downloaded all the files.

The first step has been to unlock the bootloader and I did it enabling dev options and usb debug
I used this cmd line proposed in the documentation: fastboot flashing unlock

Next step listed in the documentation is:
fastboot flash boot <boot>.img
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_kernel_boot <vendor_kernel_boot>.img

But as soon as I do the first cmd line fastboot flesh boot boot-e-3.0.4-a15-20250711508347-community-tangorpro.img the process starts but stops quickly with this error:

E:\IT\telephone\Murena Pixel Tablet\01.e-Recovery>fastboot flash boot boot-e-3.0.4-a15-20250711508347-community-tangorpro.img
target reported max download size of 261095424 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: partition (boot) not found)
finished. total time: 1.531s
E:\IT\telephone\Murena Pixel Tablet\01.e-Recovery>

Would you have any idea?
Thanks in advance

2

Just a first look

In Install page

fastboot flash vendor_boot recoveryfilename.img

… but upgrade + official → community might well need Format data.

3

Hi @aibd,

for me the format data for this device is not an issue, I can do it.
Do you do it via cmd line? Or in a14 recovery?

Thanks

4

According to the install page it will be available from the new recovery, just as if a “New install”.

5

Hi @aibd,

you said “available from the new recovery”. The stuff is that I’m blocked before I install a15 recovery. That’s the issue currently. Or did I misunderstand something ?
Or you think format data using a14 recovery before flash a15 boot/dtbo/vendor kernel and at the end recovery & e/OS/ will work fine?

Thanks

6

Where are you stuck ? I only looked very quickly the first time … was the “vendor_boot partition seemed wrong” not a fix ?

My suggestion about Format data was not really about that error directly.

7

Hi @aibd,

I’m blocked here because fastboot flash boot … returns that boot partition is not found…

Thanks in advance

8

It is different from what I first saw …

e-Recovery goes to vendor_boot.

and

fastboot flash boot <boot>.img

Did you get 4 or so small images by unzipping

recovery-IMG-e-3.0.4-a15-20250711508347-community-tangorpro.zip

giving


boot.img
dtbo.img
vendor_kernel_boot.img
e-recovery-xxx-xxx.img
9

Hi @aibd ,

I have indeed the four files and I used one for the first cmd line

10

I am so sorry, I should have got a decent sized screen straight away … I was miss reading your directory name

01.e-Recovery

Is there not a further

  1. Since the device resets completely, you will need to re-enable USB debugging to continue.

after unlock … did you do that ?

11

Hi @aibd ,

image
image872×107 2.46 KB

What do you mean? It’s the directory where the img files are and where I launch the cmd line like fastboot

USB debug is enabled I double checked again.

And I checked checksum sha256 for each file, it’s ok.

More information:
To flash .img file, it is said that you need to reboot in bootloader or download mode.
To do that I use cmd line adb reboot bootloader and I arrive on that screen:

IMG_20250809_105245
IMG_20250809_1052451920×1080 80 KB

At the bottom left:

image
image594×636 36.6 KB

At the top right:

image
image868×357 47.8 KB

At the place where you see Restart Bootlader, you can have other choices: Start, Recovery Mode, Rescue Mode (already try but tablet is blocked on a dead Android robot picture), BarCode, PowerOff
If I select Restart Bootloader, I arrive on the same screen

Thanks

12

Different terms are used for certain … from the install page we are given

  • You can also boot into fastboot mode via a key combination:
  • With the device powered off
  • hold Volume Down + Power
  • Once the device is in fastboot mode, verify your PC finds it by typing:
 fastboot devices

Really this command fastboot devices is the best way to know you are in the right place. The response should identify the device with serial number and device state. A normal response is

abc1234xyz    fastboot