Related
Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.
Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s
cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip
Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?
waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.
Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?
Hi man, i have a problem.... Let's start: i had a eu moto x (xt1052) with fr firmware, moto is stock, so locked bootloader, stock recover and no root, i had received the ota to 4.4.4 but it cause me some connectivity problem, i have done the full wipe but i didnt solve; so i try to flash again the ota file but the installation fail and when i try to restart i had a bootloop (moto remain to the M screen).
i'm able to open recovery, to charge it and pc see it; how can i solve?
i also try to use rsd but there is no 4.4.4 firmware and i cant flash 4.4.2 (downgrade)
Need more details.
Since the OTA ZIp usually erases itself from the phone after successful install, how did you try and re-install it? Where did you get it from? When you say it failed, exactly what do you mean? (did you get an error? of so, what did it say?)
And you are right... DO NOT TRY AND DOWNGRADE!! Once you have 4.4.4. on there, stick with 4.4.4 or you risk bricking or setting yourself up to brick.
Since you can get into stock recovery, try and wipe data and cache from in there. Does the phone still bootloop?
ok, so it was an ota zip that someone in the italian's forum use, when i try to flash it it fail after some passage and show something like impossible rename the file? or similar.
i have try to do wipe data and wipe cache from recovery but it's the same.
how can i solve?
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
daniele1992 said:
i try to do a fastboot erase cache and a fastboot erase data.
the first said:
(bootloader) variable not supported!
erasing 'cache'...
okay and after the seconds
with the second
(bootloader) variable not supported!
erasing 'data'...
(bootloader) invalid partition name data
FAILED (remote failure)
finished
so?
Click to expand...
Click to collapse
The partition isn't named "data", it's "userdata"
Try again with the correct command:
fastboot erase userdata
no error here but i have the same bootloop
daniele1992 said:
no error here but i have the same bootloop
Click to expand...
Click to collapse
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
daniele1992 said:
hard to find but i will try, other question if i flash the new 4.4.4 firmware (when it will be relased) will i solve?
Click to expand...
Click to collapse
Almost certainly. Hopefully the full SBF/FXZ (Full XML Zip) for your specific variant is released very soon. Good Luck with it. :good:
samwathegreat said:
Hmmm ok. There is only ONE safe way to fix you back up. It won't be the easiest thing in the world to do since you will have to have someone on the EXACT SAME variant help you with this.
Re-flash TWRP. You'll need to find someone on the exact same XT1052 firmware (who also has TWRP) make a backup of JUST system and boot (not userdata).
They will share the backup with you, and you will flash it using TWRP (restore). That should fix you up -- it is the ONLY safe way to get back on track without downgrading and risking a brick..
Click to expand...
Click to collapse
Can anyone please help me with TWRP "backup of JUST system and boot" for XT1052 with stock 4.4.4 OTA (212.44.26.en.03)?
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!!!
my phone is moto g2 xt1068
i flash it with fastboot very much because after 3 days restarting and hang in boot but after flash it is work for 3-5 days
now i want to flash it but have this error fastboot
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.979s]
writing 'partition'...
FAILED (status read failed (Too many links))
finished. total time: 1.778
please help me
thanks
Do you have twrp?
Have you tried flashing twrp if you don't have it installed?
Which ROM are you flashing?
It looks like you don't have enough space if I'm reading that error correctly
We need to know so we can help you
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
This is stock firmware, yes?
Are all your Moto G drivers up to date?
There are a number of different ways to install depending on the package type.
Some packages are flashable zips. Needs Twrp (Team Win Recovery Project)
Some are sideload packages installed via Fastboot.
Some are OTA packages (OTA, over the air) installed via phone update.
amir58hz said:
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
Click to expand...
Click to collapse
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
bejunk said:
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
Click to expand...
Click to collapse
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
amir58hz said:
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
Click to expand...
Click to collapse
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
bejunk said:
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
Click to expand...
Click to collapse
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
amir58hz said:
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
Click to expand...
Click to collapse
Thx. But i need a picture of bootloader screen, see my picture!
-> hmm in your case i would try it now with formatting internal completly.. But even better would be full formating, so when you have TWRP:
- format Internal storage
- then tick system + data + cache and format them.
- You have to reflash stock then OR (i recommend) try it with a custom rom, like you said allready tried stock many times...
To install custom rom, get these files
ROM: https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-15-1-t3786749 get latest build
GApps: https://opengapps.org/ choose ARM -> 8.1 -> nano version
put everything in sdcard or storage (after wiping it)
Then in TWRP -> factory reset in wipe menu -> install ROM zip -> install GApps -> reboot. 1st boot can take some time. Test & report.
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
bejunk said:
Thx. But i need a picture of bootloader screen, see my picture!
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
Click to expand...
Click to collapse
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
amir58hz said:
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
Click to expand...
Click to collapse
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
Thanks very much
I dont have custom rom can you advise me to download it
I flashed it if is not have problem is very good but it crash and dont work i send here my problem
Thanks again good luck
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
hi man
after one day mobile is work true thanks alot
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
amir58hz said:
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
Click to expand...
Click to collapse
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
bejunk said:
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
Click to expand...
Click to collapse
No i flash it with same my frimware
Now for flashing with custom rom it need download rom android8?
i have this error in wipping and installing rombut instal it
my error is:
e:recv error on uevent
But now flashed to 8.1 android
Thanks