Strangely soft-bricked stock Moto G - Moto G Q&A, Help & Troubleshooting

Strangely soft-bricked stock Moto G - Moto G Q&A, Help & Troubleshooting

Hi there, i have spent hours trying to recover my Moto G XT1032 using this forum and I have mad progress but my phone is still dead.
Phone:
Motorola XT1032 - it was the latest stock ROM, always updated to the newest version. (Very probably a non-branded EU retail, 5.1 ROM)
Problem:
Battery got drained. When put on charger, it was 'optimising cache app x of y' for a long time, sometimes it does this anyway.
Then it went into bootloop, stuck at the Motorola logo. It doesn't restart and the logo doesn't starts animating like it normally does.
Fastboot (Power + vol down) worked, but going into recovery failed, leaving me stuck with the same M logo.
Solutions tried:
1. Connection to computer: didn't work. Seen as 'fastboot device' when in fastboot but that's it.
2. Using Android recovery software. Useless because of the above and useless pieces of software anyway.
3. Re-flashing stock ROM. After installing Motorola drivers and mfastboot, I tried to flash FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC, and according to the phone it was successful, but it still left me stuck at the bootloop. Even after manually flashing everything from partition tables to system images.
4. I unlocked the phone to install a custom TWRP recovery. The unlock was successful.
5. Tried to install TWRP recovery - to recover my files at least -, the command line says success, the phone says
Code:
Mismatched partition size (recovery)
Many have said in this forum to ignore this message - well, I can't since it can't write the recovery partition.
6. At this point the factory recovery started working ('no command' screen, then pressing 'vol up + power')
7. I have been able to boot into TWRP with
Code:
mfastboot boot twrp-3.0.0.0_2-falcon.img
What a workaround! Well, I have at least been able to access my files over MTP. Yay! :fingers-crossed:
8. Here comes the problem: I can't wipe the device. I can't copy anything over MTP. I can't delete files over mtp: it looks like the files are deleted but they reappear after restarting the device.
Note: I can access a simple
Code:
adb shell
in recovery.
So once again, I'm unable to install a custom recovery via mfastboot, and it looks like the whole device was write-protected for whatever reason. At least I've been able to save my data thanks to the useful resources here! Any ideas about what else I could possibly try?
Any help is much appreciated!

Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy

Paradox♀ said:
Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy
Click to expand...
Click to collapse
Thanks!
It erased everything OK, at least no error messages.
Fun fact: it still boots into factory recovery after erasing the recovery partition!
Fun fact 2: I still can't flash custom recoveries like TWRP. ('Partition mismatch' error and then boots into factory recovery as if nothing changed. If I manually 'mfastboot boot twrp....img' into the image, then the internal storage shows up intact as before the phone was broken!
Then I flashed new stock ROMs, all returned OK, but still bootloop:
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
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
Here's the complete output:
Code:
D:\tmp>mfastboot erase system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.023s]
finished. total time: 0.025s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.018s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.026s]
finished. total time: 0.028s
D:\tmp>mfastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.037s]
finished. total time: 0.037s
D:\tmp>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>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.303s]
finished. total time: 0.330s
D:\tmp>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 [ 0.930s]
finished. total time: 1.018s
D:\tmp>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.036s]
finished. total time: 0.095s
D:\tmp>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.585s]
finished. total time: 0.948s
D:\tmp>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.363s]
writing 'recovery'...
OKAY [ 0.591s]
finished. total time: 0.958s
D:\tmp>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.153s]
writing 'system'...
OKAY [ 7.753s]
finished. total time: 15.907s
D:\tmp>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256953 KB)...
OKAY [ 8.132s]
writing 'system'...
OKAY [ 7.910s]
finished. total time: 16.044s
D:\tmp>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260396 KB)...
OKAY [ 8.234s]
writing 'system'...
OKAY [ 7.899s]
finished. total time: 16.137s
D:\tmp>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166176 KB)...
OKAY [ 5.274s]
writing 'system'...
OKAY [ 6.251s]
finished. total time: 11.528s
D:\tmp>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.599s]
writing 'modem'...
OKAY [ 0.763s]
finished. total time: 2.365s
D:\tmp>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.088s]
writing 'fsg'...
OKAY [ 3.177s]
finished. total time: 3.268s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.017s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.024s
D:\tmp>mfastboot reboot
rebooting...
finished. total time: 0.002s
D:\tmp>
I think I have the same symptoms as this user.
Maybe the file system is corrupted? Or the bootloader?
Or just the flash memory in the phone stopped working properly.
Let's recap:
Erasing partitions doesn't actually erase them but it returns OK
Can't erase userdata
Can't install custom recoveries
Flashing stock ROM returns OK but still can't boot.

