Database Info

Fastboot GUIDE flashing Stock Properly for OMNI

Before flashing OMNI make sure you have done this:
Click to expand...
Click to collapse
1. Unlock Bootloader
2. boot to twrp
3. If you just unlocked bootloader, you are currently booted to SLOT A.
Now from twrp reboot menu, reboot to SLOT B.
4. Reboot to system. Most probably you already booted to stock ROM with slot B also.
IF
Click to expand...
Click to collapse
You are unable to reboot to stock ROM after booting to slot B, that means the stock ROM is not there.
A error message will come (Your device is corrupt probably)
5. Boot to fastboot again
6. Now please do the procedure to flash the STOCK ROM once again.
(NOTE : Motorola has channels, like brazil, indian and other) Please check which channel your stock ROMs belong to.
If you tried to flash OMNI and it causes device corrupt please follow this guide.
The very purpose of making this thread is a Lot of people including me are facing issues with flashing OMNI. There was this issue where OMNI ROM was not booting properly and showing device corrupt after flashing it. For some it was booting and for some it wasn't. There was nothing clear. A user named @edsoi had done some testing and @vache comes to the conclusion that the commands lying on internet weren't correct that people are using to flash the Stock ROM.
So to streamline the flashing process for all of us, this thread comes to life here. On behalf of @vache i am writing this here. Hope this will be beneficial to all the community, and we can flash OMNI on our devices.
NOTE : Hope you have adb and fastboot working for this guide.
This is manual guide. You need to put each and every command one by one in the Terminal.
Fastboot Commands
fastboot devices (to check if device is detectable from fastboot)
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Click to expand...
Click to collapse

mine

mine too

Very good my friend, I already intended to make a tutorial with such commands, you only told us (I'm @edsoi kkkk)

Edsovn said:
Very good my friend, I already intended to make a tutorial with such commands, you only told us (I'm @edsoi kkkk)
Click to expand...
Click to collapse
Well thanks to your testing. Now its written here. If more users are willing to flash OMNI ROM. It would be great.

is everything working in this ROM? what about bluetooth and NFC etc..?

vietchecz said:
is everything working in this ROM? what about bluetooth and NFC etc..?
Click to expand...
Click to collapse
NFC was just fixed a few days ago. Bluetooth does work, also.

Deleted

SnowTalker said:
NFC was just fixed a few days ago. Bluetooth does work, also.
Click to expand...
Click to collapse
I still only see the omnirom from 13 May.

Join the Telegram Group of the Device that you acquire the new version

lollyjay said:
I still only see the omnirom from 13 May.
Click to expand...
Click to collapse
We have the august security patch now. I have edited the OP with more info. Hope that would be beneficial.

methuselah said:
We have the august security patch now. I have edited the OP with more info. Hope that would be beneficial.
Click to expand...
Click to collapse
Send the version link to him here, good that I copy to some acquaintances too!

methuselah said:
We have the august security patch now. I have edited the OP with more info. Hope that would be beneficial.
Click to expand...
Click to collapse
Judging by the size of the zip, I assume that GApps is not included. Which do you recommend?

lollyjay said:
Judging by the size of the zip, I assume that GApps is not included. Which do you recommend?
Click to expand...
Click to collapse
opengapps pico. I don't like google sucking whole battery in background.

Edsovn said:
Join the Telegram Group of the Device that you acquire the new version
Click to expand...
Click to collapse
how do i join the telegram group to receive the latest version of omni?

Ramaiz said:
how do i join the telegram group to receive the latest version of omni?
Click to expand...
Click to collapse
https://t.me/MotoG8PlusOfficial

Hi, what bluetooth codecs are enabled and available for use with this ROM?
Thanks

I'm sorry if this is a stupid question, but where do I find the files that are needed when flashing the lines manually?

I managed to flash Omni Rom eventually and it runs real smooth. However BT does not work at all, it only keeps crashing
Is this a known issue? is there some sort of quick fix for this?
Everything else works great though so thanks for all the work!
cheers

gustavjhagstrom said:
I managed to flash Omni Rom eventually and it runs real smooth. However BT does not work at all, it only keeps crashing
Is this a known issue? is there some sort of quick fix for this?
Everything else works great though so thanks for all the work!
cheers
Click to expand...
Click to collapse
Go to the Telegram group to see if anyone there can help you.

Phone bricked when installing twrp

Hello guys my phone is stuck in a bootloop because I tried to install twrp from fastboot.
I unlocked bootloader and started Fastboot.
Then I connected my phone to my mac via USB.
Then I ran this commands:
./fastboot flash recovery recovery.img
./fastboot flash vbmeta vbmeta.img
(The mistake I think I made was that I flashed recovery before vbmeta).
Then I restarted my phone and I could not get into android or fastboot.
Please I need help.
This is the tutorial which I used.
Thanks in advance.

Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.

jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)

jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Please do you know how to get the build number of my bricked phone?

mikkyboy said:
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
Click to expand...
Click to collapse
It's not hard to install TWRP to this device

GSI in Xiaomi 12X its possible?

hello friends
I have tried to install GSI Rom on my Xiaomi 12X and it stays on fastboot. According to Treble info it is possible to install GSI on this device but I have never succeeded.
From EU Rom I go into fastboot and run the commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
I reboot into stock recovery and do a format data and reboot
Outcome:
stays in fastboot
Has anyone managed to start any GSI on Xiaomi 12, 12 pro or 12X?
I will be attentive to your comments
Thank you

Oneplus Nord - Android 12 (ColorOS 12) - How to Root

Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?

Any help on rooting ColorOS 12 updated on Oneplus Nord?

Hi, I am undergoing the same issue. But, sort of have an idea how to fix it. Unfortunately I am a bit worried to try it out. I know there is no vendor_boot image to patch. But isn't it the same thing to patch vendor.img? Could you try patching that and let me know of the results?

I tried patching vendor image. There was an error in magosk.

I'm going to try flashing Twrp recovery on the phone and try installing magisk to root it. Will let you know how it goes

No luck, doesn't work for Android 12. Waiting on some update for rooting the Nord

puru said:
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Click to expand...
Click to collapse
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img

This worked. I am still testing though.
Link to canary - https://github.com/topjohnwu/magisk-files/blob/canary/app-debug.apk

Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
Can anyone confirm this does work without having to wipe the entire phone's data?
Thank you

Hi
This works and data is intact.

Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?

robuser007 said:
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
Click to expand...
Click to collapse
Install OOS12, install magisk and patch the boot.img, then boot into the bootloader and type the commands. After an ota, magisk must be installed in the inactive slot.

Does this also work with Magisk v25 released today?

Where can I find those files? I guess I have to move those to the fastboot folder on my pc ?
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img

robuser007 said:
Does this also work with Magisk v25 released today?
Click to expand...
Click to collapse
No, I'm not able to have a bootable magisk patched boot image, also using magisk canary release.
After I flash the patched img the Nord goes in bootloop, the only way to have it working is to flash back original boot.img
About the vbmeta.img & vbmeta_system.img I have used the extracted from payload_output folder, I think is correct?!?

Did you manage to solve this ? I really want to upgrade but not loose root.

I rollback to stable Android 11, I have tested the new version for one day and is graphically bugged everywhere, seems they release a beta, not a stable version.

I rollback to stable Android 11 with Orange Fox recovery, Root, safetynet-fix ok, ecc ecc
I have tested the new version for one day and is graphically bugged everywhere, then no recovery, no root, Color OS seems not for me for the moment.

What do you mean with graphically bugged everywhere ?
How can I stay on having root, does it work with latest canary?

robuser007 said:
Did you manage to solve this ? I really want to upgrade but not loose root.
Click to expand...
Click to collapse
I'm also not upgrading because of 'loose of root"
Still not able to find fix of safety net fix for A12..
all method i tried but safetynet is not fix.... CTS profile always FAILED...
nobody has any method which is working...

Question Flashing GSI LineageOS

Now that I have my IMEI numbers restored, I am going to again attempt to flash LineageOS over my stock Android 9.
Let's say I want the latest revision of LineageOS 18, I understand that this is the required system image;
lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img.xz
I also know a vbmeta file is required. This is where I get confused and suspect it's the reason I always get bootloop when flashing.
Do I need a stock vbmeta, a modified vbmeta or a blank vbmeta? I have quite the collection.
Also do I add flags;
--disable-verity
and / or
--disable-verification
Now last, but not least, is my sequence of flashing correct?
fastboot flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot reboot
I appreciate your time and help.

probably stock vbmeta will work, or get the one in TWRP page for Nokia 2.2