Develop Bugs

Moto E4 Guide To Full Stock Firmware Restore and Re-lock Bootloader Any Variant

Note :
Do not erase/flash Bootloader file preloader.img or preloader.bin
fastboot erase preloader
fastboot flash preloader preloader.img
Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.bin
fastboot erase pgpt or gpt
fastboot flash pgpt or gpt pgpt.img or gpt.img​
About :
With this guide you will restore stock firmware and re-lock your device bootloader.This guide is from Moto E4 Mediatek variant SKU XT1760 but can work with any Moto E4 Variant. Just grab the partition info and partition name in fastboot mode with fastboot command "fastboot getvar all". But this step isn't necessary if you take backup with miracle tool. It will dump whole firmware in scatter format. So, no need to worry if you have a different variant of Moto E4
This guide will give you the following :​
PHP:
<bootloader> : warranty (YES)
<bootloader> : unlocked (NO)
<bootloader> : secure (YES)
>> device unlocked (we cannot remove this warning !)
Requirement :
• Place all the firmware files here:
C:\Program Files\Minimal ADB and Fastboot\HERE
• A laptop/Desktop
• Unlocked Bootloader
• Enabled USB Debugging
• Moto E4 Any Variant
• USB Cable
• Minimal Adb & Fastboot Tool
• Miracle Tool
• Adb & Fastboot Commands
Step 1 : Boot into bootloader mode
Switch off your device
Hold power button and volume down button
When you see START release buttons
This is fastboot mode
Step 2 : Reboot into bootloader
Note : i recommended you to use a laptop than that of desktop. For continuous power supply. Fully charge your laptop battery.
Connect with USB Cable
Open fastboot command window
Type fastboot command:
PHP:
fastboot reboot bootloader
Now your device in fastboot mode
--- Do not disconnect ---
Step 3 : Flashing stock factory images
Type these fastboot commands:
Erasing partitions first
if you have a different variant of Moto E4, just write all the partitions name except bootloader(preloader) in a text file and replace them with the below partition names.​
PHP:
fastboot erase boot
fastboot erase efuse
fastboot erase expdb
fastboot erase flashinfo
fastboot erase frp
fastboot erase hw
fastboot erase keystore
fastboot erase lk
fastboot erase logo
fastboot erase metadata
fastboot erase nvdata
fastboot erase nvram
fastboot erase oem
fastboot erase oemkeystore
fastboot erase otp
fastboot erase para
fastboot erase persist
fastboot erase proinfo
fastboot erase protect1
fastboot erase protect2
fastboot erase recovery
fastboot erase seccfg
fastboot erase secro
fastboot erase tee1
fastboot erase tee2
fastboot erase utags
fastboot erase system
fastboot erase userdata
--- Do not disconnect ---
Now flash stock factory images
PHP:
fastboot flash boot boot.img
fastboot flash efuse efuse.img
fastboot flash expdb expdb.img
fastboot flash flashinfo flashinfo.img
fastboot flash frp frp.img
fastboot flash hw hw.img
fastboot flash keystore keystore.img
fastboot flash lk lk.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash nvdata nvdata.img
fastboot flash nvram nvram.img
fastboot flash oem oem.img
fastboot flash oemkeystore oemkeystore.img
fastboot flash otp otp.img
fastboot flash para para.img
fastboot flash persist persist.img
fastboot flash proinfo proinfo.img
fastboot flash protect1 protect1.img
fastboot flash protect2 protect2.img
fastboot flash recovery recovery.img
fastboot flash seccfg seccfg.img
fastboot flash secro secro.img
fastboot flash tee1 tee1.img
fastboot flash tee2 tee2.img
fastboot flash utags utags.img
fastboot flash system system.img
--- Do not disconnect ---
Step 4 : Re-lock bootloader
Type this fastboot command
PHP:
fastboot oem lock
Hit volume up button
Again type fastboot command
PHP:
fastboot reboot
Step 5 : Fix for system image sparse chunk
Used only when fastboot command failed to write system in system partition else when you see "sparse chunk error" wait for 10 minutes. you will see 1/20 or something operations. if not or command ended up with chunk error than use this command.​Use this fastboot command:
PHP:
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash system system.img_sparsechunk.17
fastboot flash system system.img_sparsechunk.18
fastboot flash system system.img_sparsechunk.19
fastboot flash system system.img_sparsechunk.20
Step 6 : Do not use this fastboot command
PHP:
fastboot erase preloader
This will wipe bootloader from bootloader partition and your device ended up with permanent Hard brick.
Step 7 : Fix for bootloader(fastboot) drivers
if your device isn't recognized in fastboot mode, Download USB Drivers from below attachment. Select manually "android_winusb.inf" file while updating driver software.
Download Link :
https://drive.google.com/file/d/0B0Oo-yXGY-zUMG1XRG52dFZpV1k/view
Step 8 : How to dump stock firmware
Thread link below:
https://forum.xda-developers.com/moto-e4/how-to/how-to-backup-stock-rom-moto-e4-variants-t3654976
Guide to fix boot_dataerr in miracle tool if it failed to dump stock rom
Look at the log window in miracle tool there in driver part you will see MTK preloader USB COM PORT#7. We don't need Preloader driver right now, we need MTK Android DA USB COM PORT#7. The solution is update your device driver software to fix this problem else you won't able to dump firmware in scatter format also we don't have official factory images. This is the only method to revert on purely unrooted stock firmware.
Step 9 : Minimal Adb & Fastboot download link
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
This is my last thread in Moto E4 forum and i won't support this device anymore.​

