Database Users

I think i just bricked

i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen

slowcurve said:
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
Click to expand...
Click to collapse
I just replied to your email, you efused!
This is exactly what happened to me when I bricked my gf's first bravo.
Good news is sbf and its fixed. You wont even lose any data.
IDK how this happens, seems it has happened twice now, there must be a specific change made before bootstraping that causes the check.
Either way the code group that is problematic is in the sbf, flash it and your good.
you will need to reroot, rerun nonmarket apps enabler, and re-bootstrap recovery, then reboto recovery and flash rc2 and you will be fine.

sorry for the spam... i panic'd..
i have the rsd lite i searched for sbf's and a whole bunch came up mind pointing which one i should use.
Edit: Its fixed thank you bando, you own half of my soul

[Q] Help Please. Can't mount cache, boot, or detect device

I have a Motorola Defy, and I'm a noob. I was trying to install Cyanogen Mod 7 on it, but something went awry, and here's a little about the situation. I'm using Motorola USB Drivers 4.9.0 and RSD Lite 5.3.1. I'm using a PNY 16 GB class 10 microSD card. I no longer have the stock 2 GB card. I flashed 3.4.2 177-5 Nordic onto the phone. I always forgot to put my phone into recovery mode before ever flashing these different sbf files. Nordic worked fine except it said the sd card was always unmounted even though it was plugged in. I couldn't do much which that so I flashed 2.2.1-3.4.2 107 T-Mobile US onto it (again not from recovery) and the sd began working again.
I allowed usb debugging and rooted with Superoneclick 1.9.5 ShortFuse and installed 2nd Init for Defy. I restarted it twice and then turned off usb debugging. I booted into 2nd Init (not 2nd boot), went to install zip from sd, and opened the cyanogen_jordain-ota-beta5.1.zip file. I then installed Google apps 20110613 and wakeup_fix.zip. I know this is stupid but I wasn't reading the output for each step, but I think I remember it saying that it was updating for the cyanogen. When I wiped the cache and the data, it said things like:
E:can't mount /dev/block/mmcblk1p24
(Invalid argument)
E:Can't mount CACHE:recovery/command
E:Can't mount/dev/block/mmcblk1p24
(Invalid argument)Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
(Invalid argument)
Now it's stuck on the Motorola boot logo, except it'll still enter 2nd Init boot menu.
It also could not read anything from the sd card including Cynanogen for the second time until the next day after I put the sd card into my computer and viewed it. So now it can read from the sd card again. I have no backup.
I tried reflashing it, but when I put the phone in stock recovery, no device is detected, however, my computer does recognize something's plugged in by that noise the system makes whenever I plug or unplug it. I tried using ADB shell to mount the cache on recovery mode but no luck. It says no device detected. I might not have been doing that right.
I may be forgetting some information because I tried fixing it very late last night.
I don't own very many nice things, but this is one of them, and I'd really like to get it running again. Any help will be very appreciated. Thank you all for reading my post-
Kibogami

whats your email address so i can send u the original sbf

While u boot hold vol up button ull see bootloader n connect to pc
Rsd will recognize...
Sent from my MB525 using XDA Premium App

Thank you. That worked, and the phone went into bootloader mode. RSD Lite recognized it, and then, I flashed 2.2.1-3.4.2-107 T-mobile US. After I flashed it, though, I had to manually power it up. RSD Lite said finished, but now, it's stuck in a bootloop. It shows the motoblur animation, and then, the T-mobile animation and keeps repeating the 2. So I let it do that for a little while. I went to bootloader mode to flash 2.1, but it says battery too low to program, and RSD won't recognize it.
Thanks again
Kibogami

when you power up your phone go into factory recovery vol- and factory reset should boot up fine

Ok. Got everything back to normal. Thanks again everyone. I charged my phone with the wall charger for a little while, and that got things moving again. I went to bootloader, flashed 2.2.1 again with RSD Lite, did a factory reset, and was good to go.
Does anyone know about why CM7 didn't install properly in the first place?
Thanks

the cm7 zip file also flashes a new recovery sometimes you have to reinstall cm7 from the new recovery essentially install once reboot into recovery and repeat works fine have had the same problem myself a while ago anyways glad i could help and enjoy!!!!

having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect

jsteve01 said:
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
Click to expand...
Click to collapse
Open RSDLite with administrator priviledges, make sure it is the latest RSDLite and moto drivers (6.1 I think).

[Q] Stuck at bootloader screen

So, I've exhausted just about every bit of time looking, searching, and trying everything to get my Droid 2 back working again. I'll explain everything I've tried plus the current error messages I'm getting and see if someone else can help.
Before we start, yes, I do have the current moto drivers (plus old drivers too). Yes, I've uninstalled, reinstalled the drivers and RSDLite a million times, and yes, I've rebooted after installing everything to make sure that wasn't the problem.
Right now, I've flashed the bootloader back to d2.35. But I can flash back to d2.37.
Using RSDLite, every time I flash it doesn't make it past the BP pass through mode. Right as soon as it gets to it, the computer disconnects the phone, and on the phone is says:
SW update...
Complete
And when it reboots it is still at the bootloader screen. I load into recovery, and it tells me that:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
Once I wipe cache/factory reset, I reboot and it still goes to bootloader screen.
So, I load into recovery again, and this time it gives me the error:
E: Can't open /cache/recovery/command
I've used RSDLite 4.7+patch and flashed, same thing.
I've used RSDLite 4.8/4.9/5.6 and so on, everytime, same thing.
I've burned the Linux iso to disc, booted that up, and flashed that way, same results.
I think that pretty much sums everything up. I've searched every forum, I've googled everything about the phone known to man. Usually I just silently lurk the forums since I've never encountered a problem flashing any other phone, but this one has me stumped. Thanks ahead for any information.

What is the name of the sbf you're trying to flash?
Sent from my EncounterICS droid 2

VRZ_A955_2.3.20_1FF_01.sbf
size unpacked: 455,586,301
packed: 253,561,045

Ok and what were you trying to flash when it broke?
EDIT: that is the correct sbf but you might want to check the md5
Sent from my EncounterICS droid 2

Yea, check the md5. Also, try to manually mount it in the linux terminal.

I'll check the md5 tonight, didnt think about that. And what was i trying to flash..? And mount it in a linux terminal?
Sent from my SCH-I400 using XDA App

The only md5's I can find of the file to verify it with say that it's incorrect. I'm trying several different downloads now to see if I can find one that matches. Anyone have a working sbf that I can check my md5 with theirs just to make sure?

http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
That's where my SBF's come from whenever I need to go stock. Never had a problem with it before.

MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?

I'm not sure exactly. I've never used RSDLite. I've only ever flashed on Linux.
Are you able to wipe Dalvik cache just to be sure? Also, just as a fail safe, if you have an SD card in there take it out.
Here's what I found:
Computer engineer here. Registered so I could post this and hopefully help a few of you guys out
I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:
Code:
Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyoþÿÿÿ‚qawñrawðiµ was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.
So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.
Here are step by step instructions:
Go to the folder where you installed RSD Lite
Delete any files that start with "FlashErrorLog"
Right click on "SDL.exe" and click "Run As Administrator"
Move your recovery file to the root C:\ directory
Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
In the RSD Lite folder, open the newly created FlashErrorLog... file
Count the number of junk characters after the real filename - for example if you have this error:
Code:
ERROR: \\?\c:\r.sbfqawñraï was not found.
then the junk characters are "qawñraï" and there are 7 of them, so we are going to add 7 extra letters to the real filename
Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
Point RSD Lite to the renamed file, click Start, and it should work!
Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.
Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
Click to expand...
Click to collapse
I hope that works for ya. Different phone, but same idea.

How do you wipe dalvik without clockwork recovery mod?
Sent from my SCH-I400 using XDA App

Try this tool
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
It works 100% of the time for me. As long as you can get to the bootloader screen (by pressing the up button on the hardware keyboard while powering up), it will work. Please try it and let me know how it works for you. You will need a blank CD
Sent from my DROID2 using XDA App

I already tried that. It didnt work for me. Still get the same error messages as i stated in OP and after i wipe data it still boots to the bootloader.
Sent from my SCH-I400 using XDA App

ripdarkness said:
MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?
Click to expand...
Click to collapse
read
http://droid.koumakan.jp/wiki/SBF
it's for the 2 global but should still work
also try deleting rsd lite error log
program files/motorola/rsdlite/ flasherrorlog11_15_24_45.log
yours will be different

Yeah, I don't know what it is. I think it's pretty much bricked. Nothings worked, and nothings even remotely came close to fixing it. I've tried everything. The only thing I notice is as soon as it hits BP pass through, the phone gets disconnected, and it doesn't reconnect till the phone reboots after saying:
SW update...
Complete.
And then it reboots into bootloader. So whatever it is, it's something to do with that.

Step 2/2 Installing - Update failed - Bricked?

Hi there!
I tried to update firmwmare with lots of different ROM's (B135,B136,B162,B517,B522) but always getting "Update failed" at Step 2/2 - Installing.
Is this phone bricked?
I cannot access internal card.
Any ideas before i threw it away?
Update: On sdcard i am getting error in file: sd_update.log
notes: (dld_file_ptr != -1) !
dload_sd_file_data_proc-(dld_retry >= DLOAD_RETRY) failed!

Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App

As long as you have a working pink screen, anything is solvable .

I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!

update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App

Maksimitoisto said:
update the original version you had before custom roms. update without battery. plugin power cord.
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.

mesnati said:
I do have pink screen and blue screen. I tried to mount internal with vmware ubuntu. But cannot mount it. It doesn't show up at all Don't know how to mount it.
Any ideas or help would be appreciate! Thanks guys!
Click to expand...
Click to collapse
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App

