XT1095 US Hard Brick - X 2014 Q&A, Help & Troubleshooting

Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....

madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Sorry, there is nothing you can do to fix a hard brick.
Sent from my XT1095 using Tapatalk

madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Was your bootloader unlocked? Can you boot to the bootloader?

rsa 329 said:
Was your bootloader unlocked? Can you boot to the bootloader?
Click to expand...
Click to collapse
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.

madkapitolist said:
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.
Click to expand...
Click to collapse
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.

RobbieDowie said:
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.
Click to expand...
Click to collapse
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk

AGISCI said:
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.

You might want to join the conversation going on at reddit over here I think you can go back to 5.1 by flashing the whole 5.1 image via the bootloader (including erasing userdate and cache) - I say so because that is what I did but some people say it will not work and to be honest now I'm losing confidence in my memory.... Hope we could get more insight, or at least get the official 6.0 bootloader image from moto soon.

RobbieDowie said:
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.
Click to expand...
Click to collapse
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk

bimasakti85 said:
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I actually knew downgrading was a bad idea and didn't intend on doing it. I used the MOTO_X_2014_PURE_MULTI_TOOLV4.1 which I had used in the past but didn't remember it was going to flash back to 4.2.2. The instructions on the page just say FLASH BACK TO TOTAL STOCK UNRROOTED ROM AND RECOVER-FULL-WIPE. It doesn't say anything about going to 4.2.2. When it said it was downgrading when I ran it I thought "oh, oh" but it was too late. I was trying to provide information in this thread because I hoped it would be helpful, e.g. DON'T USE THE MULTI_TOOLV4.1!. I specifically said "I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that" and what do I get? "...You ignored that message or didn't read it..." I'm already pretty grumpy about my mistake and bricking my phone and to get this kind of lashing isn't appreciated.

Related

Why Are There So Many Bricked Nexi?

Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
jiv101 said:
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
Click to expand...
Click to collapse
There are two separete issues. One is what you're describing, and one is the device just completely dying - "you can't even get to fastboot". The first one has thread here, as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no cause :/
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Tasssadar said:
as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no no cause :/
Click to expand...
Click to collapse
Are they sure of what bootloader versions they had?
I know this is a Nexus device but it has a Motorola bootloader. It is safest not to downgrade the bootloader OR the partition table from my experience with the Moto X. I know there were some exceptions and that is how jcase was able to get root on at least one bootloader version, but the general rule was don't try to downgrade the bootloader or the partition table to stay out of trouble.
I was thinking of making a post on General with this advice in it for people to help them stay out of trouble:
1) know your bootloader and partition table versions before you flash anything and if you aren't sure what will happen, do not attempt to downgrade either the bootloader or the partition table; and
2) make sure OEM unlock and USB debugging are enabled before you flash anything.
I understand that the advice above may be overkill for those who know what they are doing, but clearly people who don't know what they are doing are bricking their devices. I feel bad for them and don't want to see more people in that situation.
I was bricked by CM. Last nexus I had with cm was galaxy nexus so I don't know how cm is done on nexus 5 but why do they reflash bootloader and radios on each update. It wasn't that way before. Thats what bricked my device. I just got confirmation that I'm getting my replacement device.
akellar said:
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Still a Motorola bootloader
rootSU said:
Still a Motorola bootloader
Click to expand...
Click to collapse
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough

[Q] Best way to get off of 5.1 LMY47D?

Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
you can always use fastboot to go back to 5.0.1
stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.
EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.
Sweet, successful downgrade!
I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!
Disregard! Got it handled. Thanks guys!
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1
EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??
Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?

[POLL] What Caused You To Brick?