I'm pretty sure the eMMC (internal memory chip) has been damaged. Goodbye, phone...
Fortunately I still had my good ol' ZTE Blade sitting in the drawer.

Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.

Paradox♀ said:
Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.
Click to expand...
Click to collapse
tl;dr: can't fsck, can't format, can't mfastboot erase, can't twrp erase.
Thanks! I've tried it, it doesn't work. Looks like it's wiped, then after restart it doesn't.
But doesn't the command you have suggested before
Code:
mfastboot erase userdata
erase the data partition?
I'm concerned that the eMMC is damaged and my phone can't be put to life again - if a complete erase & flash (including partition table, see my previous post) doesn't work then what does?
Here's a df output from TWRP:
Code:
/data # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 435.3M 20.0K 435.3M 0% /dev
tmpfs 435.3M 20.0K 435.3M 0% /tmp
/dev/block/mmcblk0p33
651.7M 11.6M 640.0M 2% /cache
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /data
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /sdcard
/dev/block/mmcblk0p1 62.4M 46.5M 15.9M 75% /firmware
/dev/block/mmcblk0p34
960.6M 938.1M 22.6M 98% /system
Here's a worrisome FSCK output on the data partition:
Code:
/sbin # fsck.f2fs /dev/block/mmcblk0p36
fsck.f2fs /dev/block/mmcblk0p36
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: MKFS version
""
Info: FSCK version
from "Linux version 3.4.42-g89906d6 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Feb 26 06:48:18 CST 2016"
to "Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x31040]
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x315d9]
NID[0x31040] is unreachable
NID[0x315d9] is unreachable
NID[0x315da] is unreachable
NID[0x315e2] is unreachable
NID[0x315e6] is unreachable
NID[0x315ec] is unreachable
NID[0x315ef] is unreachable
NID[0x315f1] is unreachable
NID[0x315f4] is unreachable
NID[0x315f9] is unreachable
NID[0x31600] is unreachable
[FSCK] Unreachable nat entries [Fail] [0xb]
[FSCK] SIT valid block bitmap checking [Fail]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Fail] [0xfd3d3]
[FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x78ea]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x78f5]
[FSCK] valid_inode_count matched with CP [Fail] [0x75ed]
[FSCK] free segment_count matched with CP [Ok..] [0x15a]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Fail]
Error: Could not conduct fsync!!!
Done.
And what happens when I try to format the data partition? This:
Code:
/sbin # mkfs.f2fs /dev/block/mmcblk0p36
mkfs.f2fs /dev/block/mmcblk0p36
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
Error: Could not conduct fsync!!!
Info: format successful
Exact same error as for example here.

Hey is there any chance that you have a backup image that could be used to restore the partitions?

Paradox♀ said:
Hey is there any chance that you have a backup image that could be used to restore the partitions?
Click to expand...
Click to collapse
Well, I don't, but I used stock ROM images from this forum. It's the same stuff that was installed before failure.
If I can't run a simple fsck, then I'm 90% sure it's some hardware issue. Based on how many people are having the same problem, maybe the eMMC chips are reaching the end of their (short) lifetime.

Yeah it seems so.

Related

Help, hab check failed for recovery and boot

After the dumbest idea ever of downgrading to KitKat, I think i soft bricked my phone, it doesn't boot up.
When i try to flash a stock rom from bootloader it says:
Code:
hab check failed for recovery
hab check failed for boot
And when i try flashing a ROM or wiping on TWRP says:
Code:
unable to mount /data
unable to mount /cache
I tried everything i saw on XDA after googling many times the errors, nothing worked :crying:
One strange thing I saw was that when I tried "fastboot format data" it returned: "formatting is not supported for filesystem with type '' " , so, maybe, is a problem with the filesystem?
Help me, please :crying:

