Database Info

Error: CWM does not enter Recovery mode, turn off phone

Hello I did all the procedures to unlock the bootloader, I took notice of warning logo.bin, so q can not install CWM or TRW, the error message Mismatched partition size (recovery), and every time I put q in the recovery screen goes blank or turns black Reboot help me. my android is 4.4.2

First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?

grrrrrrrrrrrrrrrrrrrr
FaultyFirmware said:
First I just want to repeat what you said, to make sure I understand. You followed the instructions to unlock the bootloader. Then you saw the warning screen so you know the unlocked worked. You tried to install a recovery, got a "mismatched partition size" error, and you can't get into your recovery. Is this correct?
The "mismatched partition size" error is normal, and you will get this message even if the new recovery flashes properly. Are you able to get to the bootloader without any problems? From where did you download the recovery that you tried to flash?
Click to expand...
Click to collapse
so I did it all you said, the only thing different foia message on boot that the phone was unlocked with the bootloader, you know that warning?
Dai to remove this message from the unlocked bootloader, flash the logo.bin file to go back to the original boot animation from motorola, I think that the bootloader is still unlocked ...
I grab the file from CWM downloaded here XDA same, this message of "Mismatched partition size (recovery)".
Ta many say that this message is normal, it happens that I put in the recovery squeeze the power button and the phone gets the black screen, and not everything goes back even after 2 minutes.
I believe that it shuts down, a version ai step before CWM, of the mismatched message ... however I enter recovery, and he does not turn off, just restarts ...
I mean I can not even get into recovery, and therefore can not make root .
Got the point? if you want to put the names of the files I tried to flash.

Here is a program that will help you install the recovery. USB debugging should be turned on on your phone, and you should be booted into the system. Also be sure that the proper USB drivers are installed on your computer.
http://forum.xda-developers.com/showthread.php?t=2635706
Here is the latest version of TWRP.
http://forum.xda-developers.com/showthread.php?t=2561757
Here is the latest version of PhilZ. It is a modified version of CWM.
http://forum.xda-developers.com/showthread.php?t=2639583
Choose one of the recoveries listed above and install with the tool. If you flash the recovery in this way, I think it will work for you. As always, read everything carefully. Know the type of Moto G you have and be sure to choose the right files.

this is complicated again tried to do what was already done with the files that I step, and the Moto tool aio tool and also via adb, and he clicking recovery restarts, do not know what to do more lost. I made a video and played on youtube showing the process, and what happens there happened to all types of file recovery and point out that the latter (philz_touch_6.13.2-xt1033.zip).
In the video also has all specifications. Please help me

So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.

FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
i have same problem. but i cant boot into ROM or custom recovery. i try flash latest phillz recovery but still not working. there is my log
H:\MotoToolAioV3\mfastboot-v2>fastboot devices
TA929046PR fastboot
H:\MotoToolAioV3\mfastboot-v2>fastboot -w
erasing 'userdata'...
OKAY [ 3.244s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.022s]
erasing 'cache'...
OKAY [ 0.413s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.024s]
finished. total time: 3.727s
H:\MotoToolAioV3\mfastboot-v2>fastboot flash recovery cwm.img
target reported max download size of 536870912 bytes
sending 'recovery' (8556 KB)...
OKAY [ 0.356s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.676s
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:20: 6 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.060s
H:\MotoToolAioV3\mfastboot-v2>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA929046PR
(bootloader) cid: 0x0007
(bootloader) uid: E98452020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359276056402244
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 8 8:22:49 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_o2de/falcon_umts:4
(bootloader) ro.build.fingerprint[1]: .4.2/KLB20.9-1.10-1.9.1/1:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.175.44.1.falcon_umts
(bootloader) ro.build.version.full[1]: .O2.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-gc6fc9e1-00001-g6ff8
(bootloader) kernel.version[1]: 71f ([email protected]) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Mon Jan 13 04:4
(bootloader) kernel.version[3]: 6:14 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.061s
H:\MotoToolAioV3\mfastboot-v2>
Click to expand...
Click to collapse

FaultyFirmware said:
So after you select and activate recovery and you see the Motorola logo, it boots into the normal system? You have the 8GB dual-sim Brazil/India/Malaysia version? This is not a Google Play Edition? Does the box it came in say "XT1033"?
The PhilZ you chose is not the latest version. They use a unified build now, which should work on all types of Moto G. It is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon//philz_touch_6.26.6-falcon.zip That one is worth a try. Your TWRP version is correct, though, so I don't know why that didn't work.
Your USB connection seems to be working fine, and you have tried ADB and the AIO tool. Have you tried using fastboot from the bootloader? The command would be "fastboot flash recovery recovery.img" and you would do this while you are in the bootloader. You should still expect to see the partition size mismatch error.
If that fails we can try flashing everything back to stock and start fresh. Please use "fastboot getvar all" and post the results (you can remove IMEI, Serial Number, and other private information). This will tell us which stock to use.
Click to expand...
Click to collapse
ok this is the print:
D:\Downloads\Android\adt-bundle-windows-x86_64-20140321\sdk\platform-tool
oot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4108
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) cid: 0x000C
(bootloader) uid: F66F3B020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 2014-01-24
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 18 15:49:10 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.2/KXB20.25-1.31/15:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.171.44.31.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AmericaMovil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g13e395f ([email protected]
(bootloader) kernel.version[1]: lclbld52) (gcc version 4.7 (GCC) ) #1 SM
(bootloader) kernel.version[2]: P PREEMPT Thu Jan 23 21:22:07 CST 2014
(bootloader) sdi.git: git=MBM-NG-V41.08-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.08-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.08-0-g8ef2ac8
(bootloader) tz.git: git=MBM-NG-V41.08-0-gcebfadf
(bootloader) aboot.git: git=MBM-NG-V41.08-0-g04a4bc3
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.057s

Yeah, I have the same issue :-/ phone just reboots instead of going into recovery :-/ I tried cwm and philz...
Sent from my XT1032 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:19 PM ----------
Guys, I have just discovered how to enter recovery... In fastboot mode press vol-down (this selects recovery option) and then vol-up. It goes into recovery. Tested with latest philz. I tried million of times but I expected power button to choose options... Is it normal behavior?
Sent from my XT1032 using xda app-developers app

Bro, try this method.
1.Download the Android SDK
2.Download the recovery you want (I used CWM but TWRP works aswell)
3.Go to Your SDK directory then go to \adt-bundle-windows-x86_64-20140321\sdk\platform-tools\
4.Inside you will find adb, fast boot stuff like that, now put your recovery inside there and rename it to recovery.img
5.Reboot into fasboot mode (power off + Vol- )
6.Go to your platform-tools folder, now hold Shift + press Right click, and select open command window here.
7. Type in:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
8.When that is complete reboot into recovery via the fastboot menu (Volume - then Volume + to select).
I hope this works, i had this problem before so now i just do this and i dont use the MotoTool AIO.

Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.

FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Thanks I use 4.4.2

FaultyFirmware said:
Wow, so much activity. Let's get this sorted.
sinkadorable: The command for rebooting into recovery is "fastboot reboot-recovery". Without the dash, nothing happens. That's what your log describes. You can use "adb reboot recovery" to enter recovery if you are fully booted into the system.
Routerm4N: For privacy you may want to edit your post to remove the lines labeled "imei" and "serialno". These can be used to uniquely identify your phone. So you tried flashing the file I liked in my last post and were unsuccessful? I don't have a copy of you ROM you are currently using, but it looks like this stock ROM is compatable with your phone. http://sbf.droid-developers.org/download.php?device=14&file=130 Are you on Android 4.3 or 4.4? The ROM I linked will take you back to 4.3, but you can always use OTA updates to get back again later. Here are the instructions for flashing stock firmware: http://forum.xda-developers.com/showthread.php?t=2542219 It is a bit of an involved process. Only do this if you have exhausted your other options.
fabus: Yes, it is unintuitive that the "up" button activates the selected option. However, it says on the bootloader screen that this is how it works. They probably wanted to reserve the power button for powering the device on and off.
Click to expand...
Click to collapse
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo

Even with adb?
sinkadorable said:
Still cannot boot into recovery with every method was i found. When i choose boot into recovery it just looping in boot logo
Click to expand...
Click to collapse
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??