In addition to completing the poll, please leave more specific information if you can - i.e., bricked downgrading from Lollipop to Kit Kat, took an OTA without flashing back to stock, was able to recover by doing xyz, was not able to recover, screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD, had to do a warranty replacement, etc.
Edited - if you could post a follow up post with specifics after you vote, that would be great.
To the person who bricked after taking an OTA - did you not flash back to stock first? Or had you upgraded, then flashed backed to stock on a lower version (downgraded) and then took the OTA? What versions were you upgrading b/t?
To the person who bricked when they were downgrading - did you try to downgrade the bootloader? What versions were your downgrading b/t?
JulesJam said:
In addition to completing the poll, please leave more specific information if you can - i.e., bricked downgrading from Lollipop to Kit Kat, took an OTA without flashing back to stock, was able to recover by doing xyz, was not able to recover, screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD, had to do a warranty replacement, etc.
Click to expand...
Click to collapse
You should add "I'm too lazy to read." as an option in your poll.
badams1 said:
You should add "I'm too lazy to read." as an option in your poll.
Click to expand...
Click to collapse
I don't think that is the problem here. Motorola has not told anyone not to attempt to downgrade the bootloader and supposedly mfastboot will prevent a bootloader from being downgraded. Moreover, supposedly checks were put in the OTA script that would just cause it to fail if you were not entirely stock when you took the OTA. But obviously, people are still bricking downgrading and taking OTAs so somehow either fastboot or mfastboot is not preventing bricks and likewise the OTA script hasn't been perfected to prevent bricks.
At the end of the day, the real problem is in designing an OS that will brick if the BL is downgraded. They do that so that if they patch security holes in the bootloader, you can't then go back to an insecure earlier version. It is fine to block downgrades, but terrible that it bricks the phone.
Also, as far as not reading, I posted a warning post about the risks of downgrading the bootloader or partition table and lots of people are posting on that thread disputing that. So people don't know what to think.
bump
bump.
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
There is no way to unbrick it.
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
This has to go back to motorola and get a warranty replacement. It could be fixed if they would release a couple of files to us but they haven't so far.
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
Was it an actual XT1095 or a converted one? Which 5.1 where you on the original or the current or did you attempt the Brazilian? was your bootloader 60.14 or 60.16 ? did you fastboot flash partition gpt.bin and
fastboot flash motoboot motoboot.img ? If so did they not fail? and lastly you didn't attempt to lock your bootloader after the downgrade? for some reason people are trying this and even though it doesn't appear to be doing anything it just might causing an issue. There is no reason to attempt to relock your boot loader on the XT1095 it's the pure edition and warranty is not voided. When did it go black ? Was it during the 5.0 upgrade or after the reboot?
Try this site
http://www.usoftsmartphone.com/t300062.html
wolfu11 said:
Was it an actual XT1095 or a converted one? Which 5.1 where you on the original or the current or did you attempt the Brazilian? was your bootloader 60.14 or 60.16 ? did you fastboot flash partition gpt.bin and
fastboot flash motoboot motoboot.img ? If so did they not fail? and lastly you didn't attempt to lock your bootloader after the downgrade? for some reason people are trying this and even though it doesn't appear to be doing anything it just might causing an issue. There is no reason to attempt to relock your boot loader on the XT1095 it's the pure edition and warranty is not voided. When did it go black ? Was it during the 5.0 upgrade or after the reboot?
Click to expand...
Click to collapse
It is a converted xt1092, the germen variant. I converted it and after this i flashed the offical US 5.1 OTA (from here). After this i got a bootloop due to a problem with xposed and root.
So as stupid as i was,i just reflashed all the 4.4 files (xt1095 variant, with adb/fastboot from the sdk) with the motoboot and the gpt.bin, because i had them downloaded on my pc. After this i could boot again. Then I tried to take the OTA to 5.0 .11 . After this the device tried to reboot, but never booted and was hard bricked.
To the other questions, i dont know the version of my bootloader and i didnt tried to relock it.
r4ph431 said:
It is a converted xt1092, the germen variant. I converted it and after this i flashed the offical US 5.1 OTA (from here). After this i got a bootloop due to a problem with xposed and root.
So as stupid as i was,i just reflashed all the 4.4 files (xt1095 variant) with the motoboot and the gpt.bin, because i had them downloaded on my pc. After this i could boot again. Then I tried to take the OTA to 5.0 .11 . After this the device tried to reboot, but never booted and was hard bricked.
To the other questions, i dont know the version of my bootloader and i didnt tried to relock it.
Click to expand...
Click to collapse
I'd give this site a try since you're already bricked.
http://www.usoftsmartphone.com/t300062.html
wolfu11 said:
Try this site
http://www.usoftsmartphone.com/t300062.html
Click to expand...
Click to collapse
Thanks i gone try this as soon as i am home from work and then report back if it helped.
r4ph431 said:
Thanks i gone try this as soon as i am home from work and then report back if it helped.
Click to expand...
Click to collapse
That site is a site that just repeats XDA posts and the post quoted to you was deleted by the author b/c the files that were posted were for a Snapdragon 400 (MSM8626). I don't know what those files will do to your device.
This was the original thread on XDA:
http://forum.xda-developers.com/moto-x-2014/general/guide-unbrick-hard-bricked-moto-x-2nd-t2966017
Same here
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
I have the same problem dude. ¿any progress?
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
Why don't you get a warranty replacement? The XT1095 is covered by the warranty even if you unlock the bootloader.
JulesJam said:
Why don't you get a warranty replacement? The XT1095 is covered by the warranty even if you unlock the bootloader.
Click to expand...
Click to collapse
Its a converted xt1092(see me second answer) so its not covered.
Besides that motorola support told me it isnt covered under the support, not even on the xt1095. They stated it is against their tos and they wont repair it, not even when you pay them.
Sent from my D6603 using Tapatalk
r4ph431 said:
Its a converted xt1092(see me second answer) so its not covered.
Besides that motorola support told me it isnt covered under the support, not even on the xt1095. They stated it is against their tos and they wont repair it, not even when you pay them.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
That's not true in the US. In the US, the XT1095 gets warranty replacements no matter whether you unlocked or rooted.
Idk about Europe but I thought you had stronger consumer protection laws over there than we have here. I would look into it and not take No for an answer until you are sure that their policy is in-line with your consumer protection laws.
New hope here
JulesJam said:
That's not true in the US. In the US, the XT1095 gets warranty replacements no matter whether you unlocked or rooted.
Idk about Europe but I thought you had stronger consumer protection laws over there than we have here. I would look into it and not take No for an answer until you are sure that their policy is in-line with your consumer protection laws.
Click to expand...
Click to collapse
Im so glad to know that, i have a Moto XT1095 with unlocked bootloader, so today i contact the customer service via chat, they tried to helpe solve the problem, and when nothing gets better, the lady on the chat asked my IMEI, then she told me that it was still under warranty coverage, so i give her my shipping address, and now just waiting for a prepaid label to send my device for a "like new" replacement.
"Hi Ezequiel,
This is Jess from Motorola Chat Support. This is just a follow up email regarding your concern with us with reference number: 150606-001922. I just want to verify your shipping address for me to be able to process the replacement for you. Please provide me your complete shipping address. Feel free to respond to this email. Please let us know so that we can continue process your replacement.
Please feel free to chat back if you have further questions; we are open 24/7 to assist you. You may also call our Motorola Android Customer Service Department at 1-800-734-5870 during Mondays to Fridays 8am till 11pm and Saturdays and Sundays 10am till 7pm CST.
Thank you for choosing Motorola and have a nice day!"
ZekeMV said:
Im so glad to know that, i have a Moto XT1095 with unlocked bootloader, so today i contact the customer service via chat, they tried to helpe solve the problem, and when nothing gets better, the lady on the chat asked my IMEI, then she told me that it was still under warranty coverage, so i give her my shipping address, and now just waiting for a prepaid label to send my device for a "like new" replacement.
Click to expand...
Click to collapse
Good news!!!
JulesJam said:
Good news!!!
Click to expand...
Click to collapse
Thanks for this thread btw. I just bricked my device doing the same thing (5.1 OTA back to 4.4.4 factory image, black screen no bootloader/no response, QHSUSB_DLOAD shows up in device manager) and realized after finding this that that was the cause of the issue. I called customer support and will be receiving a replacement this week. It's not too bad b/c my usb port was starting to get janky so I was thinking of getting an RMA anyway so I would have had to spend the $25 on the advance RMA anyway (I really can't wait 2 weeks+ without a phone).