Done
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works

Tizianop6 said:
Finally, I made it work, I erased and formatted all what i can, then through TWRP I formatted Data and now it works
Click to expand...
Click to collapse
Can you tell me the detail how to operate? Thanks!

Mr.Ju said:
Can you tell me the detail how to operate? Thanks!
Click to expand...
Click to collapse
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions

Tizianop6 said:
I formatted all partitions through "fastboot erase" and other commands,flashed TWRP recovery, and then through TWRP I re-formatted all partitions
Click to expand...
Click to collapse
Hi Mr. Ju,
I am having the exact same problem. I tried to use:
mfastboot devices
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
But it did not work. I sitll have the "hab check failed for boot" and hancheck failed for recovery" when I tried to reflash the GPE5.1 rom.
Can you please post all the mfastboot commands you used?
Thanks
Jº

Fastboot erase command is extremely dangerous and should not be played with.
@jpmaroco - Is your Bootloader locked?

Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP

jpmaroco said:
Thanks lost101
No my boatloader is unlocked. I can't even wipe/factory reset with TWRP
Click to expand...
Click to collapse
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.

lost101 said:
Try using mfastoot: https://www.androidfilehost.com/?fid=24052804347778493
Providing a log is helpful. Copy and paste command prompt after doing fastboot commands.
Click to expand...
Click to collapse
Dear lost101,
Thanks for answering back. Here is the log:
E:\>mfastboot devices
TA92908ERZ fastboot
E:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\>mfastboot reboot
rebooting...
finished. total time: 0.000s

@jpmaroco - I meant a log of you flashing the Firmware Image.

lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
Thanks lost101, here it goes:
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>SET fastboot=fastboot.exe
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.004s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.069s]
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.339s]
finished. total time: 0.410s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.100s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.941s]
finished. total time: 1.078s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.586s]
writing 'modem'...
OKAY [ 0.802s]
finished. total time: 2.406s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.084s]
writing 'fsg'...
OKAY [ 3.179s]
finished. total time: 3.265s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.002s]
finished. total time: 0.002s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.002s]
finished. total time: 0.018s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.100s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.178s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.384s]
writing 'boot'...
OKAY [ 0.644s]
finished. total time: 1.030s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 0.621s]
finished. total time: 1.016s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.130s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.051s]
finished. total time: 16.184s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 8.239s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.069s]
finished. total time: 16.309s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.290s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 10.090s]
finished. total time: 18.380s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.640s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 0.633s]
finished. total time: 1.274s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase cache
erasing 'cache'...
OKAY [ -0.000s]
finished. total time: -0.000s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>fastboot.exe oem fb_mode_clear
...
OKAY [ 0.006s]
finished. total time: 0.022s
E:\Stock Android to GPe\GPE 5.1 Lollipop 1 click installer\GPe_5.1\GPe_5.1_OneClick>pause
Press any key to continue . . .
---------- Post added 12th December 2015 at 12:14 AM ---------- Previous post was 11th December 2015 at 11:59 PM ----------
lost101 said:
@jpmaroco - I meant a log of you flashing the Firmware Image.
Click to expand...
Click to collapse
... and I get the same results if I use mfastboot instead of fastboot.
In the Phone, after
cmd: flash:boot
I get
hab check failed for boot
after
cmd: flash: recovery
i get
hab check failed for recovery
So, this seems to me that nothing is being flashed (It still keep my old twrp-2.8.7.0.-falcon_GPE.img recovery, not the stock one in GPE5.1 Lollipop)
I can boot in TWRP (after waiting for 5-6 minutes) but I can't factory reset because it says:
E: Could not mount /data and unable to find crypto footer
E: unable to mount /data
E:unbale to recreate /data/media/folder
... done
Does the same for "Storage" (unable to mount storage)...
Factory reset complete
failed
Should I try to flash the twrp-2.8.7.0.-falcon_STOCK.img?
Thanks for all your help lost101.

Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
Use mfastboot.
Use these commands only:
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
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

lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
[/COLOR]
lost101 said:
Latest GPE 5.1 Firmware Image: https://www.androidfilehost.com/?fid=24269982086992480
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Thanks once again lost101, I appreciate your help!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

