Database Info

[Q] Help! fastboot flash appears to do nothing!

I have somehow totally trashed my Android install. I have a UK retail Moto G XT1032.
While downloading the OTA lollipop update, the download appeared to stall. I decided to give up on the update, so I switched the phone off. When I turned it back on again, every single process crashed. "Unfortunately dialler/android.process.acore/Calendar/android.process.media/etc has stopped". I can keep tapping "OK" for ever to clear these notifications, but can't actually use the phone for anything at all.
So I decided to do a factory reset from fastboot. It made no difference.
I tried a factory reset from recovery. It made no difference.
Using fastboot, I attempted to install the stock ROM according to the guide at http://forum.xda-developers.com/showthread.php?t=2542219. Everything seemed to flash OK - I got OKAY on the PC and the commands appeared to be running on the phone OK, but when it restarted, the phone was exactly the same - my wallpaper photo was still there, and the app icons that I could glimpse behind the endless notifications were my apps.
I tried several more times, this time flashing the 4.4.4 ROM (RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF). Exactly the same results - nothing changes when I restart.
It's as if the mfastboot flash commands do nothing at all! I have run all the mfastboot commands described by the guide in the order given.
I've also tried booting to recovery and connecting to ADB, but the PC cannot see the device.
I've tried replacing the recovery with CWM and TWRP .img files, but the flash command, while seeming to work, doesn't change anything at all! The recovery that I have installed is the standard KXB21.14-L1.40.
I have tried "mfastboot.exe erase recovery", before attempting to update the recovery, but it makes no difference.
Does anybody have any idea what I am doing wrong? It seems that no "mfastboot flash xxx yyy" command works at all on my phone.

Did you installfastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.

Got the same problem. I've already posted this in a few threads and didn't get any answer, though

Sounds crazy but, when you type fastboot devices with your phone connected in fastboot mode, does the command return your phone's serial #?

Yes, everything via fastboot works (says complete, done etc.) except it doesn't affect the real system. If you sideload ADB you will see that the system, data and cache partition become read-only. I've managed to remount only data partition with write privileges, but that doesn't help.

Are you flashing each partition manually? You can see your device's serial # in fastboot?

audit13 said:
Did you install fastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Click to expand...
Click to collapse
Originally, I used the version of fastboot that came with the first stock ROM I tried (falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB).
Later on, I installed mfastboot and used that instead. The results were the same. Nothing seems to actually be flashed, but there are no errors on either the PC or the phone.
ADB does not work in fastboot (I don't believe it's supposed to!), but it also will not work with the version of recovery that I have, which is why I was attempting to install CWM and TWRP in its place.

audit13 said:
Are you flashing each partition manually? You can see your device's serial # in fastboot?
Click to expand...
Click to collapse
Yes. I'm currently trying the following sequence with the XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml ROM...
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The mfastboot command returns OKAY for each of these, and a couple of yellow lines appear on the phone for each command, indicating that the right command is running, with no error messages.

I have never used mfastboot. Maybe try using fastboot to flash? I have used fastboot on my Moto G and Moto Atrix HD with great success.

Tried with fastboot, tried with mfastboot, got no errors but nothing changes. The real problem I suppose is corrupted partitions.

Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358

@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?

dog121 said:
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
Click to expand...
Click to collapse
I've just given it a go.
When flashing the ROMs, it basically runs the same mfastboot commands that I was running before, so the result was exactly the same.
However, the ADB Driver install button was worth trying. The driver supplied has enabled my PC to communicate with the phone using ADB when in recovery mode!
Unfortunately, after selecting "apply update from ADB" on the phone, and running "adb sideload <ROM zip file>", it sends it to the phone (taking a couple of minutes), and the phone says "Verifying update package", followed by "Installation aborted".
When you sideload, do you need some sort of special format ROM file?

audit13 said:
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
Click to expand...
Click to collapse
I was hoping to use the stock ROM, just to get the phone back to its original state.
If the mfastboot command does nothing, I doubt trying different ROMs will help. But I'll probably try it if I can't get anything else to work.

thanks a lot!

@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot​

