I think I bootlooped /bricked my friends droid X.
I cant even reboot into recovery correctly it keeps sayimg "E:Can't open /cache/recovery/command"
Any help?
I'm not too familiar with this error, but it seems that maybe recovery was somehow removed.
I would recommend SBFing your friend's device.
If you've never SBFed a device before I would recommend following the steps I outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=1392025
when in doubt sbf. I find the easiest way is to use the linux cd. Do a search and you'll find the .602 version. good luck
Yeah definitely SBF
Related
Okay, so here is what happened:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fussion rom, but some how ended up with two rom managers. Anyways, I tried to reset my phone to complete stock, because I want a clean start to install a rom from.
I read the tutorial, but when I got to the part when I am supposed to flash "BL_D235...HSPart.sbf", the Start button is grayed out.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .spb I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
My phone is currently stuck at the default bootloader I believe. Black screen that says:
Bootloader
D2.37
Err:A6,70,70,00,1F
MEM_MAP Blank
Service Req'd
...
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Any help is greatly appreciated, my phone is just an over priced paper weight right now. Thanks a lot.
rhannahs19 said:
I got a Droid 2, and I am almost positive I had the latest OTA. I was trying to flash the Fission rom, but some how ended up with two rom managers.
I'm guessing that trying to install 2.2.20 over 2.3.20 has caused some issues. I tried to flash the .sbf I found of 2.3.20, but I get an error, "Failed flashing process. Failed flashing process. (0x7100); phone connected."
If I pull the battery and restart, I come right back to that screen.
Am I stuck, unable to finish flashing 2.2.20, but unable to flash 2.3.20?
Click to expand...
Click to collapse
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0 because the bootloader changed and won't accept the old SBF.
If you are having trouble flashing the SBF in windows then try it with THIS method. Make sure you download the SBF I provided in the tutorial because the one you have might be corrupt or not complete.
It's not a good idea to use ROM manager's for the D2 just yet afaik. If you don't have koush's bootstrap for the D2 than you are missing a vital piece of software for backing up and restoring your phone. If you came from the D1 forget (almost) everything you know. The D2 doesn't have an unlocked bootloader and thus has to be bootstrapped in order to work around this fact.
ROM managers might be useful for downloading but if you are going to install a ROM on the D2 I'd stick with Koush's bootstrapped clockwork recovery. I've never downloaded or even seen a ROM manager so if my info on them is completely wrong please correct me. But I have flashed plenty of ROMs on my D2 via koush's bootstrap and I have SBF'd about twice using linux and it's been easy sailing and I've never had any big problems.
Sorry if I'm rambling it's almost 2 in the morning and I have to be up for class at 8.
thanks, maybe its not a rom manager, but i installed clockworkmod, i guess maybe thats another bootstrap loader? i was very good at flashing winmo roms, this is a whole new game
newk8600 said:
There should be no problem flashing an SBF of 2.3.2 over 2.2.0 I did it and I didn't have any trouble at all. You just can't flash 2.3.2 over 2.2.0
Click to expand...
Click to collapse
You mean you cant flash 2.2.0 over 2.3.2 right?
burkechrs1 said:
You mean you cant flash 2.2.0 over 2.3.2 right?
Click to expand...
Click to collapse
Yes sorry I reread my post but I didn't catch that. You can't flash 2.2.0 after flashing 2.3.20 correct.
I, in a fit of stupidity, flashed ClockworkMod v2.5.0.8 on to my Droid 2 and now have that as my recovery screen every time I boot. I would like to return to the stock recovery, preferably in a simpler fashion than recovering from an SBF (which I have never attempted before). Does the stock recovery exist as something I can flash over ClockworkMod? Or can I simply uninstall the app or delete something in Files to revert to the stock recovery?
Why do you want to get rid of ClockworkMod?
Haven't tried it yet, but this might work:
http://www.droidxforums.com/forum/d...ding-help-removing-clockworkmod-recovery.html
FWIW, installing an SBF really isn't all that difficult - you just download and install RSDLite, obtain the correct SBF, and follow the directions (which are pretty simple). You will be back to stock in no time. You could always try the steps in the linked page, and if they don't work, you can try the SBF route. It's pretty hard to brick the Droid 2 irrecoverably.
The method you provided in the forum link worked for me (I was at first timid to try it because it was marked as Droid X but I'm quickly finding that they're really not so different), and I'm sure SBF would too have worked, and if nothing else I've at least learned how to do that as well should I ever need to. Thank you.
I downloaded rom manager and bootstrap on my droid x. I downloaded flyx rom and then after it was suppose to apply it after it booted, it became stuck on the logo, going from the "droid to red eye" over and over until I pull the battery. So every time I turn it on it does the same thing. I then tried to wipe my phone by putting it into recovery mode. It says can't open/cache/recovery/command. I tried to figure out the rsdlite solution but I couldn't figure out or find a good explanation on how to use it. My bootloader is 30.04. If there is an answer to this in this forum any where please point me to it.
flyx is an ancient rom for older version of android.
if doing a factory reset doesnt help, i suggest sbf. instructions here http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
Ok thanks, I thought I knew what I was doing but i'm pretty positive i failed ...I'll try this out then.
you're welcome. if you need any help with sbf or anything, dont hesitate to ask.
I was on Liberty GB v0.3.
So after installing a ROM via flashing with clockwork recovery (DSPmanager specifically, didn't work obviously). When I rebooted, I got stuck in a boot loop, nothing special... problem was I couldn't even get into recovery, no matter what I tried. The only thing I could get to was the bootloader, so I SBF'd to full 2.3.340. Didn't work. Tried flashing 2.3.340 system only, also didn't work.
This is the bootloader error:
Code:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
...
How screwed am I? Is there any way I can fix this?
Are you using a Windows' machine to SBF the phone, via RSD Lite? If so, try using a Linux (Ubuntu) machine to SBF your phone. I got an error message myself while trying to SBF my phone on a Windows 7 machine. Tried updating drivers like 7 times to no avail. However, when I SBF'd using Ubuntu, BAM!, no issues. Here's a video to help you out.
http://www.youtube.com/watch?v=jswEsHJ8GdU
theres almost no way you can actually brick a dx since we cant flash radios or kernals, but only "soft" brick. nothing a sbf cant fix, but as the post above suggests try it on ubuntu, its so easy to get
I've gotten that error a few times using Win7 as well. I just unplug the usb and try again, usually the second or third try works fine for me.
That error occurred when I flashed an older system version. Redownload the file and make sure it is for bootloader 30.04
I have SBFed using a Linux machine before, but don't have one handy. Is is possible to SBF from Ubuntu if I just boot the OS off a disc or do I need to do a full install of the OS?
I was starting from rooted Froyo on the Droid 2 and used Koush's bootstrap to update to Gingerbread.
I downloaded the following file to do the update: Monster_2.3.3_4.5.573_updater_Rooted.zip
I think this file was corrupted, becase the update aborted, and now I am stuck at the recovery screen. I cannot do ANYTHING. I'm so fearful that I have bricked my phone.
I used RSDLite to try to sbf the bootloader, but no luck. I tried the 235 and the 237 bootloaders, but I keep getting a "Critical Error FEBE 0047" on the phone, and RSDLite says there was an error with the JUMP command. I have no idea what this means.
Guys, I really can't afford a new phone...can anyone PLEASE help me through this:/