I can not for the life of my get my Droid 2 back to its original state. I've tried both the Windows (RSDLite) and Linux method. Both of them fail. I pray that someone can help me, since I do not have insurance on my device it would cost a pretty penny to get a new one.
For Windows, these are the tools i've tried and FAILED:
1. RSDLite
RSDLite 4.7 w/ patch
RSDLite 4.8
RSDLite 4.9
Moto Connect 4.7
Moto Connect 4.8
10 different versions of the SBF file
This is my output from FlashErrorLog02_10_16_45_02
hXXp://pastebin.com/fcAxMVB6 (replace XX with TT)
Click to expand...
Click to collapse
2. For Linux, these are the tools i've tried and FAILED:
sbf_flash v1.08
sbf_flash v1.11
10 different versions of the Droid 2 SBF
This is my error output:
SBF_Flash 1.11 -> hXXp://pastebin.com/pL5urNm8 (replace XX with TT)
SBF_Flash 1.08 -> hXXp://pastebin.com/SpQcnfm1 (replace XX with TT)
Click to expand...
Click to collapse
I am hoping someone here could help me. I've spent the last 3 days trying this and reading over 1000++ threads and different methods.
Weird. Bad checksum on the SBF file?? Kind of weird.
1upyours said:
I can not for the life of my get my Droid 2 back to its original state. I've tried both the Windows (RSDLite) and Linux method. Both of them fail. I pray that someone can help me, since I do not have insurance on my device it would cost a pretty penny to get a new one.
For Windows, these are the tools i've tried and FAILED:
1. RSDLite
RSDLite 4.7 w/ patch
RSDLite 4.8
RSDLite 4.9
Moto Connect 4.7
Moto Connect 4.8
10 different versions of the SBF file
This is my output from FlashErrorLog02_10_16_45_02
2. For Linux, these are the tools i've tried and FAILED:
sbf_flash v1.08
sbf_flash v1.11
10 different versions of the Droid 2 SBF
This is my error output:
I am hoping someone here could help me. I've spent the last 3 days trying this and reading over 1000++ threads and different methods.
Click to expand...
Click to collapse
Did you check your PC's Firewall, my dear?
Sent from my marginally bricked D2.
I've tried another round of trying to fix my phone w/ Firewall disabled. I've used 8 different computers to see if it was mines that was acting up. I've tried to flash the SBF through WinXP SP2/SP3, 2000, Vista 32bit/64bit, Windows 7 32bit/64bit and Ubuntu.
I don't understand why this is happening to me :\ I'm using my old Blackberry in the meantime until I could figure out how to flash this correctly. I don't know what i'm doing wrong?
Anyone got any advices?
Sorry I didn't get back to you through PM I've been a little busy. Have you tried flashing the D2 2.37 Bootloader? (I believe that's what it is, you need the newest, but the old one won't hurt anything.) Maybe something's mucked on yours. But I'm not sure. What's the history of the device maybe that will lead to a solution?
Sent from my DROID2 using XDA App
My Droid 2 is currently using Bootloader D2.37. I've refreshed and reloaded the Bootloader.. I've also tried to downgrade it in attempt to see if it'd do anything, but it seems to not allow me to - says Failed. I followed a thread somewhere on this site.
These are the problems i'm encountering which is leading to me wanting to restore my phone.
About a week ago, my phone suddenly Force Closed on everything I attempted to open. At the moment, I was sending a text. I then rebooted my device, and oddly enough, all my "new" text I sent were gone. It only restored the last time my phone was in a usable state. Seems to not save anything I do on my phone prior to the reboot. I'm not sure what the heck the deal is. My phone still works, but every few hours I must reboot my phone.
I've already tried multiple times to Wipe Data/Cache, Uninstall Apps (once I reboot, they all come back), and deleting Bootstrap through ADB/Terminal and reinstalling. I can't even get into Bootstrap.. I just can't seem to do anything with my device. Everytime I remove or delete something, the next reboot will bring them back.
Has anyone ever heard of this weird issue? I've tried searching to see if this has happened to anyone elses Droid 2, but it seems i'm the first to encounter this
1upyours said:
These are the problems i'm encountering which is leading to me wanting to restore my phone.
About a week ago, my phone suddenly Force Closed on everything I attempted to open. At the moment, I was sending a text. I then rebooted my device, and oddly enough, all my "new" text I sent were gone. It only restored the last time my phone was in a usable state. Seems to not save anything I do on my phone prior to the reboot. I'm not sure what the heck the deal is. My phone still works, but every few hours I must reboot my phone.
I've already tried multiple times to Wipe Data/Cache, Uninstall Apps (once I reboot, they all come back), and deleting Bootstrap through ADB/Terminal and reinstalling. I can't even get into Bootstrap.. I just can't seem to do anything with my device. Everytime I remove or delete something, the next reboot will bring them back.
Has anyone ever heard of this weird issue? I've tried searching to see if this has happened to anyone elses Droid 2, but it seems i'm the first to encounter this
Click to expand...
Click to collapse
Are you sure you're correctly rooted and you have never flashed clockwork or ROM manager without installing and running bootstrap?
If you are 100% sure then I think you have a deeper issue than some messed up hardware or something like that. I can't think of anyway that would happen unless you had some program make a backup and reinstall it every boot or so and that would be weird.
What ROM's have you used? Do you have any kind of back up software that could be interfering with your setup? Do you have a backup you can restore to?
Sorry I can't help you more. This is a really strange issue.
1. Yup I am correctly rooted. I have the Superuser app, and even did a check to assure my root was intact by downloading Titanium Backup to verify my device was rooted.
2. I've installed ROMs before. When I rooted (Nov '10) I used Z4Root, and Bootstrap Recovery then installed Fission 2.2.1/2
3. Aside from downloading Titanium Backup to verify my Root. Nope, I do not use any type of backup.
4. Yes, I have a fresh backup I could restore to if I was able to get into CW Recovery.
I am thinking I should give up. I've been trying to get this fixed for about 8 days now. I'm going to be picking up a Droid 2 Global today from a Craigslist’s seller.
Have you tried turning the D2 off completely then plugging it into your wall charger while off. Then while it's plugged in and off turn it on. You might have to press power twice to get past the charging screen but if everything is fine you should hopefully be in clockwork if it's still on your phone and then you can try and restore the backup.
Have you tried a different usb cable?
Also it should still be under waranty at least from moto but you might see if VZW can help you (if that's where you got it)
Sent from my DROID2 using XDA App
Is this the Linux method you tried? It's super convenient and really easy if you know a little bit about how to work it.
http://forum.xda-developers.com/showthread.php? p=8546993#post8546993
Sent from my DROID2 using XDA App
zebra690 said:
Is this the Linux method you tried? It's super convenient and really easy if you know a little bit about how to work it.
http://forum.xda-developers.com/showthread.php? p=8546993#post8546993
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sounds like a good suggestion.
Related
To preface, I've been off the phone hacking/ROM flashing scene for a couple years now; previously working with Windows Mobile, so I know a lot has changed but I'm not largely unfamiliar with the general process of what we are doing here.
Droid 2 In Question:
System Version - Version.2.3.20.A955.Verizon.en.US (After OTA Update 03 NOV 10)
Baseband - BP_C_01.09.07P
I've got a stubborn Droid 2 that just WON'T boot to recovery. I bought a fresh Droid 2 last week, rooted via the 1-2-3 'One-Click' successfully. Then I attempted to follow AngDroid's Fission install step by step for my first ROM flash. http://forum.xda-developers.com/showthread.php?t=823473
Issues:
ROM Manager wouldn't do ANYTHING when I would select 'Reboot into Recovery' or attempting to select ROM using 'Install ROM from SD Card'.
Found and installed Koush's Bootstrapper, got 'SUCCESS!' pop-up when selected 'Bootstrap Recovery' yet when I tapped 'Reboot Recovery' nothing happened.
I then attempted to re-install the SBF (which I'm still not 100% clear on what the role of the SBF is, perhaps just the Baseband?) using both AngDroid's instructions in his Fission thread as well as using RSD Lite 4.7+patch AND 4.8 AND 4.9 instructions from this thread. http://forum.xda-developers.com/showthread.php?t=827624 All those attempts where unsuccessful. RSD wouldn't allow me to 'Start' the SBF flash which I can only assume is because I had the latest version on my Droid 2.
I then decided to restore my phone to factory and start over, so I booted the device pressing x, then search and selecting wipe data/factory reset. Once done, it rebooted and to my surprise it still had the Superuser Permissions app that was installed during the 1-2-3 One-Click process.
I went as far as to install the full Android SDK/Eclipse setup for ADB use and continued to run into 'operation not authorized', 'root not allowed on production ROMs' and 'failure' with any command attempting to remove SU Permissions app and install a diff. SU app/reboot into recovery.
I checked to see if I still, in fact, had SU permissions by re-installing Barnacle, it stated that it needed su but the Superuser Permissions app never prompt me to authorize su. There is also no way (that I see) to manually authorize su for barnacle, or any app, in the SU Permissions app.
Way Forward?
I believe that I either need to re-root and try to reboot to recovery again but I am not confident that will work.
I am starting to think that ROM Manager and Droid 2 Bootstrapper apps didn't have SU and might be why they didn't respond when I selected 'Reboot Recovery' options? As I stated I do not know how to manually authorize.
With this information, what am I to do from here?
That's strange. After root, you should be able to install SU from the market if the one click root doesn't already do it for you. When you run Koush's bootstrapper, the first time you should get a pop up from the SU program asking you if you want to allow or deny the bootstrapper. After that, everytime you load up the bootstrapper you should see a little pop up stating that it has been granted superuser privileges.
Try rooting again, this time use the 1 click root for 2.3.20 found here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html, and then go through the steps again and report back
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
wjones said:
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
Click to expand...
Click to collapse
Id wipe cache and wipe data/factory reset and start fresh. I've never had any of your problems and I think they can be fixxed with a factory reset.
Sounds like you didn't get rooted properly.
If it were me, I'd sbf and start over.
- Charge battery fully
- Get drivers from Motorola and install them (wait for it to finish)
- Get RSD 4.8+, and 2.3.20 sbf (make sure you get the full file)
- Wipe data and cache in stock recovery (access by power + X key, then search key)
- Boot into bootloader (power + Up key)
- Load RSD and make sure your device shows
- Choose the sbf and click Start
If you follow those steps exactly and sbf doesn't work, then you probably have a hardware problem either on your phone, your PC, or the USB cable.
karnovaran said:
Sounds like you didn't get rooted properly.
- Boot into bootloader (power + Up key)
Click to expand...
Click to collapse
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
wjones said:
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
Click to expand...
Click to collapse
Yeah I don't know why some methods recommend PC Mode. Sbfs are meant to be flashed in bootloader.
Honestly, it sounds like everything is working like it should be, it's just some steps are being skipped or overlooked. Like the SBF in bootloader, and the sbf doesn't erase your data, you need to do a factory reset after sbfing so thats why your superuser app was still there.
There really is no such thing as a phone being stubborn, and majority of errors like that are from the user. Not to be insulting but thats just the case. The only time I have ever seen a stubborn piece of hardware is from overclocking, where some can go higher than others due to having a better piece of wafer. But if you rooted correctly, bootstrapped, etc, there is no reason that you wouldn't be able to install a ROM.
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
wjones said:
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is this solved now? May I close it?
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
wjones said:
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No problem! I'm in no rush to close it, was just curious Hope it all goes well
DONE!
It worked like a charm! Thanks for all the support!
wjones said:
It worked like a charm! Thanks for all the support!
Click to expand...
Click to collapse
Awesome. Could you add [SOLVED] to your thread title before the mods close it?
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
Okay, so I messed up my boss's phone today. I tried to do the flash player mod to watch Hulu found here: http://androidforums.com/droid-x-all-things-root/219288-modified-flash-hulu-droid-x.html (which I did SUCCESSFULLY on my phone). Anyway, I didn't realize that he had NOT made a backup of his Stock ROM (he just rooted his phone 2 days ago). When I did the Flashplayer mod not only did Hulu not work, but any time he opened his browser to the google hompepage it would kick him out of the browser. We tried pulling the battery, clearing cache (on the browser), force stop (on the browser), and nothing worked. I swear I did EXACTLY the same method that I did with my own and mine works fine. It's odd bc the google homepage shouldn't have anything to do with flashplayer. Btw, every other page I've seen seems to work okay with his browser. Anyway, do you guys know what might have happened?
Never really messed with the hulu hack myself... worst case scenario he will need to backup his apparently and data using titanium backup. Then I would make a nandroid backup of the current state as a place to get back to as a worst case scenario. Then sbf the phone and create a clean nandroid right away... then mess with the hulu hack in the event that it doesnt work again.
Sent from my DROIDX using XDA App
Try this
Try installing Dolphin Browser HD off of the market, and choose "on Demand" when starting the first time for flash plugin. See if it works then
lulz.......
You can't reinstall flash player from the market by uninstalling updates then reinstalling?
Everyone keeps saying to do a sfb (which I wanna do for myself) and I've asked in 2 other threads how to do that and asked exactgly what it does. No one has respinded. What is it and how do I do it?
Sent from my DROIDX using XDA App
It returns the phone robots original out of the box state.
Sent from my DROIDX using XDA App
There are instructions online.. i think everyone needs to know how to sbf if they flash new roms, etc
Sent from my DROIDX using XDA App
Can you provide me with a direct link? And wouldn't a simple factory data reset work instead?
Sent from my DROIDX using XDA App
mj23kb08 said:
Can you provide me with a direct link? And wouldn't a simple factory data reset work instead?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, a factory reset only affects /data and /cache portion of the phone OS I believe. An sbf can be found here:
http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
This is the 2.3.32 full sbf that you will need to flash first. Next you will need the 2.3.34 system only sbf:
http://www.megaupload.com/?d=OXK9Q1ZG
Make sure after you do each sbf to do a battery pull, then boot into Moto recovery (hold down home button while pressing power, then when the droid comes up, press search button), then do a factory reset. This will help to ensure a clean sbf process without issues.
Good luck, and post back if you have questions.
PS make sure to use at least RSDlite 4.8 for flashing these files.
SysAdmin-X said:
No, a factory reset only affects /data and /cache portion of the phone OS I believe. An sbf can be found here:
http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
This is the 2.3.32 full sbf that you will need to flash first. Next you will need the 2.3.34 system only sbf:
http://www.megaupload.com/?d=OXK9Q1ZG
Make sure after you do each sbf to do a battery pull, then boot into Moto recovery (hold down home button while pressing power, then when the droid comes up, press search button), then do a factory reset. This will help to ensure a clean sbf process without issues.
Good luck, and post back if you have questions.
PS make sure to use at least RSDlite 4.8 for flashing these files.
Click to expand...
Click to collapse
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.
mj23kb08 said:
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.
Click to expand...
Click to collapse
RSD Lite was originally used for old Motorola dumbphones like the Razr and some early smartphones. I have an Evo now but I remember how to use it from back when I had a Razr. Just select the SBF file and after it sees the phone hit Flash. Make sure to get a second opinion from an actual Droid X user first since I'm not sure if there's anything extra that needs to be done.
mj23kb08 said:
Thank you for the links. However, I'm not familiar with RSD Lite, so I don't know how to use it or how to flash these sbf files. I clicked on the first link and the instructions seemed vague and geared more towards people who already know what they are doing. I've only tried flashing 1 custom ROM (Fission) and I've flashed various states of the stock ROM several times. So, when it comes to this sbf stuff I'm very much a noob. I'm scared to death of bricking my phone or my boss's phone for that matter, so would you mind giving me step by step instructions on how to flash these two sbf's? Or at least send a link to a site with "noob" instructions? Thanks in advance.
Click to expand...
Click to collapse
Here is the link to download RSDlite 4.8.
http://www.multiupload.com/HL0ZAL9GK8
You will want to download this, and then install it on a windows machine. Then in order to use the SFB files (use 2.3.32 first, then 2.3.34), plug in your phone to your computer. I'm pretty sure you need the Android SDK installed, and the correct moto drivers installed as well (not sure.. i've had this set up on my computer forever...). Next, turn off your phone and press and hold "volume down + camera button + power button" and this will boot your phone into bootloader. It will say 30.03 (if you are on 2.3.15 OTA update) or 30.04 (if you are on 2.3.32 or 2.3.34 releases).
Then open up RSDlite on your computer which you installed it. With the phone plugged in, choose the "..." button in RSD lite and browse to the SBF file that you downloaded (remember 2.3.32 first) and then it should show your phone as a device listed below in RSDlite. If it recognizes your phone, you can click the start button in RSDlite. It will then start doing its thing.
My recommendation is to make a nandroid backup before doing this as a last resort if something goes wrong. The first time that you run the SBF file, it may get to like 98 or 99% and then say fail (something about passing BP baseband or something similar, and your phone will reboot). Don't worry, this has happened to me a couple times when I first started using the SBF files and scared me to death. After the phone reboots, pull out the battery and replace it back in. Then hold down the "home" button while pressing the power button. Then when the picture of the little green android dude shows up, press the search button (this is the motorola recovery screen). Then go to "factory reset/wipe data" (or something similarly titled). You can navigate the menus by using the volume up/down buttons. You will make your selections by pressing the camera button.
If you dont get the little android guy to show up, then turn the phone off and try again. After you have wiped data/factory reset, you may need to activate your phone. If it doesn't automatically prompt you to do this, from the dialer app, type *228 and then call. Then choose the option to program your phone, and you will be back in business.
After an SBF, your phone is completely wiped clean, so you will need to re-root, and install bootstrap/any other mods you need.
Hope this helps. Let us know if you have more questions.
Here is a great how to guide. Great forum with lots a smart helpful people.
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
Sent from my DROIDX using XDA App
My droid 2 has been boot looping since I last restarted it. Was running GB 2.3.3 rooted. I've factory reset and cleared its cache ten times since, and my RSD Lite won't recognize it (installed drivers), so I don't know what else to do. Any ideas? If I could get an update.zip that I could load, I could load that from the Android recovery.
EDIT: My RDS Lite won't recognize my D1 either, it is upgraded to 4.9 so I'm hoping it is just a problem with the drivers on my computer, but I've tried downloading everything possible to get it to work and my computer recognizes all my phones just fine.
Id try clearing data and cache through bootstrap if its installed. If you can't use bootstrap its looking like an sbf is the only option. There's a great sbf utility called KDStaz that's a linux boot disc and sbfs back to froyo final too. You may also try other usb ports?
AndWHUN said:
Id try clearing data and cache through bootstrap if its installed. If you can't use bootstrap its looking like an sbf is the only option. There's a great sbf utility called KDStaz that's a linux boot disc and sbfs back to froyo final too. You may also try other usb ports?
Click to expand...
Click to collapse
Only one USB port on my netbook and it's running WinXP. Can't get bootstrap running either. Thanks for the suggestions though.
EDIT: Looked up KDStaz, will try it.
EDIT: No dice
if anyone else sees this he's in the bootloader not recovery im talking to him on gtalk right now but i really dont know to much about d2s since i have a hero and dont have to deal with locked bootloaders lol. anyway is there anything he can do in fastboot to get it going again because on the hero we can fastboot usb and run an ruu and that will fix it just wondering if theres anything like that on the d2.
thx in advance for any help.
Bierce22 said:
if anyone else sees this he's in the bootloader not recovery im talking to him on gtalk right now but i really dont know to much about d2s...
Click to expand...
Click to collapse
I can get into either just fine.
Tried it on a more powerful computer, and for whatever reason, the same steps worked perfectly. Thanks for the help guys.
I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!
Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...
Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.
infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.
After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.
Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk
Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?