[ROM][RAV*/SOFIA*][11][UNOFFICIAL] SuperiorOS-Xcalibur - Moto G Power ROMs, Kernels, Recoveries, & Other De

{
"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.

Related

Moto g XT1068 bootloop/bricked can't recover/flash images

HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
I then try to flash stock firmaware and I go these error:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.010s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.274s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.092s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.944s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.055s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.023s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.399s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.380s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.411s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.542s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.611s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.618s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.713s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.866s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.940s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.912s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.950s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.698s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.726s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.996s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.040s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.071s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
rebooting...
finished. total time: 0.001s
WAS HAPPEN TO MY PHONE ? PLEASE HELP ME ALL DRIVER IS PROPRELY INSTALL
roulyz said:
HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
Click to expand...
Click to collapse
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.5.0
Duck86 said:
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.0.5
Click to expand...
Click to collapse
Hum was using 2.8.5.0. Does good?
roulyz said:
Hum was using 2.8.5.0. Does good?
Click to expand...
Click to collapse
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
OK I will try but I have other xt1068 and that recovery work since 2 week pretty good on it
Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275
Wolfcity said:
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275
Click to expand...
Click to collapse
Got the version numbers mixed up. Sorry, I shouldn't be doing numbers when I'm tired
I know that....
Duck86 said:
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work I GOT all the time:
sending 'recovery' (9694 KB)...
OKAY [ 99.815s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 114.759s
NEED HELP AGAIN
roulyz said:
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work
NEED HELP AGAIN
Click to expand...
Click to collapse
Where did you get the stock firmware? What link are you using?
all fastboot command works but I got error from partition
ADB command don't work. It works fine when the phone ran well but not now :crying:
Duck86 said:
Where did you get the stock firmware? What link are you using?
Click to expand...
Click to collapse
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
roulyz said:
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Click to expand...
Click to collapse
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.
Duck86 said:
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.
Click to expand...
Click to collapse
I have done bootloader unlocked process again and get that error
D:\Android TOOLS\platform-tools>fastboot oem unlock MGYXUCQJ5XHSYVTLYACD
...
(bootloader) Unlock code = MGYXUCQJ5XHSYVTLYACD
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.
Tel864 said:
It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.
Click to expand...
Click to collapse
Whoouuuaaa!!! So what can I do?
Have you guys tryed
To boot recovery
fastboot boot recovery.img
USBhost said:
Have you guys tryed
To boot recovery
fastboot boot recovery.img
Click to expand...
Click to collapse
yes, but don't works. I got error
need help please
Moto G Xt 1068: failed remotely
Did u recover your device ?
---------- Post added at 09:57 AM ---------- Previous post was at 09:56 AM ----------
roulyz said:
need help please
Click to expand...
Click to collapse
Same with me, help me out pleaseee
Thanks

Help please !

I am leaving house for 2 weeks in 7 hours i realluy need help in flashing my phone I cant flash Vendor in fastboot
and i think it doesnt boot becxause of error flashing and erasing vendor
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash recovery twrp-3.1.1-2-v1-prague.img
target reported max download size of 471859200 bytes
sending 'recovery' (24468 KB)...
OKAY [ 0.855s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 2.042s
C:\Users\Matas Niewulis\Desktop\Pulpit>
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash erase vendor
error: cannot load 'vendor'
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot reboot
rebooting...
finished. total time: 0.341s
C:\Users\Matas Niewulis\Desktop\Pulpit>
please help me fix my device.. sorry for a mess in this post, im in a hurry
ooooh **** i restored my device to working oreder by doing fix vendor partition in twrp..
but i still have the problem with fingerprint, security, dev options etc
Vendor you can flash only by twrp/ restoring.
Which firmware do you have?

[URGENT HELP NEEDED] DEVICE WON'T BOOT. please help. please, please!!!

Okay, I had a perfectly working Moto X4 (Indian Retail version), rooted and debloated. But then the idea of going back to unrooted struck me and I flashed the ROM with no problem. Then, I went back to the Bootloader (Had USB Debugging turned on and OEM Unlock "NOT" turned on in the Developer Options) and locked the bootloader by running oem lock and then, the Phone won't boot -
It gave me the message --
" Your Device is Corrupt. It can't be trusted and will not boot."
From then, I've tried reflashing the firmware - No luck.
It gives a "Permission denied" message in cmd and fails.
Unlocking the OEM worked with the get_unlock_data but then it asked me to turn on USB debugging in the developer options (and I can' boot the phone past the message).
I've tried booting into recovery, won't work - just the same message. Tried booting into the bootable TWRP - Won't work. Same message.
Fastboot erase cache erases the cache and won't do anything else.
PLEASE HELP ME. PLEASE....​
The CMD error log reads as -->
Code:
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot devices
ZY224JGPK4 fastboot
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (37 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.115s]
finished. total time: 0.123s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bootloader bootloa
der.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.237s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.344s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash modem NON-HLOS.bin
target didn't report max-download-size
sending 'modem' (95999 KB)...
FAILED (command write failed (No error))
finished. total time: 0.010s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash fsg fsg.mbn
target didn't report max-download-size
sending 'fsg' (5508 KB)...
FAILED (command write failed (No error))
finished. total time: 0.008s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash bluetooth BTFM.bin
target didn't report max-download-size
sending 'bluetooth' (4540 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash dsp dspso.bin
target didn't report max-download-size
sending 'dsp' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.002s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash logo logo.bin
target didn't report max-download-size
sending 'logo' (2153 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_a' (19853 KB)...
OKAY [ 0.438s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.453s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516148 KB)...
OKAY [ 11.396s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 11.400s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522692 KB)...
OKAY [ 15.666s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.671s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (521055 KB)...
OKAY [ 15.620s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.626s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523959 KB)...
OKAY [ 15.885s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.893s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (521817 KB)...
OKAY [ 16.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.226s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (522195 KB)...
OKAY [ 16.019s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.026s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (524276 KB)...
OKAY [ 16.235s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.242s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system system.img_
sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (167142 KB)...
OKAY [ 3.634s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.644s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash system_b system_ot
her.img
target reported max download size of 536870912 bytes
sending 'system_b' (134369 KB)...
OKAY [ 2.931s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.942s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (237897 KB)...
OKAY [ 5.203s]
writing 'oem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 5.209s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>fastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\Achyut\Desktop\MOTO X4\platform-tools>
At the time of posting there are only stock images available for the Retail US version of the X4. The only way to get back is to have backed up your original rom and also have "OEM Unlock" enabled in dev settings. Try contacting Lenovo and tell them your issue. They may be able to assist you by providing a stock firmware image or by having you send in your device for service.
Hi, i have just made the exact mistake you did. Did you manage to find a way to fix this?
FIX
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
I couldn't fix it. And the service center is not providing warranty since I've unlocked the bootloader and they're saying it's irreparable and asking me to change the whole motherboard of a 1 month old handset. I'll be bringing the phone back from service center tomorrow and will be trying this method
bot_rosco said:
For anyone that does get this issue i have managed to find a fix.
If you are unable to flash the official firmware (7.1.1/8.0) with locked boot loader then with fastboot enter "fastboot boot boot.img", this worked for me and i was able to get into android and enable OEM unlock to unlock the bootloader and then flash the official firmware.
Click to expand...
Click to collapse
Can you PLEASE FOR the love of God elaborate,please _/|\_
achyut said:
Can you PLEASE FOR the love of God elaborate,please _/|\_
Click to expand...
Click to collapse
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
bot_rosco said:
Sure,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
achyut said:
Then? Then it'll boot back normally?? Sorry,I don't have the phone with me yet (it's in service center).
Click to expand...
Click to collapse
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
bot_rosco said:
First try factory reset (in recovery).
Go into bootloader, use vol buttons till it says boot recovery. It should reboot and show an android on its back. Press power and vol up. Then go down to format. Select the bottom option. It should take a few seconds and select reboot and it mite work if not just follow the above guide.
If that doesnt work,
download the stock firmware (i used 7.1.1) it can be found all over xda.
Use fastboot to boot the boot image e.g.
fastboot boot boot.img
Click to expand...
Click to collapse
I can't boot recovery though, shows the same message
achyut said:
am gonna try it tomorrow and if it works, you're up for a token of gratitude from my side.
Click to expand...
Click to collapse
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
achyut said:
I can't boot recovery though, shows the same message
Click to expand...
Click to collapse
i had same, worth a try tho.
bot_rosco said:
Good luck
---------- Post added at 03:16 PM ---------- Previous post was at 03:14 PM ----------
i had same, worth a try tho.
Click to expand...
Click to collapse
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
jakejm79 said:
You could try booting to the TWRP recovery, i.e. fastboot boot TWRP.img
and then wiping data from there.
Click to expand...
Click to collapse
In think this depends on the firmware as oreo has encryption that does not play nice with twrp so it may not work, worth a try though.
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
achyut said:
nope. trying fastboot boot boot.img gives a <bootloader> permission denied! message and fails
Click to expand...
Click to collapse
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
bot_rosco said:
It should start to boot, once you have booted you setup the phone and enable oem unlock in the dev options. Go back into bootloader and unlock it with fast boot (fastboot oem unlock) and if it has already been unlocked before it should unlock. If you haven't unlocked the bootloader before, now is the time to do it. Once unlocked flash stock firmware, 7.1.1 or 8.0. good luck
Click to expand...
Click to collapse
QWZR said:
Use mfastboot not fastboot, you'll have to add this to your tools. It's Motorola fastboot with proper permission.
Click to expand...
Click to collapse
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
achyut said:
my computer doesn't recognize mfastboot command. previously I've flashed the ROMs with just fastboot command
Click to expand...
Click to collapse
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
QWZR said:
You have to download it.
https://androidfilehost.com/?fid=95916177934532795
Click to expand...
Click to collapse
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
achyut said:
okay, set up and tried flashing, not working. even RSD Lite is giving "phone failed to switch to fastboot mode" error, even though the phone is in fastboot and is recognized as fastboot devices in cmd.
am running out of options now. damn...
any help? anyone??
please....
Click to expand...
Click to collapse
Have you tried the twrp method that someone mentioned above? Other than that i cant think of anything, sorry.

can anyone tell me what im doing wrong

C:\adb>fastboot devices
ZL52249ZLW fastboot
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.028s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.261s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.290s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (68142 KB)...
OKAY [ 2.223s]
writing 'modem'...
OKAY [ 0.986s]
finished. total time: 3.215s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (5188 KB)...
OKAY [ 0.176s]
writing 'fsg'...
OKAY [ 0.128s]
finished. total time: 0.311s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.036s]
finished. total time: 0.038s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.036s]
finished. total time: 0.038s
C:\adb>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin'
C:\adb>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
C:\adb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.559s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.354s]
finished. total time: 0.919s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (512397 KB)...
OKAY [ 16.663s]
writing 'system'...
OKAY [ 6.223s]
finished. total time: 22.892s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (475855 KB)...
OKAY [ 15.484s]
writing 'system'...
OKAY [ 5.472s]
finished. total time: 20.963s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (523076 KB)...
OKAY [ 16.997s]
writing 'system'...
OKAY [ 6.090s]
finished. total time: 23.094s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (508867 KB)...
OKAY [ 16.536s]
writing 'system'...
OKAY [ 5.792s]
finished. total time: 22.334s
C:\adb>fastboot flash system system.img_sparsechunk.4
error: cannot load 'system.img_sparsechunk.4'
C:\adb>fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
C:\adb>fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
C:\adb>fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
C:\adb>fastboot flash system system.img_sparsechunk.8
error: cannot load 'system.img_sparsechunk.8'
C:\adb>fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9'
C:\adb>fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0'
C:\adb>fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1'
C:\adb>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.071s]
finished. total time: 0.072s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.183s]
finished. total time: 0.186s
C:\adb>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (1423 KB)...
OKAY [ 0.053s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.150s
C:\adb>fastboot reboot
I don't root my phones anymore, but when I did, I always found the instructions to be light. A lot of people think that if you can't figure it out without much help then you shouldn't be rooting your phone. I've nearly bricked more than once phone before I figuring things out.
Read every set of directions you can find on Google, and if you can combine the puzzle pieces together correctly, then you win.
Are you sure you are flashing correct firmware for your device? what device do you have and what firmware are you trying to flash?
It the moto G6 play from Best Buy unlocked xt1922-9 this is the firmware I was told was full my device. Aljeter_0pp27.61-14_4-cid50_subsidy-DEFAULT_regulatory. But every time I flash it as you can see it comes up with errors in the bootloader even though the system images flash fine and it boots up I don't have Wi-Fi,data or Bluetooth
anotherfakeusername said:
I don't root my phones anymore, but when I did, I always found the instructions to be light. A lot of people think that if you can't figure it out without much help then you shouldn't be rooting your phone. I've nearly bricked more than once phone before I figuring things out.
Read every set of directions you can find on Google, and if you can combine the puzzle pieces together correctly, then you win.
Click to expand...
Click to collapse
Well I tried just about all of the firmware on XDA nothing seems to work even though they say it's for the G6 play I have my doubts
timelessxiii said:
Well I tried just about all of the firmware on XDA nothing seems to work even though they say it's for the G6 play I have my doubts
Click to expand...
Click to collapse
You're using the wrong commands that's it.
Gimme a screenshot of all the files in your firmware's folder and I'll give you a script
{
"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"
}
here you go
CreasingMass Dev said:
You're using the wrong commands that's it.
Gimme a screenshot of all the files in your firmware's folder and I'll give you a script
Click to expand...
Click to collapse
timelessxiii said:
View attachment 4549977
Click to expand...
Click to collapse
also send me a copy of your file flashfile.xml pls
View attachment flashfile.xml
CreasingMass Dev said:
also send me a copy of your file flashfile.xml pls
Click to expand...
Click to collapse
timelessxiii said:
View attachment 4549977
Click to expand...
Click to collapse
Here's your script, paste it inside your firmware's folder and open it with your device connected in fastboot mode, should work.
https://drive.google.com/open?id=1jhhRS2ZrkROfqULjI49Zus2xj9v-gGAt
CreasingMass Dev said:
Here's your script, paste it inside your firmware's folder and open it with your device connected in fastboot mode, should work.
https://drive.google.com/open?id=1jhhRS2ZrkROfqULjI49Zus2xj9v-gGAt
Click to expand...
Click to collapse
i give up it all started when i unlocked the bootloader the phone did not reboot and wipe data like it should have instead i got a message saying badkey in the left top screen, so when i rebooted pnone it came up but i did not have bluetooth wifi or data i thought reflashing always worked will i guess not lol , if there was a flash file for data or wifi hell i maybe able to fix it through OTAs
timelessxiii said:
i give up it all started when i unlocked the bootloader the phone did not reboot and wipe data like it should have instead i got a message saying badkey in the left top screen, so when i rebooted pnone it came up but i did not have bluetooth wifi or data i thought reflashing always worked will i guess not lol , if there was a flash file for data or wifi hell i maybe able to fix it through OTAs
Click to expand...
Click to collapse
I was able to flash twarp hopfully a custom rom would work
timelessxiii said:
I was able to flash twarp hopfully a custom rom would work
Click to expand...
Click to collapse
DaxUser has stoped , what ever that mean
could you possibly repost this script. its no longer available on google drive and it would help me tremendously.

[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.

Categories

Resources