Can't enter RECOVERY MODE - /e/OS 2.8

/e/OS Devices Motorola
,
1

I’m attempting to install /e/OS 2.8 on a Motorola XT2113-2 but can’t enter RECOVERY MODE. After executing ‘fastboot flash recovery recovery-e-2.8-a14-20250222470211-community-kiev.img’ I receive:

sending ‘recovery_a’ (102400 KB) OKAY [ 2.141s]
writing ‘recovery_a’ OKAY [ 1.559s]
Finished. Total time: 3.741s

In step 5 I manually power off the phone. Pressing [VolumeDown Power] takes me to the fastboot screen. I then use the Power Down key to select RECOVERY MODE. Although the documentation doesn’t specifically state such I assume I’m then to press the power key to boot into RECOVERY MODE. Correct?

Unfortunately I boot into Android. As a result I can’t choose Apply Update in the next step. What am I doing wrong?

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

2

what about

fastboot reboot recovery

or

fastboot boot recovery-e-2.8-a14-20250222470211-community-kiev.img

?

3

Or, if you are in Android.

Under Developer options
Enable USB debugging

Conect usb cable

adb devices

Give permission on device if asked.

adb reboot recovery

4

will only works in recovery mode or in normal mode, not from fastboot mode…

5

I know, but he said, “Unfortunately I boot into Android”

And when in Android, he can use: adb reboot recovery.

6

But it is too late in this case.

7

I executed ‘fastboot boot recovery-e-2.8-a14-20250222470211-community-kiev.img’ and received:

Sending ‘boot.img’ (102400 KB) OKAY [ 2.137s]
Booting OKAY [ 10.320s]

I assumed that would take me to a recovery screen but it took me to the fastboot START screen. If I arrow to RECOVERY MODE and press Power I again boot to Android.

8

Is it possible the problem is the recovery-e*.img file? I ask this as I successfully installed /e/OS on a Motorola Cedric. However, I had to revert to an earlier version.

I see recovery-e-2.6.3-u-20241218455571-community-kiev.img. If I execute ‘fastboot flash recovery recovery-e-2.6.3-u-20241218455571-community-kiev.img’ what happens if I boot to RECOVERY MODE?. Can I execute ‘fastboot boot recovery recovery-e-2.6.3-u-20241218455571-community-kiev.img?’

9

Perhaps another solution. Can I get around the RECOVERY MODE problem by executing a Build versus an Install?

10

Everytime you boot into Android you’re recovery is probably reverted to older version.
So.
fastboot flash recovery …
Directly after that
fastboot reboot recovery

That should work

And maybe give this one a read.

https://wiki.lineageos.org/devices/kiev/install/variant2/#

1 Like
11

I did as you suggested and I’m caught in a loop. I get the ‘The bootloader is unlocked …’ screen. The screen then displays a Motorola logo for a split second and then another Motorolo logo for slightly longer only to repeat the cycle starting with the bootloader screen. My steps were:

‘fastboot devices’
ZY220ZXKC2 fastboot

‘fastboot flash recovery recovery-e-2.8-a14-20250222470211-community-kiev.img’
Sending ‘recovery_a’ (102400 KB) OKAY [ 2.160s]
Writing ‘recovery_a’ OKAY [ 1.575s]

‘fastboot reboot recovery’
Rebooting into recovery OKAY [ 0.004s]
Finished. Total time: 0.055s

This is frustrating. As ‘fastboot devices’ responds I assume everything is correct on the phone and with adb/fastboot. The steps seem simple and I’ve reported everything I did. ?

12

@rhubarbpieguy

adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-e-2.8-a14-20250222470211-community-kiev.img

Now reboot into e-recovery to verify the e-recovery installation - IMPORTANT!

Do not use “fastboot reboot recovery”
Use Moto firmware menu (hardware button) to navigate to and to select the Recovery option.

Select Apply Update and in next screen Apply update from adb

adb sideload copy-partitions-20220613-signed.zip

Now reboot to e-recovery by tapping Advanced then Reboot to recovery

Now tap Factory Reset then Format data / factory reset and continue with the formatting process.

Return to the main menu.
Select Apply Update and in next screen Apply update from adb

adb sideload e-2.8-a14-20250222470211-community-kiev.zip

Select Reboot system now

13

The problem we were trying to solve is I couldn’t boot to RECOVERY MODE using the documentation. See my first post in this thread.

14

The /e/ documentation is in need of renovation in numerous places.

15

Great, but didn’t your post basically tell me to follow the documentation. What differs? I couldn’t boot to recovery using those steps.

I can probably get the phone back with Lenovo Motorola Rescue Assistant. Would performing a Build instead of Install be different?

Step 8 in the Build documentation mentiions Get your Image! Does that mean I can avoid using a recovery image by doing a build?

16

Maybe try the e-2.7-u recovery image or the e-2.6.3-u.

Or maybe look for an TWRP recovery image, to get an custom recover installed after that is is easier to flash an other recovery image.

I’m not sure what you mean with , “Get your Image! Does that mean I can avoid using a recovery image by doing a build?”

Alway’s need a recovery image flashed to install a custom rom.

1 Like
17

you are right here, the recovery-e could be faulty, TWRP for kiev is promissing in this situation.

@rhubarbpieguy, instructions talk about define slot a or slot b

you are not completly right here as some recent devices like Fairphone 3, 4, 5 or Gigaset GS290 are flashed by an install script and don’t need the recovery manager except for OTA updates

18

Ok, learned something new again .

19

Did find some info on extra button action, maybe useful.

1 Power off your mobile device.
2 As the second step, hold down the Volume Down + the Power key at the same time.
3 The Bootloader mode should be on the screen now.
4 After that choose the Recovery mode by using the Volume keys and the Power button to accept.

5 If you see Android robot on the screen click the Volume Up while pushing the Power button.
Your device will be in the Recovery mode.

20

I tried 2.7 but not 2.6. Are there pre-2.x archives? I ask that as I attempted 2.x on a Cedric which DID NOT WORK. If memory serves I reverted to 1.x and it was easy. I then updated through the internet.

So is there an advantage of doing a Build if I’m not deviating from an Install? I was hoping a Build might avoid the recovery image problem.