EDITING MY THREAD: original post doesn't apply anymore, because thanks to some AWESOME guys from the Brazilian Moto X Style community, we can now UNBRICK the XT1572 (at least the LATAM-DS variant) with corrupted bootloader!
XDA post (thanks @Danielo007 ):
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Moto X Style Brasil Google+ Community:
https://plus.google.com/104133179727559624127/posts/Zjc8yQgzViS
My truly sincere THANK YOU for all involved in this solution!!
dbolivar said:
I will pay US$ 30 in Bitcoins to whoever provide me working "blank flash" files for my Moto XT1572, with working instructions able to successfully unbrick the device (corrupted bootloader).
After my latest flash frenzy, my XT1572 ended up with a corrupted bootloader, being recognized only as "qhsusb_bulk" (black screen, unable to get into fastboot, recovery etc.). It can be recovered with the appropriate infamous "blank flash" files for this specific model, which are usually used with Qualcomm's QFIL utility. However, Motorola/Lenovo doesn't officially provide these files, although some users managed to release them for other Moto models.
Perhaps someone who works at an authorized repair center, or a highly skilled mobile hacker who can reverse engineer/dump the bootloader in a workable way, can provide these files and enjoy a free dinner or some beers on the weekend?
Others are free to join this bounty on their own. I won't setup a collective fund or something like that, though; if you want, pay directly the good soul who provides you the files and instructions.
DEVICE DETAILS:
Motorola XT1572, Brazilian LATAM-DS variant
Latest official firmware: Nougat NPH25.200-15 + August 2017 OTA (bootloader upgraded)
Click to expand...
Click to collapse
Honestly, the chances of acquiring the proper blankfile files is near zero... Unlike other devices, Moto devices beginning with Gen 3 (Moto X Pure/Style, Moto G 2015, Moto E2) and newer, require a digitally signed set of blankfiles (much like factory images), so it is impossible for someone to create or make them. It also seems that only Lenovo corporate centers know have these files, authorized service centers no longer have them available.
Just as you have seen that factory images leaking out has nearly halted, these are far more rare. Lenovo has taken a much tighter reign on these files and the chances of them leaking out now is slim to near zero.
Don't mean to be a downer, but the reality is that this isn't Google's Motorola anymore, and Lenovo seems to have taken a much tighter grip on such information.
acejavelin said:
Honestly, the chances of acquiring the proper blankfile files is near zero... Unlike other devices, Moto devices beginning with Gen 3 (Moto X Pure/Style, Moto G 2015, Moto E2) and newer, require a digitally signed set of blankfiles (much like factory images), so it is impossible for someone to create or make them. It also seems that only Lenovo corporate centers know have these files, authorized service centers no longer have them available.
Just as you have seen that factory images leaking out has nearly halted, these are far more rare. Lenovo has taken a much tighter reign on these files and the chances of them leaking out now is slim to near zero.
Don't mean to be a downer, but the reality is that this isn't Google's Motorola anymore, and Lenovo seems to have taken a much tighter grip on such information.
Click to expand...
Click to collapse
Damn, it will probably be my last Motorola phone. Thanks for the information, though. It seems they are intentionally making it very hard to repair. Besides this bulls**t of not distributing the blank flash files (and even digitally signing them... come on!), I've called some repair centers here (although unauthorized ones) and they mentioned that they can't even replace the motherboard, because Lenovo isn't providing repair parts anymore. I'll try an authorized repair center later, if it's the same crap, will definitely steer away from this brand in the future.
But, who knows, still hope someone shows up with the files.
dbolivar said:
Damn, it will probably be my last Motorola phone. Thanks for the information, though. It seems they are intentionally making it very hard to repair. Besides this bulls**t of not distributing the blank flash files (and even digitally signing them... come on!), I've called some repair centers here (although unauthorized ones) and they mentioned that they can't even replace the motherboard, because Lenovo isn't providing repair parts anymore. I'll try an authorized repair center later, if it's the same crap, will definitely steer away from this brand in the future.
But, who knows, still hope someone shows up with the files.
Click to expand...
Click to collapse
Eh, I don't know if Moto is any worse or better than the others... As time goes on, other manufacturers that are better will fall in line as well, under the guise of "security" and privacy. Although there is some validity to these reasons, it does hurt hobbyists like us, but we are such a small market share they don't care.
Same thing happened to me... I got moto to send me a new device for under 100 bucks. Ask for discounts. They actually give them.
moto x play
please give moto x play hard brick files help me anyone.:crying::crying:
Link not working ...................
Related
I promised myself show how Samsung treats its and how they assume responsibilities.
More here:
Samsung Galaxy S I9000 blog
Samsung Galaxy S I9000 Facebook Page
The main ideea is that i am a lucky owner of a phone that comes from a batch that was released on the market with manufacturing errors.
Other owner with same problem found out:
Finally they(samsung) informed us that the display needs to be replaced. This means the front panel in totality will be replaced. I hope to get it back in a couple
of days. The way they were handling the phone i am worried if i will get it back in acceptable condition. It has been a really traumatic experience. They informed me it was a manufacturing defect and there seems to be a batch which might have this issue.
Click to expand...
Click to collapse
After x time the displays of these phones coming from that batch lose color depth and increase brightness, the overall image quality being shattered to pieces.
To be shure my phone had this particular problem, i tried everything from the software point of view that could be done : changed to stock android, tried different custom roms, even the ones with voodoo color fixes, factory reset (of course) but nothing.
I was shure then i had that problem as the owner above and i brought it to service (i just bought the phone in november 2010). I did not know i had to put the original android from samsung, so i got a phone call the next day from samsung service, being told that i voided my warranty and i should pay 350 dolars to fix it.
I understand that rules are rules and that it says that if you use other than original samsung software you void the warranty, but they know, and i know that this is a production fault having NOTHING to do with the software .
The main ideea is the phone comes from a batch with manufacturing defects and they SHOULD asume responsability.
Don`t get me wrong, i loved this phone and Android, but the way samsung deals with this problem is outrageous and i must "be heard" .
I hope your phones do not come from that batch.
Thank you & happy flasing,
Dan Gheorghe
bbluee:
You wrote that You have master degree in computer science
BUT IT DOESN'T PROVE ANYTHING...
were were you living last years?
you were smart enough to flash new firmware but you failed with ensuring your own security and comfort as a common customer, poor you
I can bet that almost everybody on xda do know that before sending broken device (ANY device!!!) to ANY service the most secure way is to ensure it has system and enhancements oficially supported by manufacturer.
Greetings!
V.
voriax said:
bbluee:
You wrote that You have master degree in computer science
BUT IT DOESN'T PROVE ANYTHING...
were were you living last years?
you were smart enough to flash new firmware but you failed with ensuring your own security and comfort as a common customer, poor you
I can bet that almost everybody on xda do know that before sending broken device (ANY device!!!) to ANY service the most secure way is to ensure it has system and enhancements oficially supported by manufacturer.
Greetings!
V.
Click to expand...
Click to collapse
I know i did not have the "best" approach, and if any other given problem they could be right.
I did not want to brag with the degree, only to point out that i know i didn`t do anything to get the phone to have that display problem, and the fact that i know that the software in this case HAS NOTHING to do with the fact this product comes from a batch with manufacturing defects.
I know that here on xda, are people with far more android and phones knowledge than i have.
And you just gave up? This post looks like garbage to me.
"It is like i buy a laptop with windows 7 and i have a hardware problem , take it into service with a linux operating system and they say the warranty was voided." is NOTHING like modifying phone firmware. Samsung doesn't provide you with the tools to flash 3rd party firmware to your phone - if you used ODIN, you used STOLEN Samsung software.
Masters degree in computer science - lol, read the book, "overschooled but undereducated." When sending back a product for warranty service, you re-install all stock firmware; that's pretty basic knowledge.
Sounds like you're bad mouthing Samsung for something that is your fault. Personally, I wouldn't have taken it sitting down; they definitely should fix it, and making a stupid blog post to spout non-sense is just silly - demand they fix it, and know your rights under the law before you do.
phzi said:
And you just gave up? This post looks like garbage to me.
"It is like i buy a laptop with windows 7 and i have a hardware problem , take it into service with a linux operating system and they say the warranty was voided." is NOTHING like modifying phone firmware. Samsung doesn't provide you with the tools to flash 3rd party firmware to your phone - if you used ODIN, you used STOLEN Samsung software.
Masters degree in computer science - lol, read the book, "overschooled but undereducated." When sending back a product for warranty service, you re-install all stock firmware; that's pretty basic knowledge.
Sounds like you're bad mouthing Samsung for something that is your fault. Personally, I wouldn't have taken it sitting down; they definitely should fix it, and making a stupid blog post to spout non-sense is just silly - demand they fix it, and know your rights under the law before you do.
Click to expand...
Click to collapse
Ok, ok... Stop throwing rocks men ) . I said i know i have mistaken in not flashing the phone with the original firmware. Again i did not want to sound cocky in the first post.
Please excuse me if i did.
I just wanted to say i know that what i did, had nothing to do with the display problem.
Was it my fault i bought a product from a batch with manufacturing defects?
Thank you for your feedback.
here!!
(In Traditional Chinese)
Only HTC doesn't seem to unlock the hboot now!!
For those wondering here is a google translate version of the text on the page - that is why it is in bad english
Sony Ericsson last month promotional offer for mobile phone unlocking Bootloader, as it were the entire mobile phone industry has some new territory like. Samsung announced soon also Twitter 『If Google does not oppose, they will also unlock the phone Bootloader』. Motorola has been silent today audible.
Motorola promised by the end of this year's Android device for its offer unlocking services, users can own brush from a ROM.
Now even unlock a Motorola also provides that only four brands in the Android HTC did not respond due to the unknown when it said it will adhere or surrender it.
Click to expand...
Click to collapse
Sounds like HTC made no commnet
So I would say this article is one way or another. Plus maybe something is lost in that translation a little.
HTC, to this point, seems pretty good with being unlocked. I've had my Evolution now since it came out and its fully customized. The new Evolution after it also looks that way. I really thing, aside from Motorola, that the carriers may start being he ones to ask to lock or unlock he bootloaders. ISPs in the US finally out caps on bandwidth last year, I would see locked bootloaders being next. Really time will only tell, but hopefully we get to keep our freedoms. The FCC approved a device is ours when we buy it, therefore we should be able to do what we want. Hopefully companies keep that in mind instead of trying to lock stuff down.
The big business rreason is that an unlocked device lets a user stay with that device longer, as it can be customized wig the latest software features. Unlocked devices really force companies to invest in research to give us better hardware now, costing them more money. As anyway can really developed the software that goes into the phones.
My thoughts anyway...
~Max
√ This Message Sent From CM7 Nightlies HTC-Evo4G ™
Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/
aerojoe420 said:
Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/
Click to expand...
Click to collapse
Google is not who dictates it generally goes in this order
Carriers
Manufacturers
Google
If you read about Google I/O this week then you know that google is creating a plan to allow phones to get updated for 1.5 years after release. Google encourages updates it is carriers that don't.
aerojoe420 said:
Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/
Click to expand...
Click to collapse
you might want to read the article a few times to make sure you understand it. google is not telling moto to not release gingerbread and to lock the bootloader
I may have misread it from what I gathered, they delay some updates because they tell moto/samsung that they need to pass the approval process if they want the google suite on them. they didn't approve the phones delaying there release because they had skyhook instead of googles data gathering stuff on it?
"Motorola wrote back to Skyhook, explaining that Motorola’s license to use Google’s apps requires those apps to collect location data, and that Motorola’s carrier contracts require Google’s Android apps be installed on its phones. If using XPS put Motorola out of compliance with Android and thus unable to license the Google apps, it would violate its carrier contracts.”
I'm not saying I'd rather have skyhook gathering data from me. It just seems to me that we'll never get the bootloader unlocked because of contractual agreements between carrier/moto/google and they all have there own agendas, in googles case they want you to have there data gathering software.
ATT has final say over bootloader issue. Moto has already said they will release it late this year, but with the disclaimer it would be up to the carriers to allow it for "their" phones. Will not happen through those channels. If the Dev's don't get it, then we don't.
It should be expected that almost every phone in the near future will be like this. The carriers are using this to protect what they consider to be their property. The bootloader is a direct and intentional way to stop "us" from doing all the hacks we do that circumvent things they either charge for, or capabilities they have crippled for whatever reason. Themes and apk files that allow personalization is all they want done. Yes they are watching, and looking for things they need to lock in future releases. They ain't playin no more.
I'd like to see accountability from all parties. There is far too much accepted complacency and slothfulness amongst all of the accused.
I don't want to hop on board with the Google devices just to get the latest updates. There may be other phones with certain specs or strong homebrew development communities that I'd like to participate in. It shouldn't take too much for OEMs to mangle the firmware with their "skins" and for carriers to lace these updates with bloatware.
As long as they can all hurry it up, I'll be happy. Right now I'm discontent and frustrated. And I'm sure I'm not alone with these sentiments... ugh...
benefits of a bootloader we could hack are??
you mean like opening the radio for the full functionality that has been crippled? They increased it to about half its capabilities on the last update. Or loading diff drivers at boot to fix problems some folks are having. Maybe loading a different version Droid. Need to do the whole rom, not just packages. Look at threads in Dev section to see the things we can't mod because some or all of the stuff needed is hidden inside. And the things that are hacked (webtop,tethering, etc.), might see them locked by the bootloader in the future. If they make or can make or save money by keeping it from dev's, this is going to be their path to lock it down.
The new sensation just released is "locked" also. part of the new world order,,lol.
I have a problem that I'm asking for help and support, as this is a question and answer forum.
I made a post a few days ago that the moderator decided to delete because people questioned the legitimacy of my problem.
Unfortunately, I have now had the same problem a second time.
I ask that someone please give me some advice and support rather than try to say my problem is a fabrication, made up or a lie.
13/01/2017
I received notification from Motorola that a 22mb OTA security update was available.
At the time, my device, a Motorola E3 XT1700 which was running system version S124 android 6.0, was ROOTED with TWRP, and was running various modifications such as Android N-ify and Pixel style nav bars.
I was puzzled I had an OTA update, I assumed being rooted removed that event happening, but I duly downloaded this update but as I had TWRP I could not flash the downloaded update.
I used "flash fire" from Google play to install the Update.
Installation went quite slowly with my device rebooting around 6 times.
I saw a new materialistic style boot animation and my device rebooted into android.
It quickly ran into serious issues with messages of every single Google app force closing, including Google now launcher and Gboard.
I had to skip the initial set up which I noticed was no different to normal.
I managed to get into settings and my build number and kernel versions were all the same as before.
The only difference I saw was my system version had gone from S124 to S131 and the android version was 7.0, but 7.0 is not available for this device.
The device kept force closing and rebooting every 2 minutes.
I had to contact a Motorola representative here in UK and they agreed to collect my device for examination and repair, but warned I would be liable for the cost.
We did argue over this, and eventually two days later, Motorola agreed to pay for the repairs as they said I had suffered "An exploitation" due to being rooted.
My device had been "reflashed" but I would no longer be able to receive any OTA updates.
They also told me there would be no android 7 for this device, but if I wanted to flash a custom ROM when one becomes available, that was up to me.
I also asked if I could flash a back up from an E3 power to my E3 if it went wrong again, they replied I could not because the E3 and E3 power are different devices and the firmware wasn't compatible with each other.
I do not know what any of that means.
Please help me to understand it.
21/01/2017
My device was returned two days ago, but the same thing has happened today.
Another 22mb update, but this time, my system version is going from S131 to S135 and my device has gone from an E3 XT1700 to E3 power XT1706.
The E3 is a European / American version where as the E3 power is exclusive to India and Asia.
The power is not available here in UK.
I have no reason to lie about this, and have provided screenshots from my device.
Please help me understand why this keeps happening?
That's all I want to know, how has my device became something else, a totally different model number?
How can I get another OTA update if Motorola have switched the function off and told me my new reflashed firmware has all the available updates?
Please will you help me understand this rather than accuse me of making things up or not abiding to the spirit of XDA by telling lies?
I have a genuine problem and fault with my device and want answers, not people calling me a liar.
I have already posted this on the Motorola Google plus community, where I explained I'm 16 years old, and when asking for support in my previous post here about this problem, it was deleted by the moderator for questioning its validity.......
I have since found out on Motorola's own forums this is a dodgy update that if installed can cause severe problems.
Many uses are advising not to flash this update.
I sorta already knew that.
Several users on Google plus pointed out to me they use XDA and have seen this problem talked about in the forums.
Someone directed me to Motorola's OWN forum where users are telling others to not download or flash this 22mb update because it breaks things!!!!
Finally, I want to share proof of my problem by showing the forum some photos and screenshots from my device.
For information purposes, let me list the difference between the 2 E3 models.
XT1700-E3 for Europe and continental USA
Single SIM
1GB ram
8 GB internal storage
XT1706-E3 POWER exclusive to India and Asia
Dual SIM dual stand by
2GB ram
16 GB internal storage
Now Look at the photos of my own devices box and packaging.
My device is a Motorola Moto E3 XT1700.
It has one SIM slot.
It has 1gb of ram
It has an 8gb internal storage.
After applying the update in question, in my about phone settings, my device is listed as a Motorola Moto E3 power XT1706.
I now have some blanked out settings for 2simcards that were not there before this happened.
Proof that something very strange has happened, and most of you think I'm lying.
I have several explanations from Motorola now and from users of Google plus as to what and why this has happened, and Motorola have admitted to being at fault in my case.
I'm happy with the reply I got from Steve who works at the repair centre who handled my case last week.
Let's see what explanations you experts come up with.
I know the answer now, this problem was down to three factors, one being human error in the way I applied the update.......But do you know the other 2 reasons?
I just wondered if anyone will enlighten me.
bubba1601 said:
Finally, I want to share proof of my problem by showing the forum some photos and screenshots from my device.
For information purposes, let me list the difference between the 2 E3 models.
XT1700-E3 for Europe and continental USA
Single SIM
1GB ram
8 GB internal storage
XT1706-E3 POWER exclusive to India and Asia
Dual SIM dual stand by
2GB ram
16 GB internal storage
Now Look at the photos of my own devices box and packaging.
My device is a Motorola Moto E3 XT1700.
It has one SIM slot.
It has 1gb of ram
It has an 8gb internal storage.
After applying the update in question, in my about phone settings, my device is listed as a Motorola Moto E3 power XT1706.
I now have some blanked out settings for 2simcards that were not there before this happened.
Proof that something very strange has happened, and most of you think I'm lying.
I have several explanations from Motorola now and from users of Google plus as to what and why this has happened, and Motorola have admitted to being at fault in my case.
I'm happy with the reply I got from Steve who works at the repair centre who handled my case last week.
Let's see what explanations you experts come up with.
I know the answer now, this problem was down to three factors, one being human error in the way I applied the update.......But do you know the other 2 reasons?
I just wondered if anyone will enlighten me.
Click to expand...
Click to collapse
No one here is obligated to help you, despite this being a Q&A section. I'm glad you had a positive response from Moto support. Posting here in a demanding manner is not an acceptable way of asking for help. Again, the name of the site is xda-developers not xda-helpdesk.
Please be respectful at all times in the future and follow forum rules.
Thread closed.
Having a vs995 my time has come. I didn't get the memo, and had to order a stop gap phone.
I have experience in reverse engineering hardened systems and was wondering if someone could help me approximate the effort required. This is my favorite platform to date. Last I did any android rev eng was the s4 mini (SCH i435). That phone was stolen. If someone can convince me that this would take 40 hours I'd humor it.
Otherwise... I've noticed the XCover Pro is still working for many even though Verizon killed a few on the 31st. I however don't see the CFW support rolling for that platform. I did put in for the Moto G Power, someone revived VoLTE on GSI and the battery procedure is reasonable. Thoughts? Suggestions?
OnePlus Nord N200. Pops apart like it was meant to be user serviced. Plenty of CFW support. Done.
Zz~ said:
Having a vs995 my time has come. I didn't get the memo, and had to order a stop gap phone.
I have experience in reverse engineering hardened systems and was wondering if someone could help me approximate the effort required. This is my favorite platform to date. Last I did any android rev eng was the s4 mini (SCH i435). That phone was stolen. If someone can convince me that this would take 40 hours I'd humor it.
Otherwise... I've noticed the XCover Pro is still working for many even though Verizon killed a few on the 31st. I however don't see the CFW support rolling for that platform. I did put in for the Moto G Power, someone revived VoLTE on GSI and the battery procedure is reasonable. Thoughts? Suggestions?
Click to expand...
Click to collapse
Lg's implementation is odd with many frameworks needed from stock. With no documentation about their implementation, all you have to go off of is the stock rom files. It'll certainly be a challenge.
I realized as I started to dig. I need a phone by Monday so I found a compromise, the Oneplus N200. I still love my V20, it's still my favorite platform. Time permitting, I may revisit.