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.
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....
hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6
You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?
What does
Code:
fastboot devices
say?
yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader
istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again
Please paste here the output of flashing the factory image.
istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here
I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.
C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing 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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s
yes im on 6.0 marshmallow and the sdk with the latest update
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure
Then it too must be a hardware problem.
do you think so?
alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.
I Have Tried Everything But I Keep Getting This Failure In Flashing Partition . My Dad Is Getting Really Upset Reply Fast
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.248s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.117s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.379s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.215s]
finished. total time: 5.605s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.945s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.156s
G:\Moto X>mfastboot flash system system.img
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.674s]
writing 'modem'...
OKAY [ 3.582s]
finished. total time: 7.275s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.462s]
finished. total time: 0.473s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.488s]
finished. total time: 0.494s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.832s]
finished. total time: 1.183s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.019s]
finished. total time: 1.027s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.792s]
finished. total time: 0.797s
G:\Moto X>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.328s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.344s
G:\Moto X>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.453s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.546s]
finished. total time: 6.006s
G:\Moto X>fastboot flash logo.bin
unknown partition 'logo.bin'
error: cannot determine image filename for 'logo.bin'
G:\Moto X>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
G:\Moto X>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 1.203s]
finished. total time: 2.142s
G:\Moto X>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394581432 bytes
error: cannot load 'system.img': Not enough space
G:\Moto X>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54276 KB)...
OKAY [ 3.666s]
writing 'modem'...
OKAY [ 3.596s]
finished. total time: 7.293s
G:\Moto X>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.469s]
finished. total time: 0.484s
G:\Moto X>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.469s]
finished. total time: 0.469s
G:\Moto X>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.339s]
writing 'fsg'...
OKAY [ 0.829s]
finished. total time: 1.190s
G:\Moto X>fastboot erase userdata
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 1.031s]
finished. total time: 1.047s
G:\Moto X>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 0.797s]
finished. total time: 0.813s
G:\Moto X>
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
YedanyXD said:
What are you trying to do? Dowgrade to kk?
Moderator Edit:
Please use "Quick Reply" rather than "Reply" so we don't have to edit the entire OP as a quote and thus get some page real estate back. And improve page load times. Thanks.
Click to expand...
Click to collapse
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
xXAmartyAXx said:
I tried with the version on my dad's phone which was 5.1 still doesn't work. I had a backup in twrp and when I restore with that it says unable to wipe psg and phone doesn't boot.
Click to expand...
Click to collapse
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
YedanyXD said:
Do you have bootloader unlocked? Downgrade to kk or reinstall stock 5.1 by cmd
Click to expand...
Click to collapse
Boot loader unlocked
First tried to install kk accidentally then installed 5.1 by cmd but it is stuck in boot loader unlocked screen
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.
Hey guys, recently I hard bricked my sanders 1802 in way that everything I tried does not work.
After I flashed lineage 16.0, the fingerprint sensor and some other things were not working, then I tried downgrading it back to stock via fastboot, Sanders retail 8.1.
After that everthing went to hell. It got into bootloop. So i tried to restore it via Leonovo Moto Smart Assistant. Went back to bootloop and started showing some cache mount issues.
I tried over 10 different ROMs and every time it showed cache mout problems or ERROR 6, 7 and 1 in TWRP and sometimes kernel issues.
I've already tried flashing new kernels, tried every ERROR 6 and 7 solutions that are available online and nothing happens.
Right now I have it at the best shape possible, it has the latest TWRP installed (3.2.1 sanders r20), it does not show any cache nor kernel errors when I try to install a ROM, but it keeps giving me the ERROR 7 even when I delete the assert line on the updater-script file.
Searching the XDA foruns I found someone talking about getting a fresh start for the phone by flash the sdcard with mmcbk0.img. I'm not even sure if that's the right path to solve my problem, but I thought I give it a try since I have no idea what else to do.
I'm pretty noob on everything regarding android, just followed everything easily when it comes to tutorials.
Can someone please help me? Is the new mmcbk0.img file the right path or should I try somthing else? I talked to a "expert" guy here in my city and he said that the phone is gone and there's nothing I can do. Is it possible?
Have you tried TWRP 3.3
pradeeppk said:
Have you tried TWRP 3.3
Click to expand...
Click to collapse
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
voliveira92 said:
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
pradeeppk said:
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
Click to expand...
Click to collapse
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
voliveira92 said:
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
Click to expand...
Click to collapse
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
HTML:
pradeeppk said:
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
Click to expand...
Click to collapse
I'm pretty sure that I'm not missing anything.
I was able to flash Twrp 3.3.0 from this thread (https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-3-0-t3940378), but now it keeps giving me Error 7 and 'unable to mount system'.
Tried lineage and Havocs ROM. Tried altering the assert line again and no changes.
pradeeppk said:
Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there.
Click to expand...
Click to collapse
Wrong command format
voliveira92 said:
it gives me this error message:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
D302Thakur said:
Wrong command format
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
Click to expand...
Click to collapse
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
voliveira92 said:
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
Click to expand...
Click to collapse
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
pradeeppk said:
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
Click to expand...
Click to collapse
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
voliveira92 said:
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
Click to expand...
Click to collapse
Those are the lines that came with error. The phone went on a bootloop after clearing the cache and userdata.
platform-tools>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (504333 KB)...
OKAY [ 11.743s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.804s
platform-tools>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (495479 KB)...
OKAY [ 11.539s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 15.942s
platform-tools>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (65436 KB)...
OKAY [ 1.528s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.552s
platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (335882 KB)...
OKAY [ 7.802s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.841s
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
pradeeppk said:
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
Click to expand...
Click to collapse
Ok, so I repaired system file, formated data, cache and system and tried to flash from TWRP and fastboot.
On TWRP I got the same ERROR 7 as always (tried Pixel Experience and Havoc OS, as well stock firmware Sanders_NPS26.1):
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Tried again editing the assert line and the same ERROR 7 anyway.
And via fastboot (stock firmware) I got this and the phone went on bootloop after rebooting:
fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.073s
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.704s]
finished. total time: 0.828s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.163s
fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.419s]
finished. total time: 0.816s
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.511s]
finished. total time: 1.007s
fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.385s]
writing 'dsp'...
OKAY [ 0.286s]
finished. total time: 0.670s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 7.627s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.669s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 12.189s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.260s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 6.230s]
finished. total time: 18.391s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 7.196s]
finished. total time: 19.356s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 12.207s]
writing 'system'...
OKAY [ 6.143s]
finished. total time: 18.349s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 12.211s]
writing 'system'...
OKAY [ 6.929s]
finished. total time: 19.141s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 10.111s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.502s
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 1.758s]
writing 'modem'...
OKAY [ 1.088s]
finished. total time: 2.846s
fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 0.118s]
finished. total time: 0.178s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.018s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.334s]
finished. total time: 0.334s
fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot oem fb_mode_clear
...
OKAY [ 0.118s]
finished. total time: 0.118s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.185s
I have the option of switching the system file to another format on TWRP (EXT2, EXT3, EXT4, FAT, exFAT, F2Fs), could any of those help?
voliveira92 said:
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
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 erase modemst1
fastboot erase modemst2
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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
D302Thakur said:
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
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 erase modemst1
fastboot erase modemst2
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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Ok, so I tried the stock you recomended and used the codes you provided.
Here's what I got. Frozen at boot screen. Tried from -fastboot- and -minimal adb and fastboot-.
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.057s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.519s]
finished. total time: 0.641s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71941 KB)...
OKAY [ 1.678s]
writing 'modem'...
OKAY [ 0.980s]
finished. total time: 2.658s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.071s]
writing 'fsg'...
OKAY [ 0.120s]
finished. total time: 0.191s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.382s]
writing 'dsp'...
OKAY [ 0.254s]
finished. total time: 0.637s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.150s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.396s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.357s]
finished. total time: 0.754s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.490s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.452s]
finished. total time: 0.942s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.097s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.099s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (249863 KB)...
OKAY [ 5.809s]
writing 'system'...
OKAY [ 2.935s]
finished. total time: 8.744s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (260323 KB)...
OKAY [ 6.091s]
writing 'system'...
OKAY [ 3.729s]
finished. total time: 9.820s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.105s]
writing 'system'...
OKAY [ 3.309s]
finished. total time: 9.414s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.098s]
writing 'system'...
OKAY [ 3.106s]
finished. total time: 9.203s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.097s]
writing 'system'...
OKAY [ 2.928s]
finished. total time: 9.025s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.104s]
writing 'system'...
OKAY [ 2.986s]
finished. total time: 9.090s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (255675 KB)...
OKAY [ 5.971s]
writing 'system'...
OKAY [ 3.487s]
finished. total time: 9.459s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (242629 KB)...
OKAY [ 5.647s]
writing 'system'...
OKAY [ 2.830s]
finished. total time: 8.478s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (239745 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.518s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.520s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135426 KB)...
OKAY [ 3.150s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.153s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.009s]
finished. total time: 0.009s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
voliveira92 said:
fastboot flash system system.img_sparsechunk.0
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.9
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.10
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash oem oem.img
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
D302Thakur said:
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
Click to expand...
Click to collapse
Brazil, model XT1802
voliveira92 said:
Brazil, model XT1802
Click to expand...
Click to collapse
Can anyone please help me with this? I'm almost giving up on this device but I can't accept that there's nothing else I can try.