Related
I used multi_tool to flash stock ROM rather than using fast-boot and I got my Huawei nova's partition corrupted. Now I cannot flash system.img and cust.img via fast-boot. I even cannot fix gpt partition with fast-boot flash partition gpt.img
Help me, please!
Thanks in advance
Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.
where do you get the stock firmware?
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
We're you able to revert to a locked bootloader after this, I am looking forward to do so
We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier
downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions
Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks
astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition
I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.
distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?
astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
It does not work
al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help
flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry
Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.
Hi,
I try to flash android rom before a crash , i have the bootloader lock , when I try to flash the bootloader say "invalid partiton name ' for all partition when i try to flash , I already try to flash gpt.bin to set partition but the bootloader say "unknow partition 'gpt.bin' and error: cannot be determine image filename for 'gpt.bin' .
Help me please,
Mathsyx
Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the Moto X Style that died after updating via ota (the bootloader is unlocked and had downgrade) result = does not enter fastboot mode, recovery, nor loads, when it connects on the computer by usb it presents qualcomm hs-usb qdloader 9008, for those with the same problem, I was able to recover my device through a file shared by a colleague of google plus who made a dump of xt1572 that works 100% (loader.img)
File Link to Recovery
drive.google.com/file/d/0Bz770r9yW2iNU29JZkNPdkZmeG8/view
ROM link with bootloader version A0.52
androidfilehost.com/?fid=961840155545596639
MOTO X STYLE XT1572 UNBRICK GUIDE
Initial Reminders: This method has been tested on more than one XT1572 model successfully, but we can not guarantee the success of this guide in your case. NO ONE HERE IS RESPONSIBLE FOR WHAT YOU DO WITH YOUR APPLIANCE. If you have no skill / experience or do not feel confident following such guides, DO NOT GO!
Several members of this community together have come up with a solution to the "Hardbrick" problem of Style, a condition where it gives no sign of life and recognizes on the computer as "HS-USB DLoader 9008".
THINGS YOU WILL NEED BEFORE YOU BEGIN:
1 - A computer with Motorola drivers installed, fastboot files and the DiskImageRev2 program. Your Windows user needs to have administrator access.
2 - A USB cable of good quality and 100% functional.
3 - A USB microSD memory card reader.
4 - A microSD memory card. Recommendation: 16GB, class 10 and ORIGINAL!
5 - The complete ROM file.
Details of this ROM: Dual SIM. RETAIL. Region "LA" - the two simcards operate 100% in Brazil. Android 7.0. Security Patch August 1, 2017. Version Number NPHS25.200-15-3.
6 - The file "Loader.img".
7 - The battery of the unit must be charged so as to allow the unit to switch on in fastboot mode.
Each of the above may require additional steps. For this guide not to get too large these details were not included.
STEP BY STEP
Step 1 - Burn the "Loader.img" file to the microSD memory card using the DiskImageRev2 program.
Step 2 - Insert the memory card into the device and turn it on in fastboot mode. There are three possible options: (1) hold down the Power and Volume buttons for at least 10 seconds. (2) Hold the Volume minus button and connect the unit to the computer. (3) Connect the device to the computer, after it is recognized to hold the Power button until it "reboots" it automatically enters fastboot mode.
Step 3 - With the device in fastboot mode, write the ROM normally complete using the Windows command prompt.
.\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 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 flash bluetooth BTFM.bin
.\fastboot erase cache
.\fastboot erase userdata
.\fastboot erase customize
.\fastboot erase clogo
.\fastboot oem fb_mode_clear
.\fastboot reboot
This solution was the result of a joint effort of several people from the "Moto X Style BRASIL - Official" community on Google+
restores the dump into sd card, is this right ? or can you provide some instruction ?
This is for the XT1572 (not sure about other models), and yeah, you use DiskImageRev2 to write the loader.img to a sd card (32 gb card needed since it writes a 32gb partition)
After that you connect it to the computer, and press power button till it resets, it will start in fastboot mode.... then, just flash the rom you want (got mine back some hours ago with the same procedure)
@Danielo007
Good news.
Can you explain what/how did you unbrick MXP/S?
What to do with this file and after?
can confirm it works
Thank you very much
1. use Diskimage to write .img file on a 32gb card
2. put the card inside the slot
3. boot like you would boot to bootlooder (volume down + power) after some screen flash, it start in bootloader mode.
4. use fastboot to flash rom
Danielo007 said:
Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the x-style bike that died after the update via ota (the bootloader is unlocked and had downgrade) result did not connect in fastboot mode, recovery, did not load and when connecting on the computer it featured qualcomm usb qdloader 9008, for those who are with the same problem I was able to recover my device from a file shared by a colleague of google plus that made a dump from its xt1572 that works 100% o (loader.img)
File Link to Recovery
drive.google.com/drive/folders/0B9SXWV7BgmquVWZJTUp1NHJPb2M
Click to expand...
Click to collapse
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
update...
device boot only with flash card inserted
fdc77 said:
update...
device boot only with flash card inserted
Click to expand...
Click to collapse
Not really, you're using an older version of your rom, you need the same GPT.BIN file to be writen, or else your not "fixing" the bootloader, it will give " preflash validation failed" in it, with the latest rom it worked for me, i'm not using the "emulation sd card" and the phone boots as the first time
---------- Post added at 14:32 ---------- Previous post was at 14:30 ----------
See in here the file "Guia para UNBRICK em inglês.pdf" gives you the instruction needed
you are right......but i don't have stock nougat rom for xt1572 EU, anyway i was able to recover my phone, flashing a nougat flashfire backup that i had made when i install it first time.
Guys, I love you. I DO, REALLY!
Finally my bricked XT1572 is back from the dead, at least it booted into Fastboot mode. However, I don't have the full Nougat ROM for the XT1572-LATAM_DS, only the Marshmallow 6.0 ROM with December security patch. Thus, since the Loader.img is for a Nougat ROM, I can't flash the gpt.bin and bootloader.img from the MM ROM ("Preflash validation failed").
Can anyone share the full Nougat ROM (if it's available), or at least the gpt.bin and bootloader.img (then I can flash a custom ROM, for instance)?
THANKS!!!
EDIT: found it on the Google+ community, downloading now.
EDIT 2: solved!! The ROM worked with the instructions! THANKS TO ALL INVOLVED!!
Amazing... Moto staff hided this secret from people for years ))
Tried this on my xt1575 and it worked initially. Failed to flash gpt.bin and bootloader.img from the 24.49-18-8 full factory MM image. It did initially boot to the stitch screen then powered off and won't power on again. Tried letting it sit and reinstalled the sd card but it won't power on at all now. When I initially put the SD card in the white led lit up and I was able to get to recovery mode. Now nothing happens. So I wouldn't advise XT1575 users to try this loader.img
I hope this interchangeable with X1575. Or some one can create a loader.img for it. BTW you would have to fastboot the last image that was installed?
jason2678 said:
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
Click to expand...
Click to collapse
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Hi:
But finally when flash by fastboot, the destination is the internal memory or the sd card?
Regards
npatel555 said:
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Click to expand...
Click to collapse
On other Snapdragon phones I've seen this work with in the past it is kind of a fickle thing. I looked back over some old threads, and you needed an image specific to the firmware you were running at the time you bricked. I think my phone is too much of a Frankenphone right now to be a good candidate for pulling an image from. I'm pretty sure I'm on the bootloader from the MM Sept 2016 security update and the modem from the MM May 2016 security update. Currently not on a stock rom either. I could make you an image, but based on BuildUpNow's post above I think it would either not work or maybe leave you worse off than you are now.
I could get my phone back to fully Sept 2016 stock for the purpose of making an image, but that's it. The bootloader won't downgrade. The XT1575 packages haven't leaked for Dec 2016 or Nougat, and I'm not touching those OTA's as poorly as they seem to be going. I've never seen so many hard bricks reported on this device as I have in the last month or two.
Our lack of full firmware packages for XT1575 will really hinder this unless you happen to have been on older firmware. Unless you can get your hands on a firmware package same or newer than what you were running, you're going to get preflash validation failure on the bootloader and partition table, and based on the posts above it sounds like you'll still be stuck.
can you please provide loader.img for moto x play???
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
dzidexx said:
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Click to expand...
Click to collapse
I tried that and it didn't work.
I actually got my phone to boot up now though. But the phone will only boot with the sd card it in. I tried wiping it and using it for storage and the phone refuses to boot. The img has to be written to it. I also can't enter recovery mode( pwr + vol dn buttons at all). So now I'm stuck with mm6.0 and I cannot enter recovery at all. Guess I'll have to try and load the sd card on linux and see what files are on the card and see if there's anything to be modified.
Oh my goodness, thank you so much for this quick and easy fix. My phone is back from the dead and it even worked on my Moto X PURE (XT1575). You made my day, honestly, I haven't been this happy for a long time