Ok, I installed Clockwork a while ago, then removed it and unrooted (I no longer needed root access, and I'm not doing any image flashing or anything that requires it). But after removing clockwork, it still boots to that first when I reboot my phone. In case if I ever have to take my phone in to VZ or something, how do I stop it from booting to that? I'm guessing it's not just a normal app, since I've reset to factory since then to try to resolve another issue, and it's still appearing, so I'm guessing it installed itself into the ROM.
I basically rooted my phone originally to install Titanium Backup before doing the factory reset, then I was thinking of trying some custom ROM's, but I decided not to (other than a performance increase, there's nothing else I really care about right now that custom ROM's would provide). So I installed Clockwork Mod and everything else RLM703 listed (http://forum.xda-developers.com/showthread.php?t=814299&highlight=guide), then removed everything after I decided not to mod it.
I can understand your concern on the not flashing, however if you do not flash i think you also still have the Superuser app (even ifyou dont have root rights) that itself would also void your warranty. The easiest, fastest, and safest way is to Flash it using the Method below.
Go To (droid-life .com /2010/09/21/how-to-return-droid-x-back-to-android-2-1/)
((**As a new user i cant post outside links so delete the spaces after life com in order to get the proper working link.))
**
You will download 2 things. The SBF for 2.1 (Which afterwards you can use OTA to reupdate to 2.2).
RSD Lite: This program is used by Motorola to flash phones so its not some unstable application that will mess up.
After you install the drivers, THEN install RSD Lite. You must Run RSD Lite as an administrator. Shift Click RSD Lite and choose Run as Administrator (Even if you are on an administrative account). Afterwards you just navigate from RSD lite to where you have your SBF Saved, Boot your phone into bootloader, then press start. Takes about 5 minutes and you are back to a brand new Droid X.
Like i said i understand your concern on this, and im deeply sorry if you get a rare case and it does decide to mess up, but i just flashed my phone 3 times yesterday using this method and never had a problem.
Hope this helps!
Ok, I know I created a backup through ROM Manager before I stalled Clockword Mod Recovery, but now I can't find it... However, I've been having some minor issues with my phone ever since I updated to 2.2, so maybe I'll just find a stock SBF and flash back to that... That link I posted has a droid x guide, with a link to a stock 2.2 SBF, so I can just grab that and flash it tonight or something. Or even just download it at home and keep it in case if I need it down the road...
Okay so today i decide to root my phone. I heard alot about custom roms and other tweaks that make your phone do all this cool stuff. Well i try and download a custom rom, i did use the droid 2 bootstrap, and i believe i backed up on ROM Manager. after that i went and looked at roms and i downloaded Tanzanite ROM. at first i thought i was in a boot loop and i got scared because i rooted my phone last week and downloaded a custom rom wrong and it was in a boot loop. So when i thought this time it was in a boot loop, i hold X and Power button and get recovery options. i factory reset it then rebooted it, it then started up on Tanzanite ROM. I was quite happy with it, then when i try to look at my apps, they are all GONE ! There is no Market and i have no 3G coverage. I was upset and i dont know what to do. I am scared if i do something it will go into a bootloop or i will be stuck with this ROM forever. I NEED HELP ! PLEASE ! i cant afford another phone replacement. Please help me ! Please, experts, people who had this issue, somebody just please help. Thanks.
You're not stuck. There's always SBF.
SBF is your best friend. And a word of advice to you. ALWAYS find out what kind of recovery is out for your phone before you do ANYTHING like rooting or flashing. For Moto phones, SBF is your friend. HTC has RUU's.
Here is the guide to SBF your phone:
http://forum.xda-developers.com/showthread.php?t=770224
(Be sure to get the RSDlite 4.9 and the latest Moto drivers which you can find on Moto's website)
Here is the SBF file to download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
This will get you back to 100% out of the box stock.
Good luck and let us know if you get it fixed. If you have any problems or questions, feel free to PM me.
I fixed the problem. Thanks guys but i would like to know, what is SBF and what does it do? Everytime i do a new ROM i am scared of the outcome. It bootlooped once and got a new one. I will always be scared when my phone re-boots. Alot of feedback i got, has mentioned SBF and i have yet to know what it does and yet to know what it means.
I could be wrong, but I think SBF stands for System Backup File. It basically is a file that came from Motorola. Motorola uses it to get the phone back to its out of the box state, meaning it returns the phone to the same state as when you got it.
You use it if you have no way to fix your phone. As long as you can get into bootloader mode, you should be able to use the SBF. It's actually pretty hard to 100% brick these phones.
Most phone has some sort of recovery utility like this. For example, HTC has RUU (ROM Update Utility) which will do the same thing as an SBF for Moto phones. I don't actually know what other brand phones have, because I've only ever rooted HTC and Moto phones.
Also, when you flash a ROM, you say you bootloop right? Be sure before you flash a new ROM to wipe data and cache in clockwork recovery. This should prevent bootloops.
Since Josuearisty has tested my sbf on his phone, it makes me think the method only works on the phone it was created on. Its actually really simple and easy to do, and I can give instructions for both Linux and Windows on how to make it. I posted instructions a few posts down, but they're vague cause I don't like typing a lot of text on my phone. Who does?
***Your always in the danger zone when messing with SBF files, I've done this method multiple times and it worked. If you follow the instructions word for word, you should be safe. Since I got this working for my phone, I thought everyone would like to know how I did it to make their own Custom SBF for when that bad time comes.***
Things Required
RSDLite or sbf_flash
stock sbf
adb setup and working
MotoAndroidDepacker
Thread With RSDLIte, SBF, and most everything needed..
Page with MotoAndroidDepacker and other helpful tools.
Step 1
Flash your phone with the Stock sbf from The thread also contains RSDLite, SuperOneClick, and MotoDrivers if you need them.
Step 2
Use the eeblueoffee trick to bypass blur setup.
Step 3
Enable Debugging at Settings/Applications/Development/Android Debugging
***Enable Screen Always on--its directly below Android Debugging. This is very important, the phone likes to freeze while doing dd commands and the screen shuts off midway.***
Step 4
Root Phone With SuperOneClick and Enable Non-Market Apps. Then Reboot Phone.
Step 5
Open A Terminal Or Command Prompt When Phone Boots Up
5a. adb shell
5b. su
5c. dd if=/dev/block/system of=/sdcard/CG39.smg then exit adb
5d. adb pull /sdcard/ E:\ (or whereever on your system you want it, E: is my ntfs shared partition)
Step 6
Open MotoAndroidDepacker
6a. Open Sbf and unpack it
Step 7
Replace unpacked CG39.smg with the dd CG39.smg from phone
Step 8
Open MotoAndoridDepacker
8a. Open folder with all the smg's
8b. Compile Sbf
Step 9
Your done, flash the phone with the newly created sbf.
***Its a good idea to wipe data\factory reset in between stock and custom sbf flashes. SBF Flashing doesn't wipe the \data\ directory and latent crap from the previous flash can be left behind. That's why you have to wipe data\factory reset after SBFing from a custom rom, if you're curious***
Step 4.5 (Advanced and Experemental)
You can add in any extras you want between steps 4 and 5. And they have to be added to the SYSTEM PARTITION ONLY. I've only added in 2nd-init Defy, and while it got the bootmenu DIRECTLY after an sbf flash, the only links that worked were Reboot and Shutdown. I'll look for a fix when I feel up to hours of sbf flashing again. You could try to either install Titanium Backup Pro and move apps like Bravo Sideload Enabler to the system partition, or use adb to install as a system app. To be safe, I'd do as little as possible, in as few of steps as possible, for example, I only touched my phone to enter eebluroffee and to enable debugging, that's all. Then uninstall TB Pro, and continue on to Step 5. Sorry for the Wall of Text, but all this is important.
HOW THIS WORKS
After the phone is flashed with the sbf, the system partition is signed DURING the first boot. By doing a diskdump, you're able to get the CG39.smg plus the key it gets on first boot, and since the signature is already there on your custom CG39.smg from the dd, it doen't get recreated when flashing your custom sbf and booting up. I was hoping the one I made was universal, but it doesn't seem to be. I'll try to make one for us (a universal preroot) if its even possible.
***Original Post*****
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
skeevy420 said:
Like the title says, a prerooted sbf. I've tested this three times, with a stock sbf and full data\fatcory reset in between each flash. Only tested on Linux with sbf_flash. No RSDLite on Windows since I don't have it installed to test with.
You still have to use Bravo Sideload Enabler from market for non market apps. I plan to change that. I'm halfway there already, I know which xml to edit to enable non market apps, but am unsure of the syntax used in AndroidManifest.xml to edit it before compiling the apk. Another idea is to make Bravo Sideload Enabler a system app and part of the sbf, but I didn't think of it until just now, literally, right now.
With this sbf, to flash CM7 or any custom rom, the steps are simply Flash sbf, Bravo Sideload Enabler, Defy 2nd-init, flash rom.....that's it.
Also, to get around the blur setup, type eebluroffee on the soft-keyboard on the very first screen you get to, just press the menu "button" for a second or so. Sometimes it takes a few times to work.....but eventually it does.
Link to sbf: http://www.mediafire.com/?tx1sdgftp9ng5b6
Thank Josuearisty for giving me the idea, and Epsylon3 for his informative post with all the information I needed to make this.
I also tried adding in Defy 2nd-init. After flashing, it would go to the custom bootmenu, but nothing worked.
Click to expand...
Click to collapse
Great, I always thought about it, its a good thing for us.
I'd like to try on Windows and RSD Lite but I'm afraid of damaging my phone.
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this. I'll be back on in the morning, it's 1am here and I'm getting tired.
skeevy420 said:
It shouldn't hurt. Like I said, I've already flashed it 3 times. Or 7 sbf flashes in the past few hours, including stock flashes. I'd appreciate an RDS Test. I don't really want to flash the sbf again....I restored my WR1.4 nandroid only 45 mins ago after about 6 hours of testing this.
Click to expand...
Click to collapse
at least if we are rooted, we can download terminal emulator from play store and install bravo sideloader enabler from sd card.
I cant download sideloader from market cause I dont live in US, at least is a great advantage for us!
I could make sideload enabler a system app installed by default. Give me a day or two for that.
Error on Windows with Rsd Lite, just showed me the logo and then back to bootloader.
Thanks God I was able to flash the original sbf file again.
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
skeevy420 said:
Damn. Maybe the method I used only works on my phone. It's easy to do.
After stock sbf flash, do the eebluroffee trick.
Root with SuperOneClick
Adb shell
su
dd if=/dev/block/system of=/sdcard/CG39.smg
adb pull /sdcard/CG39.smg E:\
Decompile stock sbf with MotoAndroidDepacker
Replace stock CG39.smg with created one
Repack sbf with Depacker
Flash
See, its not that hard. That's all I did and it worked perfectly for me.
It's possible it only works on the phone that makes it. And you HAVE to edit the system dump. If you edit stock sbf's CG39.smg, it gives bootloader error. With this method, you could technically make a CM7 sbf.
Anybody with linux try my sbf with sbf_flash?
Click to expand...
Click to collapse
I have done that before, not decompile sbf with motoandroiddepacker, I made a backup of system using those commands.
I think that SBF will not work with any other phone, but at least is a big advance.
If everybody can do it, they will be able to flash their custom SBF alredy rooted and maybe with any other apps.
---------------------------------------------------------
The thread you posted with rsd lite and sbf file is dead, links are not working, use this post in the same thread:
http://forum.xda-developers.com/showpost.php?p=22706722&postcount=66
I uploaded the files again, I'll create a post with these files.
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
skeevy420 said:
That thread worked 4 months ago dammit.
I hope it does lead to better things, but its worth the 10 minutes of effort to make you own personal preroot sbf, and easy to do in my opinion.
Also sort of related, I think we have version 3 bootloader. That explains why if you flash a Defy sbf, you can't go back. It changes efuse level and you can't change efuse down, only up.....its what screws Defy users who go sbf crazy and flash the first thing they see. We don't have that problem cause we only have the one sbf..... Damn you Motorola.
Click to expand...
Click to collapse
I made a custom SBF now and it didnt work, what version of motodepacker did you use?
Is there anything else to do?
What about sbf calc, I think it is to determinate if sbf is good or not, I dont know.
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
skeevy420 said:
Version 1.3, not the mono one. I didn't use sbf-recalc, only used it once ever 8 hours ago actually. Do you have access to Linux and have a blank cd handy? Try flashing with sbf_flash since its what I used. I'll try with RSDLite tomorrow night, about 20 hours from now. I just installed White Rabbit Test2 and I'd like to run it for a day to see how it performs and it likes my tweaked smartass.
The instructions I posted were the ones I used, on both Windows and Linux, and worked twice. The first time I tried, all I did was edit it with " mount ./cg39.smg ./cg39 -o loop" and that didn't work. The only thin you could do different is to replace dd if=/dev/block/system with dd if=/dev/block/mmcblk1p25 the of= part stays the same.
Another possible problem is your memory card became full during the dump. It will just quit without error. You should have at least 400mb free to be safe, 330mb BARE minimum and probably not very safe. With only adding root\superuser, the created sbf should only be 378,546,533 Bytes & 378,546,533 Bytes. Those are the exact filesizes of the first two sbf's I made. Yes, they're the same size. The md5 is different.
92cb645d5a04d1221f81ee566072149f ./firmware.sbf (1)
fc4e49adf931377c8ccbd3943b3664ba ./custom.sbf (2)
I used the second one I made two more times before I posted to make sure it did work, and once earlier this evening when I flashed the wrong defy zip.
I first came across this method on a post from Epsylon3 at Defy dev on a post about BL7 sbf's not being able to root. I came across it a second time somewhere here on xda and it explained it with a bit more detail, but I had already made my second sbf by then and it worked....and I was ecstatic.
Click to expand...
Click to collapse
Im a little bit afraid of breaking my phone, just thinking about a hardbrick make not to follow with this now.
Well I used the mono one, I was not out of memory 16gb with only 2 in use.
I think the backup was fine, maybe it was something with motodepacker.
I'll try later, I think I'll try with a cliq xt I have, which has some problems, that way if something is wrong, I wont be losing a big thing!
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
skeevy420 said:
I understand that hardbrick fear. This is my only phone. My backup (oldscool razr) crapped out a while back, so I sat there looking at that terminal with the first sbf for 5 mins before the first flash, then when it didn't boot, I was like oh f&^k. Flashed stock, made the 2nd, and it worked. Made a third and it's my new sbf.
Click to expand...
Click to collapse
Well, I do it easy.
After flashing is completed:
I write eebluroff in the motoblur screen.
Enable debugger in applications.
Install sideloader enabler apk with adb
Install gingerbreak to root and 2nd init to install custom recovery from SD Card and restore my backup.
That's all I do when I flash with RSD Lite, I wish at least that the SBF file would come with sideload enabler pre-installed or the ability to install from sdcard!
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
skeevy420 said:
I noticed quite a few market enabling apps yesterday. Couldn't test cause I'm on wr1.4.
Never used gingerbreak.
2nd-init didn't function properly after sbf flash. Only access to bootmenu, shutdown and restart.
Try SuperOneClick 1.9.5. Its version I used.
Also, enable screen always on. Stock became iffy during adb when screen went off.
Click to expand...
Click to collapse
2nd init copies some files to a folder that maybe is in another code group.
At least with sideload enabler for bravo, it would be great.
We just have to install gingerbreak from sdcard to root and 2nd init defy.
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.