jpmaroco said:
I just reflashed the rom you sent me. I have the same "hab check failed" errors ;-(
And the phone just stays at the swirling dots after reboot... I think It is not writing anything ;-(. It still keeps the twrp recovery. if mfastboot was working than mfastboot flash recovery recovery.img should flash the stock (gpe) recovery, correct?
Click to expand...
Click to collapse
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.

lost101 said:
Yes. Emmc appears now to be read-only - an issue that is regularly reported on this forum and one that has no solution.
Click to expand...
Click to collapse
No solution? Só my moto g is dead for good and there's no way to recover it?

moto g2 4g model rooted after booting is failed
hi i am venkat
i am rooted my moto g2 4g , battery is low mobile is shutdown, after i am trying to power on the device one binary code is coming in that device is Locked status code : 0 showing
i am trying to start normal mode ,recovery mode, factory mode, but i am fail , i dont know how to solve this, please help me,
thank you ...

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:

Allow OEM Unlock Bootloader

Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!

axbom said:
Hello! My phone's stuck in a bootloop and flashing Stock ROM doesn't help, so I was thinking of rooting the phone. Problem is I don't have Allow OEM Unlock ticked and I can't get onto the phone to do it. Is there any way to Allow OEM Unlock from bootloader? Or any other solution that might fix the problem?
Thank you!
Click to expand...
Click to collapse
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.

acejavelin said:
The phone MUST be bootable to enable OEM Unlocking, if you can't get it to boot to turn it on, there is no way to unlock the bootloader, thus no way to root.
It might be useful if you gave us some more details about how you got into this state... what you did or what happened, specific variant, etc.
Click to expand...
Click to collapse
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!

axbom said:
Oh okay. I've got a Motorola G3, XT1541. I tried updating it to Marshmallow which resulted in the phone bootlooping so I tried following this guide http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 to fix it. Everything works fine when following the guide, I get [OKAY] on all steps in fastboot but it still doesn't work. I actually did miss the last sparsechunk file the first time I did it, so I ran it again. I can still get to the bootloader, but when trying to reach the recovery menu from there it just goes into bootloop again.
Thank you very much for helping out!
Click to expand...
Click to collapse
Did you factory default prior to flashing? That is a required step...

acejavelin said:
Did you factory default prior to flashing? That is a required step...
Click to expand...
Click to collapse
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..

axbom said:
Yeah the first time I did it through the recovery mode, after that I was unable to get into the recovery menu so I've used:
fastboot erase userdata
fastboot erase cache
Still not working..
Click to expand...
Click to collapse
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk

acejavelin said:
And you are positive it is the correct image for your device? If you got a success message for each piece and it still won't boot, I'm not sure what to say. Can you post a log or screenshot of the process?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
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.708s]
finished. total time: 0.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.551s]
finished. total time: 1.645s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.125s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.519s]
writing 'boot'...
OKAY [ 0.936s]
finished. total time: 1.471s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.486s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (243355 KB)...
OKAY [ 7.717s]
writing 'system'...
OKAY [ 8.975s]
finished. total time: 16.723s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (233538 KB)...
OKAY [ 7.478s]
writing 'system'...
OKAY [ 7.597s]
finished. total time: 15.092s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (256922 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 8.308s]
finished. total time: 16.521s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (257262 KB)...
OKAY [ 8.198s]
writing 'system'...
OKAY [ 8.303s]
finished. total time: 16.500s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (255507 KB)...
OKAY [ 8.142s]
writing 'system'...
OKAY [ 8.575s]
finished. total time: 16.717s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258021 KB)...
OKAY [ 8.225s]
writing 'system'...
OKAY [ 8.266s]
finished. total time: 16.507s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (210541 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 11.695s]
finished. total time: 18.410s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 0.974s]
finished. total time: 2.155s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Simon\Desktop\adb-fastboot-latest_win_linux>
From what I can see it all looks fine?

axbom said:
On the back of the phone it says Model: XT1541 and I'm using the XT1541 6.0 version from this thread http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 so it should be the right one!
Here's the log I get when flashing:
...
From what I can see it all looks fine?
Click to expand...
Click to collapse
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?

