Root Flashed rubiX Blurry 1.6.3, bootlooped, tried SBF and bootlooped - holy %#@*!!

[t0adman]

Well I kind of figured it was only a matter of time until this happened so I downloaded the SBF and the RSD Lite v4.8 ahead of time.

I've flashed several ROMs successfully and just today decided to flash the rubiX Blurry 1.6.3, which I verified on the post was NOT for the recently leaked Froyo.

I launched boostrapper app, booted into it, backed up the current ROM (rubiX focused - newest non-leaked), wiped the cache, installed the rubiX Blurry from the zip file, same as I'd done on all previous ROMs. It loaded way to quickly and then went into a bootloop.

So, I put the phone in Boot Loader mode and started the SBF process. I started up RSD Lite, plugged in the device, it was recognized, I browsed to VRZ_MB810_2.3.15_1FF_01.sbf and clicked start. It creates the image then boots the phone but during that process it never gets past the boot animation. I'm now at Status: Please manually power up this phone with Progress at Executed: 100%. The power button does nothing when pushed or held. Unplugging the phone from the USB and pushing the power button does nothing. Pulling the battery and powering up gets me back into the droid - robot eye boot loop.

Holy crap did I really brick my phone? Wow...

 

[BuTbKa]

recovery mode, wipe data/cashe. Thats the first thing you want to try

 

[dhoffman1421]

Is your phone charged? Have you retried it from scratch?

 

[t0adman]

Please explain how to accomplish both of those suggestions. Sorry guys, I know enough to be dangerous and that's about it. Thanks!

Phone is at about 80-90% charged.

From Koush's site:
What if my phone won't boot? How do I get into recovery without the app?
When the hijacker runs, it will automatically create the "/data/.recovery_mode" file after it finishes. This tells the system that the next time it boots, it should boot into recovery. But, when the system starts, the Droid X Recovery Bootstrap will then delete that file when Android is fully started, to prevent you from booting into recovery. So what does this mean? If you fail to boot, simply pull your battery, and your next boot will be into recovery (unless your /system is *really* hosed, in which case you need to SBF).

I think I'm *really* hosed.

 

[eulerphi8]

As you're powering up, hold the power and the home button. That should take you into recovery mode. Wipe data/cache should solve everything. SBF does not delete your data files, which is why it is bootlooping.

 

[BuTbKa]

Pull out your battery, put it back in power back and hold home button, when you see little droid press search button, then choose wipe data/cashe now by pressing camera button

 

[t0adman]

Outstanding - thanks guys. Now that I'm back into the stock OTA do I need to re-root in order to run Bootstrapper and get back into my saved ROM backups?

 

[BuTbKa]

yes, I use this all the time:
[APP]SuperOneClick v1.5.5 (Root, Unroot, Enable Non-Market App, Get UNLOCK code) - xda-developers

 

[t0adman]

yes, I use this all the time:
[APP]SuperOneClick v1.5.5 (Root, Unroot, Enable Non-Market App, Get UNLOCK code) - xda-developers

Very cool. I'm running it now and it seems to be sitting at OK ... Running rageagainstthecage...

How long does it usually take with that app?

 

[BuTbKa]

about 5 minutes.

 

[BuTbKa]

if it stock on "waiting for device" for more then two minutes, you might need to turn off your device and then turn it back on while it still plugged in

 

[t0adman]

Hot damn I'm back in business. Thanks to everyone (esp ButbKa) for the quick help. I knew I could count on the great people that contribute to this community. Phew!

 

[dhoffman1421]

Good tips indeed, need to remember these myself. Glad you are back in action!

 

[BuTbKa]

Everything I know about android I learned here....glad I can pay back to community