So I'm not familiar with Motorola devices. My wife has a Razr M on System Version 98.18.78.XT907.Verizon.en.US. An update recently came out for it and she is trying to update to it, but the update keeps failing (Android with red exclamation mark). Her phone doesn't have the Super User app on it, but it does have Titanium Backup, which says it has root access, so I'm assuming some system apps got removed. On my HTC devices I would normally run the RUU for them to reset them completely and then take the update, however I can't seem to find an RUU for the Razr M. Does this not exist? Any suggestions on how to get the OTA for her?
Sorry, I can't seem to find any info on this. The phone seems to be a dead end phone...
Nagrom Nniuq said:
So I'm not familiar with Motorola devices. My wife has a Razr M on System Version 98.18.78.XT907.Verizon.en.US. An update recently came out for it and she is trying to update to it, but the update keeps failing (Android with red exclamation mark). Her phone doesn't have the Super User app on it, but it does have Titanium Backup, which says it has root access, so I'm assuming some system apps got removed. On my HTC devices I would normally run the RUU for them to reset them completely and then take the update, however I can't seem to find an RUU for the Razr M. Does this not exist? Any suggestions on how to get the OTA for her?
Sorry, I can't seem to find any info on this. The phone seems to be a dead end phone...
Click to expand...
Click to collapse
Option1
Use the tibu on her phone to restore all frozen sys apps.
Voodoo to hide root.
Take ota.
2)
Restore to stock, http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
Go my restore & follow the sad smiley to what to do. It was written to restore ...78
House of moto link: may be easier to jump to ...94 & keep your data. Forget the ota
Ok?
Thanks man. I'll give option 2 a try as the apps are gone and there is no backup
Ok, so I can't get RSD to recognize the phone. The phone shows up in the device manager under adb. However it does not have the OK to Program message in the fastboot menu. So I can't really proceed to flash the phone using RSD. Suggestions?
Nagrom Nniuq said:
Ok, so I can't get RSD to recognize the phone. The phone shows up in the device manager under adb. However it does not have the OK to Program message in the fastboot menu. So I can't really proceed to flash the phone using RSD. Suggestions?
Click to expand...
Click to collapse
Drivers?
http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Cable? Need orig one.
Using both. Odd.
Anyone have any further feedback or help on this issue. I'm at the point where we are gonna throw her phone in the trash if we can't fix it, as she's having issues with it now and I can't really do anything with it.
Try a different USB port? Mine only works in 1 of the 3 on my laptop for some reason.
Sent from my Nexus 7 using XDA Free mobile app
Related
Does anyone have an sbf for the R2D2 Edition? I got a little too tweaky.
Thanks!
Lol.. not yet.. next time boostrap and make a back up
See if you can recover with the r2d2 rom from mydroidworld
http://www.4shared.com/file/rePStgcF/VZW_24_Full_ROM.html
I've got a nandroid backup on my SD card I jsut can't seem to get back to the bootstrapper.
Try booting up and then pull your battery and then try booting up again. See if that puts you into bootstrap.
Sent from my R2-D2 using XDA App
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Try going back into bootstrap recovery and pushing the bootstrap recovery button again. Then the reboot recovery button. That should work. I had the same thing happen to me and that worked.
Sent from my DROID2 using Tapatalk
hyatari said:
Try powering down the phone then plugging it in and boot it up. That often loads clockwork revovery on mine.
Click to expand...
Click to collapse
Yeah, for whatever reason that often does cause my d2 to boot into cwm.. I think it replaces that weird battery startup thing, did anyone else get that when they first used their d2?
Sent from my DROID2 using XDA App
rexit1982 said:
Thanks for the advice, I've been yanking the batt, pressing volume buttons and everything the only thing I can get to is the stock reset screen (android with !) and the boot loader. At this point I've probably done more harm than good resetting memory and clearing cache and stuff.
Click to expand...
Click to collapse
If your D2 won't boot all the way up (which is what it sounds like), you may be able to get into CW Recovery by one of the methods below:
1. This is the most reliable way I've found: Boot up and pull battery when the boot animation starts (after the M logo disappears). Then reinsert battery and start up...should go to CW Recovery then. Thought I spell it out just in case you hadn't tried it that way specifically.
2. Make sure there is no 'update.zip' file in the root of your SD card - again make sure NO 'update.zip' file. Then boot into stock recovery, choose the apply update.zip option, and after it aborts, pull the battery and boot up again.
3. Another set of steps that might work:
-Boot into stock recovery by holding X while powering up
-Hit the magnifying glass on the keyboard to open recovery menu
-Highlight reboot and hit "ok" on the keyboard
-When you get the "M" screen pull the battery
-Power back up and it will go to Clockwork recovery
Good luck on that....
rexit1982 said:
Oh, in case anyone wondered, the sbf fro the regular Droid 2 does not work on this bad boy. That'll teach me to mess wiht things I don;t know about. Looks like what I have is Bootloader and a copy of my backup from clockworkmod.... is there a way to build an sbf from your .img files?
Click to expand...
Click to collapse
What makes you say that...what did you try and what happened? What version of RSD Lite did you use, and what was the failure/results, etc. This is a pretty surprising thing to hear.
R2D2 and D2 are the same HW as far as anyone has seen from specs, etc., the 2.2.20 SBF not working seems odd.
Thanks.
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
rexit1982 said:
I used RSDlite 4.7. the flash get tot he reboot point and then a bootloader error thaT said "bootloader err:A5,70,70,00,1f".
Click to expand...
Click to collapse
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Redflea said:
You're two versions behind...RSD Lite 4.8 and 4.9 are out. I'd suggest you get at least 4.8 and try again. I don't have the links, but should be google-able.
When you used 4.7 you added the RSD patch on top of RSD 4.7 after you installed it, right?
What does the phone do now when you boot it up? Just sit on M logo, get to boot animation, or ?
Click to expand...
Click to collapse
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
D2.35##
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
##Updated code
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Sounds like a good project...
rexit1982 said:
Yes I did drop the patch on. The phone goes straight to a black screen with white writing that says
Bootloader
30.03**********
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
***I am not sure if these were the same numbers but the rest of the message is exact match
I googled the error, I found this was the same error that DroidX users who OTA'd to their 2.2 update and then tried to SBF back to 2.1.
I have a new device now but I am keeping hold of the old one for the next couple days to try anything anyone ahs any ideas on. When I get to my other phoe I'll try a new rdslite.
Click to expand...
Click to collapse
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Redflea said:
You mean you're going to try the newer RSD Lite on the new phone or the old phone?
Interesting that it's the same error the Droid X users were getting...that does change the game a little, doesn't it. Thanks for the additional information - a relevant "news" post is here:
http://www.mydroidworld.com/forums/...-1-any-reason-after-official-upgrade-2-2.html
So it seems like VZW may have made the same change to the bootloader w/2.4.x on the D2 that they made w/2.2 on the DX.
Click to expand...
Click to collapse
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
rexit1982 said:
I am running RDS lite 4.9 against my "old" device right now. I'll let you know how it works out. What is the current official SW version on the D2?
The VERY first time I tried this I did get a success message when it was done
I get an error now, Error sending RAM download to bootloader ... I am trying to attach pictures of the full message.
Click to expand...
Click to collapse
For the D2 (non-R2D2) it's 2.2.20, which is what the avaialable D2 SBF is...
bladearronwey said:
Actually, the mem_map blank and the bootloader messages are pretty common across all motorola phones, I've seen similar error messages on the older p2k (v300, razr, etc) type phones when you have a flash fail out at certain points. It's generally recoverable (in most cases, anyway) as long as you have a full flash (.sbf or .shx)
Click to expand...
Click to collapse
Thanks...
I believe I've also seen some comments that when flashing via a Windows box fails, that trying from a Linux setup can be more likely to be successful, but don't remember the details, so I may be garbling that info...
newk8600 said:
If you don't have a linux computer I'm working on a livecd with adb and the sbf_flash script so that anybody with a computer can flash there phone in linux. I have one version so far but I'm trying to cut down the size because it's too big for a CD.
Click to expand...
Click to collapse
Please let me know when you have this livecd available. I too had the same response on my Droid 2. I wound up having to buy a new D2, but I'm still holding onto my old one...hoping one day I might be able to revive ut. LOL
Sent from my DROID2 using XDA App
Hey guys I'm new to the site and have some knowledge regarding Android and a little about the rooting process however I am still not officially rooted.
I just brought a Motorola Droid Pro off eBay and it came with Clockwork mod Recovery I really want to get rid of it because every time I re-boot the phone it pops up. I think that means that my pro is rooted and I have used it to wipe the phone and wipe the cache hoping to also get rid of the recovery however it is still there. Is there a way to get rid of it and go back to actual stock android with the new pro update that was released a couple months ago? Thanks so much I don't really know where else to go with these questions and hoping to illicit some kind of response from this site. Thanks so much.
Sorin712 said:
Hey guys I'm new to the site and have some knowledge regarding Android and a little about the rooting process however I am still not officially rooted.
I just brought a Motorola Droid Pro off eBay and it came with Clockwork mod Recovery I really want to get rid of it because every time I re-boot the phone it pops up. I think that means that my pro is rooted and I have used it to wipe the phone and wipe the cache hoping to also get rid of the recovery however it is still there. Is there a way to get rid of it and go back to actual stock android with the new pro update that was released a couple months ago? Thanks so much I don't really know where else to go with these questions and hoping to illicit some kind of response from this site. Thanks so much.
Click to expand...
Click to collapse
1. Locate the thread with the SBF files "bricked your droid pro, SBF files" or something like that.
2. Download the SBF file for the droid pro. MAKE SURE ITS THE DROID PRO SBF.
3. Aquire RSD lite, it may be in that thread as well, otherwise find it on the internet
4. Using RSD lite, write the SBF file to the phone.
That'll set it back to factory spec, including unroot and bootloader... it'll be a few software updates back, so just manually set it to look for updates.
Thanksfor the quick reply I saw something like this somewhere while googling... I'm assuming RSD lit is pretty easy to navigate then I'm just using it to write the SBF file (I'm assuming SBF is like original factory update file) onto the SD card? Will doing this also rid of Clockwork mod recovery? Thanks again dude.
Sorin712 said:
Thanksfor the quick reply I saw something like this somewhere while googling... I'm assuming RSD lit is pretty easy to navigate then I'm just using it to write the SBF file (I'm assuming SBF is like original factory update file) onto the SD card? Will doing this also rid of Clockwork mod recovery? Thanks again dude.
Click to expand...
Click to collapse
SBF is basically a image of the phone's software. Someone pulls it off a factory fresh phone and distributes it (or, it gets pirated direct from the source)
You're not writing it to the card, you're writing it to the phone.
When you open RSD Lite, you should see the phone connected. Also, theres a button that says "..." Click that button, choose the sbf file, and hit start... wait for it to finish, then after it resets the phone and says "please manually restart the phone" you can unplug and end the program.
This will reset the phone to just like it came off the factory floor. Stock recovery, OS, bootloader, etc.
Thanks dude figured it out yesterday was a little scared but did it thanks so much again.
I Just bought a Droid X from my brother. I decided to root it and try to load a custom rom on it.
On to the problem...
I tried to install a rom onto the phone, but forgot to do a full wipe before I installed which caused the inability to boot past the Motorola logo.
Now here's the embarrassing part... I forgot to do a nand backup before I installed.
I've tried using RSD Lite, but it wont ever show the X. I know there's nothing wrong with the program because i connected my OG Droid to it and it showed right up.
I can boot into the stock recovery and bootloader. Is there anything that I can do to get this phone un-"bricked"
I don't really care if what I have to do will unroot my phone or take it back to its factory rom and settings or completely wipe everything. I just want it to work again. Everything else can either be redone or remade.
Thanks in advance
The only thing you can do is SBF. You can use RSD Lite or go the Linux way. (The Linux way is much easier and faster.)
You can Google for guides, and be sure that if you use RSD Lite that you have the correct drivers installed.
Sent from my DROIDX using XDA App
Mastur Mynd said:
...
I've tried using RSD Lite, but it wont ever show the X. I know there's nothing wrong with the program because i connected my OG Droid to it and it showed right up.
...
Click to expand...
Click to collapse
infazzdar said:
... You can use RSD Lite...
Click to expand...
Click to collapse
The correct drivers are installed, ive even un installed and reinstalled several times just to check. i'll be buying a linux powerd laptop from a friend here soon. Thanks for the tips
I hope you're not buying a Linux laptop especially for this; linux can be ran, without installation, through a cd or a flash drive.
There's even a Linux distribution floating around that is specifically for SBFing. Either way, good luck to you! =D
Sent from my DROIDX using XDA App
Make sure also that you are running RSD as an admin . Sometimes it will work without showing the device too
Yeah, I've been running as admin and in compatibility mode. O guess I can try to push a rom with it not showing. Could anyone link me to some details on how? or is it as simple as hook up in bootloader, select rom and hit start?
Also, I'm not buying the laptop specifically for this (the phone itself only cost me $20 with only the battery and battery cover missing). I intend on using it for the access to all of the developmental tools for Android. Thanks again to you both for the concern.
@infazzdar - What exactly is the "linux way" you spoke of in your first post? This seems like it may be the better way to do it
Mastur Mynd said:
Yeah, I've been running as admin and in compatibility mode. O guess I can try to push a rom with it not showing. Could anyone link me to some details on how? or is it as simple as hook up in bootloader, select rom and hit start?
Also, I'm not buying the laptop specifically for this (the phone itself only cost me $20 with only the battery and battery cover missing). I intend on using it for the access to all of the developmental tools for Android. Thanks again to you both for the concern.
@infazzdar - What exactly is the "linux way" you spoke of in your first post? This seems like it may be the better way to do it
Click to expand...
Click to collapse
The Linux way involves using terminal and an sbf flash script to SBF. Also, you don't have to install any drivers, it fails less, and I believe that it's faster than using RSD Lite.
Sent from my DROIDX using XDA App
I'm guessing there's a youtube video that can give me a step by step instructions to do that so I'll post back when I get the chance to do the SBF. Thanks a ton
Ok, somehow my rsdlite decided to recognise my phone now. its connecting, but when I choose the sbf, it says "chipset type 50 is not supported" in the status section
EDIT - YAY!! MY PHONE'S FIXED!!
Had to download a newer version of RSD lite and after that it worked like a charm. a HUUUUUGE thank you to you guys!!
Great to hear!
If this ever happens again and RSD lite just doesn't work you can always do the linux way like someone else said earlier. I can give you step by step instructions on that if you want, just send me a PM.
ljbaumer said:
Great to hear!
If this ever happens again and RSD lite just doesn't work you can always do the linux way like someone else said earlier. I can give you step by step instructions on that if you want, just send me a PM.
Click to expand...
Click to collapse
Yeah just use the distro! It's saved my butt plenty of times and only takes 5 minutes.
So after doing some edits and removing the AT&T bloatware the phone stopped wanting to allow me to add apps. Even though I had 20MB free. My phone now reboots when I put the SD card in.
So I decided to do a factory reset which worked fine but now I'm stuck on the first screen of the android set up. now the screen is just black with the taskbar at the top and the words "setup" right below it but no android icon in the center, and the emergency button is absent on the bottom.
I googled and found out that if you touch the 4 corners in a clockwise pattern this is suppose to bypass the setup and just go straight to your home screen. well this is a no-go.
The phone receives call fine and the screen is responsive when I slide the taskbar down. also when I plug it into my comp the motosuite boots up and works fine as well.
So any suggestions on how to get past this or how I can just reflash the phone?
It sounds like you don't have a launcher...
How to fix... i'm not so sure...
Maybe a forum search?
Sent from my MB508 using Tapatalk
Can someone hook me up with the launcher for the flipside. I was going to use sideloader wonder machine to reload it. since I do remember deleting it like an idiot.
I've googled he crap out of it with no success. so can someone please hook me up?
thebluetoothkid said:
Can someone hook me up with the launcher for the flipside. I was going to use sideloader wonder machine to reload it. since I do remember deleting it like an idiot.
I've googled he crap out of it with no success. so can someone please hook me up?
Click to expand...
Click to collapse
Cant you just go to android market on your computer and send a launcher to your phone that way? It automatically installs for you and if you are able to open the notification bar you should then be able to launch it to make it your default. Hope this helps.
pre4speed said:
Cant you just go to android market on your computer and send a launcher to your phone that way? It automatically installs for you and if you are able to open the notification bar you should then be able to launch it to make it your default. Hope this helps.
Click to expand...
Click to collapse
The issue is i'm stuck on the very first screen of the phone. you know when you first power one up for the first time and set up gmail and everything else. well mins is stuck on the first screen so i can't get to market to download it.
If it is stuck on the setup it doesn't sound like a launcher problem. I can get the launcher off my phone if you want it but I know after I did a NON SBF update (using android recovery) mine got stuck on the MotoBlur setup and would freeze at 95% or so no matter if it was signing into my old account or creating a new one. I had to do an SBF flash for it to work. Not sure what the problem was but using update.zip looked like it was fine but it screws something up in it.
devi59 said:
If it is stuck on the setup it doesn't sound like a launcher problem. I can get the launcher off my phone if you want it but I know after I did a NON SBF update (using android recovery) mine got stuck on the MotoBlur setup and would freeze at 95% or so no matter if it was signing into my old account or creating a new one. I had to do an SBF flash for it to work. Not sure what the problem was but using update.zip looked like it was fine but it screws something up in it.
Click to expand...
Click to collapse
I'd gladly flash it again, but the snare is I don't have debugging mode on and with that black screen I can't get to it. I even hunted for Hotkeys to get into settings. So any possibility to get the phone into debugging mode without going through settings?
thebluetoothkid said:
I'd gladly flash it again, but the snare is I don't have debugging mode on and with that black screen I can't get to it. I even hunted for Hotkeys to get into settings. So any possibility to get the phone into debugging mode without going through settings?
Click to expand...
Click to collapse
You can follow this guide located here http://forum.xda-developers.com/showthread.php?p=17042497
Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B (If you already went to Froyo then this number is going to be like 91.7 I think)
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Click to expand...
Click to collapse
Then just download the SBF listed on that post. Let me know if you are confused. I've done this about 3 times now on my phone. I keep screwing around with it and reflashing it.
devi59 said:
You can follow this guide located here http://forum.xda-developers.com/showthread.php?p=17042497
Then just download the SBF listed on that post. Let me know if you are confused. I've done this about 3 times now on my phone. I keep screwing around with it and reflashing it.
Click to expand...
Click to collapse
Thanks, I'll try that again, I've actually already tried that but RS lite doesn't seem to read my phone. but I had that issue before and I know I have to use and older version instead of 4.9. Hopefully it'll work
Thats odd. I know I just bought our phones but they came with 2.1 and it worked just fine with it. I've upped to froyo now but I never had problems. Only had problems doing the update and doing a factory reset. After doing them I needed to do the SBF. Only thing that fixed mine.
Ok I have it fixed now. I tried a few different version of RS lite. and it just wouldn't read the phone even though the phone would read the comp.
Solution: run friggin RS Lite in Compatibility mode with XP SP3. worked fine.
So the phone is up and running again, but for some reason now everytime I put my 16GB sd card in it, the phone will reboot. I'm going to format the card as FAT and see if that solves it.
Cool. Glad you got it working. Now we just need some cyanogenmod love for our phones
I am far way ahead of your problem
i had the same issue
i downloaded the SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_PDS001_SAGEATT_P033_HWp4_1FF.sbf and flashed using RSD lite 5.3.1 multi flashing desktop
however i am struck at boot loader and my mb 508 doesnt even boot into the same state after flashing
its strucked at boot loader, i also have the Blur_Version.2.159.17.MB508.ATT.en.US.zip but i can not flash it either
i tried to download the Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com but filesonic is no more supported to access downloading any kind of boot loader or other files
my question is, how can i restore my phone
current display:
boot loader:
91.7 B
ERR: A5, 70, 70, 00, IF
MEM_ MAP Blank
Service Req'd
Battery Ok
Ok to progress
Connect USb
Data cable
please help here
tnt4ever said:
I am far way ahead of your problem
i had the same issue
i downloaded the SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_PDS001_SAGEATT_P033_HWp4_1FF.sbf and flashed using RSD lite 5.3.1 multi flashing desktop
however i am struck at boot loader and my mb 508 doesnt even boot into the same state after flashing
its strucked at boot loader, i also have the Blur_Version.2.159.17.MB508.ATT.en.US.zip but i can not flash it either
i tried to download the Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com but filesonic is no more supported to access downloading any kind of boot loader or other files
my question is, how can i restore my phone
current display:
boot loader:
91.7 B
ERR: A5, 70, 70, 00, IF
MEM_ MAP Blank
Service Req'd
Battery Ok
Ok to progress
Connect USb
Data cable
please help here
Click to expand...
Click to collapse
I replied to your pm. Ill send both files if you want. Just send me your email in pm and ill do it.
Hello all,
So I have in my hands a Droid 2 on VZW which is currently not working. All I know is this:
It was rooted when my friend bought it. He received a notification for an update sometime today, installed it, and now it seems to only boot to the bootloader.
The screen basically just says:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
So, I've never used a Motorola phone before, and I'm not sure where to start. Can anyone guide me with a little hand holding to get this thing working for him again?
Thanks all.
As an update. Read around a bit, tried clearing cache, then did a full wipe, and it still ends up at the same screen each time.
did you try, rerunning the update, from recovery
not sure where it's stored or if it would be gone, from data wipe
if that doesn't work, take to verizon store, if that is an option
there is a fix for the, Droid 2 Global, here [How-to]unbricking downgraded 629 & root normal function OTA 629
someone I'm sure will, use the method, for fix for the D2
they will need a copy of the update
looks like the update is saved in the cache
so if you wipe cache or data, it should be gone
so it's verizon, wait for SBF (official or repacked)
or update failed, maybe just use old SBF 2.3.20,SBF Mirror
Tutorial/Walkthrough for flashing an .sbf to Droid 2 (rooting/factory restore)
Sbf will ether work, or bootloader will change to MEM-MAP Blank error
Is it advisable to try the old sbf, or will that be bricking his phone permanently?
Thanks!
sbf will brick phone, till correct sbf is found
Sent from my DROID X2 using xda premium
xiton said:
Hey shadow,
Did the newest sbf ever come out? I'm still trying to fix this VZW Droid 2
Click to expand...
Click to collapse
no SBF yet
does phone still say
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
if so can you get to android recovery?
Booting into Recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the lock/power button.
Once you see a warning sign with an android robot appear, press Volume Up and Down buttons.
Click to expand...
Click to collapse
DROID Wiki.
maybe you can install update, unlikely but worth a try, need to be able to put it on sd card, and rename update.zip
then select apply sdcard:update.zip in android recovery
maybe you'll get lucky
xiton said:
Hey sd_shadow,
I see the sbf file finally came out for me to fix my friends phone. I have one problem though. The battery is almost dead and I can't get the phone to charge. What can I do to get it to charge?
Thanks!
Click to expand...
Click to collapse
safest way is to buy a $5 spare battery charger like http://www.amazon.com/MOTOROLA-Droi..._1_6?s=wireless&ie=UTF8&qid=1338740850&sr=1-6
take to verizon store to charge battery,
or use the MacGyver method but I do not recommend, because you can fry your phone
edit: changed link