deej_roamer said:
Are you getting same error when you fully boot into system, connect it to pc via a data cable
and run
Code:
adb reboot recovery
??
Click to expand...
Click to collapse
I think in fastboot menu cannot run adb command

sinkadorable said:
I think in fastboot menu cannot run adb command
Click to expand...
Click to collapse
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?

FaultyFirmware said:
This is true. I was saying you can use adb if you happen to be fully booted into the system.
Edit: Obviously you weren't referring to my post. Now I can't find the delete button.... Oh well.
Sinkadorable: have you tried flashing everything back to stock from the bootloader?
Routerm4N: How's your progress?
Click to expand...
Click to collapse
Yes. Every method was i found

While in bootloader menu, VOLUME DOWN(-) is for navigation, and VOLUME UP(+) is to select or choose the option.
POWER BUTTON DOES NOTHING!
DO NOT USE THE POWER BUTTON FOR ANYTHING WHILE IN BOOTLOADER MENU!

wow nice thanks

Hey i am having the same problem
anyone got any solution.
please update it.

[Q&A] [TOOL] Unbrick Corrupted Bootloader

Q&A for [TOOL] Unbrick Corrupted Bootloader
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

How do I unbrick corrupted Bootloader in XT1069?
http://forum.xda-developers.com/moto-g-2014/help/help-wipe-xt1069-t2899434

Moto G xt1031 Failed to initiate partition and bootloader locked cant select any opt
So i was in the process of putting in a new rom on my moto g using flashify and it went all bad after reboot. It got stuck in a bootloop and any selection i made just gave me failed to validate boot image. Ive tried many different methods and none have worked or i get stuck on one of the steps. I am fairly new to custom roms kernels flashing and rooting and basically have learned what i know from teaching myself and reading up on forums.. Please help as soon as possible i will be very grateful. I have tried @Boss442 thread and kinda stuck i wish i could at least be able to send a message but since i am absolutely brand new to xda in order for me to do that i have to write 10 posts so i thought why not just write my own. Also my bootloader relocked itself so i think thats one of the reasons why i cant load anything to it or might be because i dont have adb enabled on my phone but how can i do that when i cant even get into the actual phone.

Hi, Giovanni need ur help, i stucked in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
actually my phone is bricked for the script, and I tried with all MBM versions my phone is locked now.
Helppp PLsss i need my Moto G

ditto. I think the nand might just be corrupt, though, I dunno. same error message.

torqueo said:
ditto. I think the nand might just be corrupt, though, I dunno. same error message.
Click to expand...
Click to collapse
Thx u know how fix the nand?

unexpected packet
I'm getting this on moto G, and the bootloader was corrupted after i've received and installed system update 4.4 today
opening device: \\.\COM5
OKAY [ -0.000s]
greeting device for command mode
OKAY [ 1.763s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)

I had a weird problem and posted at http://forum.xda-developers.com/moto-g/help/hard-bricked-trying-to-update-to-4-4-4-t2926071

I have error
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)

Notification LED solid on plug
Hi,
I my Moto G 4G also bricked after it ran out of battery.
The notification LED just remains solid when I plug in the USB cable.
The PC doesn't even recognize the phone.
Left it a day charging in a 1.5A charger and still wouldn't turn on.
Left it another day charging in the PC, still nothing.
Any idea if this phone still has hope?

Moto G 4G steady led
My Moto G 4G doesn't want to power on or charge anymore after losing battery 1 night.
I can't get into fastboot and the PC doesn't recognize the device.
Everytime I plug it to a charger or PC, the notification LED is just always on.
Is there still a way to salvage this?

I have this error:
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Phone breaked after OTA update from retail.en.us 4.4.3 to 4.4.4.

Wilk this procedure work on moto g 2ndgen
I have moto g 2nd gen.and its not turning on.tried most ways.none worked.it shows the qhusb_bulk in pc.wil the above procedure work or can u help with specific steps for my phone

najin said:
I have moto g 2nd gen.and its not turning on.tried most ways.none worked.it shows the qhusb_bulk in pc.wil the above procedure work or can u help with specific steps for my phone
Click to expand...
Click to collapse
I will try to make unbricker to 2nd gen, but i dont have a moto g 2nd gen, if someone can send me a broken moto g i can develop an app that repair it

