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.

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.

Request HELP for ZIP, single IMG or just S-OFF

I'm starting this thread, cause I have been responding on others threads and that's deviates from the main topic and is not fair to the O.P.
This thread is for request help, partial or full ZIP files, single images or just for S-OFF Request.
Please, provide the question and paste your phone info, by typing: fastboot getvar all
Exemple:
My phone doesn't boot, can I go back to stock?
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT7120403511
(bootloader) imei: please, no IMEI
(bootloader) version-main: 1.32.651.11
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: SPCS_001
I will do my part in my time with you to help you resolve the problem.

HELP! I wasn't able to boot after a seemingly harmless TWRP hard reset(the one where it asks to writ "yes" to confirm), it kept restarting into bootloader mode, so decided to flash the ZIP that you provided in the other thread, as it wasn,t meant for 2PYB20000, i changed my MID to 2PYB10000. It flashed fine, phone turned on, but there were no cellular signals or wifi after reboot, phone doesnt shows it imei in system nor does it shows baseband version.
so far i have tried flashing a proper 2pyb20000 ruu zip, formating the persist partion, then directly rebooting to download mode and reflashing the ruu. but the issue stayed the same.
Please help me solve this issue.
Here are the details.
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT6AX0401703
(bootloader) current-slot:
(bootloader) imei: Removed
(bootloader) version-main: 1.33.425.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.02_U114401031_125.01.70524G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: 11111111

zain rizvi said:
HELP! I wasn't able to boot after a seemingly harmless TWRP hard reset(the one where it asks to writ "yes" to confirm), it kept restarting into bootloader mode, so decided to flash the ZIP that you provided in the other thread, as it wasn,t meant for 2PYB20000, i changed my MID to 2PYB10000. It flashed fine, phone turned on, but there were no cellular signals or wifi after reboot, phone doesnt shows it imei in system nor does it shows baseband version.
so far i have tried flashing a proper 2pyb20000 ruu zip, formating the persist partion, then directly rebooting to download mode and reflashing the ruu. but the issue stayed the same.
Please help me solve this issue.
Here are the details.
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT6AX0401703
(bootloader) current-slot:
(bootloader) imei: Removed
(bootloader) version-main: 1.33.425.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.02_U114401031_125.01.70524G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
What a mess!
for 2PYB20000, i changed my MID to 2PYB10000. It flashed fine, phone turned on, but there were no cellular signals or wifi after reboot, phone doesnt shows it imei in system nor does it shows baseband version
Click to expand...
Click to collapse
So... you try to convert a BOLT to EVO.
Need to change ID model to 2PYB10000;
Flash latest Europe Version 1.31.404.1;
Flash radio.img from latest Sprint WWE 1.32.651.11 in bootloader.
You just nedded to flash the radio.img from Sprint through fastboot mode to get back the IMEI.

b8engl said:
What a mess!
So... you try to convert a BOLT to EVO.
Need to change ID model to 2PYB10000;
Flash latest Europe Version 1.31.404.1;
Flash radio.img from latest Sprint WWE 1.32.651.11 in bootloader.
You just nedded to flash the radio.img from Sprint through fastboot mode to get back the IMEI.
Click to expand...
Click to collapse
Sort of did that, but flashed the latest sprint stock FW first, so had to do the whole unlocking procedure myself to get it sim unlocked. Then flashed the european latest WWE FW and flashed the Sprint radio on top of it.
Thank a lot for the help man.

zain rizvi said:
Sort of did that, but flashed the latest sprint stock FW first, so had to do the whole unlocking procedure myself to get it sim unlocked. Then flashed the european latest WWE FW and flashed the Sprint radio on top of it.
Thank a lot for the help man.
Click to expand...
Click to collapse
No problem! I'm glad you figured it out.

