hi
and installed the firmware and the phone has been in bootloop
http://www.4shared.com/zip/UtS8KSq5ce/RETUGLB_XT1063_502_LXB2246-28_.html
commands used
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
help:crying:
Related
So I tried to restore my G using this method and failed for some reason. I am having issues trying to put my device in recovery mode now. I cna boot into fastboot, but when I try to select recovery I get a "boot up failed" message. I have tried to flast but TWRP and stock 4.4.4 recovery onto the device but I still get the same message every time. I've even tried to repeat the same process the above mentioned forum suggest and I still have no luck. Any help?
That tutorial is for the original Moto G, not the 2nd gen. Do you have an XT106x device ?
Bl00dyMurd3r said:
That tutorial is for the original Moto G, not the 2nd gen. Do you have an XT106x device ?
Click to expand...
Click to collapse
It is a second gen. XT1064.
I would try reflashing everything on the phone
Here is the bone stock 4.4.4 firmware for the XT1064: http://d-h.st/try
Download that, and this: https://docs.google.com/file/d/0B4PT9WP-u_z9NXRBWF9EV2lGcWs/edit
Extract them both into the same folder, and make a new text document.
Insert this into the document, and save it as flash.bat in the same folder as your other files
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
Plug in your phone and run the batch file at the bootloader, and your recovery / OS should work fine again
have anyone have the stock firmware for the xt1072 me and can say how to flash it only the commands that i need to flash
Fix it
commands:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Firmware:
https://mega.nz/#F!JsRmRJgb!KOYbWf-p8bPlxNZ2svbN7g
Hello everyone, firstly I want say sorry, because my english it's a ****...
My phone XT1097, stayed with "boot up failed", I already tried the many diverses formules to can resolve this problem, but always keep this errror, on the RSD the device don't is recognized, and with the ADB staying with the erro with da title of the post, that is "<bootloader> has-slot:boot: not found", I need help, I don't know what is I have to make.
Sorry again for my english, and I already say thank for everyone.
Obsv: my phone turn on in fastboot and my recovery it's normal,
img with the error:
-RSD: goo .gl/P0QynQ
-ADB: goo .gl/K2YHgK
-PHONE: goo .gl/yZW2r8
Hey, did you try to flash the files using mfastboot instead ? A bit longer but better than those tools....
You can find mfastboot here.
Just download it, extract it in a subfolder, copy your firmware files (all the files from the firmware archive), go to the extracted folder, paste them there, then I give you the following instructions (according to Motorola's official website):
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.x
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase customize [leave that out if you have special customization from motomaker]
mfastboot erase clogo [leave that out if you have special customization from motomaker]
You also have the option to erase all the data on your device with:
mfastboot erase userdata
mfastboot erase cache
And finally:
mfastboot reboot
Everything should be okay, tell me if this worked.
HI, i need your help!
I bricked my phone, i could only see a black screen.
I have managed to get around that by flashing the bootloader back.
Now my phone only boots into bootloader no matter what.
The reason is, when i try to flash a stock rom i get the message (INFOImage signed with key bad key) on almost every .img
I've tried downloading the regions that seemed to be mine but they don't work. RETAIL, RETEU, TELEU, VIPEU and so on...
My phone was brought from T-Mobile. it is the xt-1922-3 variant.
AND YES, the bootloader is unlocked. (i've also managed to flash some sort of stock recovery because twrp wouldn't work, because i can't tap the screen)
I have the same problem. How do I solve it?
@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Ragarianok said:
@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
i need help too. it says image signed with bad key when flashing bootloader.img. i have a retus moto g6. any help is appreciated
Ragarianok said:
@Alyctro
DUDE, YOU HAVE A MOTO G6 PLAY.
Try the RETAIL firmware listed here:
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
If you're trying to relock the bootloader, which should fix the "bad key" message, follow this:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
Otherwise, this should work, but you'll still get "bad key" message when flashing boot.img and recovery.img (this is due to the bootloader being unlocked):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
@Ragarianok
Perfect, it works, moto g 6 play XT1922-5_ALJETER, thanks.
Well, I'll tell you ... Well, I bought a Moto G5S Plus for that of late 2018, everything worked fine within normal, sometimes when I restarted it, there were some System errors that did not respond to which I did not pay much attention, because then it worked normal ... until the beginning of this year, the memory was a little full, so I inserted a Micro SD to free up some space and move many images that I had there. I turned it off to insert the SD and when I went to turn it on, it did not pass the Motorola Logo. I thought it was on drums or something, I reset it, did various things to it and to this day, it continues like this ...
In the first instance, not knowing much or nothing about the topic, try this:
Unsuccessfully, then I also tried clearing the cache via Fastboot, but also had no solution ...
Then there was the Hard Reset through Fastboot or reinstalling the Rom through AVOID, because I have many documents, especially Notepads with important information, as well as contacts and multimedia material that I need to recover ...
So I decided to keep looking and luckily I found an interesting post in this forum:
https://www.htcmania.com/showthread....1543&styleid=6
This gave me hope again, besides that I am lucky to have a Moto G2, so I tried the steps described in that post ... And I realized that it obviously works, it does not erase the data from the computer ... Then I proceeded to do it with the Moto G5S Plus and some commands did not work, I did a little research and realized that the files of each ROM were totally different, so I found some specific commands for the Moto G5S Plus:
(Downloading this rom: SANDERS_RETAIL_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
I also found another version of commands that differs a bit
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
In that case, following the instructions in the aforementioned post,
(https://www.htcmania.com/showthread....1543&styleid=6), I decided to take into account the recommendations and AVOID commands such as:
fastboot flash partition gpt.bin
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Everything that could erase data, but I also had doubts about these, I don't know what action they perform:
fastboot flash partition gpt.bin
fastboot oem fb_mode_set
fastboot erase DDR
fastboot oem fb_mode_clear
Finally, I decided to just use these commands, but the phone remained the same in the Logo Bootloop:
fastboot devices
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
It is here, when I ****ing turn to experts like you, since I don't know what else to do and I still have many doubts ... Do you think that data has been deleted with these procedures or is everything still the same? Is there a way to install the TWRP to save data?
Many videos and forums that I have read say that it can also be BATTERY FAILURE, but I very much doubt that it is, in addition to removing the battery from this model, yes I'm not bad I think you have to remove the display and well, many technicians do not know Buy for it ... Also normal charge when I charge it to full and the battery is consumed in the normal percentage, so that's why I don't think ... But I do need that if they are so kind to give me a hand, because I no longer know What else to do, I really sometimes make my head a madhouse with this topic ...
Friends I thank you and I am very aware. Really thank you very much
Help me!! PLEASE!!