FORUMS

Google No Longer Sending Calendar SMS Notifications

In a not entirely surprising move, Google announced that it’s putting an … more

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

Android M Preview Images – XDA TV

Android M preview images are available. That and much more news is covered by Jordan when he … more

Need help.. Bootloader Err:A5,70,70,00,1F

Thanks Meter: 0
 
By anducly, Junior Member on 23rd November 2010, 11:23 PM
Post Reply Subscribe to Thread Email Thread
26th March 2012, 06:46 PM |#31  
sd_shadow's Avatar
XDA: ASSIST
Recognized Contributor
Flag South Dakota
Thanks Meter: 2,738
 
Donate to Me
More
you just have to wait till
a: someone finds the new SBF
b: someone finds a milestone SBF that is compatible
 
 
18th April 2012, 06:09 PM |#32  
Junior Member
Thanks Meter: 0
 
More
Same issue!
I am experiencing the same issue as the gentleman who posted his:
Bootloader
D2.37
Err:A5,70,00,00,23

Battery OK
OK to Program
Connect USB
Data Cable

It's really annoying because my warranty is over and the download was automatic to my phone.. and now it doesn't work. Sigh.
18th April 2012, 06:38 PM |#33  
sd_shadow's Avatar
XDA: ASSIST
Recognized Contributor
Flag South Dakota
Thanks Meter: 2,738
 
Donate to Me
More
first try battery pull
next install update, from recovery
you might be able to SBF, if it doesn't say MEM-MAP Blank error

if those fail, there is a fix for D2G, hopefully someone will use the same method
to create a fix for D2
[How-to]unbricking downgraded 629 & root normal function OTA 629
22nd April 2012, 03:57 PM |#34  
supergear's Avatar
Senior Member
Flag Aurora
Thanks Meter: 49
 
More
There will be no fix. Once you bricked your phone you're screwed. Droid 2 is dead and unsupported by anybody. Time to move on to a new phone once you bricked the Droid 2. Sucks but Droid 2's life is over
22nd April 2012, 04:45 PM |#35  
sd_shadow's Avatar
XDA: ASSIST
Recognized Contributor
Flag South Dakota
Thanks Meter: 2,738
 
Donate to Me
More
all that is needed is a new SBF, just have to wait till it's found
24th April 2012, 01:02 AM |#36  
Albinoman's Avatar
Senior Member
Flag Seattle
Thanks Meter: 906
 
Donate to Me
More
Quote:
Originally Posted by supergear

There will be no fix. Once you bricked your phone you're screwed. Droid 2 is dead and unsupported by anybody. Time to move on to a new phone once you bricked the Droid 2. Sucks but Droid 2's life is over

I find that offensive...I still support the Droid 2. Its life isn't over yet!

Sent from my DROID2 using xda premium
24th April 2012, 01:09 AM |#37  
sd_shadow's Avatar
XDA: ASSIST
Recognized Contributor
Flag South Dakota
Thanks Meter: 2,738
 
Donate to Me
More
at least uninformed
12th May 2012, 07:09 PM |#38  
Junior Member
Flag Dubno
Thanks Meter: 0
 
More
Help! After a rollback to the stock firmware 2.2 through 2.3.4 RDS Lite, Motorola Droid 2 has stopped working, but you can bootloader on, it gives error:

Bootloader
D2.37
Err:A5,70,70,00,1F

MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
14th May 2012, 07:14 PM |#39  
Junior Member
Thanks Meter: 2
 
More
You'll have to wait till the 2.3.4 sbf files are released until you can fix it just like everyone in this thread has stated several times. You're better off just getting a new phone like I did.
16th May 2012, 08:16 PM |#40  
Member
Flag scottsdale,az
Thanks Meter: 53
 
More
i have the same issue i posess the sbf but my phone wont read in rsd anymore ...anyone have any ideas
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes