I recently bought the phone specifically to install mods and to understand more about the hardware. So I'm an absolute noob but hopefully not too dumb to follow simple instructions.
I installed the cm-12-20150304-UNOFFICIAL-titan image and things were (mostly) good.
Today I saw for the first time that the phone had detected an UPDATE. It was marked NIGHTLY but I had seen other new images on the web site that didn't appear as updates so I decided to try it. The update was downloaded and then I booted into TWRP (2.8.4) to install it.
On reboot I discovered that the touchscreen didn't work any more - no response to any contact.
I booted into TWRP and found that was affected in the same way.
I attempted to use 'fastboot' to flash a clean copy of TWRP:
--> fastboot flash recovery openrecovery-twrp-2.8.4.0-titan.img
as the start of escaping from this but I keep getting a 'Mismatched partition size (recovery)'
Then I tried just booting the recovery image:
--> fastboot boot openrecovery-twrp-2.8.4.0-titan.img
But when TWRP starts up the screen still doesn't respond.
I've tried wiping the device:
--> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.268s]
erasing 'cache'...
OKAY [ 0.082s]
finished. total time: 0.352s
and I've tried flashing a stock firmware.
--> fastboot update RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC.xml.zip
4.4.4_KXB21.85-14_cid7_CFC.xml.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
And now I am at a loss. I've exhausted my knowledge and creativity (for now) but I don't want to make things worse (if possible) through ignorance.
Is the phone 'dead'?
i have the same issue with my moto g, i've ran out of ideas for a while but im still looking for an answer so if you happen to find out whats wrong let me know!
If I find anything I will but I suspect we both have dead phones - spares rather than repair .
I tried resolving the 'Mismatch partition size' by formatting the 'recovery' partition but I just get 'cannot format partition of type raw'. My suspicion is that the partitioning/formatting of the internal memory is completely corrupted but it doesn't show up as a storage device when I connect it to my computer anymore and I can't get ADB running so I can't get any more information or anyway to zap it back to base settings so I think it may be a lost cause.
On the other hand even if the partitioning/formatting is all gone to pot the phone is, somehow, finding enough of TWRP to get the initial screen loaded - where is it finding that?
I also don't understand why 'fastboot boot TWRP.img' doesn't work because that should bypass the internal storage and go straight to RAM. That makes me worry that 'somehow' the update has screwed the screen hardware even though I find that hard to believe.
Well, as I said I bought the phone for a learning experience and I've certainly had that.
Same here (XT1068). After bootloader update and nightly installation touchscreen is dead. Its also dead after rebooting to recobery.
Ended up by restoring to factory: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Everything is working again after several boots.
How?
modules said:
Ended up by restoring to factory: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Everything is working again after several boots.
Click to expand...
Click to collapse
Exactly how did you do this? Every attempt I have made to flash the phone has failed.
Never mind, I thought you were just pointing me at firmware files. I followed the link and tried the tool but same problem.
It really doesn't like writing the partition information
Thanks for the brief hope though..
jmangan said:
Exactly how did you do this? Every attempt I have made to flash the phone has failed.
Never mind, I thought you were just pointing me at firmware files. I followed the link and tried the tool but same problem.
It really doesn't like writing the partition information
Thanks for the brief hope though..
Click to expand...
Click to collapse
I read your first post.. You did not install the stock firmware correctly! You have to extract the stock firmware zip file and flash each and every file with separate commands!
Sent from my Moto G 2014
Not really the problem
pranshubatra707 said:
I read your first post.. You did not install the stock firmware correctly! You have to extract the stock firmware zip file and flash each and every file with separate commands!
Sent from my Moto G 2014
Click to expand...
Click to collapse
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.054s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.060s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.101s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.445s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.494s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.454s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.476s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 10.393s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.420s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 10.623s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.742s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 10.549s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.596s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 9.315s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 9.375s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 2.494s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.594s
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.078s]
finished. total time: 0.079s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.117s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.174s
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.109s
erasing 'userdata'...
OKAY [ 0.246s]
finished. total time: 0.248s
rebooting...
finished. total time: 0.002s
Press any key to exit
There is a definite problem with the formatting/partitioning of the built in storage. I can't load ADB because the screen doesn't respond and normal flashing produces the results above. (Ignore the battery low message; it's been on charge for four hours but isn't updating the values although it shows as charging).
Thanks for contributing though.
jmangan said:
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Thanks for contributing though.
Click to expand...
Click to collapse
You are trying to restore to stock android lollipop? Did you receive the official android update or not? If not then your bootloader isn't updated to lollipop bootloader.. Try downloading factory image of kitkat for your device and then try restoring it maybe?
Try this
http://forum.xda-developers.com/showthread.php?p=55373304
Sent from my Moto G 2014 using XDA Free mobile app
jmangan said:
Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.054s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.060s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.101s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.445s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.494s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.454s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.476s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 10.393s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.420s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 10.623s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.742s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 10.549s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.596s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 9.315s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 9.375s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 2.494s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 2.594s
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.078s]
finished. total time: 0.079s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.117s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.174s
erasing 'cache'...
OKAY [ 0.104s]
finished. total time: 0.109s
erasing 'userdata'...
OKAY [ 0.246s]
finished. total time: 0.248s
rebooting...
finished. total time: 0.002s
Press any key to exit
There is a definite problem with the formatting/partitioning of the built in storage. I can't load ADB because the screen doesn't respond and normal flashing produces the results above. (Ignore the battery low message; it's been on charge for four hours but isn't updating the values although it shows as charging).
Thanks for contributing though.
Click to expand...
Click to collapse
are you kidding? look at your log dude!
its saying failed because of low battery. just charge it up full and try again
ggunzio said:
are you kidding? look at your log dude!
its saying failed because of low battery. just charge it up full and try again
Click to expand...
Click to collapse
He stated already that the device has been on charge for 4hrs.
Sent from my Moto G 2014
Giving up
pranshubatra707 said:
He stated already that the device has been on charge for 4hrs.
Sent from my Moto G 2014
Click to expand...
Click to collapse
Thanks, pranshubatra707, saved me pointing it out.
Well, since I can no longer see the internal storage when the phone is connected in windows, and since I can't format it with fastboot (type of 'raw' not supported) I thought maybe parted might be able to help so I plugged it into a Linux machine but parted doesn't see the storage device either.
It could be that with the various fixes MTP has been turned off/damaged (but when I had an external SD car installed Windows could still see that). But I think that's it, last throw of the dice. The partitions are gone/unrecognised. There appears to be no way to re-create/restore them and without them flashing A:WAYS fails.
I was also tempted to try booting linux on a USB stick but I doubt that the phone will boot off USB so that seems like just a waste of time - unless anyone knows better?
Thanks for the suggestions but I'm facing up to a dead phone.
My touchscreen just went non responding after installing a cm12 based rom.. I erased userdata, system and cache via bootloader with fastboot commands and restored my phone to stock kitkat.. I even restored recovery.. Then touchscreen went working again!
Sent from my XT1068
Well i'm facing the same problem after flashing some CM 12 based roms which need lollipop bootloader.
If someone has a solution for the problem please tell us.
stefan230 said:
Well i'm facing the same problem after flashing some CM 12 based roms which need lollipop bootloader.
If someone has a solution for the problem please tell us.
Click to expand...
Click to collapse
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068
pranshubatra707 said:
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068
Click to expand...
Click to collapse
I flashed lollipop bootloader before of course. The Rom I installed were the latest CM 12 nightly bulid and the latest Team UB build, which both need lollipop bootloader to boot.
My problem is that if the rom is booted the touch screen does not respond any more. Even if I try to restore a backup using TWRP 2.8.6.0 the touch screen does not respomd either.
pranshubatra707 said:
You have to update your bootloader before flashing cm12 roms
Sent from my XT1068
Click to expand...
Click to collapse
that's BS, I've updated my bootloader and the ROM (CM12 official) didn't even boot, and touchscreen wasn't working in recovery
I just flashed stock KK which is what I'm running now
My friend is having this problem with his XT1068 too. He's stuck in KitKat:
If he flashes CM12, the touchscreen won't work. CM will boot as usual, and TWRP too, but the touchscreen won't work on neither. The ROM was flashed with a Lollipop bootloader so that's not the problem.
He's on stock KitKat by following this tutorial. But when he downloads the Lollipop OTA, it won't install in the stock recovery, giving an error. Thus, he's stuck on KK.
Any ideas? Many thanks in advance!
Hi,
I posted already on antoher thread (microkat) but was sent away to supposedly here
I've got the same issue, but my history was CM12->wipe+install Titan Z-> wipe+install Microkat-> restore CM12.
Using the link to restore the device
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
you may be able to get it up and running again. This works as well with the Linux fastboot.
What I was able to discover during the troubleshooting was the output of getvar in the error case:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.4/KXB21.85-14/9:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.14.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-pINKman-kk4.4 (sluk
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.7 (GCC) ) #15021
(bootloader) kernel.version[2]: 9 SMP PREEMPT Thu Feb 19 15:31:25 CET 20
(bootloader) kernel.version[3]: 15
The pinkman kernel is actually related to microkat. But whatever I flashed, boot, motoboot, recovery, the output remained the same. A friend came to the idea to flash the system as well, as in the link. The output is now:
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-ge35b7bb-00001-gf6a
(bootloader) kernel.version[1]: 3942 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Feb 25 01:
(bootloader) kernel.version[3]: 09:46 CST 2015
Also the baseband got a value again. I will continue in the next days.
Hi, I know this thread is quite old, but I ran into the same problem.
Actually I bought the phone used and it arrived like this :/
Can any of you guys help?
If I try "mfastboot format motoboot" it tells me that raw filesystem ist not supported.
The firmware restore batchfile gives me this output:
mfastboot output said:
D:\My Stuff\Downloads\motog\Moto G 2014 [XT1068] Restore to Android 5.0.2 (22.99
.16)>"Auto Restore Script.bat"
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
error: device not found
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
OKAY [ 0.331s]
finished. total time: 0.369s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash rpm
FAILED (remote failure)
finished. total time: 100.227s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.040s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.005s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.341s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.745s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.354s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.764s
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 13.128s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 26.701s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 13.005s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.330s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 13.183s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.525s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 13.031s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.874s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 6.051s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 11.483s
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 6.580s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.618s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.992s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.994s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.079s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.114s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
rebooting...
Click to expand...
Click to collapse
Device Info said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D22FVX2
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: A5E6C5060F000000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "flashfail" configured as fastboot
(bootloader) imei: 35xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-17-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 20 17:54:23 UTC 1969"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.46-28/28:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3105.93.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:38:33 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D22FVX2
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.073s
Click to expand...
Click to collapse
I was also wondering what this means:
"(bootloader) reason: UTAG "flashfail" configured as fastboot"
I appreciate any hint.
Related
Info
C:\androidsdk\tools>fastboot getvar all
INFOversion-bootloader: 30B4
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Samsung S4 SDRAM DIE=4Gb
INFOemmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
INFOproduct: ghost
INFOrevision-hardware: 0x8300
INFOradio: 0x1
INFOsecure: yes
INFOmid: 026b
INFOserialno: T01130D03O
INFOqe: qe 0/0
INFOunlocked: no
INFOiswarrantyvoid: no
INFOmax-download-size: 805306368
INFOuid: 85828E040C000100000000000000
INFOimei: 000000000000000
INFOmeid:
INFOsku: 000000000000000
INFOcid: 0xff
INFOiccid: 89014103286406835591
INFOdate: 01-01-1970
INFOcust_md5:
INFOreason: Reboot to bootloader
INFOro.build.date: Mon Jul 15 17:06:36 CDT 2013
INFOro.build.id:
INFOro.build.tags: release-keys
INFOro.build.type: userdebug
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.incremental: 14
INFOro.build.version.release: 4.2.2
INFOro.mot.build.customerid: att
INFOro.product.name: factory_ghost
INFOro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
INFOro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-11/
INFOro.build.fingerprint[2]: 14:userdebug/release-keys
INFOro.build.version.full[0]: Blur_Version.139.9.51.ghost_att.
INFOro.build.version.full[1]: ATT.en.US
INFOkernel.version[0]: Linux version 3.4.42-xline-eng-g
INFOkernel.version[1]: fd1a699-00137-g677455b (hudsoncm
INFOkernel.version[2]: @il93lnxdroid48) (gcc version 4.
INFOkernel.version[3]: 6.x-google 20120106 (prerelease)
INFOkernel.version[4]: (GCC) ) #1 SMP PREEMPT Mon Jul
INFOkernel.version[5]: 15 17:32:37 CDT 2013
Error
Are you in bootloader or android?:bootloader
...
OKAY [ 0.109s]
finished. total time: 0.109s
sending 'partition' (32 KB)...
OKAY [ 0.234s]
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.453s]
finished. total time: 0.688s
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
flashing aboot ...
flashing sbl3 ...
flashing rpm ...
flashing tz ...
flashing sbl2 ...
flashing sbl1 ...
OKAY [ 4.875s]
finished. total time: 5.219s
sending 'logo' (636 KB)...
OKAY [ 0.313s]
writing 'logo'...
OKAY [ 0.891s]
finished. total time: 3.578s
sending 'boot' (10240 KB)...
OKAY [ 0.906s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.063s
sending 'recovery' (10240 KB)...
OKAY [ 0.922s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.094s
sending 'system' (786432 KB)...
OKAY [ 49.453s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 50.813s
Tried
ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-51_CFC_1FF.xml.zip
ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF.xml.zip
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip
One Phone screen ...
Failed to hab check for recovery: 0x56
preflash validation failed for recovery
Failed to hab check for recovery: 0x56
preflash validation failed for system failed
Invalid PIV image : system
In the output of fastboot getvar all it said your bootloader version was 30.B4, yet it said NFOro.build.version.release: 4.2.2
That is your problem. At some point that phone had 4.4.2 on it and was downgraded by skipping at least motoboot.img if not also skipping gpt.bin.
It has been advised MANY TIMES to not downgrade.
Further, the output says.. Blur_Version.139.9.51.ghost_att. that is the INITIAL SHIPPING ROM.. again, its been said that downgrading to that is an automatic brick.
AT this point, I hesitate to suggest anything. But AT YOUR OWN RISK!! you can try -> ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF.xml.zip unzip it, get the latest mFastboot and use the steps under OPTION 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
and hope it works. If it does not, then try it again with the 4.4.4 SBF.
ATT_XT1058_4.4.2-KXA20.16-1.31.1_CFC_1FF
C:\Moto>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.125s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.234s]
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.453s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.359s]
writing 'motoboot'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl1 ...
OKAY [ 5.016s]
finished. total time: 5.375s
C:\Moto>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.250s]
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.453s]
finished. total time: 0.703s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl1 ...
OKAY [ 4.953s]
finished. total time: 5.297s
C:\Moto>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (636 KB)...
OKAY [ 0.328s]
writing 'logo'...
OKAY [ 0.875s]
finished. total time: 1.219s
C:\Moto>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.938s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.094s
& same thing happening on ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
C:\Moto>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.125s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.266s]
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.422s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.391s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 4.938s]
finished. total time: 5.328s
C:\Moto>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Moto>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.266s]
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.422s]
finished. total time: 0.688s
C:\Moto>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.375s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 4.922s]
finished. total time: 6.266s
C:\Moto>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.328s]
writing 'logo'...
OKAY [ 0.891s]
finished. total time: 1.219s
C:\Moto>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.922s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.078s
Not sure what to suggest. Your phone isn't far enough gone to try this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
maybe we can get @samwathegreat to offer a few suggestions?
KidJoe said:
Not sure what to suggest. Your phone isn't far enough gone to try this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
maybe we can get @samwathegreat to offer a few suggestions?
Click to expand...
Click to collapse
Yikes! Looks like the method I *would have* suggested has already been tried and was unsuccessful.
The only way that I've found to recover a device once it starts failing validation checks on boot.img is to unlock the bootloader. After unlocking, it should be able to flash without error. Of course....middleman would have to be involved.
I don't see another option, sadly :/
samwathegreat said:
Yikes! Looks like the method I *would have* suggested has already been tried and was unsuccessful.
The only way that I've found to recover a device once it starts failing validation checks on boot.img is to unlock the bootloader. After unlocking, it should be able to flash without error. Of course....middleman would have to be involved.
I don't see another option, sadly :/
Click to expand...
Click to collapse
Yes ... i too was thinking about unlocking bootloader might solve the problem
How much $$ for a boot loader unlock ... any idea ?
aamszia said:
How much $$ for a boot loader unlock ... any idea ?
Click to expand...
Click to collapse
China Middleman thread in general section is $45, Jcase's yet to be released Sunshine tool $25. But we don't know the details of Sunshine yet, like if you must be on certain version, etc.
KidJoe said:
China Middleman thread in general section is $45, Jcase's yet to be released Sunshine tool $25. But we don't know the details of Sunshine yet, like if you must be on certain version, etc.
Click to expand...
Click to collapse
Sunshine might not work i updated it to 4.4.4 bootloaders ?
aamszia said:
Sunshine might not work i updated it to 4.4.4 bootloaders ?
Click to expand...
Click to collapse
We don't know if it will work on 4.4.4 devices.
BUT, sunshine is an **APP**. If you device can not boot into Android, well...............you can't run an app, can you?
Middleman will likely be your only option.
samwathegreat said:
We don't know if it will work on 4.4.4 devices.
BUT, sunshine is an **APP**. If you device can not boot into Android, well...............you can't run an app, can you?
Middleman will likely be your only option.
Click to expand...
Click to collapse
the phone is on .. and menu & settings all messed up .. but i think i can install an APP in this condition
DAM ... Xt907 bricked b me today .. & guess what ... the same error .. Prevalidation Failed .. .. Phone had 4.4.2 before .. I was just re-installing 4.4.2 again becasuse wifi was not working .. . Now got stuck in fastboot ..
I am UNLUCKY
What version were you coming from before you got the validation error for 4.4.2?
Sent from my XT1080 using XDA Free mobile app
Gtech145 said:
What version were you coming from before you got the validation error for 4.4.2?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
4.4.2 ........... it was the same versio i guess
yesterday i received Moto G UNLOCKED BOOTLOADER
same error PRE VALIDATION FAILED
Hi! I have a Moto G XT1072 and my stock rom (6.0 August security patch) was buggy so I decided to reinstal the stock firmware. But during the process, some lines have bootloader error. Like this:
Flasheando gpt...
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
Flasheando boot.img (kernel)...
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.828s
Flasheando recovery...
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.844s
Flasheando system (sparsechunk.0)...
target max-sparse-size: 256MB
sending 'system' (256869 KB)...
OKAY [ 8.079s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.470s
Flasheando system (sparsechunk.1)...
target max-sparse-size: 256MB
sending 'system' (257186 KB)...
OKAY [ 8.095s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.173s
Flasheando system (sparsechunk.2)...
target max-sparse-size: 256MB
sending 'system' (258793 KB)...
OKAY [ 8.141s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.204s
Flasheando system (sparsechunk.3)...
target max-sparse-size: 256MB
sending 'system' (260733 KB)...
OKAY [ 8.204s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.313s
Flasheando system (sparsechunk.4)...
target max-sparse-size: 256MB
sending 'system' (68300 KB)...
OKAY [ 2.217s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.287s
Click to expand...
Click to collapse
I have locked bootloader and no root. I was searching in XDA and Google and found that this error appears when you try to flash and invalid firmware or trying to do a downgrade (not my case). I tried two differents firmwares (EU Release and LATAM Release) but I have the same problem. So what's happening and how to fix it? Thanks and sorry for my bad english!
Factory Firmware Images are not designed for casual flashing. They are intended for flashing once, and as an upgrade. This is why you can get a 'Preflash validation' error when downgrading, and even when flashing a system version already on the phone.
Hello everbody
A a year ago I tried to install a stock rom on my XT1072, but accidentally used an XT1068 rom. When I used "mfastboot getvar all" my phone got recognized as a TITAN instead of a THEA. I managed to install Lineage, but now my phone is stuck and restarts after a few seconds while showing the "Warning Bootloader Unlocked" message.
I tried to flash the latest version of Lineage "lineage-14.1-20170728-nightly-thea" but it failed and the screen displayed the following message.
Updater process ended with ERROR: 7
Erorr installing Zip file 'sdcard1/lineage-14.1-20170728-nightly-thea-signed.zip'
Updating partition details. . .
Failed to mount '/data' (Invalid argument
. . .done
I googled this error and it appears that my device is incompatible with the OS. I think it's because of the mismatching info I highlighted in the seconds hidden part.
After this, I tried to install this (https://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075) stock rom, but most of the commands failed
C:\XT1072 - 6.0 Stock Rom>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.040s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.381s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error
C:\XT1072 - 6.0 Stock Rom>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.074s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.196s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.402s]
writing 'boot'...
OKAY [ 0.389s]
finished. total time: 0.800s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.403s]
finished. total time: 0.809s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256869 KB)...
OKAY [ 13.664s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.789s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257163 KB)...
OKAY [ 11.165s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.290s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (261045 KB)...
OKAY [ 13.967s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 14.045s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (248543 KB)...
OKAY [ 13.439s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 13.501s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (83796 KB)...
OKAY [ 4.510s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.541s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60992 KB)...
OKAY [ 2.558s]
writing 'modem'...
OKAY [ 2.070s]
finished. total time: 4.637s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.026s]
finished. total time: 0.029s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.024s]
finished. total time: 0.027s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (320 KB)...
OKAY [ 0.107s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 0.213s
C:\XT1072 - 6.0 Stock Rom>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.166s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.108s]
finished. total time: 1.281s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.139s]
finished. total time: 0.142s
C:\XT1072 - 6.0 Stock Rom>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.463s]
finished. total time: 0.465s
All of the system.img_sparsechunk failed with an "Image is too large" message and gpt.bin failed with "version downgraded for primary_gpt". After this I did "mfastboot getvar all" after I noticed that the bootloader version changed from 48.21 to 48.22. The phone is now recognized as a THEA again, but some parts are still labeled TITAN instead of THEA
C:\XT1072 - 6.0 Stock Rom>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4822
(bootloader) product: thea
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x3
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C22D9DG
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: DDF97E0215000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 353310062384405
(bootloader) meid:
(bootloader) date: 07-03-2015
(bootloader) sku: XT1072
(bootloader) battid: SNN5956A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Aug 23 22:51:53 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.99-16/10:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retde
(bootloader) ro.build.version.full[1]: .retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.22-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.22-0-gbffe41a
(bootloader) rpm.git: git=MBM-NG-V48.22-0-gbe53f43
(bootloader) tz.git: git=MBM-NG-V48.22-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.22-0-g1b80345
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1C22D9DG
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
finished. total time: 0.128s
Is there any way to fix my phone and install the Stock or Lineage Rom? Thanks for all kinds of advice or suggestions
Hi guys,
My Moto X2 (XT1097) not boot in normal mode (only in fast boot screen), i try flash stock rom with RSD Lite 6.2.4 with "XT1097_VICTARA_RETBR_6.0_MPES24.49-18-7_cid12_CFC.xml" but all times i get error...
Error info in fastboot sreen:
"Failed to validate system image"
"Fastboot Reason: Fail-through from normal boot mode"
if i try flash via "Moto Auto Flash Tool v7.1" i receive errors = (bootloader) Invalid signed image - (bootloader) Preflash validation failed - FAILED (remote failure)
Adicional Info:
1º Normal powerup, Recovery and Factory not work (if try acess return to fastboot menu and show "boot up failed")
2º I have unlock code in my e-mail (but i get error to try unlock via fastboot and device still lock)
3º In RSD Lite the device is detected (Fastboot Victara S) but "device propertis" all info is "N/A"
4º In RSD Lite after start flashing, the error show is "failed flashing process 6/27 flash boot "boot.img" -> Phone Returned FAIL."
Tecnical information:
Model: Moto X2 - XT1097
Device is Locked.
Status code: 0
Software Status: Official
Moto Auto Flash Tool v7.1 info:
Code:
Moto Auto Flasher / Root Script By Jamesjerss
________________________________________________________________________________
Connect in Fastboot Mode
(bootloader) version: 0.5
(bootloader) version-bootloader: 6100
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: 0011988140
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 0000000000000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353320064305837
(bootloader) meid:
(bootloader) date: 2015-06-12
(bootloader) sku: XT1097
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 28 4:41: 2 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/victara_retbr/victara:6.0
(bootloader) ro.build.fingerprint[1]: /MPES24.49-18-7/7:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.7.victara_ret
(bootloader) ro.build.version.full[1]: br.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_S
(bootloader) version-baseband[1]: INGLELA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g0dad312 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Thu Sep 1 10:44:51 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V61.00-0-g582b967
(bootloader) sbl1.git: git=MBM-NG-V61.00-0-g5147b20
(bootloader) rpm.git: git=MBM-NG-V61.00-0-gc54d917
(bootloader) tz.git: git=MBM-NG-V61.00-0-gacbc999
(bootloader) aboot.git: git=MBM-NG-V61.00-0-g130760b
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: retbr
all: listed above
Execution time is 1(s)
Done!
Press any key to go Home
If i try flash via "Moto Auto Flash Tool v7.1"
Code:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.093s]
finished. total time: 0.106s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.086s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.341s]
finished. total time: 0.431s
FLASHING BOOTLOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\bootloader.img': No error
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (1454 KB)...
OKAY [ 0.075s]
writing 'logo'...
OKAY [ 0.045s]
finished. total time: 0.124s
FLASHING BOOT...
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.366s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.385s
FLASHING RECOVERY...
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.374s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img': No error
target max-sparse-size: 256MB
sending 'system' (257335 KB)...
OKAY [ 8.399s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.442s
target max-sparse-size: 256MB
sending 'system' (256636 KB)...
OKAY [ 8.389s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.427s
target max-sparse-size: 256MB
sending 'system' (256815 KB)...
OKAY [ 8.400s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.436s
target max-sparse-size: 256MB
sending 'system' (260318 KB)...
OKAY [ 8.506s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.541s
target max-sparse-size: 256MB
sending 'system' (260548 KB)...
OKAY [ 8.520s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.552s
target max-sparse-size: 256MB
sending 'system' (249475 KB)...
OKAY [ 8.151s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.188s
target max-sparse-size: 256MB
sending 'system' (256925 KB)...
OKAY [ 8.398s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.432s
target max-sparse-size: 256MB
sending 'system' (257925 KB)...
OKAY [ 8.436s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.469s
FLASHING MODEM...
target max-sparse-size: 256MB
sending 'modem' (63188 KB)...
OKAY [ 2.079s]
writing 'modem'...
OKAY [ 0.852s]
finished. total time: 3.177s
erasing 'modemst1'...
OKAY [ 0.009s]
finished. total time: 0.010s
erasing 'modemst2'...
OKAY [ 0.007s]
finished. total time: 0.009s
target max-sparse-size: 256MB
sending 'fsg' (871 KB)...
OKAY [ 0.052s]
writing 'fsg'...
OKAY [ 0.054s]
finished. total time: 0.110s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.252s]
finished. total time: 0.254s
ERASING USERDATA...
erasing 'userdata'...
OKAY [ 1.463s]
finished. total time: 2.884s
Done!...Press any key to Go Menu There Press R to Reboot
Please, any help...
Sorry my english is rusty.
Does anyone know how to remove the flashing_lock and your device has loaded a different operating system to get back to the stock market?
Pictures:https://photos.app.goo.gl/B8UQEMkfR7E1mp4cA
my device:Revvlry Plus
model number:XT1965-T
Picture 1 and 3 are included in your logo.bin which is stored on your logo partition (/dev/block/by-name/logo). They appear when you unlock the bootloader. To change them you should flash a custom boot logo.
Picture 2 is the normal fastboot menu.
Did you try to flash a firmware?
you are not the only one who has the same problem
WoKoschekk said:
Picture 1 and 3 are included in your logo.bin which is stored on your logo partition (/dev/block/by-name/logo). They appear when you unlock the bootloader. To change them you should flash a custom boot logo.
Picture 2 is the normal fastboot menu.
Did you try to flash a firmware?
Click to expand...
Click to collapse
yes, flash firmware but as a device it says that bootloader is flashing_locked and doesn't allow me to flash it, it asks me for a signed image.
and for custom logo.bin I have to unlock bootloader and that doesn't help me, I want to leave it as factory stock rom.
my device:Revvlry Plus
model number:XT1965-T
darkherman said:
yes, flash firmware but as a device it says that bootloader is flashing_locked and doesn't allow me to flash it, it asks me for a signed image.
and for custom logo.bin I have to unlock bootloader and that doesn't help me, I want to leave it as factory stock rom.
my device:Revvlry Plus
model number:XT1965-T
Click to expand...
Click to collapse
The current firmware on your device can be found via fastboot command
Code:
fastboot getvar ro.build.fingerprint
Output is (e.g. my device):
(bootloader)ro.build.fingerprint[0]:motorola/ali_n/ali_
n:9/PPSS29.55-3
(bootloader) ro.build.fingerprint[1]: 7-7-2/924b9:user/
release-keys
You should read fingerprint[0] and fingerprint[1] as one line:
motorola/ali_n/ali_n:9/PPSS29.55-37-7-2/924b9:user/release-keys
In this case my current firmware is:
PPSS29.55-37-7-2
Here is a link to your firmware builds.
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
Download the firmware that is matching with the output of the fastboot command and flash it. That should restore your boot logo.
WoKoschekk said:
The current firmware on your device can be found via fastboot command
Code:
fastboot getvar ro.build.fingerprint
Output is (e.g. my device):
(bootloader)ro.build.fingerprint[0]:motorola/ali_n/ali_
n:9/PPSS29.55-3
(bootloader) ro.build.fingerprint[1]: 7-7-2/924b9:user/
release-keys
You should read fingerprint[0] and fingerprint[1] as one line:
motorola/ali_n/ali_n:9/PPSS29.55-37-7-2/924b9:user/release-keys
In this case my current firmware is:
PPSS29.55-37-7-2
Here is a link to your firmware builds.
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
Download the firmware that is matching with the output of the fastboot command and flash it. That should restore your boot logo.
Click to expand...
Click to collapse
if I tried that and it says denied, what I'm trying to do is get it back to normal because it blocks bootloader again and says: your device has loaded a different operating system
What was denied? The fastboot command to get the build? Then download the latest firmware from page provided in my link. You can always flash the same firmware that is already installed. You must try it.
---------- Post added at 10:38 PM ---------- Previous post was at 10:22 PM ----------
Is it possible to boot up into system? Then go to settings > system > about phone and search the build number. Download the right firmware and try to flash it with the mfastboot tool. It's nearly the same as fastboot but was made for Motorola devices and firmware.
Maybe it is possible to flash only the logo.bin??
Or use the Lenovo Motorola Smart Assistant to get back to stock.
WoKoschekk said:
What was denied? The fastboot command to get the build? Then download the latest firmware from page provided in my link. You can always flash the same firmware that is already installed. You must try it.
---------- Post added at 10:38 PM ---------- Previous post was at 10:22 PM ----------
Is it possible to boot up into system? Then go to settings > system > about phone and search the build number. Download the right firmware and try to flash it with the mfastboot tool. It's nearly the same as fastboot but was made for Motorola devices and firmware.
Maybe it is possible to flash only the logo.bin??
Or use the Lenovo Motorola Smart Assistant to get back to stock.
Click to expand...
Click to collapse
LMSA doesn't work, post it here https://forums.lenovo.com/t5/moto-g7-play-moto-g7-moto-g7/Revvlry-not-support-LMSA/td-p/4644912
in command mfastboot is denying me all commands to write the corresponding partition
darkherman said:
LMSA doesn't work, post it here https://forums.lenovo.com/t5/moto-g7-play-moto-g7-moto-g7/Revvlry-not-support-LMSA/td-p/4644912
in command mfastboot is denying me all commands to write the corresponding partition
Click to expand...
Click to collapse
That's strange... Are you able to boot into system?
WoKoschekk said:
That's strange... Are you able to boot into system?
Click to expand...
Click to collapse
The system boots perfectly, but the thing that doesn't work is that the verity boot of A/B that detects the integrity of the system is broken and in play store it says that the device is not certified and no apps like netflix appear and other similar apps don't appear
Enviado desde mi Moto G7 Plus mediante Tapatalk
Why did you flash another firmware with a locked bootloader?? You won't be able to install further updates with broken verity.
Which build is installed and which build are you trying to flash?
WoKoschekk said:
Why did you flash another firmware with a locked bootloader?? You won't be able to install further updates with broken verity.
Which build is installed and which build are you trying to flash?
Click to expand...
Click to collapse
do not flash other firmware I have only used TMO and you know well that it will not allow me to install other firmware from another market.
I want to return the stock rom and because I don't like to use custom rom at the moment and I want to remove the message that I know in picture when device is turning on.
log fastboot getvar all:
Code:
PS C:\Users\yunio> fastboot getvar all (bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_revvl-e7be04b-191127
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: TMO
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (2)
(bootloader) serialno: ZY226GNL47
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3F6F892B
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-26-2019
(bootloader) sku: XT1965-T
(bootloader) carrier_sku: XT1965-T
(bootloader) battid: SB18C53460
(bootloader) battery-voltage: 3752
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_revvl_n/lake_n:9/PCW
(bootloader) ro.build.fingerprint[1]: S29.83-56-8/db4d:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.7.lake_rv.rev
(bootloader) ro.build.version.full[1]: vl.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05900-sdm660.0
(bootloader) version-baseband: M636_08.23.02.46R LAKE_TMO_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1b289e4 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Wed Nov 27 03:41:16 CST 2019
(bootloader) git:abl: MBM-3.0-lake_revvl-e7be04b-191127
(bootloader) git:xbl: MBM-3.0-lake_revvl-a366ae0-191127
(bootloader) git:pmic: MBM-3.0-lake_revvl-a366ae0-191127
(bootloader) git:rpm: MBM-3.0-lake_revvl-33b79ec-191127
(bootloader) git:tz: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:hyp: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:devcfg: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:cmnlib: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:cmnlib64: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:keymaster: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:prov: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) git:storsec: MBM-3.0-lake_revvl-25bf0b3-191127
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.243s
log flash firmware command
Code:
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.107s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (37 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.136s]
finished. total time: 0.144s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (9520 KB)...
OKAY [ 1.864s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 1.984s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (76476 KB)...
OKAY [ 2.542s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.547s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (9408 KB)...
OKAY [ 0.307s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.320s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash bluetooth BTFM.bin
target max-sparse-size: 256MB
sending 'bluetooth' (400 KB)...
OKAY [ 0.016s]
writing 'bluetooth'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.027s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash dsp dspso.bin
target max-sparse-size: 256MB
sending 'dsp' (16384 KB)...
OKAY [ 0.530s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.534s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2560 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.088s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (22153 KB)...
OKAY [ 0.710s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.718s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash dtbo dtbo.img
target max-sparse-size: 256MB
sending 'dtbo' (16 KB)...
OKAY [ 0.004s]
writing 'dtbo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.020s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 15.573s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.637s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 10.307s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 10.315s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 9.359s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.366s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 9.381s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.386s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (235264 KB)...
OKAY [ 8.524s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 8.530s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system_b system_b.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system_b' (262140 KB)...
OKAY [ 9.284s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.289s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash system_b system_b.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system_b' (45272 KB)...
OKAY [ 1.453s]
writing 'system_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.457s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash vendor vendor.img
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'vendor' (262140 KB)...
OKAY [ 9.271s]
writing 'vendor'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.276s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (136156 KB)...
OKAY [ 4.350s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.355s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot flash oem_b oem_other.img
target max-sparse-size: 256MB
sending 'oem_b' (92264 KB)...
OKAY [ 2.945s]
writing 'oem_b'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 2.952s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot erase carrier
erasing 'carrier'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot erase ddr
erasing 'ddr'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.014s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>echo -------------------------------------------------------------------------
-------------------------------------------------------------------------
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>echo please scroll up and check your flash for any errors
please scroll up and check your flash for any errors
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>echo -------------------------------------------------------------------------
-------------------------------------------------------------------------
C:\Windows.old\Users\Will Celular\Downloads\Compressed\XT1965-T_LAKE_REVVL_9.0_PCWS29.83-56-8_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml>pause
Any solutions?
darkherman said:
Any solutions?
Click to expand...
Click to collapse
Your getvar all says bootloader is locked
Sent from my mata using XDA Labs
---------- Post added at 06:33 PM ---------- Previous post was at 06:30 PM ----------
Nevermind wrong thread
Sent from my mata using XDA Labs
---------- Post added at 07:17 PM ---------- Previous post was at 06:33 PM ----------
darkherman said:
Any solutions?
Click to expand...
Click to collapse
The only solution I see is
Unlock the bootloader
Root with magisk
Magisk can hide the unlocked bootloader
Sent from my mata using XDA Labs
sd_shadow said:
Your getvar all says bootloader is locked
Sent from my mata using XDA Labs
---------- Post added at 06:33 PM ---------- Previous post was at 06:30 PM ----------
Nevermind wrong thread
Sent from my mata using XDA Labs
---------- Post added at 07:17 PM ---------- Previous post was at 06:33 PM ----------
The only solution I see is
Unlock the bootloader
Root with magisk
Magisk can hide the unlocked bootloader
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I don't like to use magisk for daily use, I only use it for development and testing.
thanks for everything
darkherman said:
Any solutions?
Click to expand...
Click to collapse
Unlock the bootloader, flash the firmware and relock the bootloader. As I can see in your output of "getvar all" the warranty is already void. So you won't loose anything by it.
darkherman said:
Does anyone know how to remove the flashing_lock and your device has loaded a different operating system to get back to the stock market?
Pictures:https://photos.app.goo.gl/B8UQEMkfR7E1mp4cA
my device:Revvlry Plus
model number:XT1965-T
Click to expand...
Click to collapse
Managed to solve?
Copo Gold said:
Managed to solve?
Click to expand...
Click to collapse
MotoBootLogoMaker
Download MotoBootLogoMaker for free. Change Motorola splash screen --> logo.bin. Moto Boot Logo Maker for Motorola Moto Devices (4MiB, 6MiB, 8MiB, 16MiB & 32MiB) - All Moto devices supported Source Code: https://github.com/Franco28/Moto_Boot_Logo_Maker
sourceforge.net