FORUMS

Google No Longer Sending Calendar SMS Notifications

In a not entirely surprising move, Google announced that it’s putting an … more

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

Android M Preview Images – XDA TV

Android M preview images are available. That and much more news is covered by Jordan when he … more

[Q] Question about buying a bricked moto x

Thanks Meter: 0
 
By brurhh, Junior Member on 19th August 2014, 07:56 PM
Post Reply Subscribe to Thread Email Thread
Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:

-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.

-if the above is possible then what procedures should I follow

I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.


What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.

Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.

*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.

Sorry for the bad quality of the images but that's what the guy selling it uploaded.
 
 
19th August 2014, 08:06 PM |#2  
samwathegreat's Avatar
Senior Member
Thanks Meter: 1,830
 
Donate to Me
More
Quote:
Originally Posted by brurhh

Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:

-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.

-if the above is possible then what procedures should I follow

I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.


What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.

Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.

*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.

Sorry for the bad quality of the images but that's what the guy selling it uploaded.

You'll be rolling the dice on that one. MAYBE it can be fixed using the de-bricking procedures, but if anyone tells you that it can FOR SURE be fixed...well...I'd question their source.

If its cheap enough that you don't mind throwing that amount of money down the drain....give it a shot. Your call.
19th August 2014, 08:58 PM |#3  
KidJoe's Avatar
Recognized Contributor
Flag Thorndale/Romansville, PA
Thanks Meter: 1,295
 
More
Quote:
Originally Posted by brurhh

What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.

Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.

I call BS on that account of what happened... The bootloader is LOCKED STATUS 0. That device was never bootloader unlocked. (and having an unlocked bootloader doesn't interfere with taking an OTA)

It could be that someone used one of the older procedures to root and disable write protection, took and OTA (losing root/write protection) and later tried to downgrade to root & disable write protection again, thus causing the brick.

It could be as simple as flashing the latest ROM (4.4.4) using mfastboot. I could be as complex as using -> http://forum.xda-developers.com/moto...oto-x-t2629057 ... or it could just be a brick that can't be recovered.

Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
19th August 2014, 09:44 PM |#4  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by KidJoe


... or it could just be a brick that can't be recovered.

Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.

I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
20th August 2014, 12:18 AM |#5  
Darth's Avatar
Forum Moderator
Flag The Old Republic
Thanks Meter: 7,340
 
More
Quote:
Originally Posted by brurhh

I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.

I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.

I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.

For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.

You just don't know.
20th August 2014, 01:11 AM |#6  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by KJ

I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.

I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.

For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.

You just don't know.

Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
20th August 2014, 01:17 AM |#7  
Darth's Avatar
Forum Moderator
Flag The Old Republic
Thanks Meter: 7,340
 
More
Quote:
Originally Posted by brurhh

Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again

I don't blame you!

There's some bricks you can recover from, and some you can't.

Your odds are the same if you just go to the casino and put your money for the phone on red or black at the roulette table. If you lose you lose... But if you win... You can buy a working phone. 😀
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes