[Q] Bricked! XT1092 - X 2014 Q&A, Help & Troubleshooting

Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?

Sorry, but there is nothing you can do if it says that. You will have to send it in for repair.
Sent from my XT1095

OP said:
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did.
Click to expand...
Click to collapse
When you did that, you upgraded the bootloader and partition table to 5.1.
OP said:
So I re-flashed the 5.0 firmware that had worked previously. Same thing.
Click to expand...
Click to collapse
When you did that, it did not downgrade the bootloader and partition table - they stayed on 5.1.
OP said:
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Click to expand...
Click to collapse
When you did that, it did not downgrade the BL and PT - they stayed on 5.1.
OP said:
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
Click to expand...
Click to collapse
When you did that, the OTA tried to patch the 5.1 BL and PT as if they were the 4.4.4 BL and PT. But you were running the 5.1 BL and PT. That caused a brick.
OP said:
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Wait for someone to release the blankflash files for 5.1 (which were never leaked for 4.4.4 or 5.0 so they may never be leaked) or send it in for warranty replacement.

unfnknblvbl said:
Hi guys,
So I have an XT1092. It all started out innocently enough, when I flashed the 5.1 full firmware from the fourth post in this thread. It didn't want to work and got stuck in a... let's just call it a bootloop..., no matter what I did. So I re-flashed the 5.0 firmware that had worked previously. Same thing.
So then I figured that since it's not working, I may as well try converting it to a XT1095 as per this thread. Which worked! I was running 4.4.4 last night and all was good.
Then, it took an OTA in the early hours of this morning, which has since resulted in me losing all ability to use the phone at all.
When I hold the power button, a green light briefly flashes, which typically means that's the battery is dead (it was on charge all night, and still connected at this time). But when I hook it up to my PC, it shows up as a "QHUSB_BULK" - whatever that is.
...what can I do, guys?
Click to expand...
Click to collapse
Well, I see you used my post to downgrade to 4.4.4 and worked for you. And that's odd, because you flashed the "official" firmware of your model previously and got a bootloop. And some people are saying that downgrading your firmware from 5.1 to 4.4.4 will brick and that's not your case.... You bricked after taking the OTA and that's weird because after flashing the 5.1 of your model you upgraded your partition and your boot loader. What I am guessing here is that maybe the partitions and the boot loader of a different version like yours are incompatible with the pure edition. Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.

juliospinoza said:
Sorry for your phone, but in several post people are warning that after downgrading from a 5.1 soak you don't have to take OTA.
Click to expand...
Click to collapse
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.

JulesJam said:
These aren't Nexus devices. People can't flash whatever they want, downgrade and then take OTAs and never have to worry about bricking.
Rule of thumb - when in doubt don't flash the bootloader or partition table and never take an OTA after downgrading the bootloader.
Click to expand...
Click to collapse
That's exactly what I said, but you made it more "sophisticated" taking Nexus devices as an example. Don't see the point to repost.

juliospinoza said:
Don't see the point to repost.
Click to expand...
Click to collapse
My response was succinct, used a memorable distinction as well as a catchy rule of thumb and had adequate paragraph breaks. IOW easier to understand with a nice rhythm to it.

Try to sent to warranty centre , but in my case Motorola didn't cover me this issue.

juliospinoza said:
Maybe you can share with us what did you do after the first bootloop to downgrade to the 4.4.4, like what files did your use and what fastboot commands did you use too.
Click to expand...
Click to collapse
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.

unfnknblvbl said:
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
They should give you a warranty replacement - their OTAs should have checks in them to fail to update rather than brick a device when you are running a newer BL than the one the OTA was written to update. This is their fault. Poor coding on the part of the software devs who wrote the OTAs.
The OTAs should check the bootloader version. If it is not the version the OTA was meant to update, the OTA should simply fail to update. End of problem. One simple IF-THEN statement would prevent this.

you'd think so....

