Related
hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?
Reflash factory imagine
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.
12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing 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) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing 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) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.
Hello,
I've been experiencing lots of sudden app closes on my Moto G 2 so I decided to get the lollipop update from here: http://forum.xda-developers.com/mot...wrp-backup-t2964330/post57299580#post57299580
My phone was rooted with unlocked bootloader, and Furnace kernel installed.
I downloaded the zip from that file, followed the instructions and when I used TWRP to install the update from the restore menu, it stopped at 25% and went back to rebooting my phone.
Now it is bricked at the warning bootloader unlocked screen. I can still open TWRP but I don't know where to go from here.
Please help me fix my phone!
If you can boot into TWRP, connect your phone with your PC and use 'adb reboot bootloader' to get into bootloader. Then restore to stock.
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
It is not necessary to relock the bootloader.
You could also retry restoring that backup, but I presume you would have already done that.
well just google
humm i wish i can help
download the factory image and flash it with fastboot.
ViKtory36 said:
Hello,
I've been experiencing lots of sudden app closes on my Moto G 2 so I decided to get the lollipop update from here: http://forum.xda-developers.com/mot...wrp-backup-t2964330/post57299580#post57299580
My phone was rooted with unlocked bootloader, and Furnace kernel installed.
I downloaded the zip from that file, followed the instructions and when I used TWRP to install the update from the restore menu, it stopped at 25% and went back to rebooting my phone.
Now it is bricked at the warning bootloader unlocked screen. I can still open TWRP but I don't know where to go from here.
Please help me fix my phone!
Click to expand...
Click to collapse
Flash the stock factory image of the firmware available for your model. And secondly you have flashed the correct file on the wrong base firmware. Ad the process you did is wrong. To make the twrp ota work it is recommended that you flash xt1069 firmware and above that flash the ota update. Secondly use twrp 2.7 as 2.8 us having restoring issues.
Hello, thanks for the replies! I've flashed stock rom via bootloader and then flashed lollipop. It works perfectly now.
Thank you again for the replies
I'll Try It
I'll try it on my phone because I have the same problem as you.
Same problem
Hey guys! I have the same problem, but when i enter the comands "adb reboot bootloader", it says device not found.
i've all the motorla drivers installed and it's appearing USB connected on the fastboot screen.
Any help?
joaogabrielmatheus said:
Hey guys! I have the same problem, but when i enter the comands "adb reboot bootloader", it says device not found.
i've all the motorla drivers installed and it's appearing USB connected on the fastboot screen.
Any help?
Click to expand...
Click to collapse
if xt1068 just use any one of easy installers in my signature (pick you original or update)
download to pc - extract - read instructions INSIDE extracted folder
reefuge said:
if xt1068 just use any one of easy installers in my signature (pick you original or update)
download to pc - extract - read instructions INSIDE extracted folder[/QUOTE
Thank you for answer! It's all ok now!
Click to expand...
Click to collapse
thanks buddy :good:
HELP
I HAVE BRICK MY MOTO G 2014
I TRYED TO FLASH STOCK IMAGE BUT DON'T WORK
LOOK:
Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
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...
--------------
AFTER REBOOTING IT GO AUTOMATICALY TO BOOTLOADER AND WRITE : failed to validate boot img
Flashboot Reason: Fall-through from mot charger boot mode
I NEED HELP PLS
roulyz said:
I HAVE BRICK MY MOTO G 2014
I TRYED TO FLASH STOCK IMAGE BUT DON'T WORK
I NEED HELP PLS
Click to expand...
Click to collapse
Have you unlocked your bootloader first?
Sent from my Moto G 2014 using XDA Free mobile app
pranshubatra707 said:
Have you unlocked your bootloader first?
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
same here.. and no, i did not unlocked the bootloader any advice?
_RockNRoller said:
same here.. and no, i did not unlocked the bootloader any advice?
Click to expand...
Click to collapse
Unlock your bootloader first by following this thread http://forum.xda-developers.com/showthread.php?p=55417344
And then follow this thread to restore to stock http://forum.xda-developers.com/showthread.php?p=58564580
Sent from my Moto G 2014 using XDA Free mobile app
pranshubatra707 said:
Have you unlocked your bootloader first?
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
Yes m'y phone was unlocked, root and have twrp and work properly on a optimize Stock rom 5.0.2.
I don't know what was happened to my phone to be brick.
---------- Post added at 07:09 ---------- Previous post was at 07:06 ----------
I have followed all threat about Restoration but got partition gpt error
pranshubatra707 said:
unlock your bootloader first by following this thread http://forum.xda-developers.com/showthread.php?p=55417344
and then follow this thread to restore to stock http://forum.xda-developers.com/showthread.php?p=58564580
sent from my moto g 2014 using xda free mobile app
Click to expand...
Click to collapse
thanks!!! :d:d:d:d:d:d:d:d:d:d
roulyz said:
Yes m'y phone was unlocked, root and have twrp and work properly on a optimize Stock rom 5.0.2.
I don't know what was happened to my phone to be brick.
---------- Post added at 07:09 ---------- Previous post was at 07:06 ----------
I have followed all threat about Restoration but got partition gpt error
Click to expand...
Click to collapse
Are you able to go into your recovery?
Sent from my Moto G 2014 using XDA Free mobile app
pranshubatra707 said:
Are you able to go into your recovery?
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
No not able to go into recovery. When try it still at Motorola picture and return automatically on bootloader and say: failed to validate recovery image and boot up fail
roulyz said:
No not able to go into recovery. When try it still at Motorola picture and return automatically on bootloader and say: failed to validate recovery image and boot up fail
Click to expand...
Click to collapse
according to what you've posted in your first post.. it shows device not found! it means you dont have the proper motorola drivers installed on your pc.. please try installing proper driver from here https://www.motorola.com/getmdmwin
and then try fastboot commands
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, I got the MotoG 2014 from Amazon in the US, it came with Kitcat and in the first week it installed the OTA for Lollipop, and I was very happy with my purchase then after a couple of months it started to update something while on low battery and then the phone died, I was out of the US so turning it back to Amazon was not possible. I couldn't do anything from the recovery so I unlocked it and found some RETUSGLB Lollipop ROM and flashed it using fastboot and it came back to life. After two weeks, while I was using it, the screen went black, it would boot up and stay on the Motorola animated logo, again the recovery wouldn't work, so I decided to flash the same Llollipop again, but this time the fastboot flash command only worked with the "fastboot flash partition gpt.bin" all the others (motoboot, boot, logo, recovery, etc) gave me an error:
(bootloader) Failed to flash
FAILED (remote failure)
I've tried many of the recommendations of the forum to no avail, right now when I try to boot up the MotoG normally, it stays in a garbled screen, I guess the logo image is corrupt. Tried to flash a different Lollipop ROM, but it fails to flash also. I can boot to fastboot and use some commands like "fastboot oem partition" and "fastboot getvar all". I don't say the MotoG is hardbricked because when is in fastboot the pc recognizes it as Moto g 2014 . I cannot install any of the custom recoverys because the flash into recovery fails, but I can boot up Cyanogenmod recovery into ram. Tried to install an update from the external SD card using CM but it gives error messages about being unable to mount files and directories, which leads me to think that the Linux file system is corrupted. Cannot use ADB because fastboot nor CM recovery have the option. Using ADB sideload from CM gives error about being unable to mount files and directories too.
Since the MotoG is useless now, and I'm loosing hope about this phone, and I'm mad at Motorora for the cheap quality of their engineering that allowed the phone to fail in the first place. I'm thinking about the procedure I've seen on the forum, but used on the Moto G 2013, the one that wipes the bootloader and then blankflash the phone, risking a Hardbrick. Some people in the forum says that blankflash for 2013 wouldn't work on the 2014, others say it would, from the emmc standpoit both devices seems the same to me.
Sorry for the long story. Any suggestion to recover the MotoG is appreciated.
Thanks in advance.
Don't know exactly what wrong.
Try this : http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
It should fix your problem (There is bootloader files included in the zip file so try flashing that.)
If you think my solution isn't good enough,, wait for someone who can tell you a proper answer. Peace.
I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.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 : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s
linuxtron said:
I tried your suggestion but it failed to flash as other Roms did:
Code:
Easy Installer - Lollipop 5.x.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 : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
OKAY [ 0.319s]
finished. total time: 0.356s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.106s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 100.145s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 5.024s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 19.989s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 5.351s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 10.377s
Click to expand...
Click to collapse
Add me on Hangouts ( https://plus.google.com/108108436166506337243 ) or join #titandev at freenode.
Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,
i tried this but no luck...
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.011s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
Finished. Total time: 0.114s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (7483 KB) OKAY [ 0.792s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.959s]
Finished. Total time: 1.770s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
Sending 'modem' (76974 KB) OKAY [ 5.679s]
Writing 'modem' OKAY [ 1.922s]
Finished. Total time: 7.621s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash fsg fsg.mbn
Sending 'fsg' (2380 KB) OKAY [ 0.307s]
Writing 'fsg' OKAY [ 0.175s]
Finished. Total time: 0.500s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) OKAY [ 1.843s]
Writing 'dsp' OKAY [ 0.483s]
Finished. Total time: 2.342s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.867s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 1.116s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.0
Sending 'system' (521139 KB) OKAY [ 32.457s]
Writing 'system' (bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 32.604s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.1
Sending 'system' (504408 KB) OKAY [ 25.827s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 25.863s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.2
Sending 'system' (515109 KB) OKAY [ 23.901s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 24.041s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.3
Sending 'system' (487226 KB) OKAY [ 26.055s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 26.258s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash oem oem.img
Sending 'oem' (364938 KB) OKAY [ 19.066s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.144s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash vendor vendor.img
Sending 'vendor' (230306 KB) OKAY [ 11.192s]
Writing 'vendor' (bootloader) Security version downgrade
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 11.404s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase carrier
Erasing 'carrier' OKAY [ 0.120s]
Finished. Total time: 0.214s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.085s]
Finished. Total time: 0.098s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.189s]
Finished. Total time: 0.203s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash logo logo.bin
Sending 'logo' (1423 KB) OKAY [ 0.096s]
Writing 'logo' OKAY [ 0.150s]
Finished. Total time: 0.260s
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\Users\Ricardo\Desktop\platform-tools>fastboot reboot
richi323 said:
Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,
Click to expand...
Click to collapse
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att
madbat99 said:
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att
Click to expand...
Click to collapse
Hello and thanks for answering, yes i use this rom https://mirrors.lolinet.com/firmwar...ubsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip to restore my phoen but no luck, and retus rom the problem started but i see this rom is for moto g(6) play, i don´t know if cricket has another rom , my moto g6 forge has jeter OCP27.91-42 and I can not find that rom anywhere.
I have reviewed and donwloaded the att, retus and cricket but internally (3 roms) all are for moto g(6) play and tried with fastboot both with the same error result.
I've seen on Youtube a person who has moto G6 Forge with rom motorola/ jeter_a/jeter 8.0.0 /ocp27.91.41/43 and i think all the roms for this model should be the same but I can not find this rom.
sorry for my english i hope it is understood, any idea?
i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
richi323 said:
i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
Click to expand...
Click to collapse
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.
madbat99 said:
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.
Click to expand...
Click to collapse
You are right, I thought that it was rom of my phone. It was the update of my phone and that with the retus I could return to retail but apparently I am still learning.
maybe someone upload the rom or I'll wait for it to be published, like you say.
pd. if it possible that make a rom with other moto g6 forge without root and install with fastboot with the bad moto g6 forge
Thank you,
today with XT1922-9_JETER_A_CRICKET_8.0.0_OCPS27.91-62-7_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml my phone works again
i have a question, how can I do to unlock my moto g6 forge and use other sim?
I have tried to unlock (by code) it with 2 companies but they can not
regards
What commands do I need to put when I flash the rom? Thank you
HippiexPunk said:
What commands do I need to put when I flash the rom? Thank you
Click to expand...
Click to collapse
Use the commands in the file. You can use RSDlite with a Windows PC and it will flash it all for you. Or use RSDlite XML to batch to convert it to a .bat file for one click in fastboot. It converts it to a batch file to perform that flashes for you.
If you want to wipe data and start fresh, choose the flashfile.xml in the firmware. If you want to try to keep data, use the servicefile.xml.
If you are using official firmware, you don't need the bootloader unlocked
Find the tools here
Use RSDlite 6.2.4
works fine on windows 10.
Great tools on that page.
Get firmware from https.mirrors.lolinet.com
It looks like I'm in a similar situation. Today I went to upgrade my Cricket Moto G6 Play (XT1922-9) to Android Pie, which is available for the XT1922-9 but only for the RETUS channel. I ran the batch file in fastboot and received the "Preflash validation failed" on the boot, recovery and system partitions. Now the device only boots to the bootloader because it fails to validate the boot image. Likewise, recovery mode is inaccessible because it can't validate the recovery image. (Interestingly enough, neither of these images were actually flashed.)
Now the locked device seems completely bricked. Motorola wouldn't allow me to unlock the bootloader, and trying to flash the latest Oreo ROM for the Cricket channel also fails validation. (I had OCPS27.91-62-10 installed, but that doesn't seem to be available for download. I tried OCPS27.91-62-19.)
So am I really stuck on the bootloader with no inability to flash known-good (and properly signed) OEM firmware? How can Motorola create a system that's so fragile?