lost101 said:
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot​
Click to expand...
Click to collapse
Thanks for the idea. I happen to have a laptop running the latest Lubuntu.
I installed fastboot as you directed and re-flashed everything. Exactly the same. The commands all say OKAY, the yellow text on the phone says it's running the commands, but when I reboot - everything is exactly as it was before - including my wallpaper photo and app icons. And every single process on the phone is crashing.
I do not believe fastboot is actually working on this phone. The only commands that seem to work are the ones to unlock the bootloader and the one to reboot the phone.

@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
I.e first file is sparsechunk.0 not sparsechunk1
EDIT: Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
It's retail Brazil, but will work anywhere in the world.
I suggest you skip flashing the bootloader - motoboot.img

lost101 said:
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
Click to expand...
Click to collapse
Yup.
Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
Click to expand...
Click to collapse
OK - I downloaded this and flashed it. Exactly the same as all the previous attempts. It appears to work, but when I restart, the phone is in exactly the same state as before, as if no flashing has happened.
Here is the command line output:
Code:
C:\>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
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.353s]
finished. total time: 0.380s
C:\>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.110s]
finished. total time: 1.197s
C:\>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.105s
C:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.670s]
finished. total time: 1.030s
C:\>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.695s]
finished. total time: 1.060s
C:\>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.140s]
writing 'system'...
OKAY [ 8.155s]
finished. total time: 16.295s
C:\>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.185s]
writing 'system'...
OKAY [ 8.690s]
finished. total time: 16.885s
C:\>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.265s]
writing 'system'...
OKAY [ 8.755s]
finished. total time: 121.145s
C:\>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.255s]
writing 'system'...
OKAY [ 6.475s]
finished. total time: 11.735s
C:\>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 0.825s]
finished. total time: 2.435s
C:\>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.020s
C:\>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 3.180s]
finished. total time: 3.250s
C:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
C:\>mfastboot reboot
rebooting...
finished. total time: 0.005s
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Thanks again to all of you for your assistance in this matter.

IcyBee said:
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Click to expand...
Click to collapse
Recovery mode ADB will work in Linux. You could try side-loading the 5.0.2 OTA Update.

S.O.S

Hello guys, this is my first time being officially on the forum as a user, before I was just reading and viewing information, using some of it as well. The reason I post this thread is to see if anyone can help me out or point me in the right direction of an already existing thread for my issue.
My issue is the following. A week ago I was trying to flash a new rom and by accident I deleted the system part on the advanced option on the TWRP. After that when my phone turned on a weird line starting going up and down on the screen and the phone started to work really really slow. I asked a friend and he told me to just reflash the rom, which I did but the line and slowness still appeared after that even my WIFI stopped working (when I tried to turn it on it would turn itself off immediately) I read on a thread about a similar issue and they reinstalled the firmware of the phone and it worked. obviously I tried doing it myself, I replaced the firmware to my phone used an original copy and everything works fine, except the wifi, it still does not turn on.
Can anyone help me out? Has anyone ever hear of this issue before.
And to let you all know. Me cellphones model is Motorola Moto G TX1032
Any and I mean any assistance or information provided will be very helpful.
Thank you!!

Mr.Nomo said:
Hello guys, this is my first time being officially on the forum as a user, before I was just reading and viewing information, using some of it as well. The reason I post this thread is to see if anyone can help me out or point me in the right direction of an already existing thread for my issue.
My issue is the following. A week ago I was trying to flash a new rom and by accident I deleted the system part on the advanced option on the TWRP. After that when my phone turned on a weird line starting going up and down on the screen and the phone started to work really really slow. I asked a friend and he told me to just reflash the rom, which I did but the line and slowness still appeared after that even my WIFI stopped working (when I tried to turn it on it would turn itself off immediately) I read on a thread about a similar issue and they reinstalled the firmware of the phone and it worked. obviously I tried doing it myself, I replaced the firmware to my phone used an original copy and everything works fine, except the wifi, it still does not turn on.
Can anyone help me out? Has anyone ever hear of this issue before.
And to let you all know. Me cellphones model is Motorola Moto G TX1032
Any and I mean any assistance or information provided will be very helpful.
Thank you!!
Click to expand...
Click to collapse
Did you use a fastboot firmware image? If so what commands did you try?

Did u flash the modem,boot and radio correctly?

lost101 said:
Did you use a fastboot firmware image? If so what commands did you try?
Click to expand...
Click to collapse
What I used was "US_retail_XT1032_KXB21.14-L1.32_CFC.xml" its a zip file, I copied the contents on this to a folder where I had the adb tools and the commands I used where:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

It's would be helpful if you could provide an actual log of using these commands. Fastboot is not user friendly, and it can be the case you think a command has been successful - when it has not.

Log
lost101 said:
It's would be helpful if you could provide an actual log of using these commands. Fastboot is not user friendly, and it can be the case you think a command has been successful - when it has not.
Click to expand...
Click to collapse
Here is the log of the command process, I had to switch commands and firmware because the rest were giving me more problems aside of the wifi, this is the brazilian firmware 5.0.2 :
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.370s]
finished. total time: 0.399s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.091s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.232s]
finished. total time: 1.326s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.036s]
writing 'logo'...
OKAY [ 0.084s]
finished. total time: 0.123s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.391s]
writing 'boot'...
OKAY [ 0.760s]
finished. total time: 1.156s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.750s]
finished. total time: 1.125s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.454s]
writing 'system'...
OKAY [ 10.936s]
finished. total time: 19.394s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.456s]
writing 'system'...
OKAY [ 11.241s]
finished. total time: 19.701s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.573s]
writing 'system'...
OKAY [ 11.058s]
finished. total time: 19.642s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.463s]
writing 'system'...
OKAY [ 7.930s]
finished. total time: 13.401s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.694s]
writing 'modem'...
OKAY [ 1.455s]
finished. total time: 3.154s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.024s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.072s]
writing 'fsg'...
OKAY [ 5.602s]
finished. total time: 5.679s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
cache
erasing 'cache'...
OKAY [ 0.359s]
finished. total time: 0.361s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
userdata
erasing 'userdata'...
OKAY [ 3.168s]
finished. total time: 3.172s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboo
t
rebooting...
finished. total time: 0.002s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>
Now this firmware works fine and all but I still have the issue with the wifi, I have been reading about replacing a file on the /persist folder, and I have done so multiple times, and the issue still remains

Could you try flashing the GPE 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=59930345&postcount=610
Skip the following command for your own safety: mfastboot flash motoboot motoboot.img

Same?
lost101 said:
Could you try flashing the GPE 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=59930345&postcount=610
Skip the following command for your own safety: mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
I did the process here is the log:
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.712s]
finished. total time: 1.092s
on device appeared: hab check failed for boot
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.092s
on device appeared: hab check failed for recovery
Complete log:
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t partition gpt.bin
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
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-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
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot bootloader
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
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-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
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.032s]
writing 'logo'...
OKAY [ 0.081s]
finished. total time: 0.118s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.712s]
finished. total time: 1.092s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.092s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.507s]
writing 'system'...
OKAY [ 11.266s]
finished. total time: 19.776s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 8.591s]
writing 'system'...
OKAY [ 10.560s]
finished. total time: 19.154s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.624s]
writing 'system'...
OKAY [ 12.751s]
finished. total time: 21.378s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.693s]
writing 'system'...
OKAY [ 0.783s]
finished. total time: 1.482s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.677s]
writing 'modem'...
OKAY [ 1.292s]
finished. total time: 2.975s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.024s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.110s]
writing 'fsg'...
OKAY [ 5.614s]
finished. total time: 5.729s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase cache
erasing 'cache'...
OKAY [ 0.344s]
finished. total time: 0.345s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase userdata
erasing 'userdata'...
OKAY [ 2.976s]
finished. total time: 2.979s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot
rebooting...
finished. total time: 0.002s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>
I also included what I believe are errors, if you call it like that which are detailed at the beginning. And now when I turn the wifi on, it turns "on" but no networks are recognized ( I have one at home ) and then when the screen locks or I go back, it will appear as off.

Update
After installing this firmware and installing a file explorer with root permission, I went to /persist to modify the WCNSS file, placing a 0 on it, afterwards tried the WIFI and got my hopes up because it recognized my WIFI and it even displayed a MAC Address which I copied. After trying to connect to my wifi...it stopped working and is back to square one.

@Mr.Nomo - I'll do some more research this evening. Is everything else working for you? Calls / data etc.
UPDATE: Sometimes flashing a CyanogenMOD based custom ROM can get WiFi working again. WiFi in XPerience ROM is different again and might be worth a try: http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466

