I've searched high and low on this website to try and find a solution to my current issue and I have found nothing but more problems, so I'm going to try posting a new thread for help.
Yesterday I was in the process of unrooting my phone, I wasn't able to use some of the apps the way I wanted to. While deleting some extraneous applications powered by busybox, and then busybox itself, I lost connection to Google Services. I tried numerous times to reset the device, but even after factory reset and recovery I could not connect to Google Services (network connection working on wifi and data) and could not sign in to the device. So I decided to flash a new image to the phone to try to get rid of whatever the issue was.
I downloaded the XT1095 image from Motorola's website and used their instructions to flash it to the device. My device was originally XT1096 from Verizon, but I could not locate an image for that one, and read that I could flash to the XT1095 image for Marshmallow access anyway. I don't remember what errors I received. I was able to boot the device and sign in through Google services, but my network connection to Verizon was lost, I received an error that the network was unavailable. So I tried to work around that for a while but could not reinstate voice or data services. I could send SMS for some reason. I decided to try flashing a new image. I tried with the image I received from Motorola again, but I could not flash the system.img, received an error message "load_file: could not allocate [I don't have the number] bytes" and couldn't find a workaround, even using -P at the end of the system command.
I downloaded VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip from another thread on this site, I can't find the link to it now. I flashed with the instructions from this thread http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253 This had the separate chunk system files, so I could flash it in smaller pieces, and that worked fine, the only error was with the fsg.mbn file, I received a permission denied error. Here is a copy of the command sheet from this image flash.
Code:
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash logo logo.bin
sending 'logo' (1454 KB)...
OKAY [ 0.096s]
writing 'logo'...
OKAY [ 0.077s]
finished. total time: 0.174s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash boot boot.img
sending 'boot' (10200 KB)...
OKAY [ 0.377s]
writing 'boot'...
OKAY [ 0.480s]
finished. total time: 0.858s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash recovery recovery.img
sending 'recovery' (10280 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.462s]
finished. total time: 0.854s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.0
sending 'system' (257551 KB)...
OKAY [ 8.144s]
writing 'system'...
OKAY [ 6.608s]
finished. total time: 14.752s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.1
sending 'system' (256644 KB)...
OKAY [ 8.121s]
writing 'system'...
OKAY [ 6.681s]
finished. total time: 14.802s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.2
sending 'system' (256636 KB)...
OKAY [ 8.117s]
writing 'system'...
OKAY [ 6.722s]
finished. total time: 14.840s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.3
sending 'system' (256977 KB)...
OKAY [ 8.128s]
writing 'system'...
OKAY [ 6.240s]
finished. total time: 14.368s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.4
sending 'system' (256340 KB)...
OKAY [ 8.108s]
writing 'system'...
OKAY [ 6.076s]
finished. total time: 14.185s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.5
sending 'system' (257227 KB)...
OKAY [ 8.136s]
writing 'system'...
OKAY [ 6.498s]
finished. total time: 14.635s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.6
sending 'system' (255276 KB)...
OKAY [ 8.076s]
writing 'system'...
OKAY [ 7.245s]
finished. total time: 15.321s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.7
sending 'system' (257925 KB)...
OKAY [ 8.159s]
writing 'system'...
OKAY [ 6.240s]
finished. total time: 14.399s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash system system.img_sparsechunk.8
sending 'system' (257968 KB)...
OKAY [ 8.158s]
writing 'system'...
OKAY [ 6.184s]
finished. total time: 14.345s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash modem NON-HLOS.bin
sending 'modem' (63188 KB)...
OKAY [ 2.062s]
writing 'modem'...
OKAY [ 1.522s]
finished. total time: 3.585s
C:\Users\Lyyli\AppData\Local\Android\sdk2>fastboot erase modemst1
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot flash FSG fsg.mbn
sending 'FSG' (693 KB)...
OKAY [ 0.064s]
writing 'FSG'...
Permission denied
FAILED (remote failure)
finished. total time: 0.067s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.058s]
finished. total time: 0.058s
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.335s]
finished. total time: 0.335s
C:\Users\Lyyli\AppData\Local\Android\sdk2>fastboot reboot
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Lyyli\AppData\Local\Android\sdk2>mfastboot reboot
rebooting...
finished. total time: 0.001s
Upon rebooting device, it would not move past the "bootloader unlocked" screen, which I assume means that some file is missing but I don't know what to fix. When I turn the device off from the bootloader unlocked screen, it automatically returns to Fastboot Flash Mode now. I've tried checking many different threads for similar issues but have not found any solutions.
Troubleshooting:
I used fastboot for the first flash, then switched to mfastboot.
I have tried using RSD Lite but it does not recognize my device.
Cleared cache and userdata through mfastboot.
Thank you for any help you can offer!
Can you boot into Fastboot mode? If yes then you can try installing TWRP and flash a zip for XT1096 which will have all necessary modem files to work on CDMA network.
hamzaalijoiyah said:
Can you boot into Fastboot mode? If yes then you can try installing TWRP and flash a zip for XT1096 which will have all necessary modem files to work on CDMA network.
Click to expand...
Click to collapse
Thanks for the suggestion, the only flashable .zip I was able to find for the Moto X 2014 was a Brazilian edition for the XT1097. It was packaged without modem files so I flashed the modem from the Motorola images, as previously mentioned, and I was able to operate the phone again, but I am still not able to get a network connection with VZW.
Try https://firmware.center/firmware/Mo...ZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
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
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 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 fb_mode_clear
fastboot reboot
It make your Moto to Verizon 5.1 stock rom.
If you want 6.0MM. You gotta reinstall TWRP, and follow thread XT1095 6.0 flashable stock ROM
Good luck.
I noticed in your cmd flash log that you only flashed up to system.img_sparsechunk.8. All of the flashing guides that I have seen in various posts stop there. Failing to flash system.img_sparsechunk.9 will cause failure to boot (don't ask me how I know).
kyo167 said:
Try https://firmware.center/firmware/Mo...ZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
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
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 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 fb_mode_clear
fastboot reboot
It make your Moto to Verizon 5.1 stock rom.
If you want 6.0MM. You gotta reinstall TWRP, and follow thread XT1095 6.0 flashable stock ROM
Good luck.
Click to expand...
Click to collapse
Thanks, this got me to where I needed to be to gain connection again. I could not find a Verizon version of the software at all, so thank you for the link!
Related
I'm quite pissed with what's happening to my phone. No matter how I upgrade to lollipop (through fastboot or going back to 4.4.4 and then taking the OTA or by flashing zip through stock recovery) it doesn't recognize my home wifi. It works fine on stock 4.4.4 asia retail image
- I also noticed a strange thing, I don't know why but the Verizon logo shows up just before the boot finishes on 5.1!! I'm in India and why would verizon logo come on my phone?
- My bootloader is unlocked and also upgraded to 30BE so I can't flash gpt and boot files but rest of the files flash just fine through fastboot and I'm able to go back to stock 4.4.4 asia retail. everything works as expected (Wifi too)!!!
Somebody please tell me how can I get stock lollipop 5.1 and have the Wifi work too?
I've tried flashing 4.4.4 modem over 5.1 but it still doesn't recognizde my home wifi.. although it is able to scan all other nearby wifi!!!
Kitkat version - XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml
Lollipop version - Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03
sroy001 said:
I'm quite pissed with what's happening to my phone. No matter how I upgrade to lollipop (through fastboot or going back to 4.4.4 and then taking the OTA or by flashing zip through stock recovery) it doesn't recognize my home wifi. It works fine on stock 4.4.4 asia retail image
- I also noticed a strange thing, I don't know why but the Verizon logo shows up just before the boot finishes on 5.1!! I'm in India and why would verizon logo come on my phone?
- My bootloader is unlocked and also upgraded to 30BE so I can't flash gpt and boot files but rest of the files flash just fine through fastboot and I'm able to go back to stock 4.4.4 asia retail. everything works as expected (Wifi too)!!!
Somebody please tell me how can I get stock lollipop 5.1 and have the Wifi work too?
I've tried flashing 4.4.4 modem over 5.1 but it still doesn't recognizde my home wifi.. although it is able to scan all other nearby wifi!!!
Kitkat version - XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml
Lollipop version - Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03
Click to expand...
Click to collapse
First of all, wrong section to post.
Second, flash this through fastboot/RSDLite - https://mega.co.nz/#!U9lRFBgD!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
It's the 5.1 factory image. works on Asia retail without any problem.. try if it works
Made a separate thread in General section now.. Not sure how to delete the thread.. Can't find the option in XDA app
RSD Lite flashing doesn't work for me anymore as 1st two commands about GPT and Motoboot fail due to upgraded boot loader.. So I'll try and flash through fastboot
Sent from my XT1052 using XDA Free mobile app
sroy001 said:
Made a separate thread in General section now.. Not sure how to delete the thread.. Can't find the option in XDA app
RSD Lite flashing doesn't work for me anymore as 1st two commands about GPT and Motoboot fail due to upgraded boot loader.. So I'll try and flash through fastboot
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
RSD will work as this is a 5.1 factory image. make sure to flash gpt and bootloader, it won't fail.
if you dont flash those then you'll have gpt and bootloader from Asia.Retail and other files from Europe.Retail so future OTAs might fail
Okay done.. So if RSD lite doesn't flash GPT and Motoboot, should I manually try and flash through fastboot?
Sent from my XT1052 using XDA Free mobile app
sroy001 said:
Okay done.. So if RSD lite doesn't flash GPT and Motoboot, should I manually try and flash through fastboot?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Since you have already updated the bootloader and partition tables to the latest one from Lollipop there is no need to flash those files again. Just flash the modem, recovery, data and system files using cmd line.
Sent from my XT1053 using Tapatalk
bushako said:
Since you have already updated the bootloader and partition tables to the latest one from Lollipop there is no need to flash those files again. Just flash the modem, recovery, data and system files using cmd line.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I'm flashing through fastboot and unable to manually flash system.img
C:\adb>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394503608 bytes
error: cannot load 'system.img': Not enough space
sroy001 said:
I'm flashing through fastboot and unable to manually flash system.img
C:\adb>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394503608 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
I think you may need to flash gpt.bin first.. i'll post a log of what happened when i flashed here.. flash it in the same order..
H:\platform-tools>mfastboot devices
TAxxxxxxxx fastboot
H:\platform-tools>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.250s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.437s]
finished. total time: 0.689s
H:\platform-tools>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.350s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.979s]
finished. total time: 6.330s
H:\platform-tools>mfastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 1.385s]
finished. total time: 1.695s
H:\platform-tools>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 2.209s]
finished. total time: 3.150s
H:\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.950s]
writing 'recovery'...
OKAY [ 1.522s]
finished. total time: 2.472s
H:\platform-tools>mfastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.478s]
writing 'system'...
OKAY [ 43.636s]
sending 'system' (575387 KB)...
OKAY [ 36.324s]
writing 'system'...
OKAY [ 36.938s]
finished. total time: 166.385s
H:\platform-tools>mfastboot flash modem NON-HLOS.bin
sending 'modem' (54276 KB)...
OKAY [ 3.720s]
writing 'modem'...
OKAY [ 4.811s]
finished. total time: 8.531s
H:\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.789s]
finished. total time: 0.790s
H:\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.816s]
finished. total time: 0.817s
H:\platform-tools>mfastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.380s]
writing 'fsg'...
OKAY [ 1.154s]
finished. total time: 1.535s
H:\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 2.822s]
finished. total time: 2.823s
H:\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 18.879s]
finished. total time: 18.879s
H:\platform-tools>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.182s]
finished. total time: 0.182s
H:\platform-tools>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.604s]
finished. total time: 0.604s
H:\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.001s
H:\platform-tools>
athulele said:
I think you may need to flash gpt.bin first.. i'll post a log of what happened when i flashed here.. flash it in the same order..
H:\platform-tools>mfastboot devices
TAxxxxxxxx fastboot
H:\platform-tools>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.250s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.437s]
finished. total time: 0.689s
H:\platform-tools>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.350s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.979s]
finished. total time: 6.330s
H:\platform-tools>mfastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 1.385s]
finished. total time: 1.695s
H:\platform-tools>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 2.209s]
finished. total time: 3.150s
H:\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.950s]
writing 'recovery'...
OKAY [ 1.522s]
finished. total time: 2.472s
H:\platform-tools>mfastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.478s]
writing 'system'...
OKAY [ 43.636s]
sending 'system' (575387 KB)...
OKAY [ 36.324s]
writing 'system'...
OKAY [ 36.938s]
finished. total time: 166.385s
H:\platform-tools>mfastboot flash modem NON-HLOS.bin
sending 'modem' (54276 KB)...
OKAY [ 3.720s]
writing 'modem'...
OKAY [ 4.811s]
finished. total time: 8.531s
H:\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.789s]
finished. total time: 0.790s
H:\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.816s]
finished. total time: 0.817s
H:\platform-tools>mfastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.380s]
writing 'fsg'...
OKAY [ 1.154s]
finished. total time: 1.535s
H:\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 2.822s]
finished. total time: 2.823s
H:\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 18.879s]
finished. total time: 18.879s
H:\platform-tools>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.182s]
finished. total time: 0.182s
H:\platform-tools>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.604s]
finished. total time: 0.604s
H:\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.001s
H:\platform-tools>
Click to expand...
Click to collapse
I was indeed able to flash 5.1 image through latest version of rsd lite.. But it still doesn't detect my home WiFi.. It scans all other neighborhood WiFi though
So went back to stock 4.4.4 through fastboot and WiFi is back.. Quite strange but now I'm pissed of trying.. Have at least flashed my phone 15 times in last two days trying almost all method
Sent from my XT1052 using XDA Free mobile app
sroy001 said:
I was indeed able to flash 5.1 image through latest version of rsd lite.. But it still doesn't detect my home WiFi.. It scans all other neighborhood WiFi though
So went back to stock 4.4.4 through fastboot and WiFi is back.. Quite strange but now I'm pissed of trying.. Have at least flashed my phone 15 times in last two days trying almost all method
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
That's weird.. Have you tried resetting the router?
can you please share the 5.1 firmware for asia retail?
athulele said:
That's weird.. Have you tried resetting the router?
Click to expand...
Click to collapse
OMG!! Here I was flashing factory images going back and forth and simply resetting the router worked! So silly of me.. Thanks bud.. I'm now on stock 5.1 Asia retail and all working great
Sent from my XT1052 using XDA Free mobile app
koolguy366 said:
can you please share the 5.1 firmware for asia retail?
Click to expand...
Click to collapse
Here you go!
https://mega.nz/#!SVZ3XJTT!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
Sent from my XT1052 using XDA Free mobile app
sroy001 said:
OMG!! Here I was flashing factory images going back and forth and simply resetting the router worked! So silly of me.. Thanks bud.. I'm now on stock 5.1 Asia retail and all working great
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Heh, that's good.
sroy001 said:
Here you go!
https://mega.nz/#!SVZ3XJTT!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks dude, BTW how u flashed it? RSD lite?
koolguy366 said:
Thanks dude, BTW how u flashed it? RSD lite?
Click to expand...
Click to collapse
You can use RSD lite.. I flashed through Fastboot.. It's same thing
Sent from my XT1052 using XDA Free mobile app
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.
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.
Hi,
I have a XT1033 with unlocked bootloader, dotOS (custom rom) and TWRP 3.2.3.0 (custom recovery).
I decided to lock the bootloader and unroot my device by flashing stock rom and locking the oem, but unable to do so. I have previously once unlocked the bootloader and the after some weeks locked it again, but now when i follow the same procedure to lock the bootloader again, it didnt work.
What i did ?
I have downloaded firmware for my device (XT1033), and started to flash it with the following commands:
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash logo logo.bin
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
pause
mfastboot.exe reboot
After doing mfastboot.exe oem lock it says "hab check failed system failed to validate system image" and when i execute mfastboot.exe reboot, the device goes into a bootloop...
I have somehow repaired the thing (was able to access bootloader so flashed TWRP recovery, formatted the partitions, mounted /cache, /system, /data, flashed a custom rom, gapps) but i want the bootloader to be locked.
Here are the logs in case you need them..
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe devices
TA93401HLM fastboot
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe devices
TA93401HLM fastboot
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 2.832s]
finished. total time: 2.842s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.030s]
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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.331s]
finished. total time: 0.381s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash motoboot motoboot.
img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.120s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.052s]
finished. total time: 1.192s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.060s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.160s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash recovery recovery.
img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.410s]
writing 'recovery'...
OKAY [ 0.710s]
finished. total time: 1.140s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash system system.img_
sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.671s]
writing 'system'...
OKAY [ 10.939s]
finished. total time: 19.615s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash system system.img_
sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256953 KB)...
OKAY [ 8.697s]
writing 'system'...
OKAY [ 10.259s]
finished. total time: 18.976s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash system system.img_
sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260396 KB)...
OKAY [ 8.825s]
writing 'system'...
OKAY [ 10.299s]
finished. total time: 19.154s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash system system.img_
sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166572 KB)...
OKAY [ 5.654s]
writing 'system'...
OKAY [ 7.516s]
finished. total time: 13.180s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.732s]
writing 'modem'...
OKAY [ 1.230s]
finished. total time: 2.982s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.040s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.030s]
finished. total time: 0.040s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 5.283s]
finished. total time: 5.393s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.360s]
finished. total time: 0.370s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 3.802s]
finished. total time: 3.812s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.760s]
finished. total time: 0.760s
C:\Users\Bharat\Downloads\MOTO_G_RECOVERY>
What i want ?
A perfect solution... ASAP (To lock the bootloader, unroot the device, and return to the stock rom) Please help me... :crying::crying:
Device UNLOCKED, status code: 3
Thanks..
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.