Is my Droid 1 hopelessly broken/bricked?

[MotoCache1]

I reinstalled drivers, rsd lite doesn't recognize any device. I'm just not sure why I am no longer able to get to recovery. Status now from bootloader 2c.7c is
"Code Corrupt" and flashing "cannot program".

While this is only a minor inconvenience in the scheme of things, and I should have a replacement tomorrow (fingers crossed), if this is indeed the work of some pimply-faced basement dweller over some internet "feud", than he can go f*** himself. Get a life you loser.

Your phone is toast. Although we like to say the Droid is unbrickable, there is in fact 1 way to brick it and that is to corrupt the bootloader - which has happened on your phone.

In your OP you go from bootloops and able to boot into recovery to not being able to boot into recovery and having a corrupt bootloader. Since it is exceedingly difficult to corrupt the bootloader -- especially since there are two copies of it -- it would be interesting to know what transpired between being able to get into recovery and not.

While it is possible that the work of some pimply-faced basement dweller could have caused your boot loop, that didn't kill your phone - the corruption of your bootloader did.

It's too bad you have to turn it in. I'd really like to poke at it. Never seen a honest to goodness bricked Droid 1 before.

 

[eshdawg]

I reinstalled drivers, rsd lite doesn't recognize any device. I'm just not sure why I am no longer able to get to recovery. Status now from bootloader 2c.7c is
"Code Corrupt" and flashing "cannot program".

While this is only a minor inconvenience in the scheme of things, and I should have a replacement tomorrow (fingers crossed), if this is indeed the work of some pimply-faced basement dweller over some internet "feud", than he can go f*** himself. Get a life you loser.

Your phone is toast. Although we like to say the Droid is unbrickable, there is in fact 1 way to brick it and that is to corrupt the bootloader - which has happened on your phone.

In your OP you go from bootloops and able to boot into recovery to not being able to boot into recovery and having a corrupt bootloader. Since it is exceedingly difficult to corrupt the bootloader -- especially since there are two copies of it -- it would be interesting to know what transpired between being able to get into recovery and not.

While it is possible that the work of some pimply-faced basement dweller could have caused your boot loop, that didn't kill your phone - the corruption of your bootloader did.

It's too bad you have to turn it in. I'd really like to poke at it. Never seen a honest to goodness bricked Droid 1 before.

Well I still have my Droid, they gave it back after messing with it for about an hour. If you want to poke at it go for it, I've gotten lots of good tips and cool ROMs from this forum, so if you'd actually like it you can have it. Kind of like donating a corpse to "science" haha.

 

[eshdawg]

Also, I like the idea of being the world's first bricked droid. This is one small step backward for a man, one giant leap forward for mankind.

 

[MotoCache1]

I reinstalled drivers, rsd lite doesn't recognize any device. I'm just not sure why I am no longer able to get to recovery. Status now from bootloader 2c.7c is
"Code Corrupt" and flashing "cannot program".

While this is only a minor inconvenience in the scheme of things, and I should have a replacement tomorrow (fingers crossed), if this is indeed the work of some pimply-faced basement dweller over some internet "feud", than he can go f*** himself. Get a life you loser.

Your phone is toast. Although we like to say the Droid is unbrickable, there is in fact 1 way to brick it and that is to corrupt the bootloader - which has happened on your phone.

In your OP you go from bootloops and able to boot into recovery to not being able to boot into recovery and having a corrupt bootloader. Since it is exceedingly difficult to corrupt the bootloader -- especially since there are two copies of it -- it would be interesting to know what transpired between being able to get into recovery and not.

While it is possible that the work of some pimply-faced basement dweller could have caused your boot loop, that didn't kill your phone - the corruption of your bootloader did.

It's too bad you have to turn it in. I'd really like to poke at it. Never seen a honest to goodness bricked Droid 1 before.

Well I still have my Droid, they gave it back after messing with it for about an hour. If you want to poke at it go for it, I've gotten lots of good tips and cool ROMs from this forum, so if you'd actually like it you can have it. Kind of like donating a corpse to "science" haha.

Really!?!? I'm surprised they wouldn't want the corpse back before sending you a new one. I'd be happy to PayPal you some funds to cover the expense and hassle of shipping it to me. Send me a PM with your PayPal address and I'll get 'er done.

Of course anything I figure out I'll publish and mention it was your corpse Droid that helped with the discovery (but I don't hold out a lot of hope for that).

Thanks!

 

[eshdawg]

Your phone is toast. Although we like to say the Droid is unbrickable, there is in fact 1 way to brick it and that is to corrupt the bootloader - which has happened on your phone.

In your OP you go from bootloops and able to boot into recovery to not being able to boot into recovery and having a corrupt bootloader. Since it is exceedingly difficult to corrupt the bootloader -- especially since there are two copies of it -- it would be interesting to know what transpired between being able to get into recovery and not.

While it is possible that the work of some pimply-faced basement dweller could have caused your boot loop, that didn't kill your phone - the corruption of your bootloader did.

It's too bad you have to turn it in. I'd really like to poke at it. Never seen a honest to goodness bricked Droid 1 before.

Well I still have my Droid, they gave it back after messing with it for about an hour. If you want to poke at it go for it, I've gotten lots of good tips and cool ROMs from this forum, so if you'd actually like it you can have it. Kind of like donating a corpse to "science" haha.

Really!?!? I'm surprised they wouldn't want the corpse back before sending you a new one. I'd be happy to PayPal you some funds to cover the expense and hassle of shipping it to me. Send me a PM with your PayPal address and I'll get 'er done.

Of course anything I figure out I'll publish and mention it was your corpse Droid that helped with the discovery (but I don't hold out a lot of hope for that).

Thanks!

Yeah it would be no problem, I'll PM you tomorrow and sort it out. Hopefully, my phone will be here tomorrow, they wouldn't make any promises on that though. I was told I'll be sent a refurbed Droid, which I have mixed feelings about. Last night when I was looking into how Verizon and Asurion handled replacements, I ran into so many stories of people being on their 2nd, 3rd, 4th, etc. refurb. I'm glad I'll get a phone that has the most support and flexibility, but I don't want someone else's leftovers.

 

[furbearingmammal]

If they let you keep it, good. Most of the time it's a 10-day return-or-pay policy, but who knows. Sometimes things work out.

And it's not the first. One of, yes, but I believe Tanknspank actually bricked the first Droid. If not home then one of the RS members.

Definitely one of THE first ones, though.

If the corrupted scripts in that package loosed on the UD forums really did this to your phone then we might be in trouble if the code ever gets released.

 

[eshdawg]

If they let you keep it, good. Most of the time it's a 10-day return-or-pay policy, but who knows. Sometimes things work out.

And it's not the first. One of, yes, but I believe Tanknspank actually bricked the first Droid. If not home then one of the RS members.

Definitely one of THE first ones, though.

If the corrupted scripts in that package loosed on the UD forums really did this to your phone then we might be in trouble if the code ever gets released.

Yes, I just read that they ask you to send back your phone in the package that your new phone arrives in. Likely no one will ever know what caused it, but why would the forum be in trouble?

 

[MotoCache1]

If the corrupted scripts in that package loosed on the UD forums really did this to your phone then we might be in trouble if the code ever gets released.

Fortunately that is almost impossible. The "best" damage a script can do is to remount one of the MTD mount points as the wrong thing and/or mount it read/write and wipe it out. The mbm and mbmbackup partitions aren't mapped to an MTD, so they are pretty well insulated. Now, if you'd like an SBF that will trash your mbm, just let me know. I won't do it, but I'd want to know that you wanted it.

 

[MotoCache1]

Yes, I just read that they ask you to send back your phone in the package that your new phone arrives in. Likely no one will ever know what caused it, but why would the forum be in trouble?

That's what I thought. I'd be shocked if they just let you keep the dead one. Oh well.

When he said "in trouble" he just meant from a "this could be a problem if there are scripts that can do this sort of damage" sort of way.

 

[furbearingmammal]

What he said.

Like a lot of things, we depend on a certain level of security, even as he hack our butts off. If someone found a way to violate that security -- a successfully faked signature that allowed custom data to be installed via the stock recovery image, or a way to disable/destroy/corrupt the bootloader without flashing SBF files intentionally -- there wouldn't be a safe Droid on the planet, more or less.

 

[Tanknspank]

And it's not the first. One of, yes, but I believe Tanknspank actually bricked the first Droid. If not home then one of the RS members.

HEY

No need to bring me into this

Sent from my Droid using Tapatalk

 

[furbearingmammal]

Wow...

Now if I say Beetlejuice three times, will that work too?

 

[MotoCache1]

Wow...

Now if I say Beetlejuice three times, will that work too?

I dunno, but since you brought it up, I'd love to know what Tank did to brick a Droid...

 

[eshdawg]

Just an update, I received my "like-new" droid today... Only problem is that it doesn't turn on... WTF. Won't be Tuesday until I get another due to the holiday.

 

[MotoCache1]

Just an update, I received my "like-new" droid today... Only problem is that it doesn't turn on... WTF. Won't be Tuesday until I get another due to the holiday.

Maybe swap batteries? I guess you got a refurbed D1 and not a D2.