lost101 said:
@Mr.Nomo - I'll do some more research this evening. Is everything else working for you? Calls / data etc.
UPDATE: Sometimes flashing a CyanogenMOD based custom ROM can get WiFi working again. WiFi in XPerience ROM is different again and might be worth a try: http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466
Click to expand...
Click to collapse
Yes! Everything else is working absolutely fine, calls, data, texting, everyhing else is awesome. I tried flashing a CyanoGen rom before, it started giving me issues with the playstore and with the UI, but will definitely try it out and update you with the results.
Thank you very much for all your help. :good:

Update on the XPerience Rom
Flashed properly, no errors and aside from it being a little slow at startup everything else works. Except the WiFi Tried modyfing the WCNSS file, no success with that either. One question, if I were to delete the folder /persist and all its contents, how would that affect the phone?

Mr.Nomo said:
Flashed properly, no errors and aside from it being a little slow at startup everything else works. Except the WiFi Tried modyfing the WCNSS file, no success with that either. One question, if I were to delete the folder /persist and all its contents, how would that affect the phone?
Click to expand...
Click to collapse
I don't know what would happen, but I can say that there are some partitions on Moto G that are unique to each handset. For example, if deleting the contents of that partition / folder caused you to loose IMEI - it might be impossible to undo. Without an IMEI you could no longer make calls.

Update on the XPerience Rom #2
It seems the rest of the rom is working fine up to this point, the only problem that I've encountered aside from the WIFI is the messaging app that comes included on the rom stops working whenever I try to reply to a message or create a new one. But I think I will use hangouts for that issue, by the way if I didnt thank already for the information regarding the possible causes of deleting the /persist file...I thank you again. :good:

MOTO G XT1032 black screen

I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?

You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata

lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​

C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
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.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2

pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"

lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???

Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img

lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja

Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/

lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?

Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip

lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".

@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!

[Q] Asus Transformer TF300T bricked - not accepting flash via fastboot

Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!

rmcalingasan said:
Hi guys,
I have my friend's Asus Transformer tablet which was never rooted nor modified in any way. One time it went dead and did not boot up. When it finally turned back on, screen was stuck on ASUS logo (please see attachment below).
These were the troubleshooting steps taken:
Reset through the small opening at the side (NO GOOD)
Click Wipe Data at Recovery (NO GOOD)
Tried to flash stock rom through fastboot (NO GOOD)
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
And the error in fastboot was this:
Code:
C:\adb>fastboot devices
015d15b4f8041c04 fastboot
C:\adb>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.143s]
sending 'system' (800931 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 7.317s
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
Had the same issue. Used Linuxmint and was able to flash image with no issues.

Also had this issue happen to me one day out of the blue, with the exception of not even being able to boot into recovery. I tried everything and ended up giving up as nothing worked. I'm currently waiting for a new motherboard to see if that fixes it.

rmcalingasan said:
Hi guys,
Firmware used was: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 Only for JP SKU (Android 4.2)
Flashed using Windows 7 OS.
We'd like to know if there would be any chance to revive the tablet or is it time to bid goodbye.
Thank you and more power XDA!
Click to expand...
Click to collapse
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!

ebonit said:
...are you sure that the chosen firmware is the right one that fits to your tablet exactly? I suppose it's the wrong one, because I used to take Version WW_V10.6.1.27.5 and was successful to get a clean Stock Rom JB. I also may be wrong.
However I think it's worth to make a further attempt to flash that blob as follows:
Make a folder C:\Flash and copy the .blob from WW_V10.6.1.27.5 into the folder.
Open Minimal ADB and Fastboot and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\Flash and put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Please note, I cannot guarantee any success-everything you do is on your own risk. Good luck!
Click to expand...
Click to collapse
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...

rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's just stuck at sending 'system'.
I've tried using the sd card method but failed too.

aem2267 said:
Had the same issue. Used Linuxmint and was able to flash image with no issues.
Click to expand...
Click to collapse
Installed Linuxmint too. (Loving the interface!)
But still stuck at sending 'system' at terminal.

rmcalingasan said:
Thank you for your input. I'm currently trying it in Linux.
Here is the current status:
Code:
fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.074s]
sending 'system' (800931 KB)...
Click to expand...
Click to collapse
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?

ebonit said:
It's strange. As I wrote "sending..." takes a while then appears "write..." and the load status will be shown. Were you patient enough? Did you ever see the load status? Are you sure it's the right "blob"?
Click to expand...
Click to collapse
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.