Does this work for all variants?

andMego said:
Does this work for all variants?
Click to expand...
Click to collapse
yes, work with all variants.
already mentioned in OP.

kartik verma said:
This is my last thread in Moto E4 forum and i won't support this device anymore.​
Click to expand...
Click to collapse
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.

amarc78 said:
After you came here and cluttered the forum with a crap load of pointless threads and posts? I love it! Thanks.
Click to expand...
Click to collapse
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.

kartik verma said:
pointless threads and posts
so my posts are useless. sorry if my posts aren't fit into your expectation.
Click to expand...
Click to collapse
Personally I'm very thankful for this post, as I couldn't figure out how to do it myself. I was able to reflash stock and lock the bootloader but it wouldn't boot since it always said it was modified, so I just returned my previous e4 with the bootloader unlocked and the noverify thing flashed.

my phone refuses to verify boot.img

KyleBryant said:
my phone refuses to verify boot.img
Click to expand...
Click to collapse
will it asks for boot.sig or anything else. let me know

I figured it out

KyleBryant said:
I figured it out
Click to expand...
Click to collapse
How?

Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol

KyleBryant said:
Motorola doesn't release verified boot images. The reason it wouldn't boot for me is because I forgot to flash the no verity file lol
Click to expand...
Click to collapse
How do I lock the bootloader and get it to verify the boot image?

No idea

andMego said:
How do I lock the bootloader and get it to verify the boot image?
Click to expand...
Click to collapse
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".

kartik verma said:
fastboot oem lock (relock the bootloader)
their is nothing to do with boot image. verification is for system if you changed something and didn't disable verity " MOUNT FLAG /system ro wait,verify" your device ain't gonna boot into system.
dm-verity can be disabled by two ways either remove "verify" or change the default.prop values "ro.secure=0".
Click to expand...
Click to collapse
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?

andMego said:
Before I returned my other e4 I flashed the stock images with rsdlite and then did fastboot oem lock but then the phone wouldn't boot since it said it was modified so I had to unlock the bootloader again and flash the noverify thing in TWRP. How should I have done it to be able to return the phone with the bootloader locked?
Click to expand...
Click to collapse
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.

kartik verma said:
" it said it was modified"
First of all remove all the changes you have done in system else if you don't know where you have done changes wipe system partition and reflash system image in system partition.
don't flash gpt.img, pgpt.img, bootloader.img in fastboot mode also do not erase data in fastboot mode "fastboot erase userdata". your device must be charged upto 80% if you want your device boot after a clean flash.
as i am also facing over discharged problem.
Click to expand...
Click to collapse
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?

drganbds said:
Kartik dude tell me if this is possible....
To roll back I flash unmodified stock boot image and flash stock recovery through fastboot - reboot system - reset -relock bootloader.....can I able to do this?
Click to expand...
Click to collapse
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img

kartik verma said:
follow this method :
erase partitions only if you have factory images
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase boot
fastboot flash boot boot.img
erase system if you done changes in system partition. if not leave this step
fastboot erase system
fastboot flash system system.img
Click to expand...
Click to collapse
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.

drganbds said:
Excellent then do me a favour buddy I need stock recovery and unmodified boot images of Moto e4 mediatek variant.
Click to expand...
Click to collapse
i will upload official factory images when i get free time

