How to compile own build for XT2223-1 Moto G62 5G

/e/OS Devices Motorola
1

The manual is a little bit confusing. No ** proprietary blobs** for this device already there. I have the device at home - can I make it itself if I extract the boot.img, system.img and recovery.img from this device? Or need it any other action befor?
I made developer and activate USB-debugging - OEM Unlock activate. Now i go to bootloader and call fastboot unlock oem… Than I go to webpage of motorola and get my unlock information.
Now I am able to extract any img from the device through twrp recovery - it is not flashed to the device only booted from img by sideload.

Thanks for help me - what I do next to get the right inormation that I can build my own /e/os with apks that I wanna at first time. ^^

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

2

What is the device codename ?
[HOWTO] Find device codename

Ultimate how-to guide: Unofficial Builds using repo style for using lineage or other aosp sources that are not supported by /e/OS

[HOWTO] build /e/ the (full) classic way (no docker, no scripts, just 'make')

1 Like
3

If you know for certain the device codename then you can determine if this is a supported device.

The “extract blobs” bit will prove not required in the case of a supported device.

Personal opinion

Maybe there is a “historical legal reason” that this can never be corrected in official documentation.

4

In Settings → About Phone → Software-Channel: reteu && Android-Version: 13

Command: adb shell getprop ro.product.device
Output: rhodec

5

With rhodec you have an unsupported device so you will be on new territory https://xdaforums.com/t/custom-rom.4570493/ and extract blobs will be required … but users like you may well liberate the phone in time.

You might investigate the diffs with Lineage supported

2 Likes
6

I made some extraction of my device. I boot with a TWRP.IMG and made DD exports of partitions to backup.

7

Not sure of your experience level but may I offer Create Lineage device tree for android using aospdtgen

1 Like
8

My first custom rom was cyagenmod on a Smasung Galaxy S Plus - Still running, but It now in trash because to slow for nowadays.
My next custom rom was lineage on a Samsung Galaxy Tab 2 - Still running.

Now I wanna test /e/os but it only roms for G52 but not for G62 but the codename is the same - So I wanna try to get it work by my own. I like it to solve problems - it does not metter how long it took. I wanna to solve it.

Thanks for the next step with the device tree with aospdtgen. I give it a try but before I look to the source code that nothing bad thing made. I am a programmer so I look through the code a little bit.

9

Hello @Claudia, Welcome to the /e/ users forum.

latest working was e-0.7-n-20200623-espresso3g from @ Android-Andi during covid pause.
e-0.7-n-20200623-espressowifi was buggy…

1 Like
10

Ignore the Samsung TAB 2: I leave it with the old Version of LineageOS.

Now I am intressted in install /e/os on my new Smartphone Moto G62 5G - Codename: rhodec

1 Like
11

Status Moto G62 5G is not allowed to unlock bootloader. Missing Entry (bootloader) oem unlock: from fastboot getvar all!

I test later if command fastboot unlock worked or not.
The command fastboot oem get_unlock_data give an error.

Bad a moto device without to unlock that was bad Motorola I am moving back from you. shame you moto! How dare you!

12 
fastboot flashing get_unlock_ability

?

13

Did you confirm this with Moto Support ?

you will likely have to tweak the url for your region (where the device is sold) else you may get a wrong result!

Another url, this from rhode /e/ install page

Follow the instructions at Motorola Support to unlock your bootloader.

14

Output:

FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed

FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed

I think it is not possible with my device. That is my first device what I have without rooting ability. :face_with_head_bandage:

15

I was in usermode fastboot - I tried all commands again on the otherside with “Volume-Down-Press + Power-Press” here typed I again all commands and now it works finally. Mission completed! OEM Unlock solved. Shit user-Mode and firmware-Mode - Too many fastboot loaders.

Now, I made some backups of my device, that the command can made a factory reset after: fastboot oem unlock UNIQUE_KEY execution.

I must to write down my google-account for this device that is a uniq one.

@piero and @aibd

16

Claudia,

Before you get to far be sure to first test that all stock ROM function in the phone work as per specification. The main things VoLTE, WiFi calling and 5G data. Just test a phone a bit.

17

I have this phone I think 2 years. it works perfectly. Warrenty is out of date. so it does not matter if it bricks. but I hope it will be not brick. :nerd_face:

1 Like