Related
Hi,
I just got my Moto X Dev Edition GSM TMO last week, but I got it very unstable, while I had try to wipe cache and factory reset few times.
Some problem that I have
Numeric Keypad is not shown while using google keyboard. The problem that my email is using 2FA from google to entry my 6-digit PIN
Chrome freeze while open quite complex pages
Gmail freezing while open communication more than 3 email on the messaging mode
Path also unstable while need to scroll down and request to reload more data.
Whatsapp stuck when there's few message has beeen received
Thinking to downgrade the os to 4.4, but when I read in some thread inform better not to downgrade that might cause device brick.
Is there any other solution so I can use my Moto X for daily, while waiting for T-Mobile latest 4.4.2 rom.
Please share
Thank you
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Click to expand...
Click to collapse
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
tyapeter said:
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
Click to expand...
Click to collapse
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Let me make it easier. Just flash the system and kernel files leave everything else alone. However the ability to go back depends on how you got to 4.4.2 to begin with, OP said he took the OTA, not sure about you.
My advice assuming you're stock is to call Motorola, tell them you took the ota and these are the issues you're having. Get them to send you a new phone. I'd rather see you do that than brick your phone trying to do it yourself.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Are you sure this is correct? I was told in this thread: http://forum.xda-developers.com/showthread.php?p=50330230#post50330230 (see post #12):
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
Click to expand...
Click to collapse
So the way I understand it one cannot downgrade from 4.4.2 to any other version because bootloader in 4.4.2 was changed and is not compatible with any previous release.
tyapeter said:
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Click to expand...
Click to collapse
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
eksasol said:
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
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 erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
Click to expand...
Click to collapse
Thanks a lot, it works
Is it possible to downgrade from lollipop to KitKat? Is there any guide out there?
I have a simfree uk motox 2014 from Motorola, currently unrooted
Please let me know!
Thanks and happy holidays
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Edit: You can't just flash factory image to downgrade. See my post below.
_MetalHead_ said:
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Click to expand...
Click to collapse
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
varignet said:
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
Click to expand...
Click to collapse
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
_MetalHead_ said:
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
Click to expand...
Click to collapse
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
fbiryujin said:
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
Click to expand...
Click to collapse
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Edit: Also I take it that I should use mfastboot?
fbiryujin said:
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Click to expand...
Click to collapse
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Huh, I had never heard of RSD Lite before... I have just been using mfastboot.
_MetalHead_ said:
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Click to expand...
Click to collapse
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
fbiryujin said:
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
Click to expand...
Click to collapse
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
_MetalHead_ said:
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
Click to expand...
Click to collapse
Thanks. I'll use mfastboot just to be sure (If I even need to downgrade). Now to wait for that Walnut Finish to come back in stock :/
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
NWKENT said:
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
Click to expand...
Click to collapse
I wonder why they stopped including XML files...
_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
divergens said:
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
Click to expand...
Click to collapse
So you skipped "fastboot flash boot boot.img"?
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
divergens said:
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
fbiryujin said:
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
Click to expand...
Click to collapse
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
divergens said:
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
Click to expand...
Click to collapse
Haha my main device is sadly an iPhone 6 right now, and that's too big. I prefer the size of the iPhone 5S or the first gen Moto X. I want to be able to use the entire device with one hand while being secure in the fact that a movement or gesture won't loosen my grip on it. Sadly the world is just making bigger phones now, and the few smaller ones out there are "cheap" low budget/power options.
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
I downloaded Android Marshmallow after reading news about it through settings/about/system updates.
After downloading, the phone restarted but updatation was stuck after flashing TWRP screen (error screen photo attached)
My phone is
bootloader unlocked,
recovery TWRP
rooted
ROM is stock.
It seems the OTA update will be completed once I have stock recovery,
I have following queries
Is it necessary to revert to stock recovery to complete OTA update?
If yes, how to achieve it, what i learnt through search, I need to find Stock ROM zips and extract recovery (boot.img) and then flash it through adb?
where to look for thea stock rom and is there any easier method
It's risky, a lot of users here for some reasons got stuck whit locked/unlocked bootloader unable to boot and flash anything.
Here you can find all the motog stock roms http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
You should wait for the complete rom image for your country/model to pop there instead doing that risky thing you want do.
Thanks
Recently stock rom for xt1079 has been added to the list.
But I m trying to download from filefactory since yesterday but due to some reason, it stops in between and resume isn't supported.
Are there any other hosts
Are you sure the region of that xt1079 is right for your phonr ? check the phone box and the info inside settings to know which region/carrier you have, you must use the same identical 100% stock to avoid problems
And, do no relock bootloader !!!
yes i bought this through online retailer in India.
It is xt1079 Asia
I see in xda forum of moto g 2nd gen most of the time ppl are talking about xt1078.
What's the difference between xt1078/1079 and can't I use xt1078 ROM.
Rooting procedure meant for xt1078 worked fine for me
And Sir is relocking bootloader very risky ? suppose something goes wrong wont I be able to unlock or restore nandroid backup.
Thanks to support from Dr.nic I am finally on android 6.0
Although I have relocked my bootloader, but it is recommended to leave as it is.
If anyone stumbles here with same problem like mine i.e. unable to upgrade to android 6.0 just because of custom recovery, then pls download the firmware from filefactory.com link and flash. I'll add flashing commands as well to this post in near future.
if you have already done this rom change etc, the you must already be having fastboot, adb etc.
after connecting in fastboot mode holding VolDown and Power for few secs
run following commands
[this is for android 6.0 firmware]
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_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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I am not great expert, do this only if you have some idea, I may not be able to help you much if something goes wrong.
I can only say it worked for me
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.