Solution to flash stock rom(factory image) via fastboot and locking the bootloader..

Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:

rishivg said:
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
The quoted lines are redundant (surely they gave you an error since they don't exist in the G5+ firmware)
Otherwise, pretty standard Moto stuff... interesting that in 5th gen stuff you can lock after only flashing system sparsechunks, almost all previous devices required a complete flash with wipe to relock. https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ is another good source for stock factory ROM's (it is the official repo of FirmwareTeam), and Minimal ADB and Fastboot has a lots of "hacks" out there, so it is best to only reference the original source: https://forum.xda-developers.com/showthread.php?t=2317790
I am extremely familiar with previous Moto device, but am curious on this device what is the bootloader status number after relocking with this method and do you still get the unlocked warning screen after relocking like on previous Moto devices?

Hi,
Great if this guide works (not tested by me). However, it sounds viable. :good:
In any case, I suggest to put the original device and retail versions witht the link of the firmware. For example:
- XT1680 & retus: "POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
This is necessary. For example my is XT1685 and RETEU, then this file is not for me!

Not working. Its says cant be downgrade.

No does not work with the XT 1685 and reteu

surjeet.vishwas said:
Not working. Its says cant be downgrade.
Click to expand...
Click to collapse
what is your model number?

rishivg said:
what is your model number?
Click to expand...
Click to collapse
Xt1686 but i download another stock rom

surjeet.vishwas said:
Xt1686 but i download another stock rom
Click to expand...
Click to collapse
okay that is why it gave you error, try with the file that is mentioned in the post

This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.

Gingernut78 said:
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Click to expand...
Click to collapse
yes exactly! you ll need to flash the whole previous build again...

rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
You can flash a previous build but it won't lock the bootloader that is the problem.

Gingernut78 said:
You can flash a previous build but it won't lock the bootloader that is the problem.
Click to expand...
Click to collapse
it will

rishivg said:
it will
Click to expand...
Click to collapse
The firmware will only re-lock your bootloader in that case if it's of the same or newer patch level as your bootloader. Older firmwares, as Gingernut78 pointed out, will get you back to stock, but if you're on the August 2017 patch level (and your bootloader is at the August 2017 patch level as well), you need a August 2017 or later stock ROM to re-lock your bootloader.

rishivg said:
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
Click to expand...
Click to collapse
thank you so much you safe my life:good

rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.

ksvirdi105 said:
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
Click to expand...
Click to collapse
dont flash the bootloader! ignore that command and report!:fingers-crossed:

rishivg said:
dont flash the bootloader! ignore that command and report!:fingers-crossed:
Click to expand...
Click to collapse
Are you sure it will work perfectly. No bricking and stuff?? which commands should i skip.
And once i flash it will i be able to get ota to august patch and relock?

ksvirdi105 said:
Are you sure it will work perfectly. No bricking and stuff??
Click to expand...
Click to collapse
it wont brick your device.. try it out:good:

rishivg said:
it wont brick your device.. try it out:good:
Click to expand...
Click to collapse
Once i flash it will i be able to get ota updates.

ksvirdi105 said:
Once i flash it will i be able to get ota updates.
Click to expand...
Click to collapse
lock your bootloader, you ll get updates but not security updates.. I dont know why? Need some help from developers

Lost biometric sensor

I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?

eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work

Be careful to do not downgrade your bootloader though.
This tutorial helped me to recover biometrics in my phone (XT1676, reteu, 3/16, DualSIM).
I am not responsible for any damage! If you proceed to follow this, you're doing it at your own risk.
1. Make sure, your adb and fastboot is working.
I recommend using this one https://forum.xda-developers.com/showthread.php?t=2588979 . For me, it's fully working on Win8.1 x64. If you install it (press "Y" for all of 3 questions), but after connecting phone you see "Fastboot cedric S" with yellow exclamation mark in device manager, there's problem with driver: right click on it --> "Update driver software" --> "Browse my computer for driver software" --> "Let me pick from a list of device drivers on my computer" --> "Android devices" --> "Android Bootloader Interface" --> "Next" --> "OK" --> "Close"
(Open cmd and use "cd" command to get to directory, where's adb installed (in this case "cd C:\adb"). Then, press Enter and type "Fastboot devices". If fastboot is properly installed with corresponding drivers, you will see your device listed.)
2. Download this firmware https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view and extract it to the same directory as adb is installed.
3. Boot your phone into fastboot mode by pressing and holding power and vol- buttons for few seconds.
4. NOW, THE MOST IMPORTANT PART! Check your bootloader version.
4a. If your bootloader version is B8.25, use these commands to flash:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
4b. If your bootloader is B8.24 and lower, use these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
5. Your phone should reboot and sucessfully boot into OS in few minutes with fingerprint working.
DON'T EVEN TRY TO TAKE OTA UPDATES.
6. (optional) However, if you want to update your phone, update it manually with correct files from this site https://forum.xda-developers.com/g5/how-to/cedric-ota-archive-t3795275

Moto g5, has a biometric sensor?

666km666 said:
Moto g5, has a biometric sensor?
Click to expand...
Click to collapse
Of course, it has (fingerprint sensor at the front, under the display).

johnnywilly16 said:
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Click to expand...
Click to collapse
Sorry I'm just confirming that I need to go to stock 7.0 first? Will the debloated stock 7.0 be good enough?

eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
For anyone who finds this there is a flastable Nougat zip for Cedric which fixes finger print scanner, it is in the same thread as the soak 8.1 zip. I hope this saves others trouble as it did me. Find direct answers in telegram:
@cedricNOOBchat

Vivo OriginOS to FunTouch (And reverse)

THIS WILL WIPE YOUR DATA!
YOU MIGHT BRICK YOUR PHONE!
MAKE. A. BACKUP!!!
THIS IS A GENERAL GUIDE BASED ON THE x70 PRO PLUS AND NEEDS A LOT OF MODIFICATIONS FOR YOUR DEVICE.​
Requirements:
- Unlocked Bootloader: Guide I, Guide II
- Root to extract boot.img and recovery.img (and make a backup)
- Android Image Kitchen (AIK)
- QFIL / Split image of your target firmware
- OTA Firmware with a higher version than your Split Image
I. Root your phone ​You should backup all partitions either through magisk (if you have the current running firmware as ota.zip) or LineageOS GSI with me.phh.superuser.apk
The backup commands for the Vivo x70 Pro+ and a general guide can be found in the linked post.
If you have another device use adb to find your blocks and their proper partition names and modify the "script" from my post.
Code:
adb shell
ls -al /dev/block/by-name/
Do NOT backup userdata and sda.
II. Modify recovery​In order to enable adb in recovery we have to unpack the recovery.img and change some prop.default values. (You got this recovery.img either by backing up your partitions or having the correct ota.zip)
THIS post has a great guideline, you can skip everything TWRP related.
In Short:
1. Use AIK to unpack recovery.img
2. Delete the /split_img/*ramdisk*.zip ONLY
3. Open /ramdisk/default.prop or /ramdisk/prop.default or similar with a text editor
4. Modify according to step 22 in the linked post (care vivo uses adb.secure=1 two times, edit both properties)
5. Save, repack and flash the new recovery.img
III. Folder Structure​1. Create a new folder "transform" on your system and extract your SPLIT firmware files into a subfolder called "split". -> /transform/split/
First off identify your super_x.img files and their corresponding dynamic partitions. In general "system" should be the largest, "vendor" the second largest and odm / oem should be smaller.
You can open them with 7zip and identify their contents. Take note.
For the X70 Pro+: super_2.img = system | super_3.img = vendor | super_4.img = odm
2. Open these files in your ota.zip: /dynamic_partitions_op_list and /oem/dynamic_partitions_op_list.
Take note of the partition sizes for system, vendor, odm and vgc (ex. # Grow partition system from 0 to 5373415424).
3. Rename your OTA file to ota.zip and put it into /transform/ota/
IV. Modified Images​1. Download the attached misc-data.img and place it in /transform/modded/ (Thanks to @Pervokur).
If you flash this it tells recovery to look for "ota.zip" in /data/ on the next boot and install it if its available.
You can edit the path via hex editor but its fine for this guide. Dont flash it yet.
2. Patch the recovery.img from /transform/split/ according to step II and place it in /transform/modded/recovery-adb.img
V. Modify the flash script​1. Download my reference script and place it as info.txt into /transform/. Modify this script according to the files from your SPLIT firmware and your partition backups. Vivo phones with different hardware versions might be way more complicated. Analyze everything and take your time - you dont want to brick your device.
PAY ATTENTION: In the best case and at the very least you will have to modify vbmeta_oem, vbmeta_vgc, system, vendor, odm, oem and vgc to match your files.
DO NOT flash your fsg partition. This one basically contains your modem. If you do flash it or if you dont have signal after an ota update scroll down.
2. Go to "::RECREATE DYNAMIC PARTITIONS" and modify the partition sizes according to the values of III.2.
Code:
::OPEN A SHELL IN THIS FOLDER
::REBOOT YOUR PHONE INTO FASTBOOT (REBOOT AND HOLD POWER + VOL UP)
fastboot reboot bootloader
fastboot flash abl split/abl.elf
fastboot flash aop split/aop.mbn
fastboot flash boot split/boot.img
fastboot flash bluetooth split/BTFM.bin
fastboot flash cpucp split/cpucp.elf
fastboot flash devcfg split/devcfg.mbn
fastboot flash apdp split/dp_AP_signed_minidump.mbn
fastboot flash dsp split/dspso.bin
fastboot flash dtbo split/dtbo.img
fastboot flash factory split/factory.img
fastboot flash featenabler split/featenabler.mbn
fastboot flash storage split/firmware.bin
fastboot flash hyp split/hypvm.mbn
fastboot flash keymaster split/km41.mbn
fastboot flash logfs split/logfs_ufs_8mb.bin
fastboot flash mdcompress split/mdcompress.mbn
fastboot flash metadata split/metadata.img
::fastboot flash modemst1 split/modemst.mbn
::fastboot flash modemst2 split/modemst.mbn
fastboot flash multiimgoem split/multi_image.mbn
::fastboot flash fsg split/PD2145F_EX_fs_image.tar.gz.mbn.img
fastboot flash persist split/persist.img
fastboot flash qupfw split/qupv3fw.elf
fastboot flash recovery modded/recovery-adb.img
fastboot flash rtice split/rtice.mbn
fastboot flash secdata split/sec.elf
fastboot flash shrm split/shrm.elf
fastboot flash spunvm split/spunvm.bin
fastboot flash storsec split/storsec.mbn
fastboot flash tz split/tz.mbn
fastboot flash uefisecapp split/uefi_sec.mbn
fastboot flash vbmeta split/vbmeta.img
fastboot flash vbmeta_oem split/vbmeta_oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vbmeta_system split/vbmeta_system.img
fastboot flash vbmeta_vgc split/vbmeta_vgc_NULL_PD2145F_EXMA.img
fastboot flash vendor_boot split/vendor_boot.img
fastboot flash vm-bootsys split/vm-bootsys.img
fastboot flash vgc split/vgc.img
fastboot flash xbl_config split/xbl_config.elf
fastboot flash xbl split/xbl.elf
fastboot flash xbl_configbak split/xbl_config.elf
fastboot flash xblbak split/xbl.elf
fastboot flash modem split/NON-HLOS.bin
::RECREATE DYNAMIC PARTITIONS
fastboot reboot fastboot
fastboot delete-logical-partition system
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm
fastboot delete-logical-partition vgc
fastboot create-logical-partition system 5373415424
fastboot create-logical-partition vendor 3128008704
fastboot create-logical-partition odm 1392640
fastboot create-logical-partition vgc 348160
::FLASH DYNAMIC PARTITIONS
::VGC WILL OUTPUT AN ERROR - DONT MIND
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot erase odm
fastboot erase oem
fastboot erase vgc
fastboot flash system split/super_2.img
fastboot flash vendor split/super_3.img
fastboot flash odm split/super_4.img
fastboot flash oem split/oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vgc split/vgc_NULL_PD2145F_EXMA.img
fastboot reboot recovery
::IF IT DOESNT REBOOT JUST USE THE BUTTON ON YOUR PHONE
::NOW GO TO WIPE AND WIPE DATA & CACHE 2X
::CHECK SYSTEM -> RECOVERY SHOULD FAIL, EVERYTHING ELSE PASS
adb push ota/ota.zip /data
adb reboot bootloader
fastboot flash misc modded/misc-data.img
fastboot reboot
::LET THE PHONE START ONCE (ABOUT 1-5MIN)
::YOU ARE NOW ON FUNTOUCH
--------------------------------------------------------------------------
::YOU CAN BACKUP OTA PACKAGES FROM HERE WHEN THEY ARE DOWNLOADED (ROOT ONLY)
/data/vivo-updater/com.bbk.updater/OTAPackage/
::UPDATE TO THE LATEST VERSION VIA OTA ONLY AFTER YOU BACKUP THE OTA
::YOU MUST FLASH YOUR ORIGINAL BOOT.IMG BEFORE UPDATING
VI. Run the commands according to your modified flash script.​​VII. Problems​1. Brick?
Flash all partitions from your backup
2. No signal?
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg your-original-backup-fsg.img
3. DM-Verity Warning?
Code:
adb shell service call package 134 s16 com.vivo.daemonService i32 0 i32 0
Might be different for you but try it.
4. Fingerprint not working?
Try this post.
Huge thanks to @Pervokur for finding the bootloader exploit, guiding me through this and providing help all the way!

In general there should be an easier method without having to flash a lot of things. This is hypothetical information:
Vivo Recovery looks for device identifiers in the following locations:
Code:
/vgc/env.prop ro.*
/vendor/vgc/vendor_env.prop ro.*
/vgc/vgc.prop ro.*
/vendor/vgc/vgc.prop ro.*
/oem/oem.prop ro.*
/recovery/prop.default
/default.prop
/prop.default
If we mod the recovery of our target firmware by removing all import functions from prop.default and apply the adb fixes from post 1 we should in theory be able to fake our device identifiers for the ota.zip.
In order to boot the target firmware recovery we also need to flash boot, vendor_boot, vbmeta and dtbo from the target firmware.
Then we adb push ota.zip to data, flash misc-data and reboot to flash the ota update.
This is just a theory at the moment, if you feel adventurous you can try it and report back.

Sir, I try your way to flash x80pro, cannot boot in system...
CHECK SYSTEM in recovery show system check fail....
I'm sure the super_5 is system because it is the largest.
Use 7z check it, have system folder inside.

May work for VIVO IQOO 9 Pro also ?

i have the x70pro+ unlocked bootloader, backup the partition and modify recovery, the next step is about the ota.zip and flashing. Can you give me more details about those steps? Killuminati91. Many tks sir

NHQ Thang said:
i have the x70pro+ unlocked bootloader, backup the partition and modify recovery, the next step is about the ota.zip and flashing. Can you give me more details about those steps? Killuminati91. Many tks sir
Click to expand...
Click to collapse
This is as far as I got to on my x70pp, not sure how to make a split rom but assume it needs to be from the funtouch rom (but not the newest release)?

Killuminati91 said:
THIS WILL WIPE YOUR DATA!
YOU MIGHT BRICK YOUR PHONE!
MAKE. A. BACKUP!!!
THIS IS A GENERAL GUIDE BASED ON THE x70 PRO PLUS AND NEEDS A LOT OF MODIFICATIONS FOR YOUR DEVICE.​
Requirements:
- Unlocked Bootloader: Guide I, Guide II
- Root to extract boot.img and recovery.img (and make a backup)
- Android Image Kitchen (AIK)
- QFIL / Split image of your target firmware
- OTA Firmware with a higher version than your Split Image
I. Root your phone ​You should backup all partitions either through magisk (if you have the current running firmware as ota.zip) or LineageOS GSI with me.phh.superuser.apk
The backup commands for the Vivo x70 Pro+ and a general guide can be found in the linked post.
If you have another device use adb to find your blocks and their proper partition names and modify the "script" from my post.
Code:
adb shell
ls -al /dev/block/by-name/
Do NOT backup userdata and sda.
II. Modify recovery​In order to enable adb in recovery we have to unpack the recovery.img and change some prop.default values. (You got this recovery.img either by backing up your partitions or having the correct ota.zip)
THIS post has a great guideline, you can skip everything TWRP related.
In Short:
1. Use AIK to unpack recovery.img
2. Delete the /split_img/*ramdisk*.zip ONLY
3. Open /ramdisk/default.prop or /ramdisk/prop.default or similar with a text editor
4. Modify according to step 22 in the linked post (care vivo uses adb.secure=1 two times, edit both properties)
5. Save, repack and flash the new recovery.img
III. Folder Structure​1. Create a new folder "transform" on your system and extract your SPLIT firmware files into a subfolder called "split". -> /transform/split/
First off identify your super_x.img files and their corresponding dynamic partitions. In general "system" should be the largest, "vendor" the second largest and odm / oem should be smaller.
You can open them with 7zip and identify their contents. Take note.
For the X70 Pro+: super_2.img = system | super_3.img = vendor | super_4.img = odm
2. Open these files in your ota.zip: /dynamic_partitions_op_list and /oem/dynamic_partitions_op_list.
Take note of the partition sizes for system, vendor, odm and vgc (ex. # Grow partition system from 0 to 5373415424).
3. Rename your OTA file to ota.zip and put it into /transform/ota/
IV. Modified Images​1. Download the attached misc-data.img and place it in /transform/modded/ (Thanks to @Pervokur).
If you flash this it tells recovery to look for "ota.zip" in /data/ on the next boot and install it if its available.
You can edit the path via hex editor but its fine for this guide. Dont flash it yet.
2. Patch the recovery.img from /transform/split/ according to step II and place it in /transform/modded/recovery-adb.img
V. Modify the flash script​1. Download my reference script and place it as info.txt into /transform/. Modify this script according to the files from your SPLIT firmware and your partition backups. Vivo phones with different hardware versions might be way more complicated. Analyze everything and take your time - you dont want to brick your device.
PAY ATTENTION: In the best case and at the very least you will have to modify vbmeta_oem, vbmeta_vgc, system, vendor, odm, oem and vgc to match your files.
DO NOT flash your fsg partition. This one basically contains your modem. If you do flash it or if you dont have signal after an ota update scroll down.
2. Go to "::RECREATE DYNAMIC PARTITIONS" and modify the partition sizes according to the values of III.2.
Code:
::OPEN A SHELL IN THIS FOLDER
::REBOOT YOUR PHONE INTO FASTBOOT (REBOOT AND HOLD POWER + VOL UP)
fastboot reboot bootloader
fastboot flash abl split/abl.elf
fastboot flash aop split/aop.mbn
fastboot flash boot split/boot.img
fastboot flash bluetooth split/BTFM.bin
fastboot flash cpucp split/cpucp.elf
fastboot flash devcfg split/devcfg.mbn
fastboot flash apdp split/dp_AP_signed_minidump.mbn
fastboot flash dsp split/dspso.bin
fastboot flash dtbo split/dtbo.img
fastboot flash factory split/factory.img
fastboot flash featenabler split/featenabler.mbn
fastboot flash storage split/firmware.bin
fastboot flash hyp split/hypvm.mbn
fastboot flash keymaster split/km41.mbn
fastboot flash logfs split/logfs_ufs_8mb.bin
fastboot flash mdcompress split/mdcompress.mbn
fastboot flash metadata split/metadata.img
::fastboot flash modemst1 split/modemst.mbn
::fastboot flash modemst2 split/modemst.mbn
fastboot flash multiimgoem split/multi_image.mbn
::fastboot flash fsg split/PD2145F_EX_fs_image.tar.gz.mbn.img
fastboot flash persist split/persist.img
fastboot flash qupfw split/qupv3fw.elf
fastboot flash recovery modded/recovery-adb.img
fastboot flash rtice split/rtice.mbn
fastboot flash secdata split/sec.elf
fastboot flash shrm split/shrm.elf
fastboot flash spunvm split/spunvm.bin
fastboot flash storsec split/storsec.mbn
fastboot flash tz split/tz.mbn
fastboot flash uefisecapp split/uefi_sec.mbn
fastboot flash vbmeta split/vbmeta.img
fastboot flash vbmeta_oem split/vbmeta_oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vbmeta_system split/vbmeta_system.img
fastboot flash vbmeta_vgc split/vbmeta_vgc_NULL_PD2145F_EXMA.img
fastboot flash vendor_boot split/vendor_boot.img
fastboot flash vm-bootsys split/vm-bootsys.img
fastboot flash vgc split/vgc.img
fastboot flash xbl_config split/xbl_config.elf
fastboot flash xbl split/xbl.elf
fastboot flash xbl_configbak split/xbl_config.elf
fastboot flash xblbak split/xbl.elf
fastboot flash modem split/NON-HLOS.bin
::RECREATE DYNAMIC PARTITIONS
fastboot reboot fastboot
fastboot delete-logical-partition system
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm
fastboot delete-logical-partition vgc
fastboot create-logical-partition system 5373415424
fastboot create-logical-partition vendor 3128008704
fastboot create-logical-partition odm 1392640
fastboot create-logical-partition vgc 348160
::FLASH DYNAMIC PARTITIONS
::VGC WILL OUTPUT AN ERROR - DONT MIND
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot erase odm
fastboot erase oem
fastboot erase vgc
fastboot flash system split/super_2.img
fastboot flash vendor split/super_3.img
fastboot flash odm split/super_4.img
fastboot flash oem split/oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vgc split/vgc_NULL_PD2145F_EXMA.img
fastboot reboot recovery
::IF IT DOESNT REBOOT JUST USE THE BUTTON ON YOUR PHONE
::NOW GO TO WIPE AND WIPE DATA & CACHE 2X
::CHECK SYSTEM -> RECOVERY SHOULD FAIL, EVERYTHING ELSE PASS
adb push ota/ota.zip /data
adb reboot bootloader
fastboot flash misc modded/misc-data.img
fastboot reboot
::LET THE PHONE START ONCE (ABOUT 1-5MIN)
::YOU ARE NOW ON FUNTOUCH
--------------------------------------------------------------------------
::YOU CAN BACKUP OTA PACKAGES FROM HERE WHEN THEY ARE DOWNLOADED (ROOT ONLY)
/data/vivo-updater/com.bbk.updater/OTAPackage/
::UPDATE TO THE LATEST VERSION VIA OTA ONLY AFTER YOU BACKUP THE OTA
::YOU MUST FLASH YOUR ORIGINAL BOOT.IMG BEFORE UPDATING
VI. Run the commands according to your modified flash script.​​VII. Problems​1. Brick?
Flash all partitions from your backup
2. No signal?
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg your-original-backup-fsg.img
3. DM-Verity Warning?
Code:
adb shell service call package 134 s16 com.vivo.daemonService i32 0 i32 0
Might be different for you but try it.
4. Fingerprint not working?
Try this post.
Huge thanks to @Pervokur for finding the bootloader exploit, guiding me through this and providing help all the way!
Click to expand...
Click to collapse
Hi. I'm very much a noob in dealing with flashing and those stuff. Is there an easier way to do this? Some way that will be idiot-proof?
I currently have a x70pro+ with originOs Ocean and an unlocked bootloader (I think?), do I still need to root to do this process?
Thank you for sharing

edcsxz said:
Sir, I try your way to flash x80pro, cannot boot in system...
CHECK SYSTEM in recovery show system check fail....
I'm sure the super_5 is system because it is the largest.
Use 7z check it, have system folder inside.
Click to expand...
Click to collapse
Which files do you use for QFIL or split image and OTA firmware?

Development Unofficial Lineageos 19.1 for capri moto g10 and moto g10 power

!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot

thanks for the amazing work on this rom

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you, guys, for your awesome work. Hope we'll get a stable update. Good luck

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
So installed fine on a G10 now the problem is a lack of google apps I want it and I need magisk for half the apps to to add a custom way to run apps that need root.
I cannot get gapps on it for starters as can't go into a recovery menu it's twrp I need to do all this with and the recovery on this is stock really, I will say though that is is an amazing firmware I mean really clean brilliant work but I must have twrp so I can root but also so I can add google apps which is my primary necessity root is a distant second if at all needed i do newed my apps to make images and other tools I use it for daily driver wise.
l Tried to use this TWRP https://cloudhazy.com/download/motorola-moto-g10-xt2127-2-twrp-recovery-3-5-2/ and it fails but I know the model number XT2127-2 is correct so it just doesn't allow installing or launching it, from inside platform tools openeing in a command window here mode????
I am stuck completely now.

@PHYSC-1 you should be able to find magisk inside the attached lineageos zip. Flash that to boot and you should be rooted. I am working on gapps and dual sim currently. Also, don't feel like you are stuck. At any moment, you can flash the stock firmware and go back to stock if you are not able to daily drive lineage os without gapps.
I don't want to have gapps on my phone so I didn't work on it at all until now. I see that many people are asking for gapps, so giving it a try.
In case you don't find the magisk boot image in the lineage os zip, you can create one yourself by installing magisk app and passing this lineageos boot image to it.

@PHYSC-1 we are testing gapps on this ROM now. Me and two users present on our group are testing GAPPS on this ROM. As of now, its running smooth, will publish the update in a week or so.

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you for this work! I'm also anxious to get a stable, dual chip working version too.

I think the Gapps should be separate to ROM. Of course if it is possible.

Gapps works 2 problems found in testing 1 is a big one for anyone using screen cast the network auto switches from 2.4ghz to 5ghz and back intermittently causing screen cast to drop out mid use and this stuns it and creates constant bad image quality and freezing completely up.
Secondly this could be unrelated to the OS but it doesn't happen on official Motorola OS's when using the app from F-Droid called simple gallery pro if you edit an image and try to draw on an image the drawing occurs in the wrong position the pointer is below where you draw on?