Could someone PLEASE provide an image of the 4.4.2 Kitkat firmware (preferably Retail.EU) suitable for flashing with RSD Lite?
For all those who got stuck with a dead phone...
pj.de.bruin said:
Could someone PLEASE provide an image of the 4.4.2 Kitkat firmware (preferably Retail.EU) suitable for flashing with RSD Lite?
For all those who got stuck with a dead phone...
Click to expand...
Click to collapse
There is nothing we can do, someone needs the fastboot files from Moto / a leaked source.
Just use RSD+JB and then take the OTA to KK
dagoban said:
There is nothing we can do, someone needs the fastboot files from Moto / a leaked source.
Just use RSD+JB and then take the OTA to KK
Click to expand...
Click to collapse
No , flashing JB with RSD, which used to work before upgrading to KK, now fails with:
Downloading ...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Is there a workaround?
Or is there a way to flash the KIA20.74.rar version using just the standard recovery mode?
Or to flash CM11?
(I was in the KitKat testdrive program, and all worked fine till the application updates of last week.
Now the boot process stops while either the Motorola or Intel logo is shown.
Full factory restore using recovery mode doesn't help.
I had this twice before while on Jelly Bean, and solved it by flashing with RSD.)
pj.de.bruin said:
No , flashing JB with RSD, which used to work before upgrading to KK, now fails with:
Downloading ...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Is there a workaround?
Or is there a way to flash the KIA20.74.rar version using just the standard recovery mode?
Or to flash CM11?
(I was in the KitKat testdrive program, and all worked fine till the application updates of last week.
Now the boot process stops while either the Motorola or Intel logo is shown.
Full factory restore using recovery mode doesn't help.
I had this twice before while on Jelly Bean, and solved it by flashing with RSD.)
Click to expand...
Click to collapse
Remove the line with gpt_signed from the XML file is the rsd lite package
Hazou said:
Remove the line with gpt_signed from the XML file is the rsd lite package
Click to expand...
Click to collapse
No good, the boot and system patitions give the same problem, and still no booting.
Partition (system) Security Version Downgraded
PIV block validaton failed
eIV block validation failed for system
Invalid PIV image: systemFastboot command failedRecovery and motobp could be flashed.
pj.de.bruin said:
No good, the boot and system patitions give the same problem, and still no booting.
Partition (system) Security Version Downgraded
PIV block validaton failed
eIV block validation failed for system
Invalid PIV image: systemFastboot command failedRecovery and motobp could be flashed.
Click to expand...
Click to collapse
I had no problem flashing JB with RSD over KK
dagoban said:
I had no problem flashing JB with RSD over KK
Click to expand...
Click to collapse
Then where did you get JB?
The (Retail.EU) version I'm using is named "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml" and dated 01/17/2013.
My KK version is not the OTA, but the latest one from the testdrive program.
pj.de.bruin said:
Then where did you get JB?
The (Retail.EU) version I'm using is named "CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml" and dated 01/17/2013.
My KK version is not the OTA, but the latest one from the testdrive program.
Click to expand...
Click to collapse
"CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml" is a JB image
What if u flash the gpt.bin (or how it is called) from a 4.4.2 update zip through fastboot. This will solve the gpt security mismatch. Then try RSD-Lite again, but remove the gpt line. Or flash the system_signed, recovery_signed, boot_signed manually with mFastboot or fastboot compatible with an image that's more than 100mb. And then do a full data erase.
The 4.4.2 update zip is floating around somewhere for the gpt file, already seen it on the internet.
This should solve your problem. If it doesn't u got a far greater problem i think, or i just don't know.
Hazou said:
"CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml" is a JB image
What if u flash the gpt.bin (or how it is called) from a 4.4.2 update zip through fastboot. This will solve the gpt security mismatch. Then try RSD-Lite again, but remove the gpt line. Or flash the system_signed, recovery_signed, boot_signed manually with mFastboot or fastboot compatible with an image that's more than 100mb. And then do a full data erase.
The 4.4.2 update zip is floating around somewhere for the gpt file, already seen it on the internet.
This should solve your problem. If it doesn't u got a far greater problem i think, or i just don't know.
Click to expand...
Click to collapse
Nope, flashing gpt_signed, or any of the other signed images, with mfastboot give the same preflash validation errors as with RSD, as was to be expected.
I have found some 4.4.2 update zips, but they are all TWRP backups, not full partition images; I don't see how these can be flashed with mfastboot.
Found it! I had to unlock the bootloader, and now JB can be flashed.
I guess it would also have been possible, after unlocking the bootloader, to flash the "unofficial TWRP recovery" and then install one of the 4.4.2 TWRP backups from an SD card.
Right.
So, I was opening youtube on the last version of CM 12.1. No xposed, stock kernel, XT1068 model, when all of a sudden the phone stopped working.
Youtube wasn't opening. The phone was stuck on the home screen, all I could do was just press the home/back/recent buttons. Even long pressing power button to reboot would just take me to the power menu but Wouldn't allow me to do anything.
So in the end I long pressed the power menu to force reboot the phone aaaand... stuck on the boot logo. Not on the bootanimation, on the Motorola Bootlogo.
Managed to get to fastboot mode, tried to go to recovery, but after the twrp splash screen It would reboot to the splash screen again.
So i decided to mfastboot the original firmware. Who knows? maybe something got corrupted on cm.
Now, mfastboot is giving me weird errors.
flash partition gpt.bin gives (bootloader) Preflash validation failed
flash motoboot motoboot.bin gives FAILED (data transfer failure (Unknown error))
flash boot boot.img freezes everything and i need to reboot it to try and get to fastboot again.
Anybody knows what I should do? I'm kinda desperate here...
Thanks in advance. Peace.
(by the way, latest motorola drivers, just so you know...)
EDIT. Also, on the phone, it says
"hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
Hope I can help
Are you flashing a gpt.bin from a previous android version? You cannot downgrade gpt.bin or motoboot.bin so the error is normal. From what firmware version is the boot.img you are flashing from? Try downloading this twrp recovery img from here https://dl.twrp.me/titan and
Code:
fastboot flash recovery recovery.img
or
Code:
mfastboot flash recovery recovery.img
Then you can try flashing any rom like this AOSP one http://forum.xda-developers.com/moto-g-2014/development/rom-android-source-project-t3123109
Hope this helps. I understand how hard it is to have a phone that won't boot.
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
LudwigFerdinand18 said:
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
Click to expand...
Click to collapse
You cannot downgrade gpt
Well I somehow managed to reboot into recovery, but the great problem here is that it won't mount \data.
Now, maybe all I need is to reformat \data cause it got corrupted, but since TWRP won't mount it, I can't do much about it.
I found on another thread this command
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Which apparently formats the data partition of a phone. I suppose I'd have to change "ext4fs" into "f2fs", but I'm too scared to actually try it out.
Also because I don't know whether mmcblk0p8 is the right block for our data partition.
Jeez, I hate this.
Thanks for your help guys, but I don't think flashing recovery again would help. Nor downgrading, but I'll think about it.
EDIT.
Magic, just magic. After hours of tinkering I did EXACTLY THE SAME THINGS and now it's working. Restored the stock Rom and I'm off to install CM again.
Sorry guys and thanks so much!!!
Hi there,
a friend asked me for help with restoring his german Moto G 2014 (XT1068). The last working software on the device was the Marshmallow update. He was having software issues and softbricked the device when trying to install a custom ROM.
Fastboot mode and stock recovery is accesible, the bootloader is unlocked and the device is stuck on the "WARNING: BOOTLOADER UNLOCKED" screen when trying to boot normally.
I have tried following this guide to revert the phone back to stock firmware with a matching system image. Both the XT1068_TITAN_RETDE_6.0_MPB24.65-34-3_cid7_CFC and XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC images will flash without any error messages. However, the device does not boot the new software. Also, when trying to relock the bootloader, the mfastboot oem lock command failes with the error message Not supported command in current status!. I tried to substitute mfastboot with fastboot, changed USB cables and downloaded new copies the images, with no success.
Digging deeper, I found out that I could not wipe cache or data using the stock recovery. This will fail with the error message blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed. Further troubleshooting attempts lead me to try twrp custom recovery software (Version 3.1.1) which I could only start using the mfastboot boot twrp-3.1.1-0-titan.img command since flashing the image as custom recovery will not fail but the phone instantly and silently reverts to stock recovery - even when not rebooting inbetween. Consequently, any attempts to flash an image using the software will fail with E1001: Failed to update system image.
At this point, I have no idea what else I could try. That's why I turn to you, great community of XDA .
Any help would be greatly appreciated.
So my mom's phone started bootlooping yesterday. I've tried a couple of things to recover the data already, but nothing seems to work.
It bootloops at the "Optimising apps" part after the boot animation, is there for a couple of minutes and then reboots and starts doing it again.
The bootloader is locked and USB debug is turned off, so I can't access adb. I can't just unlock the bootloader, because as I already said I don't want to lose the data in there.
The phone probably has the latest update there is available installed, so most likely it's at 6.0.1 I think? and I think it's region RETAILDSDS (she bought it in Spain and it does have dual SIM).
Things I've already tried:
Booting into the stock recovery and trying to use adb, but it doesn't recognize the device (predictably so)
Flashing a custom recovery, I can't seemingly do that without unlocking bootloader first
Flashing a stock 6.0 firmware without erasing user data, gives the following error in cmd when trying to flash the system partition:
Code:
"writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)"
and in the phone it says:
Code:
cmd: flash: system
version downgraded for system
Invalid PIV signed system image
I accidentally flashed the wrong firmware on this device. Was meaning to flash stock firmware. But accidentally clicked the wrong "flash.bat" script. My reasoning was to fix an error with the ota update for the September patch. The bootloader is indeed locked and is not unlockable. and I can partly flash stock firmware but the boot.img and gpt.bin keep throwing a error "preflash validation failed". The bootloader logs show "failed to validate boot img". The firmware I tried to flash to fix it was the stock firmware. The variant of this device is ali. Carrier is tracfone. Someone please help. I would rather this device be of use instead of a close to $300 paper weight.
With a locked bootloader you are not able to flash anything, I believe. How about a factory reset in the recovery?