Database Users

[Q] BRICK

My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.

Hey there,
I had something similar back when I tried to root my evo 4g the first time, what I did was go to the carrier store (in my case Sprint) and acted like one day just started to act weird and they replaced it for its "factory defects"
P.S. Some stuff I learned was that I damaged the usb port.
GOOD LUCK
Sent from my beloved EVO 4G

rpierce said:
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Click to expand...
Click to collapse
a trick to get into clockworkmod recovery, turn the phone off and plug into the wall, try to turn on....well not really try, turning on the power button should boot to cwm

I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.

Bricked in need of help
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.

Macificient said:
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Click to expand...
Click to collapse
U might try pushing the power button instead of the search button when the droid and exclamation mark are on screen. Hope that helps
TappaTappaTappa

sanjeeva7 said:
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Click to expand...
Click to collapse
U might have a corrupt file missing something... try downloading the sbf file from droidmodderx's website he's got sbf for froyo and gb
TappaTappaTappa

Did you upgrade through SBF, or OTA?
What is your bootloader version?
Sent from my DROIDX using XDA App

You can try the .602 sbf linux boot disk found HERE
It works every time for me and on any computer (that can boot from a cd)
D.

sounds like, judging by your bootloader version...you may be needing to find the 2.1 sbf, flash to that, take the OTA to gingerbread.... and you may have a little more luck with current roms once your bootloader is 30.0#

Just SBF. That will fix your trouble. Almost Impossible to "Brick" the DX.

[Q] ERR:A5,69,35,00,27 after SBF

This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App

Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.

what rom was the phone running when you had the original issue?

Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.

I have the same Problem with my Defy+ what can i do?

I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.

Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.

Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.

Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!

[Q] Droid 2 Bootloader after sbf

Okay, I had bricked this phone earlier when I screwed up the flashing of a custom rom, but figured I'd fix it when I had time. Now when I need it to work, it won't
I have flashed the phone a total of about 15 times (RSDlite, sbf_flash, ezsbf, everything), and every time it goes to the bootloader screen.
I tried factory resetting it from recovery. Recovery and Bootloader mode both work, but I can't seem to boot up the phone.
Once, the phone booted android and the welcome screen was shown, then it shutdown after 10 seconds.
Is there a key combination I can press to boot regular?
And have I maxed out the rewrites to the flash?
Any help would be appreciated

rhcp1253 said:
Okay, I had bricked this phone earlier when I screwed up the flashing of a custom rom, but figured I'd fix it when I had time. Now when I need it to work, it won't
I have flashed the phone a total of about 15 times (RSDlite, sbf_flash, ezsbf, everything), and every time it goes to the bootloader screen.
I tried factory resetting it from recovery. Recovery and Bootloader mode both work, but I can't seem to boot up the phone.
Once, the phone booted android and the welcome screen was shown, then it shutdown after 10 seconds.
Is there a key combination I can press to boot regular?
And have I maxed out the rewrites to the flash?
Any help would be appreciated
Click to expand...
Click to collapse
What sbf file are you using?

These
Albinoman said:
What sbf file are you using?
Click to expand...
Click to collapse
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf
VRZ_A955_2.3.20_1FF_01.sbf
and EZSBF 1KDStaz_D2_4.5.601.iso

There's a couple of us with this problem. See my thread just a few down from this. Not sure what is going on. I've tried everything, eventually just settled on buying a DroidX instead of waiting for a fix.

I can get to recovery and bootloader, the problem is it won't boot

Have the same problem, you should be trying to get back to an earlier SBF, if you upgraded to 2.3.4, give up, still has no solution, since the SBF 2.3.4 has not leaked voi

[Help!] Bootloop.

So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.

Charge battery with mcgyver metod or with other defy & reflash it with 231 sbf. For more info read: http://forum.xda-developers.com/showthread.php?t=966537

So, there's no other option out there?...

Deformat said:
So, there's no other option out there?...
Click to expand...
Click to collapse
Recharge battery with mcgayver metod and reflash sbf, you'll need start from scratch, because your bootmenu was corrupted and you can't restore nandroid or reinstall zip

Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...

Can't acsess anything
locn said:
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...
Click to expand...
Click to collapse
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi

Heddi72 said:
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi
Click to expand...
Click to collapse
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.

bootloader
corrinti said:
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.
Click to expand...
Click to collapse
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris

Heddi72 said:
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris
Click to expand...
Click to collapse
And your battery? Is it charged?

{NEED HELP}Phone wont boot

Okay, I've done all I know to try and fix my issue, now I must reach out for help. Okay, everything was running normally until I booted into SafeStrap 3.12 and tried to restore my backup. Before the restore I made the mistake of hitting Format system using mr-rf or whatever it's called. So I did the restore successfully but now my phone wont boot past the Motorola red circle. The SafeStrap boot menu pops-up but that screen is unresponsive. I try to select Recovery or Continue but neither work, it just tries to continue I guess but nothing ever happens. I can get to AP fastboot and try to flash the 4.0.4 or 4.1.1 fastboot files through RSDlite 6.1.4 but it gets stuck at the first thing it tries to flash, I think it's gpt_main0.bin it gets stuck at. I don't know what else to do? This is my company work phone and I'll be up crap creek if I cant fix this. I can even get into the stock recovery but nothing I try works. Oh, and in the fastboot files, I read somewhere that cI have to delete the lines with "oem" and "getvar" in them, so I did that but still no-go. Any suggestions would be great.!! TIA>>

Did RSD actually say that it failed at the step you are talking about? If not, I would try it again and let it go, no matter how long it takes, until it says the step failed or fastboot is complete. Go over to Razrforums.com and look up the "All things Root" thread in Razr M section. There are procedures for recovering with fastboot, and there are files there for JB and ICS. Good luck, and get back to us if you get things resolved.