S-OFF help
Code name: htc_aca
Model 2PYB2
Bootloader version: 1.0.0.0000
CID: SPCS_001
MID: 2PYB20000
Radio: [email protected]
Firmware: ACADIA_WHL_N70_SENSE80GP_SPCS
Kernel: Linux version 3.10.84-perf-gd701a0
Android version: 7.0
HTC Sense: 8.0
SDK Version: 24
Base: 1.32.651.11 8.0_g CL863776 release-keys
Firmware name: Bad Boyz Sprint HTC BOLT v2.1
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Code name: htc_aca
Model 2PYB2
Bootloader version: 1.0.0.0000
CID: SPCS_001
MID: 2PYB20000
Radio: [email protected]
Firmware: ACADIA_WHL_N70_SENSE80GP_SPCS
Kernel: Linux version 3.10.84-perf-gd701a0
Android version: 7.0
HTC Sense: 8.0
SDK Version: 24
Base: 1.32.651.11 8.0_g CL863776 release-keys
Firmware name: Bad Boyz Sprint HTC BOLT v2.1

b8engl said:
I'm starting this thread, cause I have been responding on others threads and that's deviates from the main topic and is not fair to the O.P.
This thread is for request help, partial or full ZIP files, single images or just for S-OFF.
Please, provide the question and paste your phone info, by typing: fastboot getvar all
Exemple:
My phone doesn't boot, can I go back to stock?
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT7120403511
(bootloader) imei: please, no IMEI
(bootloader) version-main: 1.32.651.11
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: SPCS_001
I will do my part in my time with you to help you resolve the problem.
Click to expand...
Click to collapse
Please help. I installed my twrp backup and now the sound, video playback, and the home/fingerprint sensor don't work. I guess it didn't backup right, to begin with. I really don't know. I'm new to this stuff, but its fun when it works. It's really kinda sad when it doesn't. My Mom just gave me this phone because it needed the screen replaced, but was in perfect condition otherwise and I really don't want her to know I wrecked it. I've been looking for days for a download. I pretty much understand the concept of how to make it work if I had the download. I have adb installed and working and the phone is detected.
Htc 10 Evo UNLOCKED S-ON
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT6C30401953
(bootloader) current-slot:
(bootloader) imei: removed
(bootloader) version-main: 1.38.615.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: BS_US001

MaxGor80 said:
Code name: htc_aca
Model 2PYB2
Bootloader version: 1.0.0.0000
CID: SPCS_001
MID: 2PYB20000
Radio: [email protected]
Firmware: ACADIA_WHL_N70_SENSE80GP_SPCS
Kernel: Linux version 3.10.84-perf-gd701a0
Android version: 7.0
HTC Sense: 8.0
SDK Version: 24
Base: 1.32.651.11 8.0_g CL863776 release-keys
Firmware name: Bad Boyz Sprint HTC BOLT v2.1
Click to expand...
Click to collapse
I can see that you have a custom ROM, why do you need security-off?

kentuckylovely said:
Please help. I installed my twrp backup and now the sound, video playback, and the home/fingerprint sensor don't work. I guess it didn't backup right, to begin with. I really don't know. I'm new to this stuff, but its fun when it works. It's really kinda sad when it doesn't. My Mom just gave me this phone because it needed the screen replaced, but was in perfect condition otherwise and I really don't want her to know I wrecked it. I've been looking for days for a download. I pretty much understand the concept of how to make it work if I had the download. I have adb installed and working and the phone is detected.
Click to expand...
Click to collapse
Well...let me see if I can help you with that!
kentuckylovely said:
Htc 10 Evo Bolt UNLOCKED S-ON
(bootloader) kernel: lk
(bootloader) product: htc_acawhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1141600000
(bootloader) serialno: HT6C30401953
(bootloader) current-slot:
(bootloader) imei: removed
(bootloader) version-main: 1.38.615.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PYB20000
(bootloader) cid: BS_US001
Click to expand...
Click to collapse
So, for BOLT version. Download link here.

b8engl said:
Well...let me see if I can help you with that!
So, for BOLT version. Download link
Had to remove download link before I could post.
Thank you trying to help so far, but I'm still having problems.
PS C:\WINDOWS\System32\WindowsPowerShell\v1.0> fastboot flash recovery "C:\Users\sherry\Downloads\2PYBIMG_ACADIA_WHL_N70
_SENSE80G[email protected]70303_CNV_1.78_003_release_518263_signed_2_4.zip"
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 664647066 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (1048573 KB) error: write_sparse_skip_chunk: don't care size 664647066 is not a mu
ltiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 664647066 is not a multiple of the block size 4096
OKAY [ 93.072s]
Writing sparse 'recovery' 1/2 (bootloader) HOSD CL#992875
(bootloader) [email protected]
(bootloader) ERR image is not valid
(bootloader) [email protected]
(bootloader) [email protected]
Finished. Total time: 173.905s
Finished. Total time: 1
Click to expand...
Click to collapse

kentuckylovely said:
PS C:\WINDOWS\System32\WindowsPowerShell\v1.0> fastboot flash recovery "C:\Users\sherry\Downloads\2PYBIMG_ACADIA_WHL_N70
_SENSE80G[email protected]70303_CNV_1.78_003_release_518263_signed_2_4.zip"
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 664647066 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (1048573 KB) error: write_sparse_skip_chunk: don't care size 664647066 is not a mu
ltiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 664647066 is not a multiple of the block size 4096
OKAY [ 93.072s]
Writing sparse 'recovery' 1/2 (bootloader) HOSD CL#992875
(bootloader) [email protected]
(bootloader) ERR image is not valid
(bootloader) [email protected]
(bootloader) [email protected]
Finished. Total time: 173.905s
Finished. Total time: 1
Click to expand...
Click to collapse
I don't know what you are trying to do...
Just rename the file to 2PYBIMG, place in a formated fat32 microSD card, then after inserted the card to phone reboot to download mode. It will update it self!

No matter what I do it says the file is corrupt. Am I doing something wrong? I named it 2PYBIMG.zip and added it to my card but it doesn't start when I boot into download mode. I tried flashing it with twrp and it says it's corrupted.
Sent from my HTC Bolt using XDA Labs

kentuckylovely said:
No matter what I do it says the file is corrupt. Am I doing something wrong? I named it 2PYBIMG.zip and added it to my card but it doesn't start when I boot into download mode. I tried flashing it with twrp and it says it's corrupted.
Click to expand...
Click to collapse
You have TWRP, so bootloader unlocked... then, you need to lock it! You can only do this if you have security off, which is not the case here!
- fastboot oem lock ( this will relock the bootloader );
- fastboot oem rebootRUU ( switch the state to update firmware trough USB );
- fastboot flash zip 2PYBIMG.zip.
You need to verify if you don't have ex: 2PYBIMG.zip ( if that is the case, just select the file press F2 and rename it again to 2PYBIMG ).

b8engl said:
You have TWRP, so bootloader unlocked... then, you need to lock it! You can only do this if you have security off, which is not the case here!
- fastboot oem lock ( this will relock the bootloader );
- fastboot oem rebootRUU ( switch the state to update firmware trough USB );
- fastboot flash zip 2PYBIMG.zip.
You need to verify if you don't have ex: 2PYBIMG.zip ( if that is the case, just select the file press F2 and rename it again to 2PYBIMG ).
Click to expand...
Click to collapse
So I can't even get my phone to go into android now to atempt to get s-off state. Is it a hopeless case now?
Sent from my HTC Bolt using XDA Labs
---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------
kentuckylovely said:
So I can't even get my phone to go into android now to atempt to get s-off state. Is it a hopeless case now?
Click to expand...
Click to collapse
Also, your download would not unzip, but I found the file somewhere else and bought it and it unzipped ok so I think your file is corrupted somehow. If anyone needs the file I can upload it sometime, my internet is pretty slow so I'm not sure when. But if someone sees this and needs it let me know. I'm just totally at a loss here with my phone though.
Sent from my HTC Bolt using XDA Labs

