Motorola - Moto G7 Power - ocean - Documentation Suggestions

…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…

Regarding Moto G7 Power installation:

I first tried straight after unboxing the device and oem unlocking it. That bricked in a way that it didn’t turn on anymore and named itself “Qualcomm loader…something”. I then had to use “blankflash” that contains a tool called “qboot” that I found in some dubios sources, to restore the stock bootloader. I then reflashed with the stock-rom and let it apply all available updates before flashing /e/. Maybe it’s worth a hint to apply all regular android updates on this device before flashing /e/.

On the 1.16 recovery, it would be helpful to note that a message popup about restarting recovery arises. I choose “No” to continue.

Hi, I just install the os on Moto G7.
The documentation is pretty straight, only one remark: the last step is missing.
After installing the os, you have the option to install additional package yes/no
Thanks

Hi @Ken748 welcome to the /e/ forum.

/e/OS inherits this option from Lineage. /e/ expects no extra packages, but it remains an option for those who have reason to want to add anything at this stage.

The standard answer is Extra packages - No.

  • (The answer Yes does not lock the user into installing anything, that is the user can still exit.)

Hi, I was reading the flashing instruction and came across this, which is confusing.

Tip: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.

Where it says “might attempt to flash to boot__a / boot__b rather than boot_a / boot_b” and at the end “if fastboot fails to flash to boot__a, you must flash to boot_a.”.

Basically, it says the same thing or am I misunderstanding something?

hello! what happened that now the ocean went from a T build to a U build, i.e., it was downgraded to unofficial?

The community build on /e/OS U is available here. No devices have been downgraded. If in some case a U build crashes we revert to T.
The u in the ROM name stands for Android U or A 14 or /e/OS u.

1 Like

I was able to Android version upgrade my ocean from Android 13 (T) to Android 14 (U) by following the upgrade instructions at Upgrade LineageOS on ocean | LineageOS Wiki, that is simple adb sideload of the new ROM. No data was observed lost.

But ofc I did not do this without knowing I had a secure backup strategy.

From e-2.5-t-20241110446839-community-ocean; now running 2.6.3-u-20241219455571-community-ocean

1 Like

same, im upgrade to 2.6.3 with no problems

works very smooth the moto g7 power :slight_smile: thanks team :smiley:

Hi, I wish try also an upgrade, but it will be from 1.18-t-20231210360971-dev-ocean to 2.6.3-u-20241219455571-community-ocean

Is it recommended ??

Well first I have some updates to apply, I have just saw them…

/e/0S 2.4.1

and then

/e/OS 2.5

I think is better do it steps by steps, isn’t it ?

its a major upgrade…you can try it but backup your data

1 Like

Ok know using 2.5-t-20241110446839-community-ocean