moto g xt1033 rom TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF_SVC
Hi felas,
i got a xt1033 with fastboot 41.13. this device is locked and i try to flash a rom
TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12_CFC_1FF_SVC
and i got it this report
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>SET fastboot=.\mfastboot-v2\mfastboot.exe
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>.\mfastboot-v2\mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.360s]
finished. total time: 0.400s
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>.\mfastboot-v2\mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.102s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to flash partition tz
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 11.075s
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>.\mfastboot-v2\mfastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>.\mfastboot-v2\mfastboot.exe flash logo logo.bin
C:\Users\RUIVO\Desktop\#Roms moto G\Roms\TIM-BR-DS_4.4.4_KXB21.14-L1.40_37_cid12
_CFC_1FF_SVC.xml>.\mfastboot-v2\mfastboot.exe flash boot boot.img
< waiting for device >
---------------------------------------------------------------------------------------------------------------------------------------------------------
And this is device info report of my phone
---------------------------------------------------------------------------------------------------------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: c8295d
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 72E149030F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partitio
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.057s
---------------------------------------------------------------------------------------------------------------------------------------------------------
Sorry for my bad english. Im brazilian and i want to revive my xt1033.
Thanks

My Moto G died and after performing all the steps I can not revive esto.Con blankflash to 4.4.4 I have this error "FAILED (blank-flash: sdl-transfer-image: send-image: Error reading packet)"

corrupted MBM-CI_4.4.4 for Moto G
I agree with suhridkhan that this file is corrupted.
I can download it, but no zip program will work, throwing up a 'this is not a valid Win32 application' message.
Does anyone have an uncorrupted 4.4.4 blankflash file.
Or is there yet an Android 5 file?

There is huge problem(s) with my moto g.
1)when it is booted into the stock rom(i didn't change it after unlocking the bootloader and rooting ) it constantly shows that gapps have crashed.
2)when i boot into recovery(twrp 2.6.3.3) it is stuck on the teamwin screen.
3)i tried to reflash stock by the instructions given in this thread with out locking the device i.e. 4.2 and 4.4, neither cmd nor the bootloader shows any error and that every thing is flashed and erased perfectly. But there is no change in the state of the mobile i.e. problem 1 and 2 still remain.
4) when i try to follow whole instructions i.e. locking the boot loader .every thing flashes perfectly but cmd says sst failure and bootloader says "Hab check for system failed .".But there is no change in the system, when i boot the phone it still says gapps crashed repeatedly and none of the user data is erased.
5)fastboot works in bootloader and when booted into device but adb works neither in device nor in bootloader "adb get-state" always returns unknown.
6)the bootloader says status code:3(i dont know if it is supposed to mean something or not)
i Want to know if my bootloader is corrupted or not.
and how can i fix my device..
my firmware version is 4.4.4
Please do reply...
it is my only device and i can not even make calls i have been stuck with the problem since a week.

I don't understand what "Run Fastboot_IMG1" means. What exactly do I have to do?

hi
if u can get ito download mode search how to install android 5.0 lollipop on to moto g on youtube in the video the guy doing the tutorial will show u some command pronmpts to flash the stock firmware onto your phone i have a feeling this will work for u but only if u can go into download mode

[Q&A] [Recovery] Unofficial CWM - 6.0.5.0 - peregrine

Q&A for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