unfnknblvbl said:
Right, so here's what I did.
1) the 5.1 OTA never worked for me - would always fail during flashing for some reason. So when I found the above post, I flashed the "VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml" package with the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Then seeing as it didn't want to work, and from prior experience with TWRP being annoying, I then flashed the recovery with "mfastboot flash recovery recovery.img"
Then came the bootloops. Now, I say "bootloops" but it was more complicated than that. What would happen is the boot animation would load up, then once the screen "dimmed" it would turn off. As I didn't clear userdata the first time, it would do the whole "android is upgrading x/65749823562743 apps" message... then reboot after the last one, and start again from the start. I cleared cache and userdata and then something else happened; after the screen dimming, it would turn 'off' but apparently still load. Every now & then, the screen would flash on for just an instant. Long enough for me to see some kind of error, but not long enough to find out what.
Click to expand...
Click to collapse
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
unfnknblvbl said:
2) Giving up on this, I re-flashed the 5.0 "RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml" package with the following script:
Code:
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash boot boot.img
mfastboot flash recovery twrp-2.8.6.0-victara.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Nothing remarkable there, although I notice that I didn't flash gpt.bin. Can't think why I didn't do that right now, tbh
Anyway, exactly the same issue occurred!
Click to expand...
Click to collapse
Although you didn't flashed the gpt nothing would happened, just an error on fastboot, because you can't downgrade bootloader, the first time you flashed the new version 60.16 and the version on 5.0 is the 60.11.
The bootloop happened because the same reason, your data was there and the system wasn't able to make it "fit" to the new partition, the one you flashed with the 5.1.[/QUOTE]
unfnknblvbl said:
3) not having the patience to deal with that **** as it was nearing 3am, I flashed 4.4.4 "TMO_21.21.42.victara_tmo.tmo.en.US" with the following script:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot
...which worked! The phone started normally and all seemed good. I was pretty chuffed.
Then, without thinking I accepted the 5.0 OTA when I awoke all bleary-eyed this morning, and she died. And here we are.
Motorola support seems to think I should return it to them, so they're coming to pick it up on Friday morning. heh.
Click to expand...
Click to collapse
OK. After your final flash you flashed the system and erased data and cache, and the partitions were "clear" from all apps and other stuff, so the system was able to "fit" your data to the partitions properly, that's why your phone booted as brand new, am I right??? Seems that the partitions are compatible from 4.4.4 to 5.1 only if you erase data.
The problem is the next. The first flash set the new bootloader 60.16 and the new partitions, but when you didn't erase your data and cache the phone created a conflict with the old data and new partitions (that's the reason of the bootloop) but, when you flashed the 4.4.4 and erased your data the phone was able to boot with the new partitions. The brick was caused because of the OTA of 5.0 and that's because 5.0 uses bootloader version 60.11 and you were already on 60.16 and, the big problem with motorola OTA's is that they didn't check the mismatch between bootloaders like fastboot does, so the OTA forced the downgrade "thinking" it was an upgrade and bricked your phone. Fastboot didn't allow you to downgrade bootloader, but clearly OTA does and that's the reason of bricked devices.
Your phone should be on warranty because it wasn't your fault (not entirely) because of faulty OTA's.
Resuming. After you are on bootloader version 60.14 or 60.16 you can't take any 5.0 OTA because the mismatch between old and nw bootloaders.
Glad to see that motorola are taking to warranty. And thanks for your well explained situation so everybody could take it as reference!

juliospinoza said:
I think I know what generated the bootloop, happened to me two days ago. When you upgraded your system and data partition and didn't erased your data, the old data tried to "fit" the new partition, that's why the system the first time was trying to update your apps, but after failing entered again on bootloop. Don't know why this happens, from 4.4.4 to 5.0 you could upgrade without erasing data and nothing happened.
Click to expand...
Click to collapse
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.