rmcalingasan said:
Yes, I'm quite sure it's the correct blob. The JP_epad-10.6.1.27.5-20130902 shows at the top of the screen of the tablet.
One thing I noticed when erasing other parts was that it failes erasing other parts:
Code:
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot devices
015d15b4f8041c04 fastboot
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.055s]
finished. total time: 2.055s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: (Unknown error code))
finished. total time: 0.382s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase boot
erasing 'boot'...
OKAY [ 0.036s]
finished. total time: 0.036s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase misc
erasing 'misc'...
FAILED (remote: (Unknown error code))
finished. total time: 0.038s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: (Unknown error code))
finished. total time: 0.043s
ronamae-Lenovo-G400 JP_epad-user-10.6.1.27.5 # fastboot -i 0x0B05 flash system bloberasing 'system'...
OKAY [ 0.010s]
sending 'system' (800931 KB)...
I'm currently trying to download an older version of JP blob.
Click to expand...
Click to collapse
Please try the version WW_V10.6.1.27.5. WW stands for world wide. That's what I used to take. http://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Once downloaded, you need to head to the path “Settings > About Tablet” where you will have to note down the Build number. If the build number starts with “WW”, your SKU is WW. Similarly, if your build number starts with “US”, you must download the firmware for the US SKU.

Bootloop even after flashing stock firmware Moto G 3rd Gen(XT1550)

I got an OTA update for marshmallow. At this stage phone was locked, unrooted and not tampered with.
After updating OTA phone went into a bootloop.
'Allow OEM Unlock' is disabled from developer options before even updating OTA so bootloader can't be unlocked.
After bootloop, from bootloader using fastboot (and mfastboot also tried) I flashed "XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107..... ..." this marshmallow firmware using standard commands for newer Moto devies. Even after flashing firmware, still bootloop happens.
Code:
fastboot flash bootloader O:\MotoG3\Firmwares\bootloader.img
fastboot flash logo O:\MotoG3\Firmwares\logo.bin
fastboot flash boot O:\MotoG3\Firmwares\boot.img
fastboot flash recovery O:\MotoG3\Firmwares\recovery.img
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.0
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.1
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.2
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.3
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.4
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.5
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.6
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.7
fastboot flash modem O:\MotoG3\Firmwares\NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg O:\MotoG3\Firmwares\fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
pause
At this stage, phone still goes into a bootloop. Clicking on recovery from bootloader also sends phone into a bootloop so can't even access stock recovery.
Also no way to erase system as bootloader is locked.
How do I get the phone back in working state, my device is not in warranty now.
Other bootloop guides were not useful as here even after flashing stock firmware phone still goes into a bootloop. ALso no stock recovery is accessible and BL is locked.
Thanks in advance

Did everything return an OKAY?? Can you copy the whole command prompt text here, it can be really helpful.
Broadcasted from Zeta Reticuli

Yes everything went fine no issue in any command,command prompt code will re-post once i'll try again to flash stock ROM.

On the bootloader menu, connect to computer and type-
#removed code,it was invalid.#
Check if you get the default recovery screen now. We have to restore factory settings from the stock recovery first before flashing stock images. So if by this method you can access stock recovery (as you have already flashed it) you can just factory restore and again flash factory images. Best of luck.
Broadcasted from Zeta Reticuli

No this command is invalid , not working with my case.
Gravemind2015 said:
On the bootloader menu, connect to computer and type-
Code:
fastboot reboot recovery
Check if you get the default recovery screen now. We have to restore factory settings from the stock recovery first before flashing stock images. So if by this method you can access stock recovery (as you have already flashed it) you can just factory restore and again flash factory images. Best of luck.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
No this command is invalid , not working with my case.

sanju25 said:
No this command is invalid , not working with my case.
Click to expand...
Click to collapse
Yes I forgot to edit my reply, I became aware of that. I actually read it somewhere and confused with adb.
Is the phone rebooting when you go to bootloader>volume down>recovery?
Broadcasted from Zeta Reticuli