acejavelin said:
Actually, that looks perfect... And it just bootloops afterwards, meaning it actually does a reboot and NOT just getting "stuck"?
I do not have a copy of this firmware image, it has exactly 7 sparcechunk pieces (0-6)?
One more thing... before you issue the fb_mode_set command, did you do a 'fastboot format cache' and 'fastboot format userdata' or do a factory reset from recovery?
Click to expand...
Click to collapse
After issuing the reboot command at the end it goes to the white screen with the motorola logo, then the screen goes black, and then back to the motorola logo, and keep on going like that.
Yeah that's correct, 0-6 sparsechunk files. I did fastboot ERASE cache and ERASE userdata, since I can't get into the recovery menu (goes into bootloop if I try). When I try any of those commands it says Formatting is not supported for filesystem with type 'raw'.

im having the exact same problem, used the same software and carried out the same steps as you with no luck either.
from what ive read its because you need to wipe all the data first but because we get the, cant its RAW message, it wont download the firmware onto the phone even though it says it went ok. at the minute i havnt found anyone whos successfully been able to repair this fault.
mine was working perfectly untill the ota update

There is no fix for that, use your warranty if you have so

Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.

yobac said:
Hi,
I have the same problem, I've made the same steps after faulty OTA update. And the Motorola warranty shop has told me that the warranty is void because of interference in the software. I have to add that in the fastboot after "getvar all" command there's a line "iswarrantyvoid = no", so as I understand the warranty should be still valid.
Regards.
Click to expand...
Click to collapse
Contact Moto directly via their website.
Sent from my MotoG3 using Tapatalk

1st Flash via Adb !
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !

FaizanChauhaan said:
1st Flash via Adb !
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Post result !
Click to expand...
Click to collapse
It's fastboot not adb lol. Contradictory sentences
Edit: BTW motoboot.img is not present, it may refer to earlier generation of moto g. There is an line to flash bootloader.img instead. Have a look here : http://forum.xda-developers.com/showthread.php?t=3187750. Thanks.
Broadcasted from Zeta Reticuli

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

Rebooting only into Fastboot mode

Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.

krishna13 said:
Using AEX's AOSP 7.1 rom(Indian quark) from few days. Facing many issues like app crashes and no LTE mostly. Today i wanted to call someone and clicked on phone app on home screen. Suddenly a message popped up saying phone has stopped. It showed whenever i clicked on phone app. I restarted the phone. Thatsit. Its only booting into fastboot mode. Whenever i chose to select recovery mode it only boots into fastboot. checked the bootloaderlogs and found "failed to validate boot image ret=-1 bootup failed" this message.Please, I need a serious help.
Click to expand...
Click to collapse
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.

ChazzMatt said:
It's booting to the bootloader screen? You should be able to arrow up from there using the volume keys to the "recovery" option and boot to TWRP.
Once in TWRP, restore the backup you made. You did make a recent backup in TWRP, right?
OR in TWRP, do a factory reset and install a ROM. In TWRP, you can drag over whatever you want if you are connected to a PC. Works just like a flash drive. Drag over a ROM, GAPPs, etc if you don't want to install AEX's AOSP 7.1 again.
Click to expand...
Click to collapse
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...

krishna13 said:
Its not going to recovery mode again. In bootloader logs i can see boot.img failed and the ret value is -1. Even in RSD flash tool i can see that 2/18 error or 2/22 fastboot oem fb_clear error. Tried flashing original 6.0 and 5.0 firmwares both in RSD flashtool and individual fastboot commands.But i failed. ALways booting only in Fastboot. Please help me. Im living with no phone from 3 days. Please provide me a solution...
Click to expand...
Click to collapse
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.

ChazzMatt said:
But you can go to recovery mode. If it's booting to the bootloader, you can arrow up to recovery and choose that.
Oh no, you flashed original 6.0 and 5.0 firmware? OK, now you have not only wiped out your custom TWRP recovery you have have flashed older bootloader over newer bootloader which BRICKS the phone. You never, never, never flash older firmware over newer firmware unless you omit gpt.bin in the flash commands.
Even then you should also omit recovery.img in the flash commands to keep custom recovery.
Your bootloader is unlocked, right? If so, there is still hope. Hold on.
Click to expand...
Click to collapse
Yes. Still my device is unlocked. In fastboot mode, the text showing in yello color saying, Device is UNLOCKED. Status code :3.
Please help me.. Is it possible through teamviewer?? please please help me..

OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.

ChazzMatt said:
OK, read this thread.
https://forum.xda-developers.com/moto-maxx/help/bootloader-locked-acess-recovery-os-t3662683
and this one:
https://forum.xda-developers.com/moto-maxx/help/maxx-xt1225-br-hard-brick-help-please-t3661803
After that, specifically you want to download this file:
https://forum.xda-developers.com/showpost.php?p=73528589&postcount=19
Yes, it's for Brazil XT1225 but your bootloader is unlocked and there's no India equivalent posted online. You need the very latest Marshmallow stock (with latest bootloader) from Motorola and that's it. For stock you can only flash the same version bootloader you have or newer.
You will NOT be using RSDLite. You will have to use ADB fastboot. Read this post for instructions.
https://forum.xda-developers.com/dr...force-how-to-manually-flash-official-t3282077
Yes, it's for the Moto X Force, but the steps are still the same for any bootloader unlocked Motorola device. You are flashing cross-region firmware on your India XT1225 to get it back working again.
You will need to omit gpt.bin when flashing the commands.
Once your phone is working again, you will need to re-flash TWRP and root with that older SuperSu version or whatever you did the first time.
After that you can reinstall a custom ROM if you wish.
Click to expand...
Click to collapse
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.

krishna13 said:
Downloaded the files from http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/ and tried all the steps from the link u provided.These are the steps i followed.
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash system system.img_sparsechunk.11
mfastboot erase cache
mfastboot erase userdata
mfastboot oem fb_mode_clear
mfastboot reboot
But failed to reboot. In bootloader logs its showing as
"failed to validate boot image ret :-1"
Fastboot reason : fall-through from normal boot mode
any other method please?? help me with this.
Click to expand...
Click to collapse
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).

ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
Yes. My bad. i had just copied commands to show u that i followed them. But in real, i had only flashed 9 of them.
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
I am confused

ChazzMatt said:
One thing...
On that Brazil firmware link I only see 10 sparse chunks, numbered 0-9, Yet, in your post above you have 12 listed. how are you flashing 12? (0-11) You can only flash as many sparse chunks as there are, that example from the Moto X Force thread is just an example. You have to flash the exact number.
I see you did NOT flash gpt.bin, which is good.
If your bootloader is still unlocked, this should work.
The only thing else I can suggest is this powerful temp root command first, before flashing the Brazil image. But you then have to flash an "end"/"finish" command or the next time you reboot, that itself will cause a bootloop. Over in the Droid Turbo forum, they use that temp root command to flash Sunshine, so Sunshine can then unlock the bootloader. You don't need Sunshine, I am only pointing you to the temp root file, which may help you flash this Brazil Marshmallow image.
There was another thread I can't find right now, from a person in very similar circumstances to you. His bootloader was even locked -- which was worse than you. But using that temp command, he was able to revive his phone using ADB fastboot flashing. His only problem then was not ending the temp root, and now I've lost the thread.
So, try this. Flash the temp root, followed by all the ADB fastboot commands to flash that image, followed by the command to end the temp root (it's double quotation marks with a space before them).
Click to expand...
Click to collapse
This is how i did this time..
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.003s]
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.204s]
finished. total time: 0.285s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.590s]
writing 'boot'...
OKAY [ 0.123s]
finished. total time: 0.714s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.599s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.715s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.335s]
writing 'system'...
OKAY [ 1.698s]
finished. total time: 10.118s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.597s]
writing 'system'...
OKAY [ 1.551s]
finished. total time: 9.155s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.947s]
writing 'system'...
OKAY [ 1.617s]
finished. total time: 9.569s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.070s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.669s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.156s]
writing 'system'...
OKAY [ 1.622s]
finished. total time: 9.782s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.291s]
writing 'system'...
OKAY [ 1.695s]
finished. total time: 9.992s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.296s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.911s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.819s]
writing 'system'...
OKAY [ 1.568s]
finished. total time: 9.393s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.307s]
writing 'system'...
OKAY [ 1.613s]
finished. total time: 9.926s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.985s]
writing 'system'...
OKAY [ 1.379s]
finished. total time: 8.371s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.013s]
finished. total time: 0.016s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "end"
...
FAILED (remote failure)
finished. total time: 0.011s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id "finish"
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id ""
...
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\SRK\Downloads\Motorola firmware>fastboot oem config fsg-id " "
...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\SRK\Downloads\Motorola firmware>mfastboot reboot
rebooting...
finished. total time: 0.004s
but same problem..no success ..same ret :-1 in bootloader logs. Did i do wrong??

krishna13 said:
and coming to your post, so should I need to download the initroot from "got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-...ader-t3639316/" and install in my system and run the .bat file? would it work for my xt1225? there mentioned other than xt1225. after flashing all the 9 system sparse chunks from brazil firmware, is this the command to end the temp root?? fastboot oem config fsg-id " "
Click to expand...
Click to collapse
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.

ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???

krishna13 said:
i have downloaded auto-intiroot-xt1254_quark.so shall i simply install it in my system and run the bat file? so no problem for my phone? to end that, simply ill follow the command without spaces.
first ill install bat file,then flash all the fastboot commands of firmware,and before fastboot reboot, ill end the temp flash and reboot my device.is this the procedure???
Click to expand...
Click to collapse
Yes, you downloaded the right version. It's this one, even though you have an XT1225:
http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1254
Yes, install the bat file via fastboot, then run the fastboot commands for firmware, then end the temp flash and try to reboot.
IF this doesn't work, I have no other ideas really. Just variations of making sure you are flashing the firmware correctly, which you seem to be doing.

ChazzMatt said:
There was another thread I can't find right now, from a person in very similar circumstances to you.
Click to expand...
Click to collapse
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.

hitokage004 said:
That was in [All Quark][Official] Stock Firmware Moto Maxx Droid Turbo Moto Turbo, and started on page 48 - post #475.
Click to expand...
Click to collapse
Thank you! Thought I was going crazy. I KNEW I had discussed this just recently and the person used temp root and got the phone working again. Then I couldn't find the posts. But it was you who suggested the temp root tool and it worked.
Yeah, start on this page, with post 475:
https://forum.xda-developers.com/mo...tock-firmware-moto-maxx-droid-t3063470/page48
There was no final resolution to that person's problem but he was able to reboot the phone and it was working again, thanks to the temp root.

ChazzMatt said:
Yes, but to end the temp root -- it's hard to tell due to XDA formatting --but It's fastboot oem config fsg-id "", with a space between the fsg-id part and the double quotation marks. There's NO space IN the quotation marks, just a space before it.
Click to expand...
Click to collapse
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.

krishna13 said:
I had run auto-init.bat which booted my phone in fastboot mode asusual.then i followed the same steps by ending the temp root like mentioned.But same happened. in bootloader logs the same ret=-1 and also Fastboot reason : Reboot mode set to fastboot.This was all i followed.
C:\Users\SRK\Downloads\NewMoto>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (2163 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing rpm ...
OKAY [ 0.247s]
finished. total time: 0.377s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.579s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.692s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.108s]
finished. total time: 0.705s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262143 KB)...
OKAY [ 8.292s]
writing 'system'...
OKAY [ 1.721s]
finished. total time: 10.018s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (239764 KB)...
OKAY [ 7.592s]
writing 'system'...
OKAY [ 1.582s]
finished. total time: 9.180s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (250695 KB)...
OKAY [ 7.937s]
writing 'system'...
OKAY [ 1.618s]
finished. total time: 9.561s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (255001 KB)...
OKAY [ 8.069s]
writing 'system'...
OKAY [ 1.592s]
finished. total time: 9.666s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (257746 KB)...
OKAY [ 8.157s]
writing 'system'...
OKAY [ 1.625s]
finished. total time: 9.787s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (261982 KB)...
OKAY [ 8.288s]
writing 'system'...
OKAY [ 1.703s]
finished. total time: 9.996s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.608s]
finished. total time: 9.907s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (247037 KB)...
OKAY [ 7.821s]
writing 'system'...
OKAY [ 1.547s]
finished. total time: 9.375s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (262140 KB)...
OKAY [ 8.293s]
writing 'system'...
OKAY [ 1.614s]
finished. total time: 9.912s
C:\Users\SRK\Downloads\NewMoto>mfastboot flash system system.img_sparsechunk.9
target max-sparse-size: 256MB
sending 'system' (219553 KB)...
OKAY [ 6.959s]
writing 'system'...
OKAY [ 1.375s]
finished. total time: 8.341s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\SRK\Downloads\NewMoto>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\Users\SRK\Downloads\NewMoto>mfastboot oem fb_mode_clear
...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\Users\SRK\Downloads\NewMoto>fastboot oem config fsg-id ""
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.056s]
finished. total time: 0.060s
C:\Users\SRK\Downloads\NewMoto>mfastboot reboot
rebooting...
finished. total time: 0.003s
could you or someone assist me in team viewer please?? I really having bad days. no phone from 4 days.
Click to expand...
Click to collapse
These three errors you got which I'm pasting below are normal:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Click to expand...
Click to collapse
But other than that, everything shows it's flashing OK? Yet it still won't boot...
Searching the internet for that " ret=-1" error message, came across this:
https://productforums.google.com/forum/#!topic/nexus/Z-Ek9spUUMk;context-place=topicsearchin/nexus/authorid$3AAPn2wQd-FQicFC7RbavvPMsMOeXIILaxmrMVo3XYrb0P_pWrMw5VVUQIz_Dx8Ty4va61Ty_aMSFj%7Csort:date%7Cspell:false
and this:
https://productforums.google.com/forum/#!topic/nexus/9pgTA6RG85Y
Both were told they probably had hardware failure, most like flash memory.
I'm almost out of ideas. Since all your flashing did seem to go OK, how about now trying to flash TWRP again? You would be replacing stock recovery with a TWRP image. Then with phone off try using the volume + power button to boot to bootloader screen, if it will let you. Then from there you can choose TWRP. Once in TWRP (if you get that far) you can try dragging over a ROM to flash.
But if you are experiencing a hardware failure you probably won't be able to get that far.

I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.

hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
thanku for ur help. I just saw this post now. Ill try today and will update you the status.

hitokage004 said:
I'm generally not very good walking people through things, but here is something to try. It's almost exactly what you've done before, except you will use mfastboot erase for specific partitions before flashing. Do NOT erase the bootloader - it can brick the phone. You shouldn't need to temp root, since your bootloader is unlocked.
From a command prompt, in the directory/folder you have ADB/(m)fastboot:
reminder do NOT erase the bootloader:
Code:
mfastboot flash bootloader bootloader.img
Code:
mfastboot erase boot
mfastboot flash boot boot.img
mfastboot erase recovery
for stock recovery use:
Code:
mfastboot flash recovery recovery.img
for TWRP (download link) use:
Code:
mfastboot flash recovery twrp-3.1.1-mod_2-quark.img
Code:
mfastboot erase system
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot erase cache
mfastboot erase userdata
if you installed TWRP:
Code:
mfastboot reboot-bootloader
then start recovery to let it make the changes to keep it from being replaced, and then reboot
for stock recovery just reboot:
Code:
mfastboot reboot
If this doesn't work it's either failing hardware as ChazzMatt stated, or time to do things you shouldn't.
Click to expand...
Click to collapse
Nope.Bad news. Even this didnt work. All this happened because of AEX rom I suppose. Since I flashed that rom, most of the apps were force closing. I thought these bugs might be solved in future updates and continued using it. I shouldnt have flashed that rom. Should have continued RR rom. Huge terrible mistake of mine. I am not blaming the developer.Please dont take this as an offence.I know all this is our own risk and already mentioned at the beginning of the posts.Just Blaming myself...
Thanks for your and @ChazzMatt help anyways.thanku soo much..
RIP my Moto
Edit 1 : Bought new Samsung A9 pro which fulfills my needs with a good battery backup. Goodbye to my Moto Turbo.Also to this forum.
Once again My Heartful thanks to @ChazzMatt and @hitokage004

Database Info

welcome