unfnknblvbl said:
I forgot to mention; before attempting the downgrade to 5.0, I was able to enter recovery and do a factory reset - I wiped userdata and even the sdcard, and that's where it started just 'looping' with the odd screen flicker.
The fact that it still shows up as something in Windows Device Manager gives me hope. If it were completely out of warranty, I'd try to hack the Qualcomm rescue tools for other phones that report that same QHSUSB_BULK device into doing something with this.
Click to expand...
Click to collapse
The issue isn't the tools. The tool for reflashing is there. But you need a bin and hex file specific to your device/bootloader that only Moto has right now. Unless it is released/leaked, SOL right now unfortunately.
Sent from my Moto X 2014 Pure Edition using Tapatalk

So, the phone has been sent back to me on the same day they received it. No call, no email. nothing. Weird. I hope they fixed it - I assume they did, otherwise they would have contacted me for payment info.
I'll report back!

Success!
Replaced main PCB, rear inlay - software upgraded to current version 5.1.1 - checked current drain - QC/CIT passed to manufacturer's specifications. New IMEI.
Click to expand...
Click to collapse
...this is probably because I'm in Australia though, and the warranty-voiding disclaimer about unlocking your bootloader isn't legal here. I think. I am not a lawyer.
New bootloader: 60.16
Bam.

Same Model .. Hard Bricked xt1092
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?

warmachine68 said:
i bought it a month ago from flipkart.
when i was doing the OTA update from 4.4.4 to 5.0.2 the installation finished from the recovery and never booted.
when i try to plug in to PC its shows QHUSB_BULK
i tried blankflash but it says FAILED
all the drivers are installed something that ends with Qualcomm.. 9008
is there any way that i cn unbrick it myself?
Click to expand...
Click to collapse
Sorry it is impossible to fix yourself. You will have to send it in for repair.
Sent from my XT1095 using Tapatalk

Related

Wifi and 3g not working after manual ota

MOTO X 2014
I need help guys, it's urgent!!! So sometime ago (Dec 13 2014 ) i did this with adb to my phone to get it from android 4.4.4 to 5.0:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
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
Now i have been waiting for the ota of 5.1 since a lot of time but yesterday i got tired and installed the zip by going in recovery, i downloaded the 400MB zip from this forum link:
http://forum.xda-developers.com/moto-x-2014/general/ota-t3132045
But it didnt work it was saying something about a signature then i installed the 11MB zip which was a fix for users at 5.0 (me) found on the same forum link..
After installing that which installed successfully i installed the 400MB one and it completed, booted and now it's not detecting any sim and the wifi wont turn on, it keeps saying turning on wifi, please guys help i need my sim to work...thanks in advance, bye
First try clearing cache on the phone.
If that does not work, try wiping the phone.
If both of those fail, you probably will need to flash the full firmware.
Sent from my XT1095 using Tapatalk
AGISCI said:
First try clearing cache on the phone.
If that does not work, try wiping the phone.
If both of those fail, you probably will need to flash the full firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I will try and wipe the phone since i already tried clearing the cache...if i need to flash the full firmware, which firmware is it and do i need to root/unlock bootloader? i don't want to loose my warranty... what if i go to rma it like this? Is my warranty invalidated by what i did with adb? I mean will they find out?
Bye
splashzed said:
I will try and wipe the phone since i already tried clearing the cache...if i need to flash the full firmware, which firmware is it and do i need to root/unlock bootloader? i don't want to loose my warranty... what if i go to rma it like this? Is my warranty invalidated by what i did with adb? I mean will they find out?
Bye
Click to expand...
Click to collapse
I need to know what model and carrier you have to link the correct firmware.
As far as warranty goes. Warranty is only void if you unlock the bootloader. Except model xt1095, which does not lose warranty.
Sent from my XT1095 using Tapatalk

baseband missing

Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.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 system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.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 system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.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 system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi

My XT1072 stuck on fastboot flash screen - Help needed

