Related
So I don't have a procedure to fix it but the guys at #android on Freenode gave me a bunch of tips which eventually made my phone work. It loaded a custom rom (liquid smooth) and I can make calls.
Sorry if I can't give you a more precise solution... if someone can figure out the exact reason why I was able to install a custom rom properly, it would help us find a solution to fix the GPT.BIN error.
In a nutshell, I was getting errors when trying to install a custom rom via TWRP (bypassing the stock rom errors) but now I'm able to install a custom rom and run it fine. Please read the logs despite all the crap around it.
Here is the chat log... follow though and do what I did - the solution might be in some fastboot commands I tried:
[08:31] <Jonnyw2k> what does "fastboot oem unlock" say
[08:31] <asdfsdfsadf> (bootloader) Device already unlocked! FAILED (remote failure) finished. total time: 0.003s
[08:39] <asdfsdfsadf> writing 'partition'... Preflash validation failed FAILED (remote failure)
[08:39] <asdfsdfsadf> mfastboot
[08:40] <asdfsdfsadf> not sure what the error is.....
[08:40] <Khaytsus> Well that just looks vulgar at a glance
[08:42] <Jonnyw2k> asdfsdfsadf there is a "fastboot oem fb_mode_clear" command that apparently sometimes helps, but that seems to be more todo with a fastboot issue
[08:42] <asdfsdfsadf> ... OKAY [ 0.002s] finished. total time: 0.003s
[08:43] <asdfsdfsadf> same error when I flash gpt.bin
[08:43] <DrChandra> Perhaps the partition is damaged.
[08:43] <Jonnyw2k> try flashing the gpt now
[08:43] <Aevum> what phone is it ?
[08:43] <asdfsdfsadf> moto g xt1032
[08:44] <DrChandra> Consider the erase and format commands within fastboot
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> just did -w
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <Aevum> fdoijghfiodjhadt
[08:45] <Aevum> try this http://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> formatting 'userdata' partition... Creating filesystem with parameters: Size: 6173884416 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 23551 Label: Blocks: 1507296 Block groups: 46 Reserved block group size: 367 Created filesystem with 11/376832 inodes and 50150/1507296 blocks sending 'userdata' (98165 KB)... writing 'userdata'... OKAY [ 9.953s] erasing 'cache'... OKAY [ 0.24
[08:46] <asdfsdfsadf> Aevum: tried that twice... to give you some insight, I upgraded to 4.4.4 GPE on a non-gpe device, many people got bricked when they tried to downgrade
[08:47] <asdfsdfsadf> After fastboot -w command, same error when trying to partition
[08:47] <Aevum> i dont know what flashing tools motorola uses, becuase theres usuayl the fastboot and ADB
[08:47] <Aevum> and also a proprietary tool from the manufacturer for bathc flashing
[08:48] <asdfsdfsadf> RSD Lite doesn't detect hte phone in fastboot
[08:49] <Aevum> theres usualy a fastboot and a flashing mode
[08:49] <DrChandra> RSD might be asking for a fastboot version and mismatching against whatever is being returned by the bootloader. It could e part of what Motorola uses to prevent anything but their own tool from being used.
[08:52] <Aevum> can you get ADB access ?
[08:52] <The0x539> y'know what
[08:52] <asdfsdfsadf> Aevum: yes ADB works
[08:52] <The0x539> I'll wait until I actually get it
[08:52] <DrChandra> I don't think he can boot, so he won't have adb
[08:53] <asdfsdfsadf> ADB works from stock and custom recovery
[08:53] <asdfsdfsadf> They both can get pushed files
[08:53] <asdfsdfsadf> But when it's time to install
[08:53] <asdfsdfsadf> they fail
[08:53] <DrChandra> asdf: So the main OS is what isn't booting?
[08:53] <asdfsdfsadf> Yes
[08:53] <asdfsdfsadf> But main os can't even get installed
[08:53] <DrChandra> Can you mount anything from recovery?
[08:53] <asdfsdfsadf> Anything I throw at it gives a partition error
[08:54] <asdfsdfsadf> Let me go to recovery and I'll give you the exact errors
[08:54] <Aevum> you are pre flashing the correct boot.img for every rom before, no ?
[08:54] <DrChandra> I wish fastboot could boot directly into recovery. I have to operate it from the screen to get there, or double boot.
[08:54] <asdfsdfsadf> Aevum: yes
[08:55] <Aevum> and the hboot versions coinside ?
[08:55] <DrChandra> Damaged flash memory
[08:55] <Jonnyw2k> you can "fastboot boot recovery.img"
[08:55] <asdfsdfsadf> Jonnyw2k: lfashes but nothing works after it finishes
[08:55] <Aevum> i would format the whole internal memory and start over with a stock image
[08:56] <DrChandra> Jonnyw2k: Yes, but you're not booting what's on the device, and transferring it takes forever.
[08:56] <Jonnyw2k> he's trying that its the partition table that is messed up but he cant flash a new one
[08:56] <asdfsdfsadf> >adb push Rom.zip /sdcard/
[08:56] <asdfsdfsadf> Let me transfer this
[08:56] <asdfsdfsadf> IT's a rom
[08:56] <asdfsdfsadf> And I'll give you the message in TWRP{
[08:56] <DrChandra> I use TWRP
[08:57] <asdfsdfsadf> TWRP works here... it just can't install ****
[08:57] <asdfsdfsadf> Let me get the message
[08:57] <asdfsdfsadf> 1 minute
[08:57] <Sloth514> how come i feel like this conversation should b in #android-root
[08:58] <DrChandra> Well, if the main OS partition (system) is messed up, you can't mount it, and/or you can't write it, so trying to get TWRP to install Rom.zip isn't going to work.
[08:58] <asdfsdfsadf> wow
[08:58] <asdfsdfsadf> mother****ers
[08:58] <asdfsdfsadf> rom booting :/
[08:58] <asdfsdfsadf> PC detecting phone during boot
[08:59] <DrChandra> ADB to main OS?
[08:59] <asdfsdfsadf> I adb'd liquidsmooth rom.zip
[08:59] <asdfsdfsadf> and ran it from TWRP
[08:59] <asdfsdfsadf> IT installed with no issue
[08:59] <asdfsdfsadf> Rebooted
[08:59] <DrChandra> Oh, ran it. YOu didn't install it.
[08:59] <asdfsdfsadf> Liquid smooth is now loading...
[09:00] <asdfsdfsadf> Still loading. I guess the first time is slow
[09:00] <Jonnyw2k> DrChandra he flashed the rom.zip from TWRP, and now is booting the rom
[09:00] <DrChandra> He didn't say he flashed it
[09:02] <DrChandra> asdfsdfsadf: Did you do an Install from TWRP, and select Rom.zip from the sdcard?
[09:02] <asdfsdfsadf> Yes DrChandra
[09:02] <asdfsdfsadf> After pushing it with ADB
[09:02] <DrChandra> OK, he flashed it
[09:02] <asdfsdfsadf> But I tried that before and got errors
[09:02] <asdfsdfsadf> Some command I typed in fastboot must have fixed it...
[09:03] <DrChandra> How is it that TWRP knows how to write the system partition and all the flash tools don't?
[09:03] <asdfsdfsadf> But right now the issue is that I'm stuck at the animated boot scren (never got this far)
[09:03] <asdfsdfsadf> normally it takes time, but not several minutes, right?
[09:03] <Jonnyw2k> you can try and reboot
[09:03] <Jonnyw2k> press and hold power till it turn off
[09:04] <Jonnyw2k> then turn it on again
[09:10] <DrChandra> Well, if the device is badly broken enough, even fastboot won't work.
[09:10] <Khaytsus> fastboot will _always_ work unless you somehow broke the bootloader
[09:10] <DrChandra> logcat is miles above that
[09:10] <asdfsdfsadf> fastboot works, it just won't flash gpt.bin... wait let me try that again now that liquidsmooth actually got flashed though TWRP
[09:10] <Khaytsus> logcat requires the system be at least in some normal condition, even if it's boot looping or something
[09:10] <Leeds> Khaytsus: it seems that - at least at one point - fastboot was working in the sense of responding, but not working because the partition table was so screwed that it couldn't read/write partitions
[09:11] <Khaytsus> Leeds: Heh. Interesting. I suppose if you break _partitions_, yeah....
[09:13] <Khaytsus> fastboot flash partition gpt.bin <-- looks like this is what you do
[09:13] <asdfsdfsadf> So: fastboot flash partition gpt.bin Gives me: writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.423s
[09:14] <asdfsdfsadf> Which is the original error
[09:14] <DrChandra> I've never seen fastboot write to "partition" before. It's always "system", "boot", "userdata", or "cache"
[09:15] <asdfsdfsadf> The only difference between now and then is that the rom actually boots but just stays stuck on the animation screen
[09:15] <Khaytsus> That error means unsigned or unrecognized img file
[09:15] <Khaytsus> You sure this file is valid?
[09:15] <asdfsdfsadf> Yes, tried 2 copies
[09:15] <asdfsdfsadf> Ok something just happened
[09:15] <asdfsdfsadf> Rom just loaded
[09:15] <asdfsdfsadf> I'm on the home screen
(Rebooted twice after it was stuck on loading screen)
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
newklear85 said:
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
Click to expand...
Click to collapse
don't get it xD
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
hansdepaula said:
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
Click to expand...
Click to collapse
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
gpt.bin for 4.4.3 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
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.352s]
finished. total time: 0.373s
C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.302s]
writing 'recovery'...
OKAY [ 0.181s]
finished. total time: 0.485s
C:\Users\Hans\Desktop\443>
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
---------------------------------------------------------------------------
gpt.bin for 4.4.2 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\442>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Users\Hans\Desktop\442>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.165s]
finished. total time: 0.479s
C:\Users\Hans\Desktop\442>
same
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
-------------------------------------------------------------------------
my fastboot dnt write nothing,
i think, sone thing have format partitions to RAW system
and i cant white or format then..
see more logs about my case: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
maybe you can help..
thx..
newklear85 said:
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
Click to expand...
Click to collapse
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Fresroqir said:
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Click to expand...
Click to collapse
Only thread in here that can potentially make it work... almost no attention lol
For the mobile network, flash the radio that came with stock.
man, you can upload to me a new gpt.bin and motoboot.img ..
4.4.4 maybe
i only have 4.4.3 and lower versions, and it dont work..
:/
I have somehow totally trashed my Android install. I have a UK retail Moto G XT1032.
While downloading the OTA lollipop update, the download appeared to stall. I decided to give up on the update, so I switched the phone off. When I turned it back on again, every single process crashed. "Unfortunately dialler/android.process.acore/Calendar/android.process.media/etc has stopped". I can keep tapping "OK" for ever to clear these notifications, but can't actually use the phone for anything at all.
So I decided to do a factory reset from fastboot. It made no difference.
I tried a factory reset from recovery. It made no difference.
Using fastboot, I attempted to install the stock ROM according to the guide at http://forum.xda-developers.com/showthread.php?t=2542219. Everything seemed to flash OK - I got OKAY on the PC and the commands appeared to be running on the phone OK, but when it restarted, the phone was exactly the same - my wallpaper photo was still there, and the app icons that I could glimpse behind the endless notifications were my apps.
I tried several more times, this time flashing the 4.4.4 ROM (RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF). Exactly the same results - nothing changes when I restart.
It's as if the mfastboot flash commands do nothing at all! I have run all the mfastboot commands described by the guide in the order given.
I've also tried booting to recovery and connecting to ADB, but the PC cannot see the device.
I've tried replacing the recovery with CWM and TWRP .img files, but the flash command, while seeming to work, doesn't change anything at all! The recovery that I have installed is the standard KXB21.14-L1.40.
I have tried "mfastboot.exe erase recovery", before attempting to update the recovery, but it makes no difference.
Does anybody have any idea what I am doing wrong? It seems that no "mfastboot flash xxx yyy" command works at all on my phone.
Did you installfastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Got the same problem. I've already posted this in a few threads and didn't get any answer, though
Sounds crazy but, when you type fastboot devices with your phone connected in fastboot mode, does the command return your phone's serial #?
Yes, everything via fastboot works (says complete, done etc.) except it doesn't affect the real system. If you sideload ADB you will see that the system, data and cache partition become read-only. I've managed to remount only data partition with write privileges, but that doesn't help.
Are you flashing each partition manually? You can see your device's serial # in fastboot?
audit13 said:
Did you install fastboot or mfastboot? ADB commands only work if the is booted and USB debugging is on.
Click to expand...
Click to collapse
Originally, I used the version of fastboot that came with the first stock ROM I tried (falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB).
Later on, I installed mfastboot and used that instead. The results were the same. Nothing seems to actually be flashed, but there are no errors on either the PC or the phone.
ADB does not work in fastboot (I don't believe it's supposed to!), but it also will not work with the version of recovery that I have, which is why I was attempting to install CWM and TWRP in its place.
audit13 said:
Are you flashing each partition manually? You can see your device's serial # in fastboot?
Click to expand...
Click to collapse
Yes. I'm currently trying the following sequence with the XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml ROM...
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The mfastboot command returns OKAY for each of these, and a couple of yellow lines appear on the phone for each command, indicating that the right command is running, with no error messages.
I have never used mfastboot. Maybe try using fastboot to flash? I have used fastboot on my Moto G and Moto Atrix HD with great success.
Tried with fastboot, tried with mfastboot, got no errors but nothing changes. The real problem I suppose is corrupted partitions.
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
dog121 said:
Have you tried the moto flash tool??
http://forum.xda-developers.com/showthread.php?t=2934358
Click to expand...
Click to collapse
I've just given it a go.
When flashing the ROMs, it basically runs the same mfastboot commands that I was running before, so the result was exactly the same.
However, the ADB Driver install button was worth trying. The driver supplied has enabled my PC to communicate with the phone using ADB when in recovery mode!
Unfortunately, after selecting "apply update from ADB" on the phone, and running "adb sideload <ROM zip file>", it sends it to the phone (taking a couple of minutes), and the phone says "Verifying update package", followed by "Installation aborted".
When you sideload, do you need some sort of special format ROM file?
audit13 said:
@IcyBee, I see you're flashing the GB retail. Is it possible to try a different ROM such as the GPE?
Click to expand...
Click to collapse
I was hoping to use the stock ROM, just to get the phone back to its original state.
If the mfastboot command does nothing, I doubt trying different ROMs will help. But I'll probably try it if I can't get anything else to work.
thanks a lot!
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
lost101 said:
@IcyBee - I have seen this before. Try using fastboot on a Linux PC / Laptop. You can use a live cd to do this - no need to actually install Linux.
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Thanks for the idea. I happen to have a laptop running the latest Lubuntu.
I installed fastboot as you directed and re-flashed everything. Exactly the same. The commands all say OKAY, the yellow text on the phone says it's running the commands, but when I reboot - everything is exactly as it was before - including my wallpaper photo and app icons. And every single process on the phone is crashing.
I do not believe fastboot is actually working on this phone. The only commands that seem to work are the ones to unlock the bootloader and the one to reboot the phone.
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
I.e first file is sparsechunk.0 not sparsechunk1
EDIT: Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
It's retail Brazil, but will work anywhere in the world.
I suggest you skip flashing the bootloader - motoboot.img
lost101 said:
@IcyBee - does the fastboot commands for flashing the system.img files actually match the files in the firmware folder?
Click to expand...
Click to collapse
Yup.
Next I would try the only available XT1032 factory firmware image: http://forum.xda-developers.com/showthread.php?p=58534609
Click to expand...
Click to collapse
OK - I downloaded this and flashed it. Exactly the same as all the previous attempts. It appears to work, but when I restart, the phone is in exactly the same state as before, as if no flashing has happened.
Here is the command line output:
Code:
C:\>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.024s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.353s]
finished. total time: 0.380s
C:\>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.110s]
finished. total time: 1.197s
C:\>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.105s
C:\>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.670s]
finished. total time: 1.030s
C:\>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.695s]
finished. total time: 1.060s
C:\>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.140s]
writing 'system'...
OKAY [ 8.155s]
finished. total time: 16.295s
C:\>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.185s]
writing 'system'...
OKAY [ 8.690s]
finished. total time: 16.885s
C:\>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.265s]
writing 'system'...
OKAY [ 8.755s]
finished. total time: 121.145s
C:\>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.255s]
writing 'system'...
OKAY [ 6.475s]
finished. total time: 11.735s
C:\>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 0.825s]
finished. total time: 2.435s
C:\>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.020s
C:\>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.070s]
writing 'fsg'...
OKAY [ 3.180s]
finished. total time: 3.250s
C:\>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.025s]
finished. total time: 0.025s
C:\>mfastboot reboot
rebooting...
finished. total time: 0.005s
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Thanks again to all of you for your assistance in this matter.
IcyBee said:
Attached is a very blurry picture taken in poor light with my very old spare phone of the Moto G just before boot. All commands seemed OK, except for recovery.img and motoboot.img, which displayed "hab check error" in pink (not pictured).
Click to expand...
Click to collapse
Recovery mode ADB will work in Linux. You could try side-loading the 5.0.2 OTA Update.
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Try using mfastboot:
https://www.androidfilehost.com/?fid=23578570567719065
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata
Is the phone definitely an XT1033 Dual-SIM?
lost101 said:
Try using mfastboot:
Just so you are aware: very careful using the 'erase' command. Erasing certain partitions will destroy the phone. The only commands to ever really use are:
mfastboot erase cache
mfastboot erase userdata
Is the phone definitely an XT1033 Dual-SIM?
Click to expand...
Click to collapse
Yes sir it was bought in Saudi (asia) and is dual sim. The box also states that it is xt1033.
I have tried what you have suggested but the error still remains.
C:\Users\...\Desktop\mfastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 14.955s
C:\Users\...\Desktop\mfastboot>mfastboot erase userdata[/U]
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.953s
If it is of any help, the screen says that it has 41.18 bootloader, I don't exactly know what this information is for.
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
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:
Try flashing the XT1033 Retail Asia Factory Firmware Image: http://forum.xda-developers.com/showpost.php?p=58534609&postcount=519
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Do all commands manually:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk4 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
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
Click to expand...
Click to collapse
I already tried sir along with the Brazilian firmware and both returned the same error. The same partition error,
I get stuck right at the first command "mfastboot flash partition gpt.bin", it says the the phone couldn't erase the partition. I'm starting to hate motorola right now
The money I saved just to buy this phone and I only got to use it for 1 month.
I understand that my partition is likely messed up or is corrupted even though I did nothing with my phone except upgrading it to lollilop (biggest mistake ever), what I don't understand is there aren't anyone else here in the forum who seem to have the same problem as mine, its like I am the only who has this kind of error so there are no threads at all discussing on how to solve this.
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
lost101 said:
You could try booting into a custom recovery using the following command:
mfastboot boot recovery.img
Try latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
and flash one of these Lollipop zips: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 5.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.424s
titan015 said:
I can't install TWRP nor clockwerk recovery, whenever I try the same frustrating error occurs. Here:
Click to expand...
Click to collapse
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img
Flashes TWRP:
mfastboot flash recovery recovery.img
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img
Flashes TWRP:
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Try another recovery.img just in case that one was a bad download.
titan015 said:
Please help. I saved some money and bought this phone in January via a friend abroad (xt1033) and by February updated it to lollipop but few days later after the update the phone suddenly rebooted and got in the boot loop. Since then I haven't been able to use the phone for three months. It no longer has warranty because I attempted to unlock its bootloader and besides by availing the warranty I need to send back the phone from Philippines to the Kingdom of Saudi Arabia where it is bought and that is expensive and risky on my part. So now either I fix the phone myself or it goes straight to the trash bin.
I tried following threads here in the forum such as restoring the phone to stock, installing custom recoveries, flashing images. All of these returned the same error. And that is.
C:\Users\...\Desktop\adb and fastboot\Minimal ADB and Fastboot>fastboot flash
recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 10.300s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.377s
No matter what I do. The line (bootloader) Failed to erase partition always comes out. I have tried searching for the same threads here in the forum but all are unanswered. Please help me to fix this phone.
Click to expand...
Click to collapse
I have the same problem, do you managed to fix it?
kesy85 said:
I have the same problem, do you managed to fix it?
Click to expand...
Click to collapse
no. i've tried just about everything, didn't managed to fix it
hi
i have the same problem too bro, im from the philippines too..
have u fixed it yet?
no fix?
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Same for me, BUMP
hand_solo said:
Is this thread abandoned?
Is unlocking your bootloader a prequisite to flashing recovery.img? I have a soft bricked (from what I've read) XT 1032 and I forgot which Lollipop version I had (I'm a loser, I know).
I vaguely remember seeing 5.0.1 . Less likely, it could have been 5.0.2 as well, but less likely. And I'm almost sure it was not 5.1 (I would have remembered).
Anyway, since I did not want to unlock the bootloader (I have still not given up on recovering my data as I did not back them up because of the loser that I am), I did not try flashing a custom recovery like TWRP, and instead tried:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
I repeated these steps with 5.0.2 files and that had the same results.
Could this be all because my bootloader is not unlocked? Please tell me that I don't HAVE to unlock bootloader. Of course, I have never tried rooted my phone either. I was running pure OTA stock when my phone suddenly stopped booting up and went into a boot loop.
Click to expand...
Click to collapse
Anyone managed to fix this?
The best I've found...
hand_solo said:
- flashing the GPE recovery.img. I got the partition error (cannot erase).
- flashing gpt.bin, got Preflash vaidation failed
Click to expand...
Click to collapse
...is this:
Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
Fastboot Error: preflash validation failed
Try your original (or last flashed) firmware.
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076/
P.s.: I have the same problem.
titan015 said:
Sir I'm sorry but could you please elaborate more on what am I supposed to do?
What I did was download TWRP, renamed it to recovery.img and then pasted it in a folder with mfastboot in it. I then executed the command you supplied "mfastboot boot recovery.img" and heres the result:
C:\Users\...\Desktop\mfastboot>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 10.297s]
booting...
FAILED (remote failure)
finished. total time: 20.326s
on the phone it says in pink font color "Incomplete boot image for booting"
Click to expand...
Click to collapse
lost101 said:
It is possible to load TWRP without flashing it.
The following are two different commands.
Boots TWRP without flashing:
mfastboot boot recovery.img
Flashes TWRP:
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
For me the error is:
Code:
fastboot flash recovery twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
target reported max download size of 536870912 bytes
[COLOR="SeaGreen"]sending 'recovery' (9372 KB)...
OKAY [ 0.377s]
[/COLOR]writing 'recovery'...
[COLOR="Red"][B](bootloader) Permission denied
FAILED (remote failure)[/B][/COLOR]
finished. total time: 0.408s
Same thing when I try to boot instead of Flashing
Code:
fastboot boot twrp-2.8.7.0.-falcon_STOCK_NOTHEME.img
[COLOR="SeaGreen"]downloading 'boot.img'...
OKAY [ 0.347s][/COLOR]
booting...
[B][COLOR="Red"]FAILED (remote failure)
[/COLOR][/B]finished. total time: 0.354s
An unlocked Bootloader is required to flash (or boot) a custom recovery.
lost101 said:
An unlocked Bootloader is required to flash (or boot) a custom recovery.
Click to expand...
Click to collapse
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Der_K said:
But it's a Stock rom... I've tryied this custom recovery, of course, but this isn't working with a stock rom either.
Click to expand...
Click to collapse
Please try to explain more clearly. Don't use the term ROM, if you are talking about a factory firmware image - in other words - sparsechunk files.
Can you flash the stock recovery img included in the factory firmware image?
I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?
Yumi Chi said:
I am a inexperienced user I am also slow and need step by step clear instructions.. I have not once ounce of a clue how to use CMD ... ok ..
I got a Moto G X1028 from a friend who said it wasn't booting up..
found out it does boot but only into Fastboot menu..
Normal power up, recovery, and factory all when clicked, make the screen go black,then a light on top of phone blinks 3 times..
Now I have gotten it to seem idk alive, when clicking the 3 choices above sometimes it randomly will ether blink 3 times or give a system failed to verify..
although sometimes when the recovery feature does go through there is a little green android laying down with a red triangle ...
I am trying to see if theres is some hope on restoring this phone through Fastboot..
The Pc recognizes the device as Fastboot falcon S but can't enter it at all ...
I am looking for a more detailed step by step on how, if possible to restore this device ..
I have attempted many tutorials all leaving me bewildered and confused ..
I have on my PC 2 roms I think thats what they are ...
philz_touch_6.57.9-falcon.img and cm-12-20150131-UNOFFICIAL-falcon.zip...
I have installed the minimal ADB and Fastboot software
and the Motorola drivers are installed and recognizes the device as 210.12.41.falcon_cdma.verizon.en.us
So I am hoping someone can help me, understand I am slow and on top of that a newb...
and bring hope that this phone can be restored to working order ..
Note: not sure if this could help it states the device is locked, Status code 0
on screen at the time of posting this is fastboot reason: volume down key pressed
usb connected, cmd: getvar:all
So:
Can this phone be restored?
Will it be a easy task?
Can it be restored if the device is locked?
Click to expand...
Click to collapse
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.
a_gert said:
If you have access to fastboot, it is entirely possible that you can manually restore the stock 4.4.4 ROM and recovery that way. I'll have some time in the morning where I can walk you through some steps in detail if you still need it.
Click to expand...
Click to collapse
I would greatly appreciate that ^-^
Yumi Chi said:
I would greatly appreciate that ^-^
Click to expand...
Click to collapse
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
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
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!
a_gert said:
Alright, let's see what we can do for you! First things first, download the XT1028 4.4.4 stock ROM from here:
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
It's big, filefactory is slow, and that's going to take a while, so you can sit back and get up to speed on the rest of things while that is in progress. The next thing you need to do is head over to the following thread and read through the first post. You will be following the process for firmware downloaded in xml.zip format: http://forum.xda-developers.com/showthread.php?t=2542219
It sounds to me like you have done at least a solid portion of the prerequisites for this, but you can run through the list to make sure. You might want to download and install the Motorola drivers (Prerequisite 'a') if you haven't already, and you'll want to get the mfastboot-v2.zip package (Prerequisite 'c'). Once you have everything downloaded and the drivers/adb/fastboot stuff installed, the basic idea here is that we are going to take the original stock firmware piece by piece and manually install it using the phone's fastboot mode. If it works correctly, it will completely replace whatever corrupted ROM and recovery files are on your device presently and may allow you to actually boot up the phone into Android 4.4.4 KitKat at a factory default condition.
Find and locate the place where you installed adb and fastboot. On my own system, I just installed it to "C:\adb" for simplicity. In the folder, you'll see adb.exe, fastboot.exe, etc. Take the mfastboot-v2.zip you downloaded above and extract the contents into the same folder -- you should now also have a "mfastboot.exe" file there, as well. Finally, take the stock firmware zip file you downloaded from the above link and extract this into the same folder (make sure all these files are actually in the same folder as the .exe's, not in some subfolder); it contains a good dozen or so files that we are going to flash onto your phone.
In Windows, if you're in the folder with the above files and you hold down the Shift key and right click somewhere in the folder, you'll have an option from the drop down menu to "Open command window here" which should get you a nice command prompt right where you need to be. Get your phone rebooted into fastboot mode, connect it to your PC, and then we can start running through the commands if everything is working correctly.
On the post I linked above, there is a series of mfastboot commands you will have to enter one by one and confirm that it returns an [OKAY] message afterward. The only variation you should have from the original post is that you need to enter an additional command for sparsechunk4 (make sure you scroll this whole list):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
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
If everything went well, you should be rebooted into a stock Verizon 4.4.4 ROM. Take your time, let me know if you have any additional questions about the steps or you get stuck, and good luck!
Click to expand...
Click to collapse
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here
Yumi Chi said:
This ^ is what I needed simple step by step you sir are amazing ! I have everything downloaded but the rom its still going atm so once that is done ill finish the rest of steps and come back here
Click to expand...
Click to collapse
Help ...failed
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.036s]
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.346s]
finished. total time: 0.382s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.156s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.094s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.109s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Yumi Chi said:
Help ...failed
Click to expand...
Click to collapse
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
a_gert said:
Any idea as to the status of the phone before you got it? The bootloader status of 0 means it is still locked and it appears from the versioning you listed that it was on 4.4.4 already, so I'm not sure why you'd be having signature verification issues reflashing 4.4.4. At this point, I am honestly just guessing, but perhaps try reflashing the partition table again (the first command with gpt.bin), then reboot the phone back into fastboot mode and try to do the other commands on a second pass?
Click to expand...
Click to collapse
Knowing my friend shes not one for updates she must have what ever update comes with this phone by default
Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
I was suggesting that after you do the mfastboot command to flash the gpt.bin file (which, from your log appeared to work corrrectly), you could then reboot the phone into fastboot mode (turn it off, turn it back on and get it back into fastboot mode) and then resume from step two. My only theory there was that it may need to actually reformat the partitions before you go back in and start flashing things and that might be why you have the error you do.
Question 30 at: http://forum.xda-developers.com/showthread.php?t=2537119 suggests that if you are failing to flash 4.4.4 at this point, you may be stuck, so I'm just trying to walk through the steps I would try myself in your scenario.
Yumi Chi said:
the phone has to be off??? it wont turn off while usb connected ok im confused now .....the phone once charged boot only in fast boot she said it did work but she thought the battery was just going no harm was done to the device .. atm the phone is stating hab check failed for system
failed to validate system image
Click to expand...
Click to collapse
Trying to find the default that comes with this phone is not my line knowledge ....
looking on a wiki this is some things i found
its a CDMA Version XT1028 for Verizon
I have a feeling it may be this default that comes with it
Operating system Android Jelly Bean 4.3[6] (Upgradable to Android 5.0 Lollipop[7])
my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?
Yumi Chi said:
my friend never updates her phones .... I think its a 4.3 jellybean any way to check that theory and find a stock rom ?
Click to expand...
Click to collapse
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.
a_gert said:
The XT1028 originally shipped with 4.3 Jelly Bean, but it is no longer the stock ROM for this device. The part where you say it was recognized as "210.12.41.falcon_cdma.verizon.en.us" means that the device and bootloader have been updated to 4.4.4 KitKat, as that string would have been different were it still on 4.3 or 4.4.2.
Click to expand...
Click to collapse
ok ill give it another shot and try reflashing
reformat the partitions how does one do this ?
Yumi Chi said:
ok ill give it another shot and try reflashing
Click to expand...
Click to collapse
Considering the phone in your hand is a Verizon model and the bootloader is locked, Best Buy has this model in stock for $30, just in case it comes to replacing it outright: http://www.bestbuy.com/site/verizon...lack/3041063.p?id=1219086346405&skuId=3041063
each time ive gotten after gpt step one: no valid gpt found
Yumi Chi said:
reformat the partitions how does one do this ?
Click to expand...
Click to collapse
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.
a_gert said:
You were doing this when you followed the first mfastboot command that flashed the gpt.bin. Do that again, reboot the phone and go back into fastboot mode, and then resume from the second command on the list. This may or may not work, but it's all I can think to suggest.
Click to expand...
Click to collapse
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
Yumi Chi said:
well the img went through the rest well failed ...
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.035s]
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.347s]
finished. total time: 0.385s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboo
t.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.123s]
finished. total time: 1.222s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.344s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.789s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.360s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.807s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (254591 KB)...
OKAY [ 13.213s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 27.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (245234 KB)...
OKAY [ 12.917s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.143s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (257606 KB)...
OKAY [ 13.315s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 21.682s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash system system.im
g_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (125353 KB)...
OKAY [ 9.052s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.917s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 6.532s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.557s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.989s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (712 KB)...
OKAY [ 5.072s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.986s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot reboot
Click to expand...
Click to collapse
Whenever something indicates FAILED, you really don't need to keep on with the following steps. What I find odd is that you are succeeding with a couple and then the remaining ones are failing. You can try to reboot after each step that succeeds, perhaps, if that helps.
I have an xt1032. i had cm12.1 running perfectly until i decided to try cm 13.... I tried to make a backup of my system with twrp which i had installed on my phone earlier, thats when the problem started. Phone kept having bootloops. I then installed cwm recovery and flashed the same cm12.1. which booted up only once after going back into bootloops. ever since, i have tried other recoveries (non except cwm 6.x.x did but it said cant mount cache\recovery\command and cant mound \sdcard\ so it was worthless) Now i tried fastboot erase userdata and this is the error
C:\Users\RECOVERY>fastboot devices
TA8900H0U0 fastboot
C:\Users\RECOVERY>fastboot erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
C:\Users\RECOVERY>fastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.047s
C:\Users\RECOVERY>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 5.384s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.472s
is my phone toast? I hope not
So this what I did...
Somehow, I managed to make fastboot erase userdata work..
then i re-flashed twrp 7.x.x by dhacker and booted into recovery
adb push boot.img of cm12.1 to /sdcard , /cache , /system , /data just to make them sure they are writable.
then adb sideload cm12.1 from my computer
factory reset
reboot system
cm 12.1 working
reboot to recovery
adb push gapps 5.1
install gapps 5.1.zip
reboot!
And everything works!!