Related
HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
I then try to flash stock firmaware and I go these error:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.010s]
writing 'partition'...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.274s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.092s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.944s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.055s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.023s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.370s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.399s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.380s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.411s
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 13.542s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.611s
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 13.618s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.713s
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 13.866s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.940s
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 12.912s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.950s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 6.698s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.726s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.996s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 5.040s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.071s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.988s
rebooting...
finished. total time: 0.001s
WAS HAPPEN TO MY PHONE ? PLEASE HELP ME ALL DRIVER IS PROPRELY INSTALL
roulyz said:
HI EVERYBODY
I need your help to unbrick my moto g XT1068.
The phone have already bootloader unlocked.
I was run lollipop custom Stock rom Optimized (root, etc) and have trwp recovery.
Every things works fine and I use the fone about 1 week and today the phone turn automatically on bootloader screen.
I was unable to boot proprely on Normal Powerup and go to recovery.
error message: failed to validate recovery image - boot up failed
Click to expand...
Click to collapse
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.5.0
Duck86 said:
What version of TWRP are you running? Some of the older ones aren't supported anymore and have trouble flashing on the Moto G 2014. You should be using v2.8.0.5
Click to expand...
Click to collapse
Hum was using 2.8.5.0. Does good?
roulyz said:
Hum was using 2.8.5.0. Does good?
Click to expand...
Click to collapse
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
OK I will try but I have other xt1068 and that recovery work since 2 week pretty good on it
Duck86 said:
Its not officially supported and may be what the problem is.
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275
Wolfcity said:
Why do you think TWRP 2.8.5.0 is not offical supported?
http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149
This thread is under original android development and TWRP supports Moto G 2014 with this version.They did also with 2.8.4.0.
http://teamw.in/project/twrp2/275
Click to expand...
Click to collapse
Got the version numbers mixed up. Sorry, I shouldn't be doing numbers when I'm tired
I know that....
Duck86 said:
Try these:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
http://forum.xda-developers.com/moto-g-2014/development/tool-flash-boot-recovery-t2875652
Click to expand...
Click to collapse
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work I GOT all the time:
sending 'recovery' (9694 KB)...
OKAY [ 99.815s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 114.759s
NEED HELP AGAIN
roulyz said:
ok for the first link, the custom recovery is openrecovery-twrp-2.8.5.0-titan.img witch I have flashed on my brick moto g
and it works good without problem.
For the 2nd link there is no recovery img on file, it just a flashage script.
All still don't work
NEED HELP AGAIN
Click to expand...
Click to collapse
Where did you get the stock firmware? What link are you using?
all fastboot command works but I got error from partition
ADB command don't work. It works fine when the phone ran well but not now :crying:
Duck86 said:
Where did you get the stock firmware? What link are you using?
Click to expand...
Click to collapse
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
roulyz said:
the rom i flashed in the phone was Stock firmware optimised by @Shawn5162
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
and when the phone brick I have tested these link:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
and
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
Click to expand...
Click to collapse
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.
Duck86 said:
I've been thinking on it and the only other thing I can think of is to try going through the unlock bootloader proceedure again.
Click to expand...
Click to collapse
I have done bootloader unlocked process again and get that error
D:\Android TOOLS\platform-tools>fastboot oem unlock MGYXUCQJ5XHSYVTLYACD
...
(bootloader) Unlock code = MGYXUCQJ5XHSYVTLYACD
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.
Tel864 said:
It looks like the partition tables have been completely removed because the "failed to write primary gpt is a Linux error". Since none of the commands will access the partitions, I would guess the partitions need to be rebuilt. I don't have a clue how to do that on a mobile though.
Click to expand...
Click to collapse
Whoouuuaaa!!! So what can I do?
Have you guys tryed
To boot recovery
fastboot boot recovery.img
USBhost said:
Have you guys tryed
To boot recovery
fastboot boot recovery.img
Click to expand...
Click to collapse
yes, but don't works. I got error
need help please
Moto G Xt 1068: failed remotely
Did u recover your device ?
---------- Post added at 09:57 AM ---------- Previous post was at 09:56 AM ----------
roulyz said:
need help please
Click to expand...
Click to collapse
Same with me, help me out pleaseee
Thanks
Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA
messages error
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.306s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.243s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1588 KB)...
OKAY [ 0.427s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.723s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash logo logo.bin
< waiting for device >
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (2563 KB)...
OKAY [ 0.467s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.585s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.953s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.069s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.972s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.090s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (717764 KB)...
OKAY [ 46.448s]
writing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 46.565s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53644 KB)...
OKAY [ 4.224s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 4.343s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.110s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (212 KB)...
OKAY [ 0.390s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.505s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.129s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase customize
erasing 'customize'...
(bootloader) Invalid partition name customize
FAILED (remote failure)
finished. total time: 0.105s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot erase clogo
erasing 'clogo'...
(bootloader) Invalid partition name clogo
FAILED (remote failure)
finished. total time: 0.101s
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
F.xml>mfastboot fb_mode_clear
wolf1985 said:
Hello anyone! I'm looking for some help.
i have 4.2 originaly and i update the software to 4.4, after that i unlocked my bootloader, installed custom cwm and flash CM11+12 and when i want to return to stock rom i flashed stock rogers firmware 4.2, in this step everything is ok, when i try to update to 4.4 the phone turn off and trying to install the update and then is stoped and i have a messages :
Device is locked. statuts cide : 0 (why? i try to unlock it again but failed!!!)
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
im trying to re-flash the stock recovery, reboot and flash the rom 4.2 but failed !! i dont know what i can do to make the phone working again!
Well, i wish someone could help me, thanks a lot XDA
Click to expand...
Click to collapse
wolf1985 said:
C:\Users\House\Desktop\ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1F
Click to expand...
Click to collapse
(bold in the quote added by me for emphasis)
YOU CAN NOT DOWNGRADE!!! It has been warned many times that you can not downgrade due to GPT.BIN and MOTOBOOT.IMG.
The only time it was safe was downgrading from 4.4 to 4.2.2. w/Camera Update OTA as part of the SlapMyMoto/MotoWpNoMo process for those with LOCKED bootloaders,
Based on the file name you are using (from your 2nd post), you are trying to flash the ORIGINAL SHIPPING 4.2.2 ROM which does cause a brick.
Now, based your two posts, It appears your phone is an XT1058 from Rogers Canada. Is that correct? or are you just trying to flash the Rogers Canada rom?
(If your phone really is an XT1058 from Rogers)... At this point, there are two options.
1. If you can get the phone to boot into fastboot mode, Download the 4.4.4 SBF for Rogers Canada (RCI) from -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 . (NOTE: If your phone is NOT a Rogers XT1058, then download the newst SBF for your phone's carrier and model!) and use the Requirements and Option 5 from -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and hope it works. If it works, it will flash you to stock 4.4.4. At that point, you can try to re-unlock the bootloader. And never think about flashing any other older ROM again!
2. If you can't get into Fastboot mode to flash, Go to -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 for help.
Thanks KidJoe
You save me !!!!! thanks so much for your help !!!!! :good::good::good::good:
Recovery not working
i try to enter into recovery but the phone turn on, the recovery not working|
wolf1985 said:
i try to enter into recovery but the phone turn on, the recovery not working|
Click to expand...
Click to collapse
The stock recovery work fine sorry, thank you for your help
VZN XT1254 Droid Turbo All stock. bootloader locked. softwarefficial, bricked help!
I rooted with KingRoot yesterday, and then ran SunShine installer, and somewhere between that its soft bricked my device. I was using a kinda faulty usb cable, to go back and forth between command prompts for adb and fastboot, but this issue didnt arise till my first Kingroot experience, which I must add is pretty lame, but then sunshine forced closed during the process and forced a device reboot. It rebooted in bootloader , fastboot is still working, device is charging, but the bootloader log reads : Failed to validate boot image. Cant access recovery or nothing, just fastboot, my baseband is MDM9625_104651.11.05.16.02R Quark_Custom, VZN XT1254, my locked bootloader status is keeping me from getting any of my files flashed successfully, Ive got copies of RSDlite 6.2.4 , my drivers installed, adb fastboot, and my stock image of VZN_/SU4TL-44, no success on flashing, plz help.
Just wondering, why did you use kingroot? It is not needed anymore.
https://youtu.be/6avEPGWB8E0
Sent from my XT1254 using Tapatalk
Sunshine shouldn't have bricked your device. But I believe in the moto maxx forum you'll find images to flash in fastboot.
http://forum.xda-developers.com/showthread.php?p=59659400
I'm not necessarily saying sunshine did brick my device I'm saying sunshine and kingroot together did cause some issue due to sunshine just wanting to constantly force close, so I rebooted the device, and it's got stuck in a soft brick boot loader loop, recovery including all other options but fastboot will respond, I am new with motorolla devices, especially on the 5.1 os, I picked up this phone as a trial and error device to do whatever with, I did follow rootjunkies video on using kingroot, I know now the method was outdated, lesson learned, but I can't get no fastboot flash commands to stick due to the original secured state of the bootloader, I've always steered away from motorolla and vzn due to the locking methods of the boatloader , phone was free hope I can get out of this state now lol
Thanks for the two post , I am attempting now I will update with results
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
lwilliz87 said:
Keep getting failed remote failure, I'm on a stock locked Boatloader, should I be trying rsdlite
Click to expand...
Click to collapse
RSDlite does nothing more than automate fastboot. If fastboot won't work, RSDlite won't work. What commands, exactly, are you trying to use to flash the images that you're trying to flash? If you're using that link to the Moto Maxx forum that mrkhigh provided, that won't help you, since the SU4TL-44 Droid Turbo firmware is not listed there. This is the one that you want: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. I'm pretty sure that "remote failure" is what fastboot says when you attempt to flash an image that is not meant for the device, or an image that is an older version of the image that is on there (which is the case if you're trying to flash any of the firmwares listed on the Moto Maxx page).
Didn't note it stopped at .38
Remote failure
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
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...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
lwilliz87 said:
You are correct. yes I get remote failure, but I have already went thru rootjunk several times and downloaded that exxact VRZ_XT1254_SU4TL-44_44_CFC.xml.zip , I have the adb and fastboot both installed, and needed files, I have also mfastboot in there too. Ive ran the BAT.exe thru command prompt, Ive tried this with the same file mentioned above from rootjunkysdl, and from moto-firmware : Following out tonight
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>VRZ_XT1254
_SU4TL-44_44_CFC.bat
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>SET fastbo
ot=fastboot.exe
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.009s]
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...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.155s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash motoboot bootloader.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2163 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 0.384s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash radio radio.img
target reported max download size of 536870912 bytes
sending 'radio' (86165 KB)...
OKAY [ 5.709s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.736s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2860 KB)...
OKAY [ 0.170s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.201s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.097s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.386s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16400 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.292s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (235017 KB)...
OKAY [ 13.362s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 17.003s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (250150 KB)...
OKAY [ 14.529s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.634s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (261098 KB)...
OKAY [ 9.887s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.120s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk4
target reported max download size of 536870912 bytes
sending 'system' (246901 KB)...
OKAY [ 9.053s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.100s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk5
target reported max download size of 536870912 bytes
sending 'system' (247563 KB)...
OKAY [ 9.430s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.515s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk6
target reported max download size of 536870912 bytes
sending 'system' (246206 KB)...
OKAY [ 9.523s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.608s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk7
target reported max download size of 536870912 bytes
sending 'system' (258024 KB)...
OKAY [ 9.215s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.405s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk8
target reported max download size of 536870912 bytes
sending 'system' (260155 KB)...
OKAY [ 9.700s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.923s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk9
target reported max download size of 536870912 bytes
sending 'system' (254924 KB)...
OKAY [ 9.498s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 23.768s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe flash system system.img_sparsechunk10
target reported max download size of 536870912 bytes
sending 'system' (174885 KB)...
OKAY [ 7.398s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 9.558s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase ddr
erasing 'ddr'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.010s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>fastboot.e
xe oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.005s
C:\Users\-_-\Downloads\VRZ_XT1254_SU4TL-44_44_CFC.xml\Firmware XT1254>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
TheSt33v said:
Hmmmm. Interesting. Did you try entering the commands manually in a command prompt without using the batch file?
Click to expand...
Click to collapse
Yes I have tried entering the commands indiviually. only one that will come back with ok clear status most of the time without any failure is the fastboot flash boot boot.img , thats when i do it by itself, and today I downloaded the verizon wireless software assistant, it detected the phone needed repair, downloaded it downloads the correct software as it says, I have been selecting keep data, and then after numerous failed attempts and redownloads I been selecting erase devices data, and when it goes to flash it fails before even the first go, Im pretty sure my drivers are right, I dont know what to do . I hoping that maybe if this keeps on and with fingers crossed the new 6.0 update will hit my device soon and the software assistant will be able to update it for me with no problems, or I can flash it with no problems, right now I am uninstalling everything Motorola and gonna retry the VZW upgrade/repair again.
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
Jtag will be the only solution
SaschaElble you just need to lay back on this stuff, you are going to do far more harm than good.
A) no sunshine didnt cause this, please backup this statement, its pretty obvious what is going on here
B) you need to stop advising people on these things, especially trying to get people to flash things that will hardbrick phones
C) example of B, motorola hasnt enabled jtag in ages
D) jtag doesnt fix emmc problems, jtag doesnt fix a hardware issue.
SunShine "doesnt touch any of that" either, again you are going off on things you don't understand. We even published a disclosure of what sunshine does touch, wish you had read it prior to throwing blame at us : http://theroot.ninja/disclosures/TRUSTNONE_1.0-11282015.pdf
This looks like some emmc issue imo.
SaschaElble said:
Sunshine did cause this unusual soft-hard brick. (Well, more like a faulty usb cable) I'll explain:
Fastboot is unable to run ANY commands that read or write to the device, EXCEPT for getvar all.
No flashing, erasing, get_unlock_data, ect.
Can't flash gpt,boot, bootloader ect.
Since I was unable to intentionally hardbrick his phone by flashing the turbo prototype engineering edition boot loader, he can't get into a hardbrick where he could use qh_loader.
To sum it up: Fastboot is broken, can't force a true hardbrick, kingroot doesn't touch any of this. Sunshine does.
This is a TRUE hardbrick, as we can unbrick hardbricks, but this is fubar'd royally.
...It's almost as if a totally different, and incompatible bootloader was flashed, but the conversion process was not completed by sunshines app. The entire partition table is messed up, and trying to flash gpt.bin to correct this fails as well. So a deeper rooted problem is present.
Jtag will be the only solution
Click to expand...
Click to collapse
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
SaschaElble said:
A) Kingroot by itself sure didn't do it. User observed your app foreclosing and then device restarting, while this may be the intended sequence of events, the end result was a bricked turbo
B) Hardbricking via eng edition bootloader its a tested and unbrickable situtation.
C) Jtaging in this case had nothing to to with my intentional hardbrick, as hardbricks can be unbricked without jtag
D) How does this appear to be a emmc hardware problem? Device would boot into qh_loader mode if this was the case, as aboot would be unreachable.
E) Another user reported sending device out for jtag repair services, without further research I would assume such exist. In the most extreme cases, removing the emmc chip and flashing can be done.
SunShine "doesnt touch any of that" - This is assuming defined behavior, we are talking about undefined behavior = You can't prove it did, or didn't. But you can logically deduce that only sunshine modify's the way the turbo boots at the bootloader level. It may VERY well be that your app worked 100% as intended, but user's device had unexpected consequences. Still faulting sunshine.
This looks like some emmc issue imo. Again, a faulty emmc would cause the SoC to boot in to QH_Loader (unbrick mode) - This is not a faulty emmc. Even IF it was, this was directly after your app force closed and the device restarted.
Click to expand...
Click to collapse
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
beaups said:
1.) Sunshine did not do this, period. Nothing in the sunshine apps gets anywhere near anything like this
2.) eMMC very frequently fail such that they can be read but not written. It's not uncommon at all
3.) JTAG is disabled on Motorola devices. Don't make assumptions.
By your logic, if I fill up my gas tank tomorrow and get a flat tire right afterwards, the bad gas caused it? Nice logic there.
--beaups
Click to expand...
Click to collapse
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
It is pointless indeed. We have the code, we know exactly what it is capable of, and its not capable of what's happened here. Argue all you want, you just continue to reinforce you have no clue how these devices work.
--beaups
Sent from my XT1254 using Tapatalk
Fine, I'm done.
SaschaElble said:
1.) Effects the way the bootloader makes decisions
2.)It failed right after sunshine, if still readable device should at least boot to recovery mode.
3.) This is really a pointless argument. Nit pick all you want.
By that logic turbo's come with tires and gas tanks. Where can I get mine?
Click to expand...
Click to collapse
1) this isnt a bootloader issue, its an emmc issue, pretty dang obvious, i can see it from 30k feet up
2) I found his device ID, he never purchased sunshine (ask him), SunShine never actually ran on the device, because he never purchased it, SunShine never touched his device, just the purchasing framework (Which tests for root, basic compatibility etc) ran, and it doesnt touch anything.
Sanity tests can't cause harm?
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Either way the timing still sucks
Hi Guys,
I have Moto G2 (XT1068) 2014 edition. I was using stock rom (5.0.2)
How the Problem started:
Dropped the phone.
What is the Issue:
Cannot charged - When connecting to wall charger, the bootlodaer icon shows and again device restarts. But i can enter Fastboot Menu. The phone will charge for some time then again restarts and enters boot loop (If battery is completely drained then it should start and then display the charging animation rt?).
When connecting to PC via USB same thing happens. When i enter boot menu, it shows Charging for few minutes then it says Battery - OK. IT does not enter boot loop in this case. But when i select 'Recovery' or 'Normal Powerup' or 'Factory Reset', it goes to 'Powered by Android' screen and then again goes into boot loop.
What I have tried:
1. Tried some fastboot commands 'erase usedata' & 'erase cache'.
2. I tired flashing Stock firmware. Used this guide - http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
3. I unlocked bootloader. Flashed TWRP. But issue is not resolved. I cant enter Recovery coz phone will boot loop.
Need help!
@lost101
Kindly help. I have created new thread as u said.
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Here u go:
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Restore to Original Stock Motorola Firmware for Motorola
Moto G 2014 Titan(XT1068) Provided with Unlock Bootloader
Please Do press Thanks Button If u really liked My Work @bhu999
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
OKAY [ 0.325s]
finished. total time: 0.358s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.102s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.048s]
finished. total time: 1.153s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.057s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.273s]
finished. total time: 0.640s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.280s]
finished. total time: 0.695s
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.419s]
writing 'system'...
OKAY [ 6.401s]
finished. total time: 14.900s
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.271s]
writing 'system'...
OKAY [ 6.629s]
finished. total time: 15.310s
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.310s]
writing 'system'...
OKAY [ 6.372s]
finished. total time: 14.685s
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.774s]
writing 'system'...
OKAY [ 5.227s]
finished. total time: 13.005s
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.288s]
writing 'system'...
OKAY [ 0.870s]
finished. total time: 2.168s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.958s]
writing 'modem'...
OKAY [ 1.200s]
finished. total time: 3.597s
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.033s
erasing 'modemst2'...
OKAY [ 0.026s]
finished. total time: 0.031s
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.080s]
writing 'fsg'...
OKAY [ 0.090s]
finished. total time: 0.190s
erasing 'cache'...
OKAY [ 0.128s]
finished. total time: 0.132s
erasing 'userdata'...
OKAY [ 1.158s]
finished. total time: 1.158s
rebooting...
finished. total time: 0.003s
Press any key to Exit
Press any key to continue . . .
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Flashed 5.0.2 stock manually:
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
F:\Minimal ADB and Fastboot>fastboot devices
ZX1D63NZQP fastboot
F:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.316s]
finished. total time: 0.362s
F:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.029s]
finished. total time: 1.140s
F:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.048s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.419s]
writing 'boot'...
OKAY [ 0.272s]
finished. total time: 0.707s
F:\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.300s]
finished. total time: 0.672s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.176s]
writing 'system'...
OKAY [ 6.326s]
finished. total time: 14.534s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.148s]
writing 'system'...
OKAY [ 6.660s]
finished. total time: 14.808s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.177s]
writing 'system'...
OKAY [ 6.348s]
finished. total time: 14.525s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.662s]
writing 'system'...
OKAY [ 5.256s]
finished. total time: 12.918s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.289s]
writing 'system'...
OKAY [ 0.863s]
finished. total time: 2.151s
F:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.645s]
writing 'modem'...
OKAY [ 1.101s]
finished. total time: 2.751s
F:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.017s
F:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.079s]
finished. total time: 0.174s
F:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.142s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.131s]
finished. total time: 1.131s
F:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.000s
F:\Minimal ADB and Fastboot>
'''''''''''''''''''''''''''''''''''''''''''''''''''''
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Let me try these
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Still bootloop
now m worried
I used easy installer. Too tired for manual. Its 1 am here
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Easy Installer - Marshmallow 6.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 5
FACTORY RESET - Wiping NOW ......
erasing 'userdata'...
OKAY [ 1.151s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.125s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 1.327s
Done!.........
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 2
LOCKED BOOTLOADER STOCK ROM - FLASHING PARTITIONS.
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.528s]
finished. total time: 0.530s
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
OKAY [ 0.336s]
finished. total time: 0.384s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.120s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.052s]
finished. total time: 1.176s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.088s]
writing 'logo'...
OKAY [ 0.066s]
finished. total time: 0.158s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.385s]
writing 'boot'...
OKAY [ 0.262s]
finished. total time: 0.652s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.684s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257431 KB)...
OKAY [ 8.188s]
writing 'system'...
OKAY [ 6.459s]
finished. total time: 14.652s
target max-sparse-size: 256MB
sending 'system' (255474 KB)...
OKAY [ 8.128s]
writing 'system'...
OKAY [ 7.409s]
finished. total time: 15.542s
target max-sparse-size: 256MB
sending 'system' (257554 KB)...
OKAY [ 8.206s]
writing 'system'...
OKAY [ 5.798s]
finished. total time: 14.009s
target max-sparse-size: 256MB
sending 'system' (250957 KB)...
OKAY [ 8.068s]
writing 'system'...
OKAY [ 5.577s]
finished. total time: 13.650s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.635s]
writing 'modem'...
OKAY [ 1.150s]
finished. total time: 2.790s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.063s
target max-sparse-size: 256MB
sending 'fsg' (1012 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 0.093s]
finished. total time: 0.217s
RELOCKING BOOT LOADER.....(if possible)
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.521s]
finished. total time: 0.523s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.186s]
finished. total time: 0.189s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option :
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
lost101 said:
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
Click to expand...
Click to collapse
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Fir3lordZuk0 said:
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Click to expand...
Click to collapse
What happens if you use the 'mfastboot boot twrp.img' command?
lost101 said:
What happens if you use the 'mfastboot boot twrp.img' command?
Click to expand...
Click to collapse
''''''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.285s]
booting...
OKAY [ 0.221s]
finished. total time: 0.507s
''''''''''''''''''''''''''''''''''''''''''''''''''''''
After this on phone, i see 'powered by android' screen with motorola logo...after that it shows bootloader warning and then again it restarts and goes to boot loop
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
lost101 said:
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
Click to expand...
Click to collapse
TWRP - 3.0
Same behavior with Philz Touch
''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.268s]
booting...
OKAY [ 0.237s]
finished. total time: 0.504s
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot CWM_Touch_Titan_v2.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
OKAY [ 0.237s]
finished. total time: 0.586s
'''''''''''''''''''''''''''''''''''''''''''''''
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
lost101 said:
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
Click to expand...
Click to collapse
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Fir3lordZuk0 said:
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Click to expand...
Click to collapse
The phone appears to have been physically damaged (internally) by the fall. I don't know of any solution other than maybe replace mainboard - cheap off ebay if pulled from a screen-damaged unit.
Thanks a lot for your time and help!
I appreciate it
Okay. I have this titan device of my friend which always boots to fastboot mode with the below message
Fastboot Reason UTAG "flashfail" configured as fastboot
When I connect USB and key in fastboot devices command it does show up.
Code:
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>fastboot devices
ZX1D647QP3 fastboot
I somehow managed to get oem_unlock_data and I managed to unlock the bootloader.
I tried to flash the Stock Rom (Marshmallow) and the problem arises here with all commands failing.
Not even a single command gets succeeded.
Including a few error messages.
Code:
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.002s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.336s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 5.080s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 10.991s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.028s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 20.018s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.338s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.391s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 5.347s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.407s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257467 KB)...
OKAY [ 13.111s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.203s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (255482 KB)...
OKAY [ 13.055s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.215s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257534 KB)...
OKAY [ 13.113s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.192s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (244425 KB)...
OKAY [ 12.701s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 17.780s
C:\Martin's Storage Space\Softwares\Moto G2 Stable OS\Stock>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 6.599s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 11.687s
Please advise as to what can be done.
Looking forward for your support. Thanks in advance.
PS: I am not sure if USB Debugging is turned on in the device because this phone wasn't tweaked much by my friend.
Can someone help please? Absolutely no luck.
Probably wrong ADB-version. Go back to firmware following
this manual
If it's a non functioning ADB/fastboot version I recommend to use
Mini_ADB_&_Fastboot_v1.1.5.:
https://androidfilehost.com/?fid=4349826312261610127
or if this one produces errors too
minimal_adb_fastboot_v1.4.3_setup.exe:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
Install it in the root of C: not in programs or other folders, windows may deny needed rights than.
All recommended drivers installed?
Correct firmware?
Sent from my Moto G5 Plus using XDA Labs