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

Root Am I screwed until SBF is available?

Himself2006

Lurker
Sep 10, 2011
4
0
Just got my first ever Droid yesterday and attempted to follow my friend's advice to root it - well that went smoothly. Then I attempted to do the next step of removing the Bloatware and this is where my f'ing noob/stupidity kicked in and I apparently deleted some important file which caused me to receive Force Close errors when I tried to add/view my contacts. I started reading around on the forums and saw where people suggested to fix it by downloading the System/Apps Dump folder (which I did from TBH) but after moving the files to my SD card and then using Root Explorer to copy/move the apps into the System/Apps folder on the Droid it started spamming FC errors again so I took out the battery and put it back in and now it's stuck on the reboot loop.

Really hoping I didn't just throw $260 down the drain and I don't have the money to fork out for another Bionic/smart phone - can't go back to my old phone either since it was basically dead and that's why I went with a new phone...

I know this can be fixed once the SBF file is released/determined but I've never had a Droid and not sure how long this process can take...

Any advice other than to not be an f'ing idiot?
 
I've done a full factory reset/clear cache from the Recovery boot and no luck, it gets stuck before the Droid eye appears in the boot sequence, freezes just after the word DROID appears on the phone.

I had deleted like 14 files but not sure exactly without having my phone back on and it was a delete, not a rename (I've since learned my lesson and plan to buy TiBu Pro to freeze files for future once I get this resolved...lol)
 
Upvote 0
I've done a full factory reset/clear cache from the Recovery boot and no luck, it gets stuck before the Droid eye appears in the boot sequence, freezes just after the word DROID appears on the phone.

I had deleted like 14 files but not sure exactly without having my phone back on and it was a delete, not a rename (I've since learned my lesson and plan to buy TiBu Pro to freeze files for future once I get this resolved...lol)

Ive rooted my droid x and never felt the need to delete files...im sorry that it inst working. hopefully you can figure something out. im about to try to root mine....
 
Upvote 0
I've done a full factory reset/clear cache from the Recovery boot and no luck, it gets stuck before the Droid eye appears in the boot sequence, freezes just after the word DROID appears on the phone.

I had deleted like 14 files but not sure exactly without having my phone back on and it was a delete, not a rename (I've since learned my lesson and plan to buy TiBu Pro to freeze files for future once I get this resolved...lol)

If you're able to get adb to work with your phone in its current state, with the help of someone who knows how to, I think you could potentially reinstall the apps you deleted
 
Upvote 0
If you're able to get adb to work with your phone in its current state, with the help of someone who knows how to, I think you could potentially reinstall the apps you deleted

Yep.

However, I've done a lot of app development and debugged my apps while my phone is connected via the ddms debugger. I've watched the ddms screen while my phone boots-up, waiting for the adb connection to appear so that I could start seeing the debugging messages. Well, on the Droid X, my phone doesn't appear in the ddms window (indicating the adb daemon is alive) until looooong after the phone has passed the M logo, the red Droid eye, the lock/unlock screen, and the notifications that the SD card is being mounted.

I also just did a test (using my Droid X--not a Bionic) where I did an "adb devices" from the Windows Prompt (DOS command line) continually while my phone rebooted. Its not good news: the M (Motorola logo), red Droid eye, lock/unlock screen, and SD notifications come and go and its still about 10-15 seconds after that that the adb client on my PC is able to "see" (connect with) the adb daemon on the phone.

Chances are slim that the boot has gotten far enough for the adb daemon to be started...(but it can't hurt to try).

Good luck.
 
Upvote 0
I wonder if the fact of booting into the tools choice the last selection in the bootloader/recovery choice menu, makes a difference of when the phones shows up for adb devices.

again I am no real dev of any kind but besides the D3 and now the bionic i do not belive we have had these options under bootloader/recovery before in a phone and maybe the tools option has something to do with it.

If anyone with a bionic that is in a boot loop can try to access adb devices in a bootloop following the OP link to the xda droid 3 site and you can get it to work not only would you have a way to repair your phone but we all would if we screw it up.

If anyone in a bootloop would like some help with the instructions I can be of assistance but again I am not a dev so my knowledge is limited
 
Upvote 0
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