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).
guys can you please share the url of Android 5.1.1 factory image for Nexus 6 build LMY47Z ( XT 1100 )
Cateye said:
guys can you please share the url of Android 5.1.1 factory image for Nexus 6 build LMY47Z ( XT 1100 )
Click to expand...
Click to collapse
Go here > https://developers.google.com/android/nexus/images
You can ignore the fact that Google labeled it "Sprint and USC". Many users on XDA report that it works just fine on XT1100.
cam30era said:
Go here > https://developers.google.com/android/nexus/images
You can ignore the fact that Google labeled it "Sprint and USC". Many users on XDA report that it works just fine on XT1100.
Click to expand...
Click to collapse
Are you sure ? i am asking because i wont be able to send it to Motorola for repair or warranty... Secondly do i have to root the cellphone in order to use factory image ?
Cateye said:
Are you sure ? i am asking because i wont be able to to send it to Motorola for repair or warranty ... Secondly do i have to root the cellphone in order to use factory image ?
Click to expand...
Click to collapse
Yes, I'm sure. And it is using a stock Google image, you can RMA it. No, you do not need to root, but you do need to unlock your bootloader to use the "fastboot flash" command in bootloader. Do not relock bootloader unless you have to RMA it.
cam30era said:
Yes, I'm sure. And it is using a stock Google image, you can RMA it. No, you do not need to root, but you do need to unlock your bootloader to use the "fastboot flash" command in bootloader. Do not relock bootloader unless you have to RMA it.
Click to expand...
Click to collapse
Thanks for the swift response. Thing is i wont be able to RMA in any circumstances. i live in Pakistan & Motorola is not officially available in my country & i bought it from grey market. That's why i paid US$800 for 32GB
Cateye said:
Thanks for the swift response. Thing is i wont be able to RMA in any circumstances. i live in Pakistan & Motorola is not officially available in my country & i bought it from grey market. That's why i paid US$800 for 32GB
Click to expand...
Click to collapse
All factory images work on all nexus 6.
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.
Hey, I'm returning my phone to Amazon. I'm on 7.4.2 and used DirtyCow method to root and unlock the device? So I have to unroot and unlock and if so how so I go about it. Thanks.
emperus said:
Hey, I'm returning my phone to Amazon. I'm on 7.4.2 and used DirtyCow method to root and unlock the device? So I have to unroot and unlock and if so how so I go about it. Thanks.
Click to expand...
Click to collapse
I don't know if they check returned items.
Why are you returning it?
mrmazak said:
I don't know if they check returned items.
Why are you returning it?
Click to expand...
Click to collapse
A lot of distortion with the microphone. May exchange it.
Was thinking about getting a new tablet because my Amazon Fire 5th got bricked during a Flash Fire Lineage Update. Since it was 5.1.12 when I bought it and the bootloader was unlockable and there was no way to ever install TWRP, I don't know much about tablets but am looking for one I can install TWRP and custom ROMs. Are the 713/813 good choices or would another tablet be recommended?
Thanks
RozWellZ said:
Was thinking about getting a new tablet because my Amazon Fire 5th got bricked during a Flash Fire Lineage Update. Since it was 5.1.12 when I bought it and the bootloader was unlockable and there was no way to ever install TWRP, I don't know much about tablets but am looking for one I can install TWRP and custom ROMs. Are the 713/813 good choices or would another tablet be recommended?
Thanks
Click to expand...
Click to collapse
I've had great results with the t813
I've got a 713.
The bootloader is unlockable, had it rooted an hour after delivery, ran stock for a few weeks, have it running Lineage now, working just fine.