General [CLOSED]Project discontinued

[CFKod]

Any plans to add support to Motorola Edge 20 Fusion (XT2139-2) ?

It will work sir. Its also called kyoto

 

[zedzded]

It will work sir. Its also called kyoto

Isn't kyoto is the codename for Motorola Edge 20 Lite, which is different than the Fusion model?

UPDATED: doesn't look like they are the same. This guy almost bricked his Fusion by using code written for the Lite version.

 

[puh63]

Thanks for your help, but it doesn't work. I don’t understand what the mistake is ... The bootloader unlocked, installed the root, installed the recovery (the data was decrypted), the last point remains ... I am attaching a photo, can my mistake be seen here?

 

[puh63]

I read and write through a translator, I apologize for the inaccuracies ...

 

[CFKod]

Releases · forforksake/android_device_motorola_kyoto-pbrp

recovery tree for Motorola Edge 20 Lite 5G - mt6853 - kyoto - forforksake/android_device_motorola_kyoto-pbrp

github.com

A12 release

 

[CFKod]

Thanks for your help, but it doesn't work. I don’t understand what the mistake is ... The bootloader unlocked, installed the root, installed the recovery (the data was decrypted), the last point remains ... I am attaching a photo, can my mistake be seen here?

Dude that is strange.. Let me just run through the steps again my side
You do have the latest adb and fastboot installed?

 

[CFKod]

Isn't kyoto is the codename for Motorola Edge 20 Lite, which is different than the Fusion model?
View attachment 5722519

UPDATED: doesn't look like they are the same. This guy almost bricked his Fusion by using code written for the Lite version.

Hmmm only the processor is different
I fail to see how unless you try booting to android on the boot image itself

You simply need to install the recovery ramdisk using the release zip

 

[CFKod]

You can try it without a patched vbmeta, fyi

I read and write through a translator, I apologize for the inaccuracies ...

 

[puh63]

Drivers from this site Version 1.4.3. And yes, the phone works fine without patched VBmeta. Only the system remains encrypted when the phone boots up. Read-only, no changes can be made by explorer.

 

[CFKod]

I patched the boot.img - I patched it.
I flashed TWRP.img and installed TWRP from a zip file.
Rebooted from recovery to fastboot.
Command C:\adb>fastboot flash vbmeta_a --disable-verification --disable-verity vbmeta.img
fastboot: unknown option -- disable-verification.
astboot flash vbmeta_a ----do you need an A?
vbmeta stock, from the stock firmware.
Maybe you need a patched vbmeta?????
Where to get or how to patch yourself?

The a is not needed as it depends on what slot you are in

Try just fastboot flash vbmeta vbmeta.img

If that works then add the disable flags and do it again

 

[CFKod]

Drivers from this site Version 1.4.3. And yes, the phone works fine without patched VBmeta. Only the system remains encrypted when the phone boots up. Read-only, no changes can be made by explorer.

What android version are you using by the way? I have now released it for a12

 

[puh63]

A11

 

[puh63]

OK . I'll try.

 

[puh63]

Gives out this

 

[CFKod]

Gives out this

Drivers from this site Version 1.4.3. And yes, the phone works fine without patched VBmeta. Only the system remains encrypted when the phone boots up. Read-only, no changes can be made by explorer.

it your version of adb fastboot (1.43 is a version from android 6.0 on this forum)

install from this thread instead

 

[puh63]

We did it!!!! Thank you very much for the help!!! The drivers were to blame...

 

[CFKod]

Haha no problem

 

[CFKod]

Thread closed. All future development will be on Orangefox, where full user decryption has been obtained.

 

[Oswald Boelcke]

Thread closed. All future development will be on Orangefox, where full user decryption has been obtained.

Thread closed on request of OP!

Regards
Oswald Boelcke
Senior Moderator