Hi,
I have an XT1072 which was rooted and running CM. Since I wanted to install stock ROM, I used the Windows Tool from this forum to restore stock Android. By doing so, I was stuck with Bootloader locked screen.
Since then I am stuck on Fastboot Flash Mode screen (see pic attached).
When I try to connect my device to the same PC or any other PC and try mfastboot or fastboot or any command, it just says Waiting for device. I have all the required drivers installed in all the PCs I tested.
Using the volume buttoms, I am able to select any option, but it wont open any option (such as Normal Powerup or Recovery)
Can someone help?
Thanks
anyone?
ram11 said:
anyone?
Click to expand...
Click to collapse
Your system image is signed using incorrect key. Reflash system partition with factory image.
LuK1337 said:
Your system image is signed using incorrect key. Reflash system partition with factory image.
Click to expand...
Click to collapse
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
ram11 said:
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
Click to expand...
Click to collapse
You need to get fastboot drivers...
LuK1337 said:
You need to get fastboot drivers...
Click to expand...
Click to collapse
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
ram11 said:
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
Click to expand...
Click to collapse
Join #titandev at freenode in 20 mins, I'll try to help you out.
Sent from my Moto G 2014 LTE using Tapatalk
Any luck?
Hi Guys,
I know this is a long shot as this is an old thread but did you get anywhere with a resolution to this?
I'm in the exact same position.
Tried flashing with different factory roms and "fastboot boot" to try force it to boot a twrp image
I'm also stuck here, anyone has had any luck?
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.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
mfastboot reboot
Click to expand...
Click to collapse
This will flash the fw, factory reset and reboot the phone.
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it
dr.nic said:
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
This will flash the fw, factory reset and reboot the phone.
Click to expand...
Click to collapse
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
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 reboot
Click to expand...
Click to collapse
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
Bootloader should check if boot and system images are correct otherwise it should send user back to bootloader.
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
I gave this a shot as suggested and I'm getting this error:
C:\Users\Nick\Downloads\New folder>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259279 KB)...
OKAY [ 9.742s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.131s
Also getting the error:
version downgraded for system
Invalid PIV signed system image
Out of tricks stock flash + factory reset always worked for me sorry.
I noted my phone model/region before doing anything (xt1072-thea-reteu) got the right fw and it worked fine, maybe was another problem giving the same error "failed to validate system image" unable to boot and stuck in bootloader, weird.... :\
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
nickkk93 said:
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
Click to expand...
Click to collapse
My phone is in a drawer I'd love to be able to fix it because I really miss Android now but it there doesn't seem to be a solution... I am no giving up hope entirely though!
I tink that I have similar problem with my X1072.
After unroot with Kingroot and install AdAway and TWRP from Google Play I even noticed that I hadn't unlock bootolader.
Now I can't reboot my phone without entering in Bootloader and reseting to factory defaults. After some reboots no data has been deleted.
I have tried to reflash the entire phone but In bootloader mode the phone is not detected by the computer, so I can't flash. I'm stucked. by now
josepmanel said:
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Click to expand...
Click to collapse
Have you had any luck at all? My phone has been in a drawer for a couple of months now...
Guys try flashing the latest MM stock i discovered an error too in my old update script /sniff.
Run the *.bat as admin .
Stock zip for XT1072:
MEGA Mirror 1
MEGA Mirror 2
Fastboot+mfastbootv2
BAT File
MM Flash BAT said:
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
Click to expand...
Click to collapse
Also remember if you are on another model and not XT1072 you should dl the correct image for your phone from HERE Look if Android 6 is available for your country, if you have gb-de-fr-es you can use the EU stock image.
Unpack everything in the same folder and launch the *.BAT as admin

Firmware/Rom downgrade XT1072 -No sound-

Hi All!
Here is my situation, I have a moto g xt1072 (Jan 2016) which came with a faulty problem, no sound after 5 seconds of been started. I checked everything (Factory reset via recovery), including both speakers, (both working at 7.5 ohms). Do you think a firmware change or a different ROM can help or it's time to let it go?
Base band: M8926_309101.02.03.19R THEA_EMEA_CUST
Kernel: 3.4.42-gef77327 [email protected] #1
System Version: 24.41.34.thea_retes.retesall.en.EU retes
Complation numer: MPB24.65-34
Everything is stock, no changes were made.
Thanks in advance!!!
@lost101
did you look here
http://forum.xda-developers.com/moto-g-lte
sd_shadow said:
did you look here
http://forum.xda-developers.com/moto-g-lte
Click to expand...
Click to collapse
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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​
murrayhawk said:
Yep, if you are familliar with this process could you mind writing me a list of steps in order? I'll investigate 1 by 1 later, I've found so much info that's confusing. My phone is unlcock for any cellphone company, but It's not root, it's stock.
I used to install custom ROM's on my old Defy + but I things are very different now for what I'm seening. :S
Click to expand...
Click to collapse
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
lost101 said:
Fastboot flash the latest full factory firmware image for your model.
mfastboot download: https://www.androidfilehost.com/?fid=24052804347778493
XT1072 Retail Spain Android 6.0 Factory Firmware Image: https://www.androidfilehost.com/?fid=24533103863143791
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219 (See specific fastboot commands below)
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​
Click to expand...
Click to collapse
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
ora69 said:
please dont mess up the flash.. because then you're pretty much ****ed.. as far ive seen and read and heard and tried, there will be no fix..
Click to expand...
Click to collapse
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
murrayhawk said:
I don't have anything to lose, this phone is rebooting itselft every 2 minutes.
Click to expand...
Click to collapse
please, if anything gives a fail, post it on the thread! I myself have hard bricked this device, and now im trying to find the testpoint for it, ive already invested hours into this.. and i have no progress!, its worth it to post it on a thread
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
The guide I linked to is not about downgrading. Ignore references to Android 4.3 - it still applies to Android 6.0. It sounds like you have not installed the usb drivers for your phone in Windows. This is a prerequisite. These Moto G drivers will also work for your phone:
Moto G USB Drivers (WinXP/7/8/10 32Bit-64Bit)​
Test Fastboot is working by typing: fastboot devices
You may also be able to use RSD Lite - but this again will require you have installed USB drivers for your phone.
murrayhawk said:
mfastboot download: Done
firmware download : Done
Fastboot: I'm not quite sure what is this about, is this for the new firmware installation? The guide you point says something about downgrading 4.3 to 4.2 and I'm running 6.0 stock.
I tried the first command (mfastboot flash partition gpt.bin) and it got stuck at : Waiting for device.
should I root the phone first?
can I use RSD Lite?
Click to expand...
Click to collapse
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
sd_shadow said:
my opinion is use RSD lite first, unless there is not a specific firmware file for your carrier/region...
or there is a high rate of flashing failure with the firmware available.
if RSD lite fails, best to post errors from pc and phone here
before try again, if there's not an obvious fix
then try mfastboot.exe
fastboot.exe is generic android, mfastboot.exe is Motorola specific, for moto's unique system.img...
avoid usb 3.0 ports
make sure the firmware downloaded is correct size, verified MD5 is best.
verify drivers are correct when the device is in fastboot mode
I have generic moto instructions in my
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
i think the tip you gave to avoid usb 3.0 ports will really help, didnt realize i was using the usb 3.0 port
Ok, this is what I did so far: (I'm running Windows 7 64b).
1. RSD Lite 6.2.4: Installed
2. Motorola Mobile Drivers Installation 6.4.0: Installed
3. Motorola Device Manager: Installed
1. I started the mobile into the recovery mode
2. Connected the moto cable to the pc
3. Opened RSD Lite, loaded the new firmware and hit start boton
4. The process reached a "please reboot manually...."
5. The phone starts but with the old firmware in it.
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
murrayhawk said:
More Updates: I ran mfastboot sequence and every command returned OKAY. The issue still remains intact, sound works for 5 seconds, and the firmware has not been updated.
Any thoughts?
Click to expand...
Click to collapse
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
I want to see a full and complete log of the fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Ok, please check the attachment.
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
lost101 said:
It looks increasingly like your issue is hardware, not software related. The only remaining software option I can suggest is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Can you explain why does it retain the original firmware after mfastboot commandas ran well?
Just a quick reminder. This moto g XT1702 Jan2016, is not rooted, bootloader is locked and has everything stock, it came with Android 6.0 installed.
murrayhawk said:
Can you explain why does it retain the original firmware after mfastboot command as ran well?
Click to expand...
Click to collapse
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
lost101 said:
How do you mean original Firmware? You are flashing a Stock Android 6.0 firmware image.
Click to expand...
Click to collapse
What I have right now is : System Version: 24.41.34.thea_retes.retesall.en.EU retes and after flashing to XT1072_THEA_RETES_6.0_MPB24.65-34_cid7_subsidy-DEFAULT_CFC.xml. I'm still having 24.41.34.thea_retes.retesall.en.EU retes.

Installation error rom XT1078

hello all right with you, I hope so, I am Brazilian, and I would take a doubt on the bike variant g2 xt1078 of my region (Brazil).
Accidentally I Flashed the ROM xt1068 on my mobile xt1078, and now the first command "mfastboot.exe flash partition gpt.bin" shows the error "GPT Version Downgrade". And then camndo "mfastboot.exe flash system system.img_sparsechunk.0" It also shows the error "Image is too large" with this system partition has been reduced or changed, I wonder if this has repair, and that any suggestion and welcome.
@lost101 
 @Kamin4ri
 @VitaTaf
 @parrotgeek1
l.rochas
Is your Bootloader unlocked?
lost101 said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
yes unlocked.
What is the exact name of the XT1078 firmware image your are currently trying to flash?
lost101 said:
What is the exact name of the XT1078 firmware image your are currently trying to flash?
Click to expand...
Click to collapse
this and the image of factory with august patch
XT1078_THEA_RETBR_DS_6.0_MPBS24.65-34-5_cid12_subsidy-DEFAULT_CFC.xml
mfastboot flash partition gpt.bin
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
And the rest of the commands operates normally
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said
l.rochas said:
@lost101
does not work, same mistakes previously said
Click to expand...
Click to collapse
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
It seems to be a very risky method, but not hurt to try.
l.rochas said:
It seems to be a very risky method, but not hurt to try.
Click to expand...
Click to collapse
You already almost completely destroyed your handset by flashing the wrong bootloader. You don't exactly have many options here.
lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
I've tried this method.
After a backup of all partitions on another default XT1078, the restore process on my phone finished with error only on /system or /data (I don't remember well).
Then I've tried to boot, but it had boot loop, just blinking very fast the Warning screen of unlocked bootloader.
It didn't work. :/
The only working method was merging XT1068 and XT1078 ROMs. Now Wifi and Mobile Data are working.
Now I can't change this ROM. Lineage or the whole XT1078 stock can't be installed.
The problem was that I didn't realize I was applying a XT1068 ROM on a XT1078 phone.
As all partitions were changed by flashing gpt.bin, the correct gpt.bin of XT1078 can't be applied.
Any solution????
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
benjausen said:
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
Click to expand...
Click to collapse
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
peacehope said:
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
Click to expand...
Click to collapse
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
benjausen said:
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
Click to expand...
Click to collapse
I don't have now a LineageOS ROM to check, but if I'm not wrong, it doesn't have each separated file as Stock ROM. Am I wrong?
I've flashed many Stock ROMs manually file by file, but never with custom ROMs.
Can you please provide any link teaching this with custom ROMs? I really want to try this.
Maybe this can be a solution, and if it works we will help many people here.

Categories

Resources