Database Develop

[Q] XT1095 fastboot flash system.img failed

Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?

YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot

libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s

YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.

juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx

YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?

JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?

YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.

YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?

JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s

YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files

Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095

JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed

YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?

JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone

YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.

JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60

YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.

JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device

dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.

fastboot error lg optimus l90 D415

So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing

SMOKYxPANDA said:
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
Click to expand...
Click to collapse
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.

0000.0000.00 said:
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
Click to expand...
Click to collapse
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing

SMOKYxPANDA said:
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
Click to expand...
Click to collapse
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?

0000.0000.00 said:
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
Click to expand...
Click to collapse
No, i'm not trying to save any data, I want a fresh start, the problem when trying the "fastboot oem unlock" command is that it gives me an error, again i put a link below to show you what appears when trying that command..
https://drive.google.com/file/d/0B0shRlbnxbQpeFlxcWxjS0l1eE0/view?usp=sharing

This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing

SMOKYxPANDA said:
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
Click to expand...
Click to collapse
Something probably happened..
Can you please send the results of fastboot getvar all so I can check.

I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view

SMOKYxPANDA said:
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
Click to expand...
Click to collapse
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s

SMOKYxPANDA said:
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
Click to expand...
Click to collapse
Then try flashing twrp and the bootstack and Tell me how it goes from there.

0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
0000.0000.00 said:
Then try flashing twrp and the bootstack and Tell me how it goes from there.
Click to expand...
Click to collapse
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img"
Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...

SMOKYxPANDA said:
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img" Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
Click to expand...
Click to collapse
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
0000.0000.00 said:
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
Click to expand...
Click to collapse
After that, run fastboot reboot recovery to reboot into recovery. Press the advanced button and then press the button that says adb sideload with the touchscreen and start it. Then to install the zip run adb sideload zipname where zipname is the name of the zip you want to flash.
After that boot back into the download mode thing to reflash recovery and then reboot into recovery with fastboot reboot recovery. After that I would flash the zips for a ROM and optionally gapps with adb sideload.

This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing

SMOKYxPANDA said:
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
Click to expand...
Click to collapse
Were you able to flash recovery and boot into it?

0000.0000.00 said:
Were you able to flash recovery and boot into it?
Click to expand...
Click to collapse
No, you can observe in the picture where it gives me the same error message, unknown command

SMOKYxPANDA said:
No, you can observe in the picture where it gives me the same error message, unknown command
Click to expand...
Click to collapse
Could you please send me a picture of the output of fastboot devices.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
I think the fastboot on the phone has issues because it seems to not flash anything. I think you should try this >>> https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>

asahi7 said:
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

thanks, already did, unfortunately seems like there is a problem with the rom. i flash each file but when i test again i always get slb1 corrupt. no recovery, no download mode. it was worth the try

Root Assistance RP2 Android 9 pie, latest updates.

Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)

Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk

blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin

In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock

blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.

Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445

[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:
No data with carriers using Verizon network
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 : https://t.me/MotoG8Power
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 G Power
Contributors
vache, Dark98
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Beta Release Date: 2020-08-02
Created 2020-08-02
Last Updated 2020-08-28

I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.

jhjhjhjhjhjh said:
I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.
Click to expand...
Click to collapse
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.

Work on Moto g8 power 2041-1?

wanderleiAlfa said:
Work on Moto g8 power 2041-1?
Click to expand...
Click to collapse
Yes, XT2041-1 and XT2041-3 (sofiar).

Any way to get this without G apps? Trying to degoogle my life.

Is this just the stock rom?

BMO0071 said:
Is this just the stock rom?
Click to expand...
Click to collapse
No, this is OmniROM.
Juno_ said:
Any way to get this without G apps? Trying to degoogle my life.
Click to expand...
Click to collapse
Should be doable for the next build.

Weird. I flashed it and I was still on stock ?

Is OmniSwitch included in this ROM?
Thanks for your work.

Ulfys said:
Is OmniSwitch included in this ROM?
Thanks for your work.
Click to expand...
Click to collapse
Yes.

vache said:
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.
Click to expand...
Click to collapse
Yes .
Thanks ..
Whenever you upload a build for the Moto g power I'll test it...

@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved

I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)

Ulfys said:
I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)

Q9Nap said:
@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved
Click to expand...
Click to collapse
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip

vache said:
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)
Click to expand...
Click to collapse
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.

Reflashed today on my g8 power and got a boot loop halp
Edit: flashed unified test build and the rom booted sucessfully

vache said:
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip
Click to expand...
Click to collapse
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!

Ulfys said:
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.
Click to expand...
Click to collapse
Something wrong on your side, make sure you're using the last fastboot version.
Q9Nap said:
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!
Click to expand...
Click to collapse
https://drive.google.com/file/d/19oiGM7yRzbxOsZXd4vYKDpbTW8ajNOU5/view?usp=sharing
By using the product.img you will have adb working.
I would need kernel logs : adb shell dmesg > dmesg.txt

System integrity is compromised error after restoring using Moto smart assistant.

I've had my Moto G6 rooted for some time now. An ota update for PPS29.118-15-11-16 was continually nagging so I uninstalled Magisk and installed it.
Upon reboot when checking for updates I now get the following:
As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software.
I tried restoring to factory using Lenovo Moto smart assistant and that worked as it should. I still get the same "System integrity is compromised" error. I was under the impression that this would be reset upon doing this factory reset.
How would I get this message to be removed as I don't ever remember seeing it when this phone was rooted all this time.
Thanks

If I downgrade back to my last version PPSS29.118-15-11-9 the "System integrity is compromised" is NOT present.

Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.

minipretzel said:
Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.
Click to expand...
Click to collapse
without Magisk = system recognizes your unlocked bootloader
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.

I know this thread is old but I have the exact same problem.
I also restored stock roms from PPS29.118-15-11-16 using Smart assistant. I was already at this version, but I did the update anyway, as I have read that the smart assistant rescue would completely restore the phone to stock condition. But this didn't clear my "System Integrity..." message.
Just fyi, I actually ran the smart assistant commands manually... The SA failed to update my phone so I reconstructed the commands from the xml file and executed them one by one to find and fix this problem.
I re-ran the standard rescue after this and it was fine.
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Thing is, I do have magisk installed , as I wanted to root the phone. But this doesn't clear the message as it did for the OP.
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
But the article by alexmaisa is from 2019 and is for a G5S....
Any ideas would be greatly appreciated.

pdpantages said:
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Click to expand...
Click to collapse
With magisk installed it's quiet normal.
pdpantages said:
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
Click to expand...
Click to collapse
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.

WoKoschekk said:
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.
Click to expand...
Click to collapse
Thank you for the input. My bootloader was locked so the lock commands just reported this. When I ran the subsequent commands I got an error about unable to flash (bc the bootloader was locked)..... I thought maybe the original post had a typo so I switched to two "unlock" commands as the first commands. This unlocked me, and all the subsequent commands completed OK, including the final lock. But after setup I still have the System Integrity msg when I check for s/w updates under System menu.
The original post was from 2020 so possibly my version of Magisk (24.3) is the cause.?
I have most of what I want; latest stock ROMs and phone is rooted... just want to clear the problem with s/w updates.
I found another command set that that flashed the boot, system and oem twice.. I have cut these commands below. Unfortunately I don't recall where I got the bat file. It was called FLASH_OEM_LOCK.bat. Again these commands issue a lock command followed by some flash cmds which I thought would not work with the bootloader locked? Does a lock command not take effect until after reboot or something? Anyway, here they are:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear

@pdpantages That's the way to relock the bootloader and get the status "oem_locked":
1. Flash the current complete firmware
2. !!! THIS STEP IS HIGHLY RECOMMENDED !!!
If your bootloader will be relocked successfully after these steps, you won't have any options to fix errors! So, this is your last chance...
Important functions to check: are you able to boot into system, mobile (data) connections, Wifi
boot into system and check everything's working fine.
3. Are you really sure everything`s fine?
4. *** The following shows fastboot commands + output for a better understanding of what we are doing here. I took them from the last relock of my Moto G6 ***
Reboot into bootloader and run these commands:
Code:
########################################################################
# new lines beginning with "#" are comments and should not be executed!!
########################################################################
$ fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
finished. total time: 0.001s
$ fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.002s]
finished. total time: 0.002s
# no need to flash the whole firmware (= valid Android images) again since we already did it in step 1.. Skip it and run lock command again.
$ fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed boot.img a second time!
$ fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.919s]
writing 'boot'...
OKAY [ 0.518s]
finished. total time: 1.438s
$ fastboot oem lock
...
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed system/oem.img AND vendor.img (it's also signed since it contains sensitive firmware data, too) a second time!
$ fastboot flash system system.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 9.463s]
writing 'system'...
OKAY [ 5.836s]
finished. total time: 15.300s
(...flashing all other sparse images of system...)
$ fastboot flash vendor vendor.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'vendor' (254668 KB)...
OKAY [ 8.950s]
writing 'vendor'...
OKAY [ 5.484s]
finished. total time: 14.434s
( ...flashing all other sparse images of vendor...)
$ fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (153181 KB)...
OKAY [ 5.566s]
writing 'oem'...
OKAY [ 4.727s]
finished. total time: 10.294s
# now bootloader is satisfied and can be locked (yeah!!)
$ fastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.163s]
finished. total time: 0.163s

Thank you kindly for the into. The notes in particular clarified things for me quite a bit, and I understand that issuing the unlock commands as I did was incorrect. I will try it shortly and report the success or failure of my attempt.
My bl is currently locked- my intent is to unlock it (2 commands) , let the phone reset and boot, verify with "fastboot flashing get_unlock_ability" that it is in fact unlocked, and start your procedure from there...
Thank you again for the help. I expect your post will be helpful to others too.

pdpantages said:
I will try it shortly and report the success or failure of my attempt.
Click to expand...
Click to collapse
So I did as promised. The basic answer is that it worked as described. A few notes follow; things I wonder about and error msgs I saw.
Procedure: Not exactly as outlined above; my boot loader was locked so I issued some unlock commands:
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.006s]
Finished. Total time: 0.006s
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.001s
rigel:/home/pdp/adb>fastboot flashing unlock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
Finished. Total time: 0.001s
So, I got errors trying oem unlock but "flashing unlock" worked and the phone booted when I entered the second one. Not sure if this is an issue or not.
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found". But despite this, the commands appeared to work so I carried on.
rigel:/home/pdp/adb> fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (22528 KB) OKAY [ 0.901s]
Writing 'boot' OKAY [ 0.381s]
Finished. Total time: 1.675s
In the end, everything worked as expected- the "System Integrity..." message was gone from the Software update setting, and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message).
Magisk: After all that, I still wanted to root my phone... I thought i would be able to install Magisk using twrp.
I tried booting into twrp recovery using adb (not flashing recovery.img ) but this didn't work. So in the end I unlocked my bootloader again. (required the unlock key) to install Magisk.
WoKoschekk said:
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.
Click to expand...
Click to collapse
I was hoping the above would apply to me but it didn't; I now see the "System Integrity message" again in my software update settings. It is manageable- if I really want a software update I now know how to revert the phone to stock. Now that I am rooted I can make backups with Titanium Backup which was my primary motive for rooting in the first place .
Thank you again for the help, WoKoschekk , it is much appreciated.

pdpantages said:
Not sure if this is an issue or not.
Click to expand...
Click to collapse
It seems to be an issue because oem unlock does work for me. But as long as your bootloader is unlocked it does not matter.
pdpantages said:
and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message)
Click to expand...
Click to collapse
It happens on Moto G6+ devices but not on our device.
pdpantages said:
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found".
Click to expand...
Click to collapse
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.

WoKoschekk said:
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.
Click to expand...
Click to collapse
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]

pdpantages said:
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]
Click to expand...
Click to collapse
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools

WoKoschekk said:
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools
Click to expand...
Click to collapse
Adb version 1.0.39
fastboot version 0.0.1-4500957
I don't like to use windows but I ran Motorola Rescue & Smart Assistant tool there... If I have to use windows again I will update it.