[Q] R2D2 sbf - Droid 2 General

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

Related

[Q] Advice for SBF restore.

Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Sadly, yes. Since you didn't back up before you started you will have to SBF to get a stock ROM. Be sure to make a nandroid of your modded ROM, SBF, root, backup, then flash back and forth.
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
CBX133 said:
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
Click to expand...
Click to collapse
yea. a nandroid backup is the backup you create in cw recovery
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
CBX133 said:
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
Click to expand...
Click to collapse
the activation system has been down for a few hours now. You can try *22899. Or do it online here http://www.verizonwireless.com/b2c/activate. Or just call the 1800 number and do it with a csr.
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
CBX133 said:
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
Click to expand...
Click to collapse
of course it's just a coincidence. flashing a rom or doing an sbf to your phone does not cause the verizon activation system to crash. lol. whenever you sbf your phone or do a factory reset, you have to do the *228 to reactivate. thats normal.
Just some info... when I wipe out my phone and boot it up (skipping) activation it works already. Found this out by wiping my phone, booting it up, and I got a text message immediately. Lol.
CBX133 said:
Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Click to expand...
Click to collapse
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Steven58 said:
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Click to expand...
Click to collapse
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Here's what I used to guide me through the sbf...
Here is a link to the guide I used. It is for the 2.1 SBF though.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
Here are the instructions with my modifications for 2.2...
IMPORTANT!!! - the directions are for restoring 2.1 so you do not do some of the steps! They were the best I could find. I followed them except for things that did not apply.
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9
You will need to patch this after installing. There is an .ini file included in the folder that needs to be placed in your install directory. /Program Files/Motorola/RSD Lite
I used 4.9 and did not have to patch any files- the above step was unnecessary.
3. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file here...
http://rootzwiki.com/
4. Unzip the SBF file to your desktop
i did not unzip mine to the desktop- i put it where i stash my android files- it made no difference.
5. Run RSD Lite, and click the “…” button, then find the SBF file that you just unzipped to your desktop and select it.
Starting here i followed the directions to the "t". Went through all the steps. !!!!!MAKE SURE YOU START WITH 100% BATTERY!!!!!! It takes a long time and if your phone dies during the process it is a nightmare.
6. Plug your Droid X into your computer and power it down
Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
7. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
8. When the flashing is complete, unplug your phone
The Droid X will likely not boot up all the way, so pull the battery out
Put the battery back into the phone and reboot into Recovery mode ( Hold the HOME button and press POWER until you get an exclamation mark. Release the HOME button and press the SEARCH button)
Using the VOLUME UP/DOWN buttons, navigate to “wipe data/ factory reset” option on the screen, and press the CAMERA button halfway down to execute.
When complete, choose to reboot your phone
9. It takes a while. Hope this helps. And I hope it goes smoothly. It was nerve racking for me. After you have finished the process you will not be rooted. Use the market app "Z4root" or which ever method you prefer.
good luck.
Click to expand...
Click to collapse
thepolishguy said:
Here's what I used to guide me through the sbf...
Click to expand...
Click to collapse
i really appreaciate the guide and quick response im going to try to save these for future refrence.
just tried this method for the experience on the droid i bricked. worked like a charm was a bit easier too. phone rebooted on its own. i wiped just to make sure since i need to send it back to vz i already got my replacement. but this definetly gives me a little more confidence knowing i can bring it back from the dead if i have to. thanks again.
detailed sbf restoration instructions
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
sure! from http://androidforums.com/droid-x-al...ing-custom-rom-theme-how-unbrick-droid-x.html
*my note: make sure you install moto dx drivers on your PC: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
C. UnBRICKING INSTRUCTIONS:
HELP ME. Ima noob! I BRICKED MY PHONE!
1. go to Home and DL the leaked full OTA FROYO 2.2 .SBF file.
2. Download and install RSDLite v4.8 (it should be on Home if not, go Google it.)
3. If your phone is stuck on the load screen, pull the battery, wait a minute, push the battery back in and restart with the phone’s Boot Loader Mode (do this by pressing the red camera button + volume down + power button  hold all of them in the order that I stated until your phone flashes briefly). Your phone should flash white and a Boot Loader menu will come up. Make sure there is at least 20 to 25 percent battery life remaining in order for the reformat of you phone to complete. If your phone dies in the middle of this process GOD HELP YOU.
4. Run the RSDLite File and connect your Droid X to your computer via USB.
5. Browse for the .SBF file you downloaded in step 1 and click “Start”, at which point the program should run and your phone will proceed to unbrick
6. EASY RIGHT?
7. Once unbricking you will have to go through reactivation of your phone. This is normal so just go through the steps you did when you first started.
8. GUESS WHAT? You made a backup of your previous customizations REMEMBER? If you don’t want to deal with the hassle of re-downloading your entire life onto your phone again follow the “ROOTING” instructions in Part A and redownload Bootstrap and reboot into recovery mode to RESTORE the backup you made by following steps 2-11 in Part B….except you won’t be going to “install from sdcard” you will going to “Backup and Restore” and “Restore from sdcard”.
HELP Please - Error running SBF in RSD Lite
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
rossi28usa said:
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
Click to expand...
Click to collapse
did you put the patched pst_flash.ini file in the rsdlite install directory?
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
rossi28usa said:
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
Click to expand...
Click to collapse
yea, you can only do it after installing the program. it has to be closed though when you do it and you have to overwrite existing file. if you did all that properly, then it may be a corrupted sbf. I would just install rsdlite 4.8 or 4.9 and retry. those dont require a patch.. if no workie, then redownload sbf.
rsd lite 4.8 is here http://www.multiupload.com/HL0ZAL9GK8
I can't remember the order I did it in so I'll re-install with the instructions you gave. Thank you! I'll report back.

OH NO! Another messed up Droid X

A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?
check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/
It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!
My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community

[Q] A bit of help

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.

[Q] Milestone 2 in bootloop

Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.

Attempting to fix a friends VZW Droid 2...

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

Categories

Resources