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

Root I think i did something terribly wrong...

I was following the "From Stock 2.0.1 to Bugless Beast ROM (for beginners)" Guide and i guess somewhere along the process i did something terribly wrong.

My droid is now stuck at the Motorola logo from the boot screen. It doesnt loop it just stays there. I've tried going to the recovery screen and using my old backup but it doesnt seem to be working.

Anyone have any idea what i did wrong, or how i can fix it? Any help would be greatly appreciated.
 
This just happened to me, too. It turned out the battery was very low AND I had accidentally chosen to install the update.zip from 2.1 instead of 2.01 like I had intended.

I don't know exactly what went wrong, but I left the thing on the charger for a while, then started it with the "x" key so that it would go back into the utility that allowed me to restore the backup I had just made of my previously freshly rooted install.

Whew! That worked. I decided I would go with the "clean" start; I've installed the 2.01 ROM and just for fun I'm going to try the 2.1 ROM. It's fairly easy once you know the steps...so I can't resist. ;)

Did you try the ROM or update.zip method?
 
Upvote 0
Well, let us know what happens. I figured if worse came to worse I would pop out the micro sd card and manually replace the possibly corrupted backup with the version I copied to my computer and restore from there.

PS: Lessons learned: definitely BACKUP! Do not skip that step. And watch to make sure your battery level doesn't get too low. (Elementary, I know.)
 
Upvote 0
How are you charging? When the battery gets extremely low charge from a wall outlet instead of USB. Much more effective. One way I have gotten out of a "sbrecovery loop" (after a full charge) is to turn the phone off, do a battery pull (always give it a couple of minutes when doing a pull), remove the SD card, and boot (you will get an error). I then shut down the phone, reinstalled the card, and for some reason (maybe just my luck) it rebooted fine.
 
Upvote 0
I left my phone charging all night and apparently it didnt work :/

I'm currently trying to just reset the phone by using RSDLite and the .sbf file but when i connected my phone it said the battery was too Low.

Are you charging from the wall outlet? Once again, don't use USB from your computer to charge when the battery is that low.
 
Upvote 0
Was the phone turned on during the charge (I believe the Droid needs to be in an "On" state to successfully charge.
Mine charged just fine completely off so I don't think that is the issue, but I don't know for sure. I would pull the battery, wait a minute or two, put it back in and leave it off while connected to the charger and see if that works any better.
 
Upvote 0
Yeah that worked. :D Battery is high enough to use RSDLite and the .sbf file but its not working.

I hit start and a message showed up saying "Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected"

It also gives me a "Platform is not defined for CDMA_TYPE-MSM6800_CHIPSET" in the status section when i first plug it in...


I think im the unluckiest droid user ever >_>
 
Upvote 0
Yeah that worked. :D Battery is high enough to use RSDLite and the .sbf file but its not working.

I hit start and a message showed up saying "Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected"

It also gives me a "Platform is not defined for CDMA_TYPE-MSM6800_CHIPSET" in the status section when i first plug it in...


I think im the unluckiest droid user ever >_>


U ever get up and running? I was thinking grab another nandroid image , or maybe Virgin OEM. Make sure the first thing u do is wipe, then try a recovery.
 
Upvote 0
I had to go with RSDLite 4.6 as well, but still didn't work on my Win7 64. Worked fine on a win7 32 bit. Got rid of the Platform not defined OMAP error and the flash failed error. Dunno, just different combinations of hardware and software seemed to do the trick. Hope this helps someone not spend 5 hours searching for answers like me.
 
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