black screen cwm
EDIT: SOLVED (with somcom's recovery toolkit http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710 /please feel free to delete this post which now only serves as proof of my incompetence)
........................................................................
hello, i've just bought a moto lte (uk) xt1039
have successfully unlocked bootloader
trying to flash recovery via fastboot but having issues
seems to flash ok but then when rebooting into recovery device show (nearly) black screen with some white flickers.
i can boot into bootloader and access via fastboot on windows 7
i downloaded recovery and rom on the moto (before erasing partitions and being unable to boot) and have copies on laptop too.
what have i done? how can i get recovery working to install a rom?
thanks so much for your help, sorry I couldn't find answer here (I tried!
C:\Users\prosody\moto g\RECOVERY>fastboot devices
TA003002KC fastboot
C:\Users\prosody\moto g\RECOVERY>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA003002KC
(bootloader) cid: 0x0007
(bootloader) channelid: 0x49
(bootloader) uid: B6C1B20515000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Nov 9 17:24:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_o2gb/peregrine:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.56/52:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_o
(bootloader) ro.build.version.full[1]: 2gb.o2gball.en.GB
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Tue Aug 5 22:4
(bootloader) kernel.version[3]: 2:49 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: o2gb
all: listed above
finished. total time: 0.100s
C:\Users\prosody\moto g\RECOVERY>fastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.078s]
erasing 'userdata'...
OKAY [ 0.243s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.070s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 0.449s
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.113s]
finished. total time: 0.117s
C:\Users\prosody\moto g\RECOVERY>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.118s]
finished. total time: 0.122s
C:\Users\prosody\moto g\RECOVERY>fastboot flash CWM-6.0.5.0-peregrine.img
unknown partition 'CWM-6.0.5.0-peregrine.img'
error: cannot determine image filename for 'CWM-6.0.5.0-peregrine.img'
C:\Users\prosody\moto g\RECOVERY>fastboot flash recovery CWM-6.0.5.0-peregrine.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (7752 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.426s]
finished. total time: 0.746s
C:\Users\prosody\moto g\RECOVERY>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Users\prosody\moto g\RECOVERY>

Blinking stripes when trying recovery
I just wanted to add that I too have trouble booting into CWM recovery. The screen goes black and some flashing stripes appear accross the screen before it goes completely black. Basically it's unusable...
I can hold the power button and the phone reboots as normal.
The bootloader is unlocked and the phone is rooted.
I hope this information is useful in some way and some fix can be found.
(I have the same problem with TWRP by the way.)
I'm so sorry, you can all ignore what I wrote above.
I fixed it the same way as noted in the post above...
Cheers,

I flashed the CWM recovery as described but when I try to enter it I only get a black screen. I also tried the non-touch version of the recovery but that didn't make any difference. Ideas!?
*edit*
Followed the instructions above and got stuck in the bootloader. Then somehow managed to flash CWM using the Toolkit mentioned above.
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
Click to expand...
Click to collapse
What's with the flashboot commands posted by prosodyspeaks, I guess that erasing the boot was somehow responsible for being unable to boot the system!?

Every time I create a recovery to my external SD card, it hangs at "Generating md5 sum" but works fine when its in the internal storage. I always have to restart my phone manually. Is there a fix to this, or can I just make a recovery to my internal storage and move the entire recovery folder to my external SD card?

Will this work this the Lollipop 5.1 bootloader?

SJHacker said:
Will this work this the Lollipop 5.1 bootloader?
Click to expand...
Click to collapse
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.

Try this
The easiest method to install CWM without pc:
1. Download the file on your phone (I moved it to the internal storage)
2. Download Flashify from Play Store
3.Go to "flash" section and select "flash recovery image"
4. Click on "choose a file"
5. Choose the downloaded file
6. Click on this file and select "yup"
7. CWM should be now installed
I have tried this method with my device (Motorola Moto G 4G) and everyrhing went well.

_Immanuel_ said:
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.
Click to expand...
Click to collapse
Thanks!

Does latest version supports the ext. sdcard used as internal in a marshmallow rom? Thx

Flashing Problem (Bricked phone)

Dear,
I bought a mobile XT1032 in Chile and had the bright idea to install Android 5.0.0, but before that should turn my phone GPE and worked smoothly for about two months, but a few weeks ago the screen began to random failures for example the phone is locked and unlocked without my intervention or the screen, the phone is locked, blinking (as it had voltage changes, such as when you move a flashlight with almost empty and this flashing batteries). I decided to go back to Android 4.4.4 Stock, however this time I did the procedure without considering the consequences, I first downloaded and installed the GPE 4.4.4, then downloaded and installed the Stock Brasil 4.4.4, then tried to go back to stock Movistar Chile but failed to find the 4.4.4 nowhere, so I decided to install the 4.4.3. My mistake. After that my phone did not work more.
Now if I switch it displays the message "Unlocked Bootloader" then shows motorola logos (the world turning) and then the screen goes black but not off (note that is on because it has brightness and that was with that flicker as if he had mentioned voltage failures) but this does not show anything.
I tried installing all the tutorials I found on the internet to revive my phone, I got about 15 different roms and nothing works. I can enter fastboot and no problems (strangely fastboot screen does not flash, it is as if he had nothing wrong), I can also enter recovery (either in recovery flashing display). If I make a recovery "wipe data / factory reset" does well, but if I do "wipe reset partition" android logo shows the blue loading bar appears 2 seconds and the phone reboots.
I not been possible to change the recovery of stock for some other recovery (eg Philz) because although fastboot or mfastboot shows that the process was well (sometimes shown on the phone that is making a downgrade) this does not change the recovery.
Currently my phone is flashed (at least it is assumed that no starts beyond the worlds of motorola) with Android 5.0.2 I downloaded some other forum.
I think, without knowing for sure, for more than I try with the common commands this dont "touch" or change the system version. It's like I always show as well (including with commands in cmd and phone) but practically nothing happened.
I appreciate any guidance to solve my problem.
I attach a "getall var" from my phone
-----------------------------
C:\WorkingMotoG>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300B3Y4
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D3BDB4030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 15 12:11:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_tefcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Movistar.en.CL
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 01:58:53 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.059s

Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.

