Database Develop

[Q] problems with fastboot flash boot boot.img

Hi,
I'm trying to flash boot.img into my xt890 that I created following the Motorola instructions.
I compiled it and then created the boot.img using:
mkbootimg --kernel bzImage --ramdisk ramdisk.img --output boot.img
After that my boot.img size is 4.3M.
Then I run adb reboot-bootloader and I have my phone on AP fastboot flash mode (secure boot)
Then fastboot devices, works well.
But when I run fastboot flash boot boot.img I get
[email protected]:~/android/out/host/linux-x86/bin$ ./fastboot flash boot boot.img
sending 'boot' (4356 KB)...
OKAY [ 0.682s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 0.946s
and on the phone :
Downloading
Invalid image size for partition boot
Fastboot command failed
Any help would be greatly appreciated

Best way to remove "Unlocked Bootloader Warning" and /or "bad key" upon startup?

Best way to remove "Unlocked Bootloader Warning" and /or "bad key" upon startup?
Have an unlocked rooted Moto G6 (standard) and was wondering whats the current best way to "hide" that the bootloader has been unlocked. I have seen tutorials on replacing it with the "Bad Key" notification, is there a way to hide or change the "bad key" notification?
Thanks!

Greasebob said:
Have an unlocked rooted Moto G6 (standard) and was wondering whats the current best way to "hide" that the bootloader has been unlocked. I have seen tutorials on replacing it with the "Bad Key" notification, is there a way to hide or change the "bad key" notification?
Thanks!
Click to expand...
Click to collapse
If you flashed magisk and removed dm verity, it should say n/a
But it's always going to say that. No matter what

madbat99 said:
If you flashed magisk and removed dm verity, it should say n/a
But it's always going to say that. No matter what
Click to expand...
Click to collapse
This is the perfect time to bring up something I noticed about that. The N/A screen does not appear when using the command "fastboot boot twrp.img". I don't know how fastboot skips that, but finding out would probably give us a fix.

Spaceminer said:
This is the perfect time to bring up something I noticed about that. The N/A screen does not appear when using the command "fastboot boot twrp.img". I don't know how fastboot skips that, but finding out would probably give us a fix.
Click to expand...
Click to collapse
But it still says bad key when the bootloader is unlocked. I thought removing dmverity changed it to n/a
Are you saying there is no message when you fastboot boot TWRP? That is interesting.

madbat99 said:
But it still says bad key when the bootloader is unlocked. I thought removing dmverity changed it to n/a
Are you saying there is no message when you fastboot boot TWRP? That is interesting.
Click to expand...
Click to collapse
No message at all, it will literally insta-boot twrp. Moto splash, then twrp. It's the only time I get to see the splash. I also never get "bad key" unless dm-verity is enabled. But, if you trip dm-verity and then disable it later, I think "bad key" will still show up. Pretty sure that happened to me, and booting the stock recovery then flashing twrp again fixed it. My memory is a bit fuzzy, but I think that's what happened. I noticed the fastboot thing when I was doing all that work on twrp.
Edit: Didn't mean to repeat what you already knew about dm-verity. I missed that some how. I'm going try grep on the bootloader and hopefully snoop some info about it.

madbat99 said:
If you flashed magisk and removed dm verity, it should say n/a
But it's always going to say that. No matter what
Click to expand...
Click to collapse
Can you please explain to me how to do that? I did flash magisk and the phone is rooted. I just want to remove that warning screen, can you please direct me how to do this? Im not sure what it means to remove dm verity.

Greasebob said:
Can you please explain to me how to do that? I did flash magisk and the phone is rooted. I just want to remove that warning screen, can you please direct me how to do this? Im not sure what it means to remove dm verity.
Click to expand...
Click to collapse
Magisk should have removed dmverity already. It should say n/a instead of bad key. But I don't know what steps you took to root so I can't say. Mine now says "n/a" in notification. It's always going to have a message. It's just the way it is.

You can Change the "Orange" Logo in the Logo.bin with some image with MotoBootLogoMaker. Then flash it via adb fastboot.
I Use this image, and the annoying "warning bootloader unlocked" dissapear
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

madbat99 said:
Magisk should have removed dmverity already. It should say n/a instead of bad key. But I don't know what steps you took to root so I can't say. Mine now says "n/a" in notification. It's always going to have a message. It's just the way it is.
Click to expand...
Click to collapse
Mine still boots with the Motorola "Device has been unlocked and cant be trusted" screen. Its a standard G6 model. Steps I took to root were to unlock bootloader, install TWRP and new boot image, and then run Magisk. I then downloaded rootchecker from Google play and it indeed says the phone is rooted.
So Im good to just push the new screenshot binary with ADB fastboot? Is it any easier or better to do it with TWRP as some are saying? Also, if so, how would one do it with TWRP?
Thanks my friend!

Yiyotop said:
You can Change the "Orange" Logo in the Logo.bin with some image with MotoBootLogoMaker. Then flash it via adb fastboot.
I Use this image, and the annoying "warning bootloader unlocked" dissapear
Click to expand...
Click to collapse
What directory is the Logo.bin located in the phone? Is is in root? Also, what is the command to flash via adb fastboot?
Thanks!

Greasebob said:
What directory is the Logo.bin located in the phone? Is is in root? Also, what is the command to flash via adb fastboot?
Thanks!
Click to expand...
Click to collapse
Fastboot flash logo.bin

madbat99 said:
Fastboot flash logo.bin
Click to expand...
Click to collapse
Im getting the following when I try to flash the logo.bin:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo.bin
< waiting for any device >
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_b logo.bin
target reported max download size of 534773760 bytes
sending 'logo_b' (1436 KB)...
OKAY [ 0.050s]
writing 'logo_b'...
(bootloader) Invalid partition name logo_b
FAILED (remote failure)
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_a logo.bin
target reported max download size of 534773760 bytes
sending 'logo_a' (1436 KB)...
OKAY [ 0.040s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.040s
Apparently the logo is in a different directory? Can you help with this?

Greasebob said:
Im getting the following when I try to flash the logo.bin:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo.bin
< waiting for any device >
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_b logo.bin
target reported max download size of 534773760 bytes
sending 'logo_b' (1436 KB)...
OKAY [ 0.050s]
writing 'logo_b'...
(bootloader) Invalid partition name logo_b
FAILED (remote failure)
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_a logo.bin
target reported max download size of 534773760 bytes
sending 'logo_a' (1436 KB)...
OKAY [ 0.040s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.040s
Apparently the logo is in a different directory? Can you help with this?
Click to expand...
Click to collapse
Nevermind I got it! fastboot flash logo logo.bin worked! Now my screen works like a charm!!!!

Greasebob said:
Im getting the following when I try to flash the logo.bin:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo.bin
< waiting for any device >
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_b logo.bin
target reported max download size of 534773760 bytes
sending 'logo_b' (1436 KB)...
OKAY [ 0.050s]
writing 'logo_b'...
(bootloader) Invalid partition name logo_b
FAILED (remote failure)
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo_a logo.bin
target reported max download size of 534773760 bytes
sending 'logo_a' (1436 KB)...
OKAY [ 0.040s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.040s
Apparently the logo is in a different directory? Can you help with this?
Click to expand...
Click to collapse
Greasebob said:
Nevermind I got it! fastboot flash logo logo.bin worked! Now my screen works like a charm!!!!
Click to expand...
Click to collapse
Great, Now Enjoy It! :good::good:

Greasebob said:
Nevermind I got it! fastboot flash logo logo.bin worked! Now my screen works like a charm!!!!
Click to expand...
Click to collapse
Where can download the Motorola boot logo maker? I can't find it anywhere on XDA. I get one thread result, which just links to source code for it.
Edit: Think I just found it. Is there a newer one than from 2015?

Spaceminer said:
Where can download the Motorola boot logo maker? I can't find it anywhere on XDA. I get one thread result, which just links to source code for it.
Edit: Think I just found it. Is there a newer one than from 2015?
Click to expand...
Click to collapse
I dont know, I just used one of the pretty logo.bin files provided a few pages back, on my standard Moto G6. It worked fine with the proper command, lol.

Greasebob said:
I dont know, I just used one of the pretty logo.bin files provided a few pages back, on my standard Moto G6. It worked fine with the proper command, lol.
Click to expand...
Click to collapse
How can I use adb to pull logo.bin from my G6? Thank you for the help.

raginhomosapien said:
How can I use adb to pull logo.bin from my G6? Thank you for the help.
Click to expand...
Click to collapse
While in twrp use: "adb pull /dev/block/bootdevice/by-name/logo stocklogo.bin" to dump the stock logo.
Open that up in the editor, dump the normal bootlogo to png, replace the "orange"-logo with the normal bootlogo image, save the logo as a bin.
Finnaly flash the new logo with "fastboot flash logo newlogo.bin"

Slowking said:
While in twrp use: "adb pull /dev/block/bootdevice/by-name/logo stocklogo.bin" to dump the stock logo.
Open that up in the editor, dump the normal bootlogo to png, replace the "orange"-logo with the normal bootlogo image, save the logo as a bin.
Finnaly flash the new logo with "fastboot flash logo newlogo.bin"
Click to expand...
Click to collapse
i did this warning text remains only backround is changed. i replaced orabge 1 and orange 2 images with motorola image and still text is visible I am 100 percent positive that this software will not work for mororola edge 30...

[ROM][SOFIA*/RAV*][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : [URL]https://t.me/MotoG8Official[/URL]
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G8
Contributors
vache
Source Code: [URL]https://github.com/omnirom/[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28

This should be flashable via TWRP. Trying to install via method described only partially installs on A/B filesystem. Download link broken.

swear000 said:
This should be flashable via TWRP. Trying to install via method described only partially installs on A/B filesystem. Download link broken.
Click to expand...
Click to collapse
Since when twrp is mandatory to flash a ROM ?
I don't get what do you mean by partially. And link is working fine.
Edit: my bad, link was broken, updated.

flashed all of this twice and it just boots to twrp and asks for a password not i did flash twrp first from the other forum for the moto g fast

Clothian said:
flashed all of this twice and it just boots to twrp and asks for a password not i did flash twrp first from the other forum for the moto g fast
Click to expand...
Click to collapse
Make sure you have downloaded the build after I updated the link.
About twrp asking for password, expected behaviour after a data format without booting a ROM to populate encryption bits.

Ok so I just flashed back to stock and started over but now it just reboots on repeat I’m going to try to reset everything again and start over
---------- Post added at 06:42 PM ---------- Previous post was at 06:22 PM ----------
Clothian said:
Ok so I just flashed back to stock and started over but now it just reboots on repeat I’m going to try to reset everything again and start over
Click to expand...
Click to collapse
i figured out while flashing its saying no such file or directory on system and product but flashes boot and vbmeta just fine

Clothian said:
Ok so I just flashed back to stock and started over but now it just reboots on repeat I’m going to try to reset everything again and start over
---------- Post added at 06:42 PM ---------- Previous post was at 06:22 PM ----------
i figured out while flashing its saying no such file or directory on system and product but flashes boot and vbmeta just fine
Click to expand...
Click to collapse
You're not in fastbootd mode as detailed in OP.

Debugging
vache said:
Since when twrp is mandatory to flash a ROM ?
I don't get what do you mean by partially. And link is working fine.
Edit: my bad, link was broken, updated.
Click to expand...
Click to collapse
Sending 'boot_a' (65536 KB) OKAY [ 2.481s]
Writing 'boot_a' OKAY [ 0.939s]
Finished. Total time: 3.420s
Sending sparse 'system' 1/2 (781344 KB) OKAY [ 27.651s]
Writing sparse 'system' 1/2 (bootloader) Invalid partition name system
FAILED (remote: '')
Finished. Total time: 27.777s
Sending sparse 'product' 1/2 (781344 KB) OKAY [ 29.659s]
Writing sparse 'product' 1/2 (bootloader) Invalid partition name product
FAILED (remote: '')
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 4
OKAY [ 0.010s]
Finished. Total time: 0.014s

swear000 said:
Sending 'boot_a' (65536 KB) OKAY [ 2.481s]
Writing 'boot_a' OKAY [ 0.939s]
Finished. Total time: 3.420s
Sending sparse 'system' 1/2 (781344 KB) OKAY [ 27.651s]
Writing sparse 'system' 1/2 (bootloader) Invalid partition name system
FAILED (remote: '')
Finished. Total time: 27.777s
Sending sparse 'product' 1/2 (781344 KB) OKAY [ 29.659s]
Writing sparse 'product' 1/2 (bootloader) Invalid partition name product
FAILED (remote: '')
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 4
OKAY [ 0.010s]
Finished. Total time: 0.014s
Click to expand...
Click to collapse
Something wrong on your side, make sure you're in fastbootd mode and you have the latest fastbootd binary.

Magisk
vache said:
Something wrong on your side, make sure you're in fastbootd mode and you have the latest fastbootd binary.
Click to expand...
Click to collapse
I installed Magisk and TWRP. TWRP is not required to flash all ROMs, it just works better under normal situations.

vache said:
Something wrong on your side, make sure you're in fastbootd mode and you have the latest fastbootd binary.
Click to expand...
Click to collapse
I also have the same problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.114s]
writing 'boot_a'...
OKAY [ 0.526s]
finished. total time: 2.643s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (786384 KB)...
OKAY [ 27.157s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 27.163s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\product.img
target reported max download size of 805259264 bytes
sending sparse 'product' 1/2 (786384 KB)...
OKAY [ 27.608s]
writing 'product' 1/2...
(bootloader) Invalid partition name product
FAILED (remote failure)
finished. total time: 27.617s
I tried it on a G8 bike and in power both teams make me the same mistake

SilverKaito said:
I also have the same problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 2.114s]
writing 'boot_a'...
OKAY [ 0.526s]
finished. total time: 2.643s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (786384 KB)...
OKAY [ 27.157s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 27.163s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product C:\Users\Desu\Downloads\omni-10-20200823-sofia-rav-IMG\product.img
target reported max download size of 805259264 bytes
sending sparse 'product' 1/2 (786384 KB)...
OKAY [ 27.608s]
writing 'product' 1/2...
(bootloader) Invalid partition name product
FAILED (remote failure)
finished. total time: 27.617s
I tried it on a G8 bike and in power both teams make me the same mistake
Click to expand...
Click to collapse
Are you in fastboot or fastbootd?
To get into fastbootd, you need to type
'fastboot reboot fastboot' in a cmd window while you are in the regular fastboot screen.
Then flash the rom.

Beetle84 said:
Are you in fastboot or fastbootd?
To get into fastbootd, you need to type
'fastboot reboot fastboot' in a cmd window while you are in the regular fastboot screen.
Then flash the rom.
Click to expand...
Click to collapse
you're right I'm already let myself install the rom but it doesn't just start it turns on and turns off

omnirom
OmniROM and twrp works correctly thanks I want to modify the volume of the headphones vendor / etc / mixer_path.xml when I save changes it tells me an error occurred, the changes will not be saved, could you help me thanks

Headphones
swear000 said:
I installed Magisk and TWRP. TWRP is not required to flash all ROMs, it just works better under normal situations.
Click to expand...
Click to collapse
good afternoon onmi rom and twrp root works correctly I want to increase the volume of the headphones vendor / etc mixerpath when saving changes I get an error some solution thanks

Couldn't get this working. Probably because my rav is LATAM distribution (rav, not rav_t). When flashed from fastbootd, I got a bootloop. Thankfully TWRP is working fine, so I could boot stock from the other A/B slot.

Success!
I had a number of issues while flashing this, as follows:
- I flashed TWRP before doing anything to attempt to flash Omni. As it turns out, fastbootd doesn't work correctly with TWRP installed, so I had to restore to stock before trying again.
- The Omni GSI has to be flashed to slot A by doing fastboot set_active a before you try to flash the partitions.
- When flashing the 20200823 build linked in OP, using the instructions listed, I got a "not enough space to resize partition" error. I attempted to resolve this by doing fastboot delete-logical-partition system_a and fastboot delete-logical-partition product_a - this was the wrong thing to do as it caused an issue mentioned earlier in the thread ("no such file or directory" when trying to flash those partitions), and I restored to stock to resolve this.
- I was able to get the partitions flashed by doing them in a different order than listed in OP. I successfully flashed by doing boot, product, system, vbmeta in that order.
- Once the partitions were successfully flashed, rebooting the device caused it to bootloop, showing the Moto logo for a few seconds and immediately rebooting. I resolved this by flashing an older boot.img from the Telegram channel (attached to this post). Flashing the older boot.img with the product, system, and vbmeta from the 20200823 build linked in OP got my device booting.
Thanks to the folks on Telegram for the help in getting this going.

Great work

Fastbootd errors
I cant seem to get any of the files to flash in fastbootd mode
i get this error
remote: No such file or directory
any help would be appreciated

devenkawaler said:
I cant seem to get any of the files to flash in fastbootd mode
i get this error
remote: No such file or directory
any help would be appreciated
Click to expand...
Click to collapse
Have you tried updating your fastboot binary? I used to use minimal adb and fastboot until this device. I had the same issue, and had to update the binary to get it to work properly.

[ROM][ResurrectionRemix 8.6.x][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
​Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​
combination of performance, customization, power and the most new features, brought directly to your Device.​
​
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​
​
​
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
​
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
​

To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.

Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.

I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?

NeoSDAP said:
I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?
Click to expand...
Click to collapse
Try flashing product instead of system first.

Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.

_huck_ said:
Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.
Click to expand...
Click to collapse
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.

I am SO HAPPY that resurrection remix has just come out for the Moto G Power. I have been waiting!!! I just saw this today, but I can't seem to get it to work.. As seems to happen when people are trying to root the moto G power.. The touch screen will stop working.. I did get mine to root, using this page:
Messed up trying to root
i know there are other threads on this topic. But after going through them I cant find the fix. I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works. I used lmsa to download the stock rom...
forum.xda-developers.com
But I do not know how to apply the same fix after I try to install resurrection remix? I do not have touch screen working after I load.
I am using adb, not sure it twrp is available for moto g power yet, and if that would be the way to get it to work?
I'm using moto g power, sofia variant (usa).. XT2041-4

I tried again and I'm actually getting the following errors:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.418s]
writing 'boot'...
OKAY [ 0.821s]
finished. total time: 2.248s
PS C:\adb> fastboot flash system system.img
target reported max download size of 805263360 bytes
sending sparse 'system' (786388 KB)...
OKAY [ 18.732s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.749s
PS C:\adb> fastboot flash product product.img
target reported max download size of 805263360 bytes
sending 'product' (575564 KB)...
OKAY [ 12.511s]
writing 'product'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.539s
PS C:\adb>

@cxskate
You aren't in fastbootd. You are in fastboot mode. From the screen you are at in the above screenshot, type fastboot reboot fastboot.
You should reboot to a new screen with fastbootd in red across the top.
Flash the images there.

I'm still having a problem...
My phone does not enter into FastBootD mode... The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following:
Please any advice? Very much appreciated.
PS C:\adb> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>

Beetle84 said:
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.
Click to expand...
Click to collapse
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!

_huck_ said:
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!
Click to expand...
Click to collapse
Awesome! What are the little things? I'll add to the bug list

I'm going for a Degoogled setup and this rom is the first one that worked with microg without hassles. I installed minMicrog standard and Majisk, toggled the baked in signature spoofing, and was up and running in minutes. VERY AWESOME!

Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks

etienne_9000 said:
Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks
Click to expand...
Click to collapse
Google 'unlock Motorola bootloader'
You need a code from Motorola.

Beetle84 said:
Google 'unlock Motorola bootloader'
You need a code from Motorola.
Click to expand...
Click to collapse
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.

etienne_9000 said:
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.
Click to expand...
Click to collapse
Did you tick the OEM unlock allowed option in developer settings?

Trying to figure out how to load gapps on with adb now??
I actually was finally able to enter FastBootD mode using a different method I found on youtube, but wasvstill getting errors when I tried to flash.. FAILED (remote: No such file or directory)
UPDATE I copied all the new files to the adb folder on the C: drive and i got it to work.. Got RR up and running, but still..
I'm trying to figure out how to load gapps on with adb now??
Method I used to get fastboot D:
(
),

Beetle84 said:
Did you tick the OEM unlock allowed option in developer settings?
Click to expand...
Click to collapse
Yes i did. Just tried again to "fastboot oem get_unlock_data" and still getting "FAILED (remote: Command not supported in default implementation)"

[ROM][RAV*/SOFIA*][11][UNOFFICIAL] SuperiorOS-Xcalibur

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About US:
Superior OS is a AOSP based custom ROM with some minimal features to fulfill the users demands nowadays.
********************************************
UPDATES WILL BE ADDED TO THIS POST EACH MONTH AS MUCH AS POSSIBLE. CHECK FOR UPDATED LINKS! IM UPDATING THE LINKS TO THE FEB PATCH
********************************************
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
***GAPPS ARE INCLUDED IN ROM***
HOW TO INSTALL:
1. Fastboot -w (in bootloader)
2. Flash images
- fastboot reboot fastboot
- fastboot set_active a
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash product product.img
- fastboot flash vbmeta vbmeta.img
3. Reboot
AND THATS IT!
****FLASHING MICROG BUILD****
1. Flash all images (same steps above)
2. Boot into rom
3. Reboot into TWRP
4. Flash magisk
5. Flash microg.zip (included in the link provided)
6. Reboot
New Update:
- Added new thermals from Xiaomi
- Improved RAM management
- Performance Optimizations
- Added Pixel Camera blobs
- Added Miracast
Download ROM:SuperiorOS_May-patch
SuperiorOS Core Team
AOSP
Lineage OS
DirtyUnicorns
PixelExperience
AospExtended
Syberia OS
Nitrogen OS
Pixys OS
@bcrichster
@Beetle84
@asineth
@Rondeau79
@gearsofwar567
@kjjjnob
Special thanks:
@vache
Important Links
Loved the ROM? Want to help it imporove? Gift us with some credits!
Superior OS source
Device Trees: https://github.com/h0pk1do/android_device_motorola_sofiar
Vendor Trees: https://github.com/moto-sm6xxx/android_vendor_motorola_sofiar
Kernel Trees: https://github.com/Odin1101/Project-Sofia
Telegram Group
Telegram Channel
EXPERIENCING BUGS?
PLEASE LET ME KNOW!
SuperiorOS Version Name: Xcalibur
Build Type: UNOFFICIAL
Source Code: SuperiorOS
XDAevDB Information
SuperiorOS A11 sofia*/rav*, ROM for the Moto G8 Family
Contributors
Source Code: https://github.com/SuperiorOS
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2021-01-27
Last Updated 2021-03-26

sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.

fix-this! said:
sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.
Click to expand...
Click to collapse
i just updated the instructions and if you have the latest twrp, don't worry flashing will work

Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s

rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
Okay so two things :
1. For whatever reason it's flashing to the B partition which it shouldn't.
2. You need the latest platform-tools
Before you flash again, fastboot -w and then type
Fastboot set_active a
I'll adjust that in the instructions

Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

rpcribari said:
Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Which device do you have?

rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
XT2041-4

rpcribari said:
XT2041-4
Click to expand...
Click to collapse
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?

Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol

gearsofwar567 said:
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?
Click to expand...
Click to collapse
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)

I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?

rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.

Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.

fix-this! said:
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.
Click to expand...
Click to collapse
I guess I don't understand the difference between fastboot and fastbootd. From TWRP 3.5 I'm going to Reboot then Fastboot.

bitscott84 said:
Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol
Click to expand...
Click to collapse
So basically this:
1. You cannot flash the rom via twrp, you must flash the images per the instructions
2. No you cannot currently make backups with twrp because of dynamic partitions. Still trying to work that out
3. Software defects, that is something you would have to find out for yourself when you flash. The status of the rom said "stable"

rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
Is it not booting?

fix-this! said:
I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?
Click to expand...
Click to collapse
Good to hear and there will be updates. In TWRP, hit the "reboot" tab and the tile That says "fastboot" is the new fastboot built into twrp

halliessed said:
Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.
Click to expand...
Click to collapse
You'll get updates faster than Motorola
January 5th 2021 is latest patch

gearsofwar567 said:
Is it not booting?
Click to expand...
Click to collapse
No it doesn't boot. It just keeps rebooting back to the bootloader.