Help!! I may have bricked my Droid

[nammysu]

Hey all,

So I rooted and installed 2.1. Worked great for a few days. Then I tried to use some apps that require root, but it wouldn't work. I tried opening a terminal to su root, but it would force close because Superuser Permissions wasn't responding. It seems like I lost root. So this is where I think I broke it. I re-ran the update.zip that I used to root it in the beginning. The phone still turns on, but I get a LOT of forcecloses when booting up. Everything forcecloses like Google voice search. It still kind of works, but it's really slow and crashes a lot.

Any way to get passed this without restoring from backup?

[R1Lover]

That's what backups are for, just do a restore and your all good.

[nammysu]

That's where I'm dead in the water.... I have no good backups.

[nerdbox08]

It's not a brick, the phone still functions.

There IS a way you can get it back to stock and start over.

Unroot/Unbrick your phone using .sbf

This is risky since this is the file that Verizon uses to fix what you've messed up, but since you took the plunge to do something that voids your warranty anyways(even if you can remove it, which you are trying to do) this can fix it.

I'm just passing along the information, I take no credit nor responsibility for this.

[Tanknspank]

That's where I'm dead in the water.... I have no good backups.

Had a problem last night with someone who didn't make a backup and we had to reflash his phone...

If that is what you wana risk doing then I can point you into the way of the thread too...

^Ha, he already put it up.

[nerdbox08]

That's where I'm dead in the water.... I have no good backups.

Had a problem last night with someone who didn't make a backup and we had to reflash his phone...

If that is what you wana risk doing then I can point you into the way of the thread too...

^Ha, he already put it up.

When these files became available, I did the while process just to make sure I could, even though I didn't need to.

The first time I went through it, I did it wrong and got no result, the second time I read the directions all the way through and it worked flawlessly.

In the event I really mess my crap up, I can save my phone. :P

Edit: I think I actually got the 2.1 .sbf when I saw it floating around....

[52brandon]

unless you fried the hardware, your phone is not bricked

with that said, flash an .sbf file using rsd lite, re-root and start over. Not the ideal situation, but thats why we make backups. There really aren't a lot of options on this one

[MJ5150]

I'll give you $100 for your bricked phone.

-Mike

[Tanknspank]

That's where I'm dead in the water.... I have no good backups.

Had a problem last night with someone who didn't make a backup and we had to reflash his phone...

If that is what you wana risk doing then I can point you into the way of the thread too...

^Ha, he already put it up.

When these files became available, I did the while process just to make sure I could, even though I didn't need to.

The first time I went through it, I did it wrong and got no result, the second time I read the directions all the way through and it worked flawlessly.

In the event I really mess my crap up, I can save my phone. :P

Edit: I think I actually got the 2.1 .sbf when I saw it floating around....

Yea, I just hate it when people have a problem, fear the worse, then it could be simply fixed by a backup that only every thread suggest you do before trying something...

I'll give you $100 for your bricked phone.

-Mike

We've already stated it's not bricked and how he could fix it... And it's not bricked if you can even turn it on...

[nerdbox08]

I'll give you $100 for your bricked phone.

-Mike

Don't be mean. The phone isn't bricked. You know better, don't take advantage of his ignorance.