• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bricked it. Yay/sarcasm.

So, I was trying to manually install the gingerbread OTA and ran into a few snags. I was missing a few core apps that I uninstalled when I rooted. Well I first was missing the blockbuster one, so I found the apk for that and the apk for the madden one cause i figured i might as well get 'em both so that's what i did. Tried again, got stock with yet again another missing apk, this time it was skype. So i downloaded every skype there was and even the original apk. This time it said my framework-res was missing. That's not possible since that was essential to the phone. But I found the original online and over-wrote it and rebooted. Endless bootloops. Took it to verizon and they said I killed it. :(

PS: Keep in mind I had to re-root and un-root every time i had to install one of those system things. So i think its what killed it.

Now verizon is sending me a certified X in the mail to take place of the one i bricked.

My question is, will they be able to tell I was messing with root and the file system? I couldn't get the phone past the android screen.

(I didn't know if this should go in root or general, so it's here, sorry for putting it in the wrong section if I did)
 
My question is, will they be able to tell I was messing with root and the file system? I couldn't get the phone past the android screen.

(I didn't know if this should go in root or general, so it's here, sorry for putting it in the wrong section if I did)

I just filed a warranty claim on my DX, it would re-boot at will, usually when a power cord was plugged in. They were real specific in asking if my phone was rooted, and said that if it was they would charge me $199 for the warranty replacement phone.

WHO KNOWS if that was true, but of course I was rooted, and of course I flashed it to the original OS before sending it back.....and it was still rebooting after I removed Root - so, Root had nothing to do with my troubles.

Your replacement phone will likely be no better, and might be worse than the one you have. It will be a certified refurbished phone. Search this site, you will see what it takes to fix your phone.
 
Upvote 0
I bet with 99% confidence that you're not bricked and that we can get your phone running again

Well, seeings as the SBF file is going to take an hour to download. I'ma head to bed. I'll mess with it in the morning and let you guys know how it works.

I'm all excited about "flashing" my phone. I always thought it was going to be a pain and a difficult process but now that i read up on it and have most of the stuff on my computer, It seems rather easy.

Thanks for all you guys assistance!
 
Upvote 0
if your stuck in bootloop

hold home and power to turn on the device, but continue to hold home til you see the exclamation droid, and then hit your search button, wipe your data and cache, and your phone should boot up within 5 minutes

I tried that.

Also, now I have RSD Lite, and the sbf, but I keep getting "Failed flashing process. (0x7100); Phone connected."

Whats that mean?
 
Upvote 0
I tried that.

Also, now I have RSD Lite, and the sbf, but I keep getting "Failed flashing process. (0x7100); Phone connected."

Whats that mean?

Same thing happen to me. I ended up having to rename the SBF file to dx2.sbf and it worked great. There are a few threads about it.



I saw one poster that mention to rename it to dx1.sbf, dx12.sbf, dx123.sbf and so on until dx12345.sbf worked for him.

a different thread but its the same concept just explained really well.
http://androidforums.com/droid-all-...ailed-flashing-process-0x7100-rsd-lite-2.html

Little confusing but it worked.
 
Upvote 0
Are you using Windows 7 on your computer? Sometimes Windows 7 and RSD Lite don't get along very well together. I had the same problem and had to go to Windows XP. When I switched to XP, it worked just fine

I'm using Windows 7 Home Premium, Yes. I have an XP machine that I may try it on.

Is RSDlite recognizing your phone? Also are you manually putting your phone into bootloader mode?

Yes, it's recognizing my phone. It says It's connected and gives me the details on it.

Same thing happen to me. I ended up having to rename the SBF file to dx2.sbf and it worked great. There are a few threads about it.



I saw one poster that mention to rename it to dx1.sbf, dx12.sbf, dx123.sbf and so on until dx12345.sbf worked for him.

a different thread but its the same concept just explained really well.
http://androidforums.com/droid-all-...ailed-flashing-process-0x7100-rsd-lite-2.html

Little confusing but it worked.

If XP doesn't work, I'll try renaming it. :) I'll let you guys know what happens.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones