No Valid operating system could be found

Using /e/OS Troubleshooting
1

Hi @ll

Since this morning, my device shows ‘no operating system could be found’.
The bootloader is locked and I cannot flash via ADB fastboot because OEM is not selectable.
How can I get it back?
flashing_locked:cid:0x0032

My device is the Moto Edge 40 Pro.

2

Are you running /e/OS. Do you know the version you were running [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc.

You might hope to repair by adb sideload

Unusual in /e/OS as locking the bootloader does not appear on the install page Install /e/OS on a Motorola edge 40 pro - “rtwo”.

Can you recognise e-Recovery? Is the message coming from e-Recovery? If not please can you show an image.

1 Like
3

No e-recovery avaible…

IMG_20250716_152152
IMG_20250716_1521521920×2560 270 KB

This what I get.

OEM unlocking is not active, i habe the new unlock code from motorola but i get this:
(bootloader) check 'OEM unlocking"
…
fastboot: error: command failed

how can i active OEM on adb?

4

Is this a repair, install or something else entirely?

5

on the phone is e/os 3.0.1 a15

i dont know what happens,

but oem unlocking is disabled and i cant boot the phone.
to (re)unlock the bootloader i need to enable it.
is there a way to active OEM via adb?

6

You could try using the Motorola tool to bring the phone back to stock ROM. Just be aware if you do it demands an email address and all contacts and (I think) to read all emails in the email account (not kidding) to use the tool. So I recommend you use an email account with no little or no data in the account.

I have another thread on it in here somewhere… actually here: Can't boot phone ID: bad key - #3 by rhubarbpieguy

7

In your image the Volume keys drive a menu. Can you change to any other mode ?

8

yes,
start
restart bootloader
recovery mode (doesn’t work)
power off
bootloader logs
barcodes

Motorola’s Software Fix doesn’t work. it stop working after check installed firmware.

9
  • the worst : Internal emmc memory can be defect or inaccessible
  • the simplest : did you try to turn off, then boot instead of just reboot
10

Yes I try many solutions I find on the net…

On another forum says me the only way to resolve the problem is to reflash the ufs chip.

But this is over my capacity…

Phone repair center says me that this is to expensive to repair.
One solution is to replace the Mainboard or find someone that want to repair it privately.

I’m now searching where to buy a Mainboard…

Thx to support me :slight_smile: