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.
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
Hi guys,
I'm a bit lost and unsure what to do.
I installed GummyJar, and like an idiot, didn't read that I need to be on 2.3.320 or 2.3.340.
I was previously on ZapX for 2.2 (purchased phone in early October). So I'm not sure what to do. Is there an SBF that will directly put me on 2.3.340? Would it be wiser to flash to my original SBF (the_gift2.zip I believe), and let my phone automatically get the OTA update?
I'm not really sure what the best thing to do is.
Thank you for any advice and help.
Did you create a back up before you installed Gummy? I know that is praobably a stupid question since you are asking how to SBF -but I thought maybe you didn't think about restoring your backup?
How to perform the sbf:
I did this. It worked for me. I TAKE NO RESPONSIBILITY IF THIS DOES NOT WORK FOR YOU OR IF YOU MUFF IT UP.
ok- so here is the link that I used as a guide - 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.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
You probably have already done this.
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9 download here...
http://dl.dropbox.com/u/7782384/RSD%20Lite%204.9.rar
3. 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.
4. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file. Make sure you use the right sbf file or you will really be hosed!!! if you are on 2.2 you can get the full sbf file from here...
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
5. 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.
6. 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.
7. Plug your Droid X into your computer and power it down
8. Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
9. After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
10. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
11. When the flashing is complete, unplug your phone
12. 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)
13. 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
14. 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.
15. good luck.
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
EtherBoo said:
Thank you very much. An extra question to go along with this.
Once I SBF, I'm assuming I'll be back at stock (ick). How long will it take for the OTA to apply? Can I manually update it from there?
Click to expand...
Click to collapse
Well- of everything goes right you should be able to go to your phone settings, scroll down to the bottom to "About phone", then "System updates". You should be able to manually update from there.
If you get a "your device is up to date message," then something went haywire. Hopefully that won't happen.
Oh yeah - here is the link for "z4root" -you can use it to root your phone after the update...
http://dl.dropbox.com/u/7782384/z4root.1.3.0.apk
If your phone won't manually update, there is an update.zip floating around here. I have it - but not on the computer I am currently working from -sorry.
Again I want you to know - I am not an expert at this - if something goes wrong I will not be able to help you fix it (probably). I just followed the guide and it worked for me. So if something happens when you follow the guide -I am sorry but I won't be much help.
Thank you. Everything took about 2 hours (SBFing, downloading and installing update, reinstalling apps, etc), and I have the newest Kernel version from the OTA update, and GummyJar 2.5 back on.
I had a bit of trouble SBFing, it kept failing for some reason, but I found a fix via googling around the various Droid forums.
Thank you again, you've been extremely helpful.
Help with Droid X in Buffalo NY
ive tried everything I could for almost a week now.... Stuck in Bootloader Screen 30.04 Err A5,70,70,00,1F MEM_MAP Blank Service Reqd Battery Ok OK To Program..... I came to a Droid X last week from a Rooted for over a year Droid 1 with never a problem flashing... With new Droid X tried to flash Gummy Jar last sat without a wipe ( I know my stupidity thought coming from stock phone could get away with it trying to rush but boy was I wrong) after being stuck at loading gummy jar icons tried to factory reset... been stuck at the bootloader screen since.. tried flashing 1.13.6.2_1sbf and 2.3.32_1FF sbf... got newest drivers and rsd 4.8... ran as administrator... phone never shows either... got it once to do something in rsd saying phone was being programmed with 2.3.32 but when it said finished waited hours never rebooted .... stuck dont know what to do....anyone local want to give it a go email me please [email protected] or try to walk me through what i have to do step by step.... thanks
2.2 is looking for AttMusic40.apk to continue the installation.
Anyone has this file ?
Thanks
Forget it. Just flash the SBF. But if you really wana then it's attached. Make sure to put in /system/app and don't try to install it from there either just move it and leave it then do the update.
It's not worth the stress. Even though I had the apk I couldn't get past the error. I used the sbf and everything is awesome now.
Thanks guys.
I got past that now it's looking for: BlurSNMessagingEngine.apk
I have no clue how to do a sbf. Don't even know what that is and how to install it.
Are there any tutorials and download link for it?
Until then, how about BlurSNMessagingEngine.apk?
Get the SBF from here: http://modmymobile.com/forums/629-motorola-bravo-general/561492-stock-sbf-file-bravo.html, download RSD Lite, put the sbf file in your C: drive, put your phone into recovery mode, and start flashing. Also, I hope you don't have Windows 7, because RSD doesn't like it.
I'm in this issue too. I backed up (so I thought) all my ATT apps using Titanium. Went to reinstall, and they were all there (with line through), but no actual backup??? Mine too choked on Attmusic40. I download the one from this thread and copied to /system/app. No love, it has a different checksum and fails. This may plague you too.
RSD Lite
I'm pretty new to this too but I can tell you new guys a helpful tip. RSD Lite is the software Motorola uses on their devices to reboot bad SW devices. It's free to download. You have to access Bootloader to get it to work correctly once it's installed on your CPU and running. To do that, power the phone down. Then, power it back up while holding the Volume Up button. That's how I got it going. Once RSD Lite recognizes your phone and you click the button to go, it's pretty automatic from that point on. Just download the SBF. My phone couldn't find AT&T Hotspot Locator.Apk. I realized that I deleted it through Titanium Backup and when I went back to the market to get it, the app itself had been merged into the MyAT&T app. This didn't give me the necessary apk to run the OTA install from AT&T. I even work for the company. Trust the guys up top, the SBF is ten times easier.
bullet358 said:
the SBF is ten times easier.
Click to expand...
Click to collapse
Very true. Go to my thread; it has the downloads and support: http://forum.xda-developers.com/showthread.php?t=1035778
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.
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