Database Develop

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][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Downloads: https://asineth.me/post/android-rav/
Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
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
If you are on the Moto G8/G Fast and your display cutout is misbehaving, enable your overlay like so:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
I've tested with Magisk v20.4 & OpenGapps Pico, to flash, temporarily boot into TWRP with fastboot.
Working:
Display
Touchscreen
Wi-Fi
Bluetooth (including audio)
Headphones via 3.5mm
Internal Speaker
Moto Actions
Calls/SMS/LTE/VoLTE on Verizon
Issues:
Vibration motor is broken
Stock wallpaper animation (fixed by changing it)
Rav (G8/G Fast) users must enable their overlay manually
Source:
LineageOS
Device tree
Vendor tree
Kernel tree
Telegram:
https://t.me/MotoG8Official
Credits:
@Vachounet - helped a lot, original device/vendor tree, TWRP build
@kjjjnob - some LineageOS changes to @Vachounet's tree
This is my first ROM release, thanks for your guy's help!
XDA:DevDB Information
[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1, ROM for the Moto G8
Contributors
asineth
Source Code: https://git.asineth.gq
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 17.1-20200915
Stable Release Date: 2020-09-14
Created 2020-09-15
Last Updated 2020-09-15

Nice work
Instalation was easy, everuthing is working as described or not working as described.
What would you think about setting your work for Micro G support?

atiolon said:
Instalation was easy, everuthing is working as described or not working as described.
What would you think about setting your work for Micro G support?
Click to expand...
Click to collapse
Might provide microG builds if there's interest.

asineth said:
Might provide microG builds if there's interest.
Click to expand...
Click to collapse
I vote for it.

****ed up, send help.
Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b

FoxySheila said:
Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b
Click to expand...
Click to collapse
I had many bad experiences trying to understand my Rav better. So I think I can help with this one. Let's try the following things:
- BOOT ON STOCK B
Turn on your phone on Fastboot (pressing and holding turn on + volume down). If it works, the screen will be with that Android toy.
Then you plug USB and type fastboot reboot fastboot to enter fastbootD mode.
When screen goes to fastbootd (if you didn't flash TWRP) you can type fastboot set_active b and then fastboot reboot. If you're on TWRP, just don't type anything in password and then set Slot B as active and reboot.
Now you're on stock again, probably.
- TRY AGAIN TO INSTALL LOS
On stock running, you can plug it again on computer and reboot via ADB to fastbootD mode with adb reboot fastboot.
In fastbootD mode, you can try again the steps, not forgetting to put them on Slot A. and wipe userdata with fastboot -w.
- DON'T FLASH TWRP. JUST BOOT FROM IT WITHOUT INSTALL IT.
When you want to use TWRP to install GApps or Magisk, use it not flashing. just type fastboot boot twrp.img from fastboot or fastbootD mode.
Everything should work from this.

Thanks for the reply, a few questions.
I already have twrp installed, I'd be happy to get rid of it but don't know how to, fastboot reboot fastboot open's twrp, or does nothing at all. Adb reboot fastboot does work, but it takes me to what I'm assuming is my stock bootloader? I think the issue is that I need to get rid of twrp and get my recovery back, but I don't have a stock recovery file to flash, "fastboot flash recovery.img" or whatever it would be. I had to use Lenovo's rescue software earlier to put my stock os back on it. The phone isn't behaving as it should, or perhaps its my computer. I digress, when I try to activate a partition with the aforementioned command to do so, it gives me an error like that's not one of the commands it accepts. I tried three different flavors of adb, and they all reproduced the same syntax error. How would you proceed; and do you have a recovery img that I could use, I can't find one via google or loli. Edit: Progress has been made as using your suggestion I was able to get into fastbootD, the **** still wount mount with that command though. Edit 2: Managed to get adb shell working as it should be and flash the files but it just boot looped the phone, please advise. I got an error that said wipe successful after the last command but then it says not automatically formatting.

...
.....

FoxySheila said:
.....
Click to expand...
Click to collapse
First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img
Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware

Hey there, thanks for the reply.
Beetle84 said:
First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img
Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware
Click to expand...
Click to collapse
Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.

FoxySheila said:
Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.
Click to expand...
Click to collapse
Switch the active slut and flash again...

Hey, thanks for the suggestion.
m666p said:
Switch the active slut and flash again...
Click to expand...
Click to collapse
I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5

FoxySheila said:
I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5
Click to expand...
Click to collapse
Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.

Flashed this no problems. Only major issue I've noticed so far is Android Auto doesn't function (plugged in, mirroring). Any chance of this being fixed?

Nothing
m666p said:
Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.
Click to expand...
Click to collapse
Tried it your way, got bootlooped again, not working.

Hi All,
I am new to android and also new to flashing custom roms.
I followed the instruction in the OP but got stuck with following error, i am in fastbootd just to get that info out of the way.
[email protected]:/home/michael/Downloads/platform-tools# fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 17.069s]
writing 'system_a' 1/2...
OKAY [ 6.594s]
sending sparse 'system_a' 2/2 (517844 KB)...
OKAY [ 16.871s]
writing 'system_a' 2/2...
FAILED (remote: Operation not permitted)
finished. total time: 44.807s
please help?
additional info, I've unlocked the bootloader via motorola website, but I did not do the patch stock firmware with magisk step and came directly to flashing custom rom, if this makes any difference?
mods: I've made the same post in the omniRom thread, if this is not allowed, I apologize here, and please remove this post and keep the omniRom post, thankis.

Heyo, wealcome to "my hell".. I mean the thread
Yea, I've tried to come at flashing this without getting bootlooped for over a month in as many ways and angles as a person can imagine, and it always boot loops, even for omni rom. Can't flash in twrp becuase it says invalid zip. I have followed the instructions both here and elsewhere to a ****ING t, but nothing. So either I'm a dumb sack of **** or there's something going on with my phone, maybe both? Anyway, a fun factoid I discovered a while back after ****ting my pants for a while thinking I bricked my phone is Lenovo has a rescue agent that for free, resets all moto firmware from regular fastboot back to stock. I've used it over a dozen times in the last month for the aforementioned boot looping. Here it is, I'll be around but for right now, it's clearly beyond me. https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa

Hi, I was able to install everything perfectly and I was also able to get the vibration to work, the only problem is that I cannot enable screen clipping, I have tested it in fastbootD as in fastboot and it does not take command "cmd overlay enable org.omnirom.overlay. moto.rav ". I would need your help to solve that little problem, many thanks to everyone who can help!

Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>
Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT
---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------
Greydesk said:
Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>
Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT
Click to expand...
Click to collapse
Nevermind. In Linux, adb can be run normally, but fastboot is a sudo command.

To help anyone who is not familiar with flashing, especially in Linux, here is the terminal output of my successful flash:
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.006s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 15.017s]
Writing 'system_a' OKAY [ 3.363s]
Sending sparse 'system_a' 2/2 (467728 KB) OKAY [ 13.203s]
Writing 'system_a' OKAY [ 3.090s]
Finished. Total time: 34.727s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.473s]
Finished. Total time: 2.269s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash product product.img
Resizing 'product_a' OKAY [ 0.006s]
Sending 'product_a' (512204 KB) OKAY [ 14.631s]
Writing 'product_a' OKAY [ 3.290s]
Finished. Total time: 17.972s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash vbmeta vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.047s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot -w
Erasing 'userdata' OKAY [ 0.628s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.654s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:55 PM ----------
Question: Can I get rid of the Motorola boot warning that says the bootloader is unlocked and has the pause?

[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] [TIRAMISU] [AOSP] [OOS12] [kebab] [lemonades] riceDroidOSS v10.2 android project [OFFICIAL]

riceDroid for OnePlus 8T|9R [kebab][lemonades]
{
"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"
}
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
CORE build only - comes with basic gapps, no setupwizard
Device specific changes
Based on OOS 12 Firmware, Flashing OOS 12 firmware is a must before installing, boots on OOS13 firmware but touchscreen doesn't work
Shipped with OOS Camera - most features exposed working.
Shipped with Chaeyo.0 kernel - based from OOS 12 kernel source - CFS scheduler focused kernel.
Credits
LineageOS kebab team - for most of device/kernel tree changes
chandu078 - base device/vendor tree
cjh1249131356 - oneplus camera source
Notes
I will only maintain Official GMS core variant based on OOS 12 due to limited free time. Other variants will be officially maintained by sir manidreddy a.k.a Lord Itachi
If you have any type of concerns, please address it here, I'll try to accommodate as soon as I see the message.
Changelog
Source Changelog
Download link
riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
Installation Guide
Fastboot - recommended method
1. Download SDK platform tools here and follow this tutorial
2. Reboot to fastboot
3. Enter fastboot mode
4. Perform flashing commands listed on attached file: fastboot-commands
5. Enter recovery mode
6. Wipe data/cache/dalvik-cache
7. Sideload preferred zip files (magisk, gapps etc.)
8. Reboot to system
Sideload - recommended for those who were able to flash oos 12 on both A/B slots
1. fastboot flash recovery.img from firmware payload.bin
2. Reboot device into recovery mode
3. Enter ADB sideload mode
4. adb sideload ROM.zip
5.Wipe data/cache/dalvik-cache
6. Sideload preferred zip files (magisk, gapps etc.)
7. Reboot to system ​
Android OS version: 13.0.0_r30
Security patch level: February 2023
Build author/Device Maintainer: dlwlrma123
Device tree source code: https://github.com/ricedroidOSS-devices/device_oneplus_kebab
Device vendor source code: https://github.com/ricedroidOSS-devices/vendor_oneplus_kebab
Kernel source code: https://github.com/ricedroidOSS-devices/android_kernel_oneplus_sm8250
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team

Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
02/22/23 - Filename: riceDroid-13.0-202302220426-kebab-v10.2-CORE-OFFICIAL.zip
- fixed misc bug from source
- fixed dolby effects
- portrait video mode is a bit usable
- last update for kebab from me, my oneplus 9R got a vertical green line after trying OOS 13, so i will be selling the device at a low price and will shift to another device.

Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

RainGater said:
Wonderful to see riceDroid on 8T. I have been using it on Xiaomi 11T pro and love riceDroid.
I am currently on OOS 13 firmware on kebab. Do I have to downgrade it to OOS 12 firmware? If so, which version of the firmware?
Would this version be okay to flash riceDroid?
OP8T_DDR4_Android12_C36_IN_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.

dlwlrma123 said:
Hi! Downgrading to OOS 12 firmware is a must to avoid flashing related problems, about the version, i believe any version is fine.
Click to expand...
Click to collapse
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?

RainGater said:
Thanks. I don't see installation instructions as I am currently on latest Nameless A13 ROM with OOS 13 firmware.
So, basically
1. adb reboot recovery
2. sideload the OOS 12 firmware
3. sideload ROM
4. sideload Magisk 25.2
5. sideload NikGapps OMNI A13 as I need setup wizard to copy data from Google backup (NikGapps-omni-arm64-13-20230111-signed.zip)
6. wipe Data
7. reboot to system
Does it sound right?
Click to expand...
Click to collapse
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors

dlwlrma123 said:
Oh dear, i forgot to add the installation guide, thanks for this. I'll add a guide in a few minutes. As per your installation, i believe the method is same for other roms, you may want to use fastboot method (fastboot enhanced or native fastboot) to avoid recovery installation errors
Click to expand...
Click to collapse
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?

RainGater said:
I can flash nikgapps OMNI (NikGapps-omni-arm64-13-20230111-signed.zip)) along with Magisk, correct? Since you are only providing core, would it be a problem to flash OMNI?
Click to expand...
Click to collapse
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.

dlwlrma123 said:
i can only recommend nikgapps addons to avoid conflict with google apps shipped with core.
Click to expand...
Click to collapse
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!

RainGater said:
Hmmm... I am not able to install setup addon (NikGapps-Addon-13-SetupWizard-20220908-signed.zip) as it's giving me this error: Skipping setupwizard due to insufficient space. Bummer!
Click to expand...
Click to collapse
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..

dlwlrma123 said:
It seems like i wasn't able to setup partitions spaces for flashable zips, I will create a new build with this problem addressed, Sorry for the inconvenience..
Click to expand...
Click to collapse
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.

alp47470 said:
I was about to flash.. should i wait for this new build ? Also the fastboot enhance link isn't working.
Click to expand...
Click to collapse
Hello, fastboot enhance link updated, thanks for noticing! The current build is fine if you're just gonna flash magisk but if you are going to flash external gapps, its better to wait for the new build. Ill upload the new build after testing.

dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
Fixed version has been pushed for changelogs, please refer to post#2

Nic
dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Nice. Thanks for quick fixes
Can you please confirm if the build has in-built app lock ?

alp47470 said:
Nic
Nice
Can you confirm if the build has in-built app lock ?
Click to expand...
Click to collapse
Yes, it has in-built applock feature.

Thanks for this beautiful rom. After flashing i noticed that there is some dullness when seeing photos or wallpapers (like more on the darker side). Tried all display calibrations like vivid, saturated etc. Is that normal?
Flashed based on 12.c.36 using adb sideload for OnePlus 9r

dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Thank you for the quick fix. BTW, will I be able to flash the full Gapps or only the add-ons?

dlwlrma123 said:
Changelog:
01/21/23 - Filename: riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
- prevented unknown device error when performing adb sideload
- removed experimental changes from prebuilt/default kernel
- resized partitions for flashable packages support (gapps addons etc)
Click to expand...
Click to collapse
I am getting the error when sideloading the ROM. Please see the attacehd image. I downloaded again and still the same error.
EDIT: Now, my partitions are corrupted and even when flashing through fastboot, I am getting partition not found errors. How do I get it working now? Only MSM or will it boot now even after the "partition not found" errors?
Code:
Sending 'boot_a' (98304 KB) OKAY [ 3.370s]
Writing 'boot_a' OKAY [ 0.384s]
Finished. Total time: 4.936s
Sending 'dtbo' (24576 KB) OKAY [ 0.896s]
Writing 'dtbo' OKAY [ 0.109s]
Finished. Total time: 1.072s
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785977 KB) OKAY [ 28.109s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (388144 KB) OKAY [ 14.265s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending 'odm' (172264 KB) OKAY [ 6.317s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (777676 KB) OKAY [ 28.438s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (764421 KB) OKAY [ 27.478s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.065s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'recovery' (98304 KB) OKAY [ 3.534s]
Writing 'recovery' OKAY [ 0.339s]
Finished. Total time: 3.935s

dlwlrma123 said:
Fixed version has been pushed for changelogs, please refer to post#2
Click to expand...
Click to collapse
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh

RainGater said:
Now, my 8T is stuck in a current image have been destroyed and cannot boot stage. smh
Click to expand...
Click to collapse
Damm.. well do MSM i guess