audit13 said:
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
Click to expand...
Click to collapse
All the files loads OK, gpt.bin with exception of boot.img, it says: "version downgraded for boot" in the phone.
BTW: I do what you say about recovery and keep showing stock recovery. Dont show error messages, just no work.
Thanks anyway for you time...

Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?

audit13 said:
Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
Click to expand...
Click to collapse
I'm trying to flash philz_touch_6.58.7-falcon.img
Thanks for your time

Did you try TWRP?

audit13 said:
Did you try TWRP?
Click to expand...
Click to collapse
Yes, but dont work neither

So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?

audit13 said:
So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?
Click to expand...
Click to collapse
Now my phone is recognized by Windows as "Qualcomm HS-USB QDLoader 9008". I try to fla**** with MotoFlasher and says:
OUTPUT: opening device: \\.\COM12
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x3B4BDD3
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.000s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.000s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.001s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.010s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:

That's not good. You may have to try the unbrick method to fix it.

audit13 said:
That's not good. You may have to try the unbrick method to fix it.
Click to expand...
Click to collapse
Which method? Can you gave me instructions or a link, please...?

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

flashing with fastboot does nothing

My moto g get stucked on a blank screen after the motorola logo animation.
I tried going into the recovery and wiping data and cache. Nothing happened.
I tried unlocking the bootloader --> No problem, it's unlocked now.
I tried reflashing the stock ROM via fastboot. Apparently all goes OKAY, all commands pass without problems, but when I reboot, still a blank screen.
I tried flashing a new ROM (5.0.2 Lollipop). Same problem, apparently it flashes everything ok but when reboots... nothing.
I tried to update only the recovery to ither Team Wins or Clockwork, they flash without problems but when I go to the recovery I get the stock one (I didnt reboot the phone went straight to recovery after flashing, and tried rebooting the phone as well).
I also tried to update only the bootloader (right now I'm at 41.13) tried to update it to 41.18, same problem... Apparently it flashes but when I reboot I still get the 41.13
Finally, I tried to hard-brick my phone using the Bootloader Bricker Tool posted here: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 and nothing happened.
So basically, it seems that everything I do via fastboot (or mfastboot - I tried both) it goes through without problems, but then it either reverts back to stock when the phone reboots or actually it doesnt write anything.
Any help, will be greatly appreaciated.
This is my getvar:all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T09290UV3C
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: ADC65E030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 18: 9:42 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxar/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.AR
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:31:45 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s

Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.
Here is the exact 4.4.2 Firmware Image:
http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz

Thanks for the reply.
Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.
That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\

The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.

lost101 said:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
Click to expand...
Click to collapse
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
oversleeper said:
Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
Click to expand...
Click to collapse
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...

epexy said:
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
Click to expand...
Click to collapse
I have two devices with the same problem as yours, one = motorola logo -> full animation -> black screen. And another boots up normally, but have a forgotten password, but if I try to enter recovery mode then "Boot Up Failed" message appear, and after I flash the device (and use erase userdata command), the device still have the password and all data apparently (the device boot up fast too).
The only thing that seems to work with fastboot is unlocking bootloader, and relock fails (even showing sucessful)
No one have this problems and have solutions ?????

I have the exact same problem. Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.