Here is whole command prompt code @Gravemind2015
sanju25 said:
Yes everything went fine no issue in any command,command prompt code will re-post once i'll try again to flash stock ROM.
Click to expand...
Click to collapse
Code:
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
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.715s]
finished. total time: 0.727s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.503s]
finished. total time: 1.600s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.065s]
finished. total time: 0.122s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.524s]
writing 'boot'...
OKAY [ 0.761s]
finished. total time: 1.291s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.526s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.301s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (247489 KB)...
OKAY [ 7.767s]
writing 'system'...
OKAY [ 6.453s]
finished. total time: 14.229s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (230229 KB)...
OKAY [ 7.314s]
writing 'system'...
OKAY [ 5.119s]
finished. total time: 12.442s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (259434 KB)...
OKAY [ 8.229s]
writing 'system'...
OKAY [ 5.816s]
finished. total time: 14.055s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (254590 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 5.677s]
finished. total time: 13.765s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (254861 KB)...
OKAY [ 8.111s]
writing 'system'...
OKAY [ 6.110s]
finished. total time: 14.230s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258017 KB)...
OKAY [ 8.183s]
writing 'system'...
OKAY [ 5.610s]
finished. total time: 13.802s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (251037 KB)...
OKAY [ 7.967s]
writing 'system'...
OKAY [ 9.902s]
finished. total time: 17.876s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
sending 'system' (14420 KB)...
OKAY [ 0.549s]
writing 'system'...
OKAY [ 0.372s]
finished. total time: 0.929s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36988 KB)...
OKAY [ 1.258s]
writing 'modem'...
OKAY [ 0.678s]
finished. total time: 1.940s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.091s]
finished. total time: 0.095s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.109s]
finished. total time: 0.113s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2280 KB)...
OKAY [ 0.216s]
writing 'fsg'...
OKAY [ 0.084s]
finished. total time: 0.307s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.102s]
finished. total time: 0.106s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.094s]
finished. total time: 0.097s

Gravemind2015 said:
Yes I forgot to edit my reply, I became aware of that. I actually read it somewhere and confused with adb.
Is the phone rebooting when you go to bootloader>volume down>recovery?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Yes, only thing phone is doing is re-booting

sanju25 said:
Yes, only thing phone is doing is re-booting
Click to expand...
Click to collapse
Sorry, after seeing the logs, I am out of ideas. You can check the folder for any extra sparsechunk files (sparsechunk8 or 9, I cant remember the exact no. For xt1550). I had to do it once and it worked flawlessly the very first time, same xt1550 and same package, weird you have to face this.
Broadcasted from Zeta Reticuli

sanju25 said:
No this command is invalid , not working with my case.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <suffix> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
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 erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the form <protocol>:<hostname>[ort] where <protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <suffix> Specify slot suffix to be used if the
device supports slots. This will be
added to all partition names that use
slots. 'all' can be given to refer
to all slots. 'other' can be given to
refer to a non-current slot. If this
flag is not used, slotted partitions
will default to the current active slot.
-a, --set-active[=<suffix>] Sets the active slot. If no suffix is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message
no what to do...pls help me

reeeju said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
usage: fastboot [ ]
commands:
update Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash [ ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase Erase a flash partition.
format[:[][:[]]
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar Display a bootloader variable.
set_active Sets the active slot. If slots are
not supported, this does nothing.
boot [ [ ] ] Download and boot kernel.
flash:raw boot [ [ ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
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 erase partition before
formatting.
-s Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the form :[ort] where is either tcp or udp.
-p Specify product name.
-c Override kernel commandline.
-i Specify a custom USB vendor id.
-b, --base Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size Specify the nand page size
(default: 2048).
-S [K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot Specify slot suffix to be used if the
device supports slots. This will be
added to all partition names that use
slots. 'all' can be given to refer
to all slots. 'other' can be given to
refer to a non-current slot. If this
flag is not used, slotted partitions
will default to the current active slot.
-a, --set-active[=] Sets the active slot. If no suffix is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message
no what to do...pls help me
Click to expand...
Click to collapse
Thats normal because fastboot does not have the option to reboot directly into recovery. So your command-
Code:
fastboot reboot recovery
is invalid.
Try this-
Code:
fastboot reboot-bootloader
From bootloader, press volume down twice to enter recovery.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Thats normal because fastboot does not have the option to reboot directly into recovery. So your command-
is invalid.
Try this-
From bootloader, press volume down twice to enter recovery.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Then how to get twrp recovery which image file to be flashed?

Vikas Tewatia said:
I can give u a link to the latest working twrp v3.2.0.r for moto g3
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Here is the thread : http://forum.xda-developers.com/showthread.php?t=3170537.
Broadcasted from Zeta Reticuli