I have a cricket xt1045, and after attempting to flash the US retail version of the 5.1 firmware onto the phone, I'm unable to get out of fastboot mode, and can't successfully reflash any firmware, even the cricket branded one. I get a "preflash validation failed" error:
C:\...>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.388s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.825s
my cid is one I can't seem to find any firmwares for, 0x0010 . Do CIDs need to match in order to flash at all? if so, is anyone aware of any cid 10 firmwares out there I could flash? The cricket one i was able to find is cid16.
The error I get when attempting to boot is "failed to validate system image".
Any help anyone might have would be greatly appreciated, or if I could provide any more information that would help anyone help me, please let me know. Thanks.
Did you ever figure out a solution? I'm in the same boat as you. Sorry for the gravedig.
No, I sold the phone as is on eBay and got a Moto X. Look through my old posts, I was talking in a different thread with another guy that had the same problem, might be something helpful there. Good luck.
Lol Same exact problem. There's a graveyard of these damn Cricket XT1045's and cheapskates that want more than they offer. Lol
Related
Help I have a Telstra Xoom with OTA 3.1. I rooted this then found another update to 3.2 had just arrived so I tried to follow this (http://forum.xda-developers.com/showthread.php?p=13799427#post13799427) to take it to the stock Telstra img H.6.1-38-9_Telstra_Australia.
All was working fine until the command:
fastboot flash system system.img
I got this:
sending 'system' (262144 KB)..
FAILED (remote: (00120003))
finished. total time: 202.745s
What can I do now?
On the xoom it says:
Failed to process command error(0x120003)
Where do I go now.
Please reply very urgent.
Thanks a million...
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.
If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium
Did you try just running the RUU ?
Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess
i have done many moto g using file below
ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
but now this file error as below
C:\MOTO G>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.359s
phone screen flash logo error is """version downgraded for primary gpt"""
customer said he tried to upgrade-after it hang in logo
help me
Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.
lost101 said:
Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.
Click to expand...
Click to collapse
my phone bootloader shows unlocked in fastboot mode
you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)
alwayspunk said:
you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)
Click to expand...
Click to collapse
i think now 5.1 the lateset version.
from where i get official firmware?
zonetrichur said:
i think now 5.1 the lateset version.
from where i get official firmware?
Click to expand...
Click to collapse
i can not post spam, anyways check the ultimate guide to flash gpe in general section. theres a link to the firmware there
i tried many many recovery files also
that also error
so i think it emmc problem-am i right?
zonetrichur said:
i tried many many recovery files also
that also error
so i think it emmc problem-am i right?
Click to expand...
Click to collapse
May i know whether u flashed stock firmware, because i also getting same error and phone struck in "Bootloader unlocked warning screen" in startup...
So my Moto 4g has freeze and reboot during the last official lollipop update and now my phone is unable to boot
I try to reflash a stock rom using fastboot mode (and mflashtool) but I got errors
sending 'recovery' (10240 KB)...
OKAY [ 0.382s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.770s
After searching on xda forum it seems that the bootloader is locked so I'v try to use motorola's website to get the unlocked code (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) but I'v always get the error "Your device does not qualify for bootloader unlocking"
I've try to remove place and using the Unlock Data Scrub Tool but always the same issue.
As my phone is unable to boot is there anyway to unbrick it ? Maybe and official tool able to flash with locked bootloader or something ?
Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!