XT1095 on 5.1 with 60.16 Bootloader - Need help Downgrading

I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .
adm1jtg said:
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .
Click to expand...
Click to collapse
I thought the system image is supposed to be flashable even when not locked. Motorola's instructions for returning something to stock has the bootloader and partition flashed - what's the point in doing that if you can't downgrade it?
Anyways, I have tried to unlock it, but since it is running android 5.1, it requires me to set the OEM Unlock option in Android Developer's Settings. Unfortunately, when the phone boots up, I cannot get into any settings without entering the google account information that was used to protect the phone in the first place. So I'm stuck - 5.1 won't let me get far enough to set the setting to unlock so I can't unlock bootloader to revert back to an earlier system version.
darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
Try flashing the 5.1 images. I don't know if that will work but it seems like it might since you're not technically downgrading which would require an unlocked bootloader. Just follow all the commands on Motorola's website.
Sent from my XT1095 using Tapatalk
There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk
AGISCI said:
There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Not quite...I got motorola to accept it under warranty to replace it. The IEMI says the phone was bought in Feb. 2015, so it still has a chunk of warranty left on it.
That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk
AGISCI said:
That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Is that really a huge problem? They will know who claimed the warranty and I'm sure can notice if anyone is abusing that. Not perfect, but not terrible either. Besides, when the phone is turned in for a warranty, how does Moto know that the reason it's locked out is not due to my own google account?
Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk
AGISCI said:
Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.
darkprime said:
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.
Click to expand...
Click to collapse
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk
AGISCI said:
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, I stand corrected, but Moto doesn't know if I was the first end user or not. I'm sure I wasn't, but good businesses will honor warranties even when technically against the agreement, terms, or expiration.
Anyways, back on topic - if someone knows of something else I can try while I still have the phone, I would like to hear it.