mesnati said:
Hi!
Thanks for try helping me. But as i said earlier. I tried with all official ROM's but stuck at step 2/2. Always getting update failed.
Click to expand...
Click to collapse
Also tried without battery. It is the only way to update. With battery cannot go further from "step 1/2 Unpacking"

julle131 said:
Try mounting internal throught ubuntu in pink screen. Then Put b138 there, remove anything else from internal. Then remove battery from phone and put it to charger. Then start update. If it fails, start it again. After that go to recovery and do factory reset.
Sorry for my english. Im in a bit hurry.
from my Desire HD using XDA App
Click to expand...
Click to collapse
How to find device to mount? dmesg show me nothing.
Any help would be helpful

[email protected]:/home/xxx# lsusb
Bus 002 Device 002: ID 12d1:1035 Huawei Technologies Co., Ltd.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
I can see device with "lsusb" but cannot mount it
Anyone?

julle131 said:
In development section, blefish has tutorial to get usb in pink screen back.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks julle!
But seems to me that you don't understand the problem.
Here are the steps from blefish:
1 Download update-B518-bootloader.zip from MediaFire.
2 Save it to the root of your SD Card.
3 Start the phone in recovery mode (recommended recovery is 5.5.0.4)
4 Select "install zip from sdcard"
5 Select "chooze zip from sdcard"
6 Select the zip you downloaded before.
7 Select yes.
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.

Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode

mesnati said:
I am already STUCKED in step 3. Because i do not get to RECOVERY MODE!!!
I am having only PINK screen (VOL +, VOL -, power button) and BLUE screen (VOL +, power button). That's it!
And CANNOT access to internal card on Windows neither on Linux Ubuntu.
Click to expand...
Click to collapse
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
mesnati said:
Guess Huawei officials has USB drivers to access internal card on Windows or Linux but they don't share them with us
I have android_winusb.inf driver but cannot install it and recognize device in pink or blue screen mode
Click to expand...
Click to collapse
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).

Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App

julle131 said:
Sorry, but im running out of ideas. It seems you have bootloader locked, and without recovery we cant unlock it... what happens if you install official 2.2 and after error try to install it again? We must get the bootloader unlocked.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You are making me laugh )
I cannot install NOTHING!!! That's the main problem

qwerty12 said:
I got the blue screen when I accidently forgot to put boot.img back in its place on the image partition.
My hypothesis is, based on that, the first UPDATE.APP (the smaller one) changes the partition layout (which would delete all the files), while the larger UPDATE_G.APP starts installing all the files: /system but - more importantly - the image partition where boot.img, AMSS.mbn and recovery.img are stored. If the update did not take, then they won't be there and the bootloader can't start them up. In my case, I was able to mount the image partition in Linux and put the boot.img back. Hopefully I'm talking out of my ass. :\
Ah! I was able to mount the partition in Linux because I'm using the B512 bootloader; you must have the B540 bootloader (or whatever is its equivalent for the U8800). I guess Huawei's laissez faire attitude towards rooting (you could browse / from the computer!) is going away now that they're moving into the big time (deals with AT&T, the Honor etc.). I don't know how you can downgrade if you can't boot to something like recovery.
Actually, these work: http://www.mediafire.com/?j33yo9wy9bspm86
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
You are right!
So the device should be bricked now? I cannot give back to warranty 'cause i already did it once If i send also this one they will laugh at me and of course they will not give me another phone

But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?

mesnati said:
But after i installed those drivers you've attached i am getting no more exclamation mark in Device manager. hmmm. Please look at attached pic. What now?
Is there a chance to getting to device through hyperterm or something?
Click to expand...
Click to collapse
qwerty12 said:
But you can't ADB from the bootloader (or use them to mount a partition); it's for running Qualcomm QPST (though I couldn't figure out how to get it working).
Click to expand...
Click to collapse
Actually, I haven't tried HyperTerminal on the COM ports/modem - maybe it could, somehow, let you do something? Changing the USB mode would be great...
If you do figure out QPST, you'll need the firmware in a form it can understand - maybe you'd have to get another device to dump its firmware...
Regarding warranty: Couldn't you make the case that it was an official firmware update that caused your phone to brick?

mesnati said:
You are making me laugh )
I cannot install NOTHING!!! That's the main problem
Click to expand...
Click to collapse
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App

julle131 said:
I am bad in english, so it might be the problem cant express my self right. I know it fails, but run it again after the fail. I am hoping it unlocks bootloader. Then you can access the phones whole memory from ubuntu.
Someone, if you understand this sh*t im writing, please translate it to real english
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Your english is ok I tried 100 times after it fails and every time same error appears "Update failed"

R2D2 - Bootlooping, SBF failed 0x70BE

Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!

http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html

Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!

ezsbf has helped a lot of people
Sent from my MB870 using xda premium

so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas

Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2

did you try wiping cache or data?

delete this

jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up