kentuckylovely said:
Also, your download would not unzip, but I found the file somewhere else and bought it and it unzipped ok so I think your file is corrupted somehow.
Click to expand...
Click to collapse
Because the file is encrypted, that's normal!

b8engl said:
Because the file is encrypted, that's normal!
Click to expand...
Click to collapse
I'm sorry if I offended you. I didn't know it wouldn't open because of that. But is my phone hopeless now?
Sent from my HTC Bolt using XDA Labs
---------- Post added at 11:55 AM ---------- Previous post was at 11:55 AM ----------
kentuckylovely said:
I'm sorry if I offended you. I didn't know it wouldn't open because of that. But is my phone hopeless now?
Click to expand...
Click to collapse
Thank you for trying to help me.
Sent from my HTC Bolt using XDA Labs

kentuckylovely said:
I'm sorry if I offended you. I didn't know it wouldn't open because of that.
Click to expand...
Click to collapse
Take it easy! You didn't offend me in any way.
kentuckylovely said:
Thank you for trying to help me.
Click to expand...
Click to collapse
Well... this is difficult because you don't compreend some basic functions. I recomend that you search purhaps youtube or read some more on some forum. Because I alredy sent the correct file! You only need to do the steps correctly to get back the phone again.
Please, don't repost the same issue on the thread. Just send me a private message, I will respond through there.

b8engl said:
What a mess!
So... you try to convert a BOLT to EVO.
Need to change ID model to 2PYB10000;
Flash latest Europe Version 1.31.404.1;
Flash radio.img from latest Sprint WWE 1.32.651.11 in bootloader.
You just nedded to flash the radio.img from Sprint through fastboot mode to get back the IMEI.
Click to expand...
Click to collapse
what will be the command to flash the radio.img ?????
---------- Post added at 03:49 PM ---------- Previous post was at 03:28 PM ----------
how to get S-OFF because it in S-ON HTC 10 evo
no fastboot flashing possible friends
CID-HTC__059
MID-2PYB20000
OS-1.33.425.6

Sanaullahshuaib said:
how to get S-OFF because it in S-ON HTC 10 evo
no fastboot flashing possible friends
CID-HTC__059
MID-2PYB20000
OS-1.33.425.6
Click to expand...
Click to collapse
If you have # you could try dd command!
Also you can get S-OFF easily with this service on eBay.

No root so how dd method

moto one vision hard bricked

i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Take it to a service center for flashing the firmware?

D A R K 9 said:
i unlocked the bootloader and then unknowingly i gave command " fastboot erase all ".
now the device is not powering on and not even responding,no screen on (even when inserting charger).
can anyone suggest a solution??
Click to expand...
Click to collapse
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183

muppetz said:
Don't take strictly right but I've done it some time ago on a Snapdragon phone . For this you absolutely need for Motorola One Vision Qfil files and Flashone app for Windows . The whole process is very simple but finding proper Qfil files ROM is a pain in the butt .
If you find these files somehow , anywhere , anytime don't forget to share .
...............................
Or use this : https://forum.xda-developers.com/moto-z/help/help-moto-z-dead-brick-t3809740
Or this : https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
Click to expand...
Click to collapse
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.

D A R K 9 said:
ya but i used to do same cmd for sony and mi mobile but never faced this issue,i didnt expect this thing from a motorola device.now they are saying to change sub board for not power on reason reason at service center.
Click to expand...
Click to collapse
You're right . It doesn't explain their proposals if you just did a simple cmd to the phone as you said . Maybe they try to squeeze some extra bucks from you . I'm sorry , man .

hard bricked one vision
its showing as exynos9610 in device manager,any leads from here??

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
good news , it seems pc recognize phone , further steps to bring back phone , no clue, but I supose it's primordial to flash partitions . Google it .