New update bootloops my phone, help please!

Hey guys, so my mom was using the Turbo yesterday when she was prompted to an update. Now according to a few searches there was a soak test out or something? Not sure, since I have the Turbo 2. But regardless, she went to apply the update and now that phone won't boot up. It lights up with the M logo screen and then goes to andy where he's got the rotating box in his belly, and underneath it says "Erasing...". I can't get to any of the other options from the screen where you hold Volume Down while powering up. All of the options lead to the same erasing screen. The phone will reboot after two or three minutes and go back to the same thing. Been doing this for hours. I have it sitting on a charger and will take a look at it when I come back from work but I'm wondering how to remedy this? I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use. Not familiar with ADB so if that's the route I have to go, I'd appreciate a write up on how to use it. Willing to install custom firmware if I have to as well. I just need to get the phone working asap. My mom works nights and she is currently phoneless, so this is a safety concern of mine.
Also that screen where you hold Volume Down, it says battery okay and all that but it says the phone software is modified. Not sure why, I know that she completely incapable of doing that. And I didn't modify anything when I had the phone. Not that is matters though, it's out of warranty so Verizon or Moto probably won't be too useful.
Any and all help appreciated. Currently not in the position to buy a new phone so I'd prefer fixing this one up if I can. Thanks!
Xelios029 said:
I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use.
Click to expand...
Click to collapse
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Never, which is why I'm confused why it says software status modified. The sunshine and mofo mods were released after I upgraded to the turbo 2 so I never even had a chance. But thank you though! Really appreciate it, I was scared that some part of the memory had failed or something. My only question from here is how do I get the phone into the mode to required to RSD it? Because even if I select the bootloader option from that screen where you hold volume down while powering up, it goes to that erasing screen no matter what.
EDIT: Got home from work and downloaded all the files. RSD 6.1.5, Motorola Device Manager for the drivers, and the FXZ file. No dice. It won't recognize the device in RSD even though windows is making that sound when a device is connected. No luck on RSDLite 6.2.4 either.
EDIT2: Okay ugh, now I don't know what to do. Turns out RSD didnt detect it because the cable was not directly plugged into the motherboard. Took me a while to figure that out. So I got it detected and I flashed that file you put above and I'm still having the same problem. It reboots once everything is finished flashing and then goes back to the "Erasing..." screen.
EDIT3: SUCCESS!!! Thank you so much! I swear I was thinking I was going to have to replace the phone. Let it sit at the Erasing screen after flashing it for a bit and it eventually rebooted itself and started the Droid splash screen. What a huge relief! Hopefully these updates help with someone else who may run into the same problem.
Glad it worked for you!
And it helped you were persistent.
ChazzMatt said:
Glad it worked for you!
And it helped you were persistent.
Click to expand...
Click to collapse
Thanks again, much appreciated!
ChazzMatt said:
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Click to expand...
Click to collapse
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
KARIM9377 said:
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You have to ask them. I don't know. But we've been surprised before by their talent.
ChazzMatt said:
you have to ask them. I don't know. But we've been stories surprised before by their talent.
Click to expand...
Click to collapse
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
KARIM9377 said:
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
Click to expand...
Click to collapse
Every time Sunshine released an update to force unlock the Droid Turbo bootloader, Verizon releases an OTA "security update" to block it.
This next rant is not towards you but to other longtime Droid Turbo owners... (Like anyone who has owned a Droid Turbo for over two months. Anywhere from 2 months - 2 years.)
People just need to UNLOCK their bootloaders before taking any updates. NEVER, NEVER, NEVER take an OTA update. If there's anything worthwhile it will be posted HERE on XDA and you can flash it manually. Just unlock your bootloader and you don't have to worry about Verizon "blocking" Sunshine because your bootloader will already be unlocked!

Categories

Resources