XT1095 on 5.1 with 60.16 Bootloader - Need help Downgrading - X 2014 Q&A, Help & Troubleshooting

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.

Related

Can't re-lock the bootloader

Hi guys i have the dev edition moto x. I rooted it and unlocked the bootlaoder, because i wanted to try out custom roms. i amtr now trying to put the phone back to stock. I followed the guide and i got the stock image back on the phone, but for some odd reason the bootloader wont get locked. I get sst lock failure in the command window. I need to send this phone back. any advice?
It's impossible to lock it again. If you have the pure edition you didn't lose your warranty anyway so don't worry.
Sent from my XT1095 using Tapatalk
AGISCI said:
It's impossible to lock it again. If you have the pure edition you didn't lose your warranty anyway so don't worry.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
You can relock your bootloader.
flameinthefire said:
Hi guys i have the dev edition moto x. I rooted it and unlocked the bootlaoder, because i wanted to try out custom roms. i amtr now trying to put the phone back to stock. I followed the guide and i got the stock image back on the phone, but for some odd reason the bootloader wont get locked. I get sst lock failure in the command window. I need to send this phone back. any advice?
Click to expand...
Click to collapse
Always read and read some more before you take someone's word.
Straight from the horses mouth.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91987/p/1449,8620
matt99017d said:
You can relock your bootloader.
Always read and read some more before you take someone's word.
Straight from the horses mouth.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91987/p/1449,8620
Click to expand...
Click to collapse
Actually that does NOT put it back to locked. There are 3 bootloader states:
Locked
Unlocked
Relocked
Once you unlock it, it is impossible to go back to locked. He can only change it to "relocked" which anyone can see that it has been unlocked before. Try searching the forums more and you will see what I mean.
Sent from my XT1095 using Tapatalk
AGISCI said:
Actually that does NOT put it back to locked. There are 3 bootloader states:
Locked
Unlocked
Relocked
Once you unlock it, it is impossible to go back to locked. He can only change it to "relocked" which anyone can see that it has been unlocked before. Try searching the forums more and you will see what I mean.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Relocked would be re-(LOCKED)
hence it is locked. Meaning that you can only flash signed images. You are right in the fact that people can see that it has be unlocked before. But when its relocked the bootloader is still locked.
matt99017d said:
Relocked would be re-(LOCKED)
hence it is locked. Meaning that you can only flash signed images. You are right in the fact that people can see that it has be unlocked before. But when its relocked the bootloader is still locked.
Click to expand...
Click to collapse
... For warranty purposes "relocked" does not help. With relocked they WILL know that he unlocked it.
Sent from my XT1095 using Tapatalk
For warranty purposes it does not matter when you have the pure edition. They have already said that its still covered under warranty.
In the first post he says he wants to lock it to send it back, but the point is that it does not matter and that they will know anyway.
Sent from my XT1095 using Tapatalk
AGISCI said:
In the first post he says he wants to lock it to send it back, but the point is that it does not matter and that they will know anyway.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Even if he never unlocked they would assume it has been unlocked anyway and if unlocking a Pure Edition would void the warranty (which it apparently doesn't) his warranty would already be void. When you put your ID string into the website to get the unlock code it very clearly tells you that once you click continue they update the device as unlocked in their records whether you actually unlock it or not because you asked them for the unlock code.
Well if he has dev edition moto x instead of pure edition then he probably needs to search OG moto x thread not the 2014 moto x
This is all irrelevant. Unlocking the bootloader on an XT1095 will not void the warranty per Motorola's website. Also per their website....requesting and have the unlock code for your device sent to you is the same as actually unlocking the device. In other words, they know what devices they sent out unlock codes for and as soon as they send that code they then assume that it was used and the device was unlocked. It does not matter if you decide not to use the code, if they sent it, then they consider it used on the device. They caution about that in the verbage that they want you to read before requesting the code. That of course does not apply to the Pure Edition (XT1095) since they consider that model a developers edition. So unless you have somehow damaged the device and it will no longer work properly, it really does not matter if the bootloader is unlocked or locked.

[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).

[Q][Solved] Relocking the bootloader

Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.
May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095
I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.
Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095
Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?
Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..
The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png
Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.

Request: modified userdata.img for 60.16 bootloader

I'm currently in the process of getting an xt1095 taken care of through warranty, but I want to fix it myself first if I can. This phone is locked out due to android device protection - android 5.1 won't let me log into the phone to change settings. I could unlock the bootloader to load an older system image that doesn't have android device protection, but I need to get into the phone first to set the OEM Unlock option. From what I can tell, the settings for android should be in userdata.img. Can someone post a userdata.img file that was created using the 60.16 bootloader and have the dev options (to include usb on and oem unlock on) set? If so, I would like to try to flash that and see if I can then unlock this phone.
Thanks!
If I understand correctly, you wouldn't be able to flash any images without an unlocked bootloader, right?
First off, nobody do it. If you do he will have access to your information and accounts.
Second it won't work, because it won't be signed by motorola so it would fail to flash on a locked bootloader anyway.
Sent from my XT1095 using Tapatalk
floepie said:
If I understand correctly, you wouldn't be able to flash any images without an unlocked bootloader, right?
Click to expand...
Click to collapse
You can flash factory images, but you shouldn't be able to flash a userdata.img since that isn't part of the stock image.
But I'm not understanding how you are locked out of your own phone here. Are you not able to log in to one of the accounts you've used on your device before? If you've reset your password recently you may need to wait 72 hours to get signed back in but that should certainly be quicker than sending it in for a warranty claim.
raptir said:
You can flash factory images, but you shouldn't be able to flash a userdata.img since that isn't part of the stock image.
But I'm not understanding how you are locked out of your own phone here. Are you not able to log in to one of the accounts you've used on your device before? If you've reset your password recently you may need to wait 72 hours to get signed back in but that should certainly be quicker than sending it in for a warranty claim.
Click to expand...
Click to collapse
No, his problem is that he bought the phone on ebay used and the previous owner's account is on it and can't be removed without the previous owner's password. There is nothing that he can personally do.
Sent from my XT1095 using Tapatalk
AGISCI said:
No, his problem is that he bought the phone on ebay used and the previous owner's account is on it and can't be removed without the previous owner's password. There is nothing that he can personally do.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ah, I didn't understand that from the original post. I was briefly locked out myself and it turned out it was due to a password reset.

XT1095 US Hard Brick

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.

Categories

Resources