Related
Hi, guys!
It's been about 24h since I had purchased my Moto X (Unlocked), and I've already broken ip
So here's the story of my unit:
From the box it came with 5.x, i've been using it for roughly two-three hours with Telus sim, everything was totally fine.
Then I got myself into a situation, where I wanted to install CM12. So I did, everything was fine (except for the battery life), and I went to sleep.
First thing in the morning, I wanted to try something new (Flyme OS). And there the stuff went wrong. I wanted to do a full wipe of the phone.
I did it, by manually erasing each partition one by one.
Then I had several attempts of installing it, having them all failed. At this point, I had realized that I don't want to install it anymore, so I have downloaded the stock firmware and flashed it up with this sequence:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw !!! (was not sure that this was right)
fastboot oem fb_mode_clear
HOWEVER! On my first attempt, modem file was not right (as my phone was continuously rebooting on first setup (while choosing wifi network).
The second attempt with different NON-HLOS.bin file went ok, wifi is working like charm.
BUT now there is no cellular connection at all! I have tried two SIM (Telus and Megafon, which both work inside my iPhone 6)
{
"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"
}
At this point I'm totally stuck and desperately ask for your help
What variant is it? e.g. XT10xx
Danz207 said:
What variant is it? e.g. XT10xx
Click to expand...
Click to collapse
It is XT1097, sorry for not mentioning that
egorikem said:
XT1097
Click to expand...
Click to collapse
Google tells me that's an AT&T variant, is this correct?
In any case, I have never seen
Code:
fastboot oem fb_mode_set
and
Code:
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw !!! (was not sure that this was right)
fastboot oem fb_mode_clear
used to restore firmware. I suggest heading to the Motorola ROM Support Page (linked in 'unlocking bootloader' page) and downloading the official AT&T variant (is available) then flashing, omitting these commands, and using the ones provided at the bottom of the support page.
Hopefully that reverses anything those extra commands did.
Good luck.
Danz207 said:
Google tells me that's an AT&T variant, is this correct?
In any case, I have never seen
Code:
fastboot oem fb_mode_set
and
Code:
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw !!! (was not sure that this was right)
fastboot oem fb_mode_clear
used to restore firmware. I suggest heading to the Motorola ROM Support Page (linked in 'unlocking bootloader' page) and downloading the official AT&T variant (is available) then flashing, omitting these commands, and using the ones provided at the bottom of the support page.
Hopefully that reverses anything those extra commands did.
Good luck.
Click to expand...
Click to collapse
Thanks for the response! However, my unit was purchased at Stapes (lol, I know) as a Unlocked version. I know, it is confusing for me as well. And yes, I have tried about 5 versions of firmware, none worked. I even made a little script to automate the process:
github.com/egorikem/Flash-Android
Code:
I was able to find a device with fastboot serial of TA9890DMWW
Any key to continue, or Ctrl+C to abort
Flashing partition...
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.112s
Done
Flashing motoboot...
target reported max download size of 536870912 bytes
sending 'motoboot' (2022 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.217s
Done
Rebooting device...
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Done
Flashing logo...
ERROR: Unable to create a plug-in (e00002be)
< waiting for device >
target reported max download size of 536870912 bytes
sending 'logo' (467 KB)...
OKAY [ 0.016s]
writing 'logo'...
OKAY [ 0.048s]
finished. total time: 0.065s
Done
Flashing boot...
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.353s]
writing 'boot'...
OKAY [ 0.419s]
finished. total time: 0.773s
Done
Flashing recovery...
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.426s]
finished. total time: 0.800s
Done
Flashing system...
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.110s]
writing 'system'...
OKAY [ 6.969s]
finished. total time: 15.078s
Done
target max-sparse-size: 256MB
sending 'system' (256089 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 4.991s]
finished. total time: 13.094s
Done
target max-sparse-size: 256MB
sending 'system' (256726 KB)...
OKAY [ 8.099s]
writing 'system'...
OKAY [ 5.298s]
finished. total time: 13.397s
Done
target max-sparse-size: 256MB
sending 'system' (256695 KB)...
OKAY [ 8.114s]
writing 'system'...
OKAY [ 5.439s]
finished. total time: 13.553s
Done
target max-sparse-size: 256MB
sending 'system' (256177 KB)...
OKAY [ 8.096s]
writing 'system'...
OKAY [ 5.828s]
finished. total time: 13.924s
Done
target max-sparse-size: 256MB
sending 'system' (257618 KB)...
OKAY [ 8.155s]
writing 'system'...
OKAY [ 5.380s]
finished. total time: 13.536s
Done
target max-sparse-size: 256MB
sending 'system' (257940 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 4.782s]
finished. total time: 12.939s
Done
target max-sparse-size: 256MB
sending 'system' (64164 KB)...
OKAY [ 2.063s]
writing 'system'...
OKAY [ 1.219s]
finished. total time: 3.283s
Done
target max-sparse-size: 256MB
error: cannot load './system.img_sparsechunk.8': No such file or directory
Done
Done
Erasing previous bands...
erasing 'modemst1'...
OKAY [ 0.052s]
finished. total time: 0.052s
erasing 'modemst2'...
OKAY [ 0.048s]
finished. total time: 0.048s
Done
target reported max download size of 536870912 bytes
sending 'fsg' (694 KB)...
OKAY [ 0.023s]
writing 'fsg'...
OKAY [ 0.040s]
finished. total time: 0.064s
Done
target reported max download size of 536870912 bytes
sending 'modem' (62248 KB)...
OKAY [ 2.038s]
writing 'modem'...
OKAY [ 1.229s]
finished. total time: 3.267s
Done
erasing 'userdata'...
OKAY [ 1.308s]
finished. total time: 1.308s
erasing 'cache'...
OKAY [ 0.305s]
finished. total time: 0.305s
Done
Rebooting device...
rebooting...
finished. total time: 0.001s
Done! Have fun, your device is ready
egorikem said:
Thanks for the response! However, my unit was purchased at Stapes (lol, I know) as a Unlocked version. I know, it is confusing for me as well. And yes, I have tried about 5 versions of firmware, none worked.
Click to expand...
Click to collapse
Hmm. Well, on the Moto X General page there is a guide for converting any variant (inc. XT1097) to a XT1095 Pure Edition. As of 5.1, all modems are compatible with any version so I'd suggest giving that a go and report back. OTA's should work, check the thread for confirmation. Plus this way you get direct updates from Motorola.
Good luck.
Any option for writing imei or creating .bak file or .bat file via root browser to read sim card
---------- Post added at 05:43 AM ---------- Previous post was at 05:36 AM ----------
Danz207 said:
Google tells me that's an AT&T variant, is this correct?
In any case, I have never seen
Code:
fastboot oem fb_mode_set
and
Code:
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw !!! (was not sure that this was right)
fastboot oem fb_mode_clear
used to restore firmware. I suggest heading to the Motorola ROM Support Page (linked in 'unlocking bootloader' page) and downloading the official AT&T variant (is available) then flashing, omitting these commands, and using the ones provided at the bottom of the support page.
Hopefully that reverses anything those extra commands did.
Good luck.
Click to expand...
Click to collapse
but i am from india using indian device i flashed stock verizon rom by mistake and then i lost my network any help guys please....
Hi guys.
My little cousin got an old XT1058 and he was very happy playing that new Pokemon game. Unfortunately, yesterday he come with the phone in bootloop.
Whats is hapennig:
Phone start boot procedure and a few seconds after animation is shown the phone turn off. I'm able to enter in fastboot mode.
What I tried so far:
- factory reset, wipe cache
- restore to 5.1 stock ROM
I live in Brasil, so this ROM was used XT1058_GHOST_RETBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml
Tried this 4.4.4 ROM but couldn't write it, it seens to be some sort of protections to prevent an older ROM to be installed XT1058_RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF
- install custom recovery
TWRP and CWM: both write fine but when I try to enter in recovery right after the install process stock recovery is shown. I even tried erasing recovery before writing custom and writing custom two times.
What I didn't tried so far:
- that procedure envolving RIFFBOX/QHSUSB_DLOAD drivers. I think it's for a last resource and at least in my case (fastboot working) would need opening and putting some test point to ground to enter in some special mode.
Maybe it can be useful, but in fastboot is shown:
AP Fastbooot Flash Mode (S)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
and
Device is UNLOCKED Status Code: 3
Battery OK
I would like to ask if anyone could please help me to make this kido happy again! Thanks in advance.
are you sure it is xt1058? check back of the phone or go to bootloader and check barcodes or "mfastboot getvar all"
if bootloader is unlocked, there are plenty of chances your phone will come back to life.
jameeldroid said:
are you sure it is xt1058? check back of the phone or go to bootloader and check barcodes or "mfastboot getvar all"
if bootloader is unlocked, there are plenty of chances your phone will come back to life.
Click to expand...
Click to collapse
Hi! I'm sorry for taking so much time to reply. I was working outside my area and I couldn't check those infos.
Here is a screenshot of "get var all":
{
"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"
}
Thanks for helping!
That var "product: ghost" comes from the hardware itself or it's coded on software? I mean, how could I say if it's really an XT1058?
That one is from software, the hardware one is SKU which has blanked out right now due to wrong flash maybe.
jameeldroid said:
That one is from software, the hardware one is SKU which has blanked out right now due to wrong flash maybe.
Click to expand...
Click to collapse
Is there anythning I could try?
dolence said:
Is there anythning I could try?
Click to expand...
Click to collapse
did you try to flash a Marshmallow rom such as AICP?
dolence said:
Is there anythning I could try?
Click to expand...
Click to collapse
Not yet. Would be possible to flash this ROM using stock recovery? Because everytime I flash CWM or TWRP it seens to be overwrited by stock. Even if I boot right after flashing it.
Trying to flash it via adb sideload. I will report back in a few minutes.
UPDATE: fail.
Oh, in the back of the phone I found the model. It was very hard to read but it says:
XT1058 ANATEL MODEL NO. 1323-13-0330
FCC ID IHDT56PA1 TYPE MODD7
dolence said:
Not yet. Would be possible to flash this ROM using stock recovery? Because everytime I flash CWM or TWRP it seens to be overwrited by stock. Even if I boot right after flashing it.
Click to expand...
Click to collapse
Can you mention other carrier names from BR? It will help find the right rom for your phone.
There must be Anatel specific rom for this because the one you flashed RETBR is not working.
Anatel is our regulatory agency. Main carriers are Vivo, Tim, Oi, Nextel and Claro. Thanks for helping.
Is there anything else I could try?
1. Initially Flash all Images using Fastboot except system image (system.img)
2. Flash TWRP in the same process, Reboot in recovery.
3. Now when TWRP is opened, wipe all (data, cache, delvik) and Perform a Factory Reset.
4. Reboot Device in Bootloader again, Now Flash System Image(system.img) and stock recovery (optional, only if u want stock recovery).
5. Reboot
(Strictly use the Images/Files meant for your Device Model.)
vijayid_94 said:
1. Initially Flash all Images using Fastboot except system image (system.img)
2. Flash TWRP in the same process, Reboot in recovery.
3. Now when TWRP is opened, wipe all (data, cache, delvik) and Perform a Factory Reset.
4. Reboot Device in Bootloader again, Now Flash System Image(system.img) and stock recovery (optional, only if u want stock recovery).
5. Reboot
(Strictly use the Images/Files meant for your Device Model.)
Click to expand...
Click to collapse
Code:
C:\adb fastboot mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.113s]
finished. total time: 0.115s
C:\adb fastboot mfastboot>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.259s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.442s]
finished. total time: 0.706s
C:\adb fastboot mfastboot>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.028s]
finished. total time: 5.401s
C:\adb fastboot mfastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (245 KB)...
OKAY [ 0.319s]
writing 'logo'...
OKAY [ 0.856s]
finished. total time: 1.179s
C:\adb fastboot mfastboot>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.947s]
writing 'boot'...
OKAY [ 1.337s]
finished. total time: 2.288s
C:\adb fastboot mfastboot>fastboot flash recovery twrp-2.8.7.0-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
finished. total time: 1.783s
C:\adb fastboot mfastboot>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54272 KB)...
OKAY [ 3.710s]
writing 'modem'...
OKAY [ 2.395s]
finished. total time: 6.110s
C:\adb fastboot mfastboot>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.447s]
finished. total time: 0.453s
C:\adb fastboot mfastboot>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.447s]
finished. total time: 0.449s
C:\adb fastboot mfastboot>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.358s]
writing 'fsg'...
OKAY [ 0.804s]
finished. total time: 1.169s
C:\adb fastboot mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.176s]
finished. total time: 0.178s
Hi! Thanks for helping me on my journey. I've tried to flash everything except system and booting into TWRP but dead Android picture is shown and after pressing "power+vol up" stock recovery still being loaded. I don't know if it's expected to be like this but recovery flashing seens to be taking less time then expected:
Code:
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
Any thoughts on this?
dolence said:
Code:
C:\adb fastboot mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.113s]
finished. total time: 0.115s
C:\adb fastboot mfastboot>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.259s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.442s]
finished. total time: 0.706s
C:\adb fastboot mfastboot>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.028s]
finished. total time: 5.401s
C:\adb fastboot mfastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (245 KB)...
OKAY [ 0.319s]
writing 'logo'...
OKAY [ 0.856s]
finished. total time: 1.179s
C:\adb fastboot mfastboot>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.947s]
writing 'boot'...
OKAY [ 1.337s]
finished. total time: 2.288s
C:\adb fastboot mfastboot>fastboot flash recovery twrp-2.8.7.0-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
finished. total time: 1.783s
C:\adb fastboot mfastboot>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54272 KB)...
OKAY [ 3.710s]
writing 'modem'...
OKAY [ 2.395s]
finished. total time: 6.110s
C:\adb fastboot mfastboot>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.447s]
finished. total time: 0.453s
C:\adb fastboot mfastboot>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.447s]
finished. total time: 0.449s
C:\adb fastboot mfastboot>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.358s]
writing 'fsg'...
OKAY [ 0.804s]
finished. total time: 1.169s
C:\adb fastboot mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.176s]
finished. total time: 0.178s
Hi! Thanks for helping me on my journey. I've tried to flash everything except system and booting into TWRP but dead Android picture is shown and after pressing "power+vol up" stock recovery still being loaded. I don't know if it's expected to be like this but recovery flashing seens to be taking less time then expected:
Code:
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
Any thoughts on this?
Click to expand...
Click to collapse
you need to use twrp-2.8.7.2
vijayid_94 said:
you need to use twrp-2.8.7.2
Click to expand...
Click to collapse
The same with 2.8.7.2, unfortunately.
dolence said:
The same with 2.8.7.2, unfortunately.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Dont reboot.. choose recovery from fastboot menu.. this will not over write it, or simply try fastboot boot twrp.img
Salik Iqbal said:
Fastboot flash recovery twrp.img
Dont reboot.. choose recovery from fastboot menu.. this will not over write it, or simply try fastboot boot twrp.img
Click to expand...
Click to collapse
I was choosing recovery from fastbbot menu. It doesn't work at all.... Booting via command doesn't work as well.
Code:
C:\adb fastboot mfastboot>fastboot boot twrp-2.8.7.2-ghost.img
downloading 'boot.img'...
OKAY [ 0.798s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.899s
C:\adb fastboot mfastboot>
dolence said:
The same with 2.8.7.2, unfortunately.
Click to expand...
Click to collapse
check your pm and get me over facebook. i am not much active on xda these days.
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.
{
"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.
{
"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.