D A R K 9 said:
its showing as exynos9610 in device manager,any leads from here??
Click to expand...
Click to collapse
Look in the OP for a rom to flash in fastboot.

gee2012 said:
Look in the OP for a rom to flash in fastboot.
Click to expand...
Click to collapse
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610

D A R K 9 said:
sadly its not going to fastboot mode.as of matter still screen not showing anything,only thing just pc shows a device connected in usb as exynos9610
Click to expand...
Click to collapse
Try the adb command ` fastboot devices` and see if you get a serial number.

I'm also in this same situation. Been looking all around for solutions but all i come across are fixes for qualcom devices. Even all the blankflashing posts are qualcom. My guess is that we need to find software that'll work with exynos chips that isn't samsung. Adb, fastboot and mfastboot commands don't work because in its current state the device is only recognized as "Exynos9610"

I have the same problema. Im trying to follow this thread:
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865/amp/
My problem is that my computer is Windows 10 and it can't load the Exynos drivers, I hope that you have good look with that. You should try to change the cfg archive to load bootloader.

Found something intresting on "lolinet" today. A "blankflash" for kane.
Could be worth a try for sure, if you're hardbricked.
I have not tried it so I've no idea if this is legit.
The procedure would probably be something like:
Unzip all files.
Install drivers (ImageWriterUSBDriver_1113_00.exe).
Open "Multidownloader_64bit_1.4.1.exe".
Connect device to usb and let multidownloader detect it.
In the "box", browse for the "usbbooting.cfg" that is present in the kane_blankflash and hit start.
My guess is that it's supposed to reboot to fastboot once it's done writing the files so that you can reflash full firmware from fastboot, like it is with blankflash for other moto devices.
Let us know how it goes if anyone tries it.

Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
target max-sparse-size: 256MB
sending 'fwbl1' (16 KB)...
OKAY [ 0.040s]
writing 'fwbl1'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fwbl1
FAILED (remote failure)
finished. total time: 0.082s
Click to expand...
Click to collapse
My phone get vars
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190729
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB WDC SDINDDH4-128G FV=1268
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: 0057049924
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 000003B54E4B96FA0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 354154101426432
(bootloader) meid:
(bootloader) date: 05-09-2019
(bootloader) sku: XT1970-1
(bootloader) carrier_sku: XT1970-1
(bootloader) battid: SB18C43602
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Aug 28 2:48:21 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/kane/kane_sprout:9/PSAS29
(bootloader) ro.build.fingerprint[1]: .137-16-4/fc9db:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.221.4.kane.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld115) (Android (4691093 based on
(bootloader) kernel.version[2]: r316199) clang version 6.0.2 (]
(bootloader) kernel.version[3]:
(bootloader) kernel.version[4]: 83abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (
(bootloader) kernel.version[6]: hain/llvm 34361f192e41ed6e4e8f9aca80a4ea
(bootloader) kernel.version[7]: 7e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Mon Jul 29 06:52:16 CDT 201
(bootloader) kernel.version[9]: 9
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190729
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
Click to expand...
Click to collapse
Anyone can helpme?

Okay, I know the last message here was almost 2 years ago, but I'm just here to confirm, that I've tried this blankflash and indeed, it works.
So I've rewritten both bootloader A and B slots with /dev/zero and tried to reboot. Of course, nothing happened, but the device was detected and booted into fastboot. Everything was working there. Than just flashed bootloader_a and bootloader_b and it booted like nothing happened.

danmaya said:
Error
I'm in trouble, too.
I can even enter fastboot but do not accept to update, the following error appears.
My phone get vars
Anyone can helpme?
Click to expand...
Click to collapse
So here you have probably broken UFS (device's internal storage). If the files you try to flash are signed, but you still can't load them, then it means, you have corrupted memory. With this, go to service, they could try to replace UFS chip with another one. From what I can see, your bootloader is locked, so try to unlock it and then flash the firmware, maybe this will work.