Database Users

Help: Dont laugh - Bricked my phone

Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance

SysAdmNj said:
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
Click to expand...
Click to collapse
Looks like an SBF is in your very near future.
Go to the Development subforum and search there.
If you have not applied the OTA 2.2 update, you will need the instructions to SBF back to 2.1 and then apply the 2.2 leak, and load your ROM from there.
If you have already done OTA 2.2, there is also an SBF that will restore /system only. It Might save you.
BE ABSOLUTELY SURE YOU DO NOT FLASH the 2.1SBF if you were on OTA 2.2. If you do, it will be game over.
Let us know how you fair.

One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.

SysAdmNj said:
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
Click to expand...
Click to collapse
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.

MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that

MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
Click to expand...
Click to collapse
Correct, I cannot get back into clockwork recovery.
I can get into android recovery but I cant do much from there.

Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html

SysAdmNj said:
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
Click to expand...
Click to collapse
Yes. I think that is your only hope at this point. If it doesn't work, I think you are SOL.

I did something very similar to this, flashing the 2.2 System SBF fixed it

I'm back up and running. Thanks people.

good for you man. seriously. just read a couple threads like this. makes me real nervous about flashing roms.

Not nervous since I have insurance
Seriously I caused my issue with a silly mistake. Usually its smooth sailing.

Weird sbf?? getting ready for fission..

ok, im confused....i just sbfed to get ready for this rom and once it finally booted back up i still had my old wallpaper on it, still running launcherpro and i get the message saying that dx overclocker was going to app ly the overclock in 90 seconds and so on. it did have the stock status bar and so on. but what i did right away i just did a factory reset and wiped cache in the recovery screen and now i seem to be back to factory..i just checked and dont have root..is this normal operation for sbf?

yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven

akanealw said:
yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven
Click to expand...
Click to collapse
But the weird thing is after sbf still had my apps and settings..had to wipe in order to get it all factory fresh.

Are you sure you did a full sbf rather then the system sbf. Full sbf should wipe all data along with system.
Sent from my DROIDX using XDA App

deadlyv2 said:
Are you sure you did a full sbf rather then the system sbf. Full sbf should wipe all data along with system.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?

jredecop said:
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?
Click to expand...
Click to collapse
Hmmm..just did it again. Same thing

jredecop said:
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?
Click to expand...
Click to collapse
that is the full sbf. after you've successfully sbf'd, you have to boot into recovery and do a wipe data and cache. that will complete the process of returning it to stock.

akanealw said:
yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven
Click to expand...
Click to collapse
razorloves said:
that is the full sbf. after you've successfully sbf'd, you have to boot into recovery and do a wipe data and cache. that will complete the process of returning it to stock.
Click to expand...
Click to collapse
Ok all is normal then! Thanks guys

Thanks for taking the time out to do that. I highly suggest that anyone who is having weird problems like slide reboot, battery manager FCs and whatever weird stuff some people have reported to SBF. I know it is a huge pain in the butt. It may help with some of those weird bugs that some users have and if you do want to track down the slide to unlock problem it will help with that too. The slide reboot problem has been something found in the stock ROM and other custom ROMs so it is not unique to this ROM. If we all work together maybe we can find what is causing it.
If you anyone would like to test what could be the final build of 2.0.1 ROM then please join us on IRC... http://webchat.freenode.net/ #teamdefuse & #fissiontest
Thanks!

Angdroid said:
Thanks for taking the time out to do that. I highly suggest that anyone who is having weird problems like slide reboot, battery manager FCs and whatever weird stuff some people have reported to SBF. I know it is a huge pain in the butt. It may help with some of those weird bugs that some users have and if you do want to track down the slide to unlock problem it will help with that too. The slide reboot problem has been something found in the stock ROM and other custom ROMs so it is not unique to this ROM. If we all work together maybe we can find what is causing it.
If you anyone would like to test what could be the final build of 2.0.1 ROM then please join us on IRC... http://webchat.freenode.net/ #teamdefuse & #fissiontest
Thanks!
Click to expand...
Click to collapse
sorry, im a newb, how do i download from here?
edit..neverming..install process same as 1.2.1?

[Q] Can you remove Droid X Bootstrap?

Any help is appreciated, I'm still fairly new with Android, but trying to learn my way around.
When the OTA update for 2.2.1 came out, I decided to do a factory reset because I'm just picky like that, and I like to be fresh coming out of OTA updates. Prior to the factory reset, I was running stock 2.2, though I was rooted using the manual (D2) method through adb, I had bloat frozen with Titanium Backup, and I had Droid X Bootstrap installed.
I unfroze the bloat and did the 2.2.1 update prior to factory reset. I did not unroot prior to the OTA. After the OTA I did a factory reset. I expected the bootstrap to go as well. It didn't, and I noticed immediately because I was booting into its recovery every other reboot because I was no longer rooted.
I still had the superuser icon (ninja) in the app drawer, however was no longer rooted of course, so I loaded z4root and let it "unroot" me, and then let it root again, which fixed the Bootstrap recovery issue.
Here's my problem. Obviously the factory reset did not wipe everything because bootstrap was still trying to load. My phone is definitely more sluggish than it was prior to the factory reset. Different types of screen lag are very noticeable and the phone really lags later in the day if I don't reboot. I loaded less apps after the reset than I had prior to, but otherwise did nothing different. I want to try to remove the bootstrap too, as well as anything residual to try to figure this out, even if I do have to factory reset again, because it's definitely not stable the way it is. Is it possible to remove it, and how so?
I'm aware that this may not fix the problem, and to me it doesn't even make sense that it would, but I definitely feel something "off" here and for my own peace of mind I'd like to remove it at least for now just to see. I've done factory resets before and the phone always feels much snappier once it's back up and running. This time it's worse than when I started.
Any assistance would be greatly appreciated.

You would have to flash a stock sbf. Correct me if I am wrong but I think that stands for system boot file. That should take care of everything. I am sure u can find the thread on the forum on how to do it. Just to mention I think that all the boot strap does is hijack your normal boot process by interrupting it allowing u access. It doesn't actually replace the boot process.
Sent from my DROIDX using XDA App

Info on the bootstrapper can be found here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Basically it replaces the logwrapper.bin file which gets executed very early in the boot process. This allows bootstrapper to control the rest of the boot sequence.
To *just* remove bootstrapper, I think there is a backup of the original logwrapper executable stored in /system, so you could just replace the exploited version with the original.
However, if you are having issues, I would suggest you just go ahead and flash back to complete stock:
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
Make sure you are still on the 2.3.15 version before using this. Once you take the OTA (to 2.3.340) I don't think this SBF will work any longer.

So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App

sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.

crxin said:
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The .340 update "upgrades" your bootloader to 30.04. I've read that the 2.3.15 SBF will not work with this bootloader.
There are some SBF files produced by Team Black Hat (at Leaked 2.3.320 and patch files to put you to 2.3.340), but I've not used them.
I think you can find more info on those at mydroidworld (or you can support TBH by buying their app in the marketplace and downloading direct from there)

jaynyc22 said:
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
Click to expand...
Click to collapse
I'm not sure what you mean?
Try uninstalling from Manage Applications and re-install?
Do you mean the DroidXBootstrapper UI or the logwrapper exploit?

[Q] Updated to 2.3.340 but still update download message

I downloaded the new update and installed it. Took me forever to get my root back but I finally got the phone where I want it. Unfortunately, the droid x is still trying to download the update which keeps failing. I contacted Motorola and they told me to do a factory rest and that might resolve the problem but they were unsure. How do I tell the phone it is up to date without having to reset everything?

If you do a factory reset, and the OS version is not .340, then the update did not work.
*DISCLAIMER - This Can Be Dangerous*
I would suggest using RSD Lite and the. 340 SBF to update the DX to the latest software version.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.

I did the update already and the system shows 2.3.340. All I am trying to change is the phone trying to download the update and continually failing.
I don't want to do a factory reset unless it is the last resort. I do have RSD Lite but I am a little leery of flashing the phone. Is there a full SBF file available for the 2.3.340 or can I just run the update again?
Sorry for all the questions I just don't want to brick the phone and I am new to all of this.

Olson-clan said:
I did the update already and the system shows 2.3.340. All I am trying to change is the phone trying to download the update and continually failing.
I don't want to do a factory reset unless it is the last resort. I do have RSD Lite but I am a little leery of flashing the phone. Is there a full SBF file available for the 2.3.340 or can I just run the update again?
Sorry for all the questions I just don't want to brick the phone and I am new to all of this.
Click to expand...
Click to collapse
If the phone keeps trying to update, then something is likely corrupt with the software. Try this as a test:
Reboot into Clockwork Recovery
Make a Nandroid backup
Do a factory reset and also wipe cache and data
Reboot and see if you still have .340 and get prompted for the update
If you still have .340 and get prompted, then you will most likely have to SBF and start over. You can always restore the Nandroid backup to go back to your original settings and data.

OK, I will try that. Noob question though, do I need to unroot before factory reset? If so, will I also need to delete superuser.apk or will the reset delete all of that?
Thanks for all your help.

There is no need to remove root first. If you lose it in the restore just run z4root again.
Also, just to clarify my last post, the Nandroid backup would only be used if a reset doesn't fix the problem. You would then be able to restore everything back and use a program like Titanium Backup to save your data in a format that could be restored over top of a new ROM.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.

Thanks for all your help and patience. Just one more bank of questions before I start this. Do I need to rename the bloatware I changed after rooting or will the reset take care of that? Once I reset, I will need to reroot to install the backup with Droid X bootstrap, correct? Lastly, worse case scenario I have to SBF to start over, is there a full 2.3.340 SBF out there?

There is a version of .340 that has most of the components of an SBF, but it is not the actual full release. I have .320 Full and .340 System-Only on my machine, and I used them both when first updating. After the .320 update is successful, you will only need the .340 System-Only until a newer one is leaked.
Once done with both SBF files, you will use Motorola's recovery to do a Format Cache and also a Factory Reset. This will put everything back to the day you opened the phone, without root and Clockwork.
When ready to root again, install z4root (available here on XDA), reboot, then run z4root and finally, install DX Bootstrapper. You will be all set to use Root Explorer and remove the bloat all over again. Before removing the bloat, I strongly suggest creating a Nandroid backup so that you can easily get it all back in the event you need to do a warranty exchange and the USB port stops working.

So here's the latest. Did a Nandroid back up and then cleared the cache followed by a factory reset. I didn't unroot or even flash the SBF files just to see what happened. The root was still there. I had to download root explorer again along with launcherpro but otherwise the phone was good to go. Checked system updates and low and behold, it was up to date!! So far it is working just fine, had to reinstall the apps I had before that I liked but all in all it's right where it needs to be. Thank you NotATreoFan for all your help.
On a side note, I had rooted the phone via the terminal emulator so I don't know if that made a difference in keeping the root. z4root may give different results.

Glad to hear it worked for you.

[Q] Need help with unbricking/resetting, and RSD Lite

So I've been trying to flash back to factory, and I got RSD Lite and the SBF file, and the program and everything recognizes the phone in bootloader.
However, when I go to run the process, it goes through 'creating disk image' really fast, then says 'phone is not compatible with multi-interface super-file'.
What do I do? I didn't brick it, but It won't boot, all I get is the boot image till it runs out of battery.
HELP??

thatkidoptimus said:
So I've been trying to flash back to factory, and I got RSD Lite and the SBF file, and the program and everything recognizes the phone in bootloader.
However, when I go to run the process, it goes through 'creating disk image' really fast, then says 'phone is not compatible with multi-interface super-file'.
What do I do? I didn't brick it, but It won't boot, all I get is the boot image till it runs out of battery.
HELP??
Click to expand...
Click to collapse
Make sure to plug the phone in to the wall charger and let it charge to a full charge. Then unplug the wall charger, pull the battery. Then plug the wall charger back in with the battery still out. Put the battery back in and power up the phone. It should boot to bootstrap recovery. From there, you can restore a backup.
As for SBF: Are you on 2.3.340? If so, flash this file via bootstrap recovery:
http://www.megaupload.com/?d=4AO672L1
This is maderstcok .340. It is basically a clean system flashable zip that is pre-rooted. Will get you back to a clean slate.
ONLY USE THIS if you are 2.3.32 leak or 2.3.34 already. Here is the original page about it on droidxforums:
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html

SysAdmin-X said:
Make sure to plug the phone in to the wall charger and let it charge to a full charge. Then unplug the wall charger, pull the battery. Then plug the wall charger back in with the battery still out. Put the battery back in and power up the phone. It should boot to bootstrap recovery. From there, you can restore a backup.
As for SBF: Are you on 2.3.340? If so, flash this file via bootstrap recovery:
This is maderstcok .340. It is basically a clean system flashable zip that is pre-rooted. Will get you back to a clean slate.
ONLY USE THIS if you are 2.3.32 leak or 2.3.34 already. Here is the original page about it on droidxforums:
Click to expand...
Click to collapse
Ok, charging now. What if I don't have a backup? It's not my phone, and I can't guarantee this guy was smart enough to do one...

Then download the maderstcok file on your pc, move to your sd, manually boot into clockwork and install the zip from sd. It will work on any system version from 2.3.15 and up. If that doesn't work and there's no backup. Try wiping data/cache and reboot.
And if you're SBFing what is the bootloader?
For 30.04 you need the full SBF for 2.3.320 or system only 2.3.340 along with rsdlite 4.8+
For 30.03 you need the full SBF for 2.3.15 or 2.3.320 along with rsdlite 4.6+

So do I have this right? If I am on 2.3.340 there is no need to sbf? Simply use the maderstock image and restore it to be back to stock and that will accept OTA updates?

rocko73 said:
So do I have this right? If I am on 2.3.340 there is no need to sbf? Simply use the maderstock image and restore it to be back to stock and that will accept OTA updates?
Click to expand...
Click to collapse
Yes, you could use Maderstcok if you feel more comfortable flashing files. Just an FYI in case you didnt know, there is now a full 2.3.340 sbf... You can find it at mydroidworld
I also have a link in my guide in the Droid X general forum

SysAdmin-X said:
Yes, you could use Maderstcok if you feel more comfortable flashing files. Just an FYI in case you didnt know, there is now a full 2.3.340 sbf... You can find it at mydroidworld
I also have a link in my guide in the Droid X general forum
Click to expand...
Click to collapse
Nice info. One quick question. I have never had to reactivate my phone after installing any of these roms. Is using the sbf file or maderstock different than doing a factory wipe/reset is I were already bone stock?

rocko73 said:
Nice info. One quick question. I have never had to reactivate my phone after installing any of these roms. Is using the sbf file or maderstock different than doing a factory wipe/reset is I were already bone stock?
Click to expand...
Click to collapse
I'm not quite sure what you mean by these ROMs.... The files being suggested are SBF files, which are used to return your phone to an "out of the box" state depending on which Verizon update you are running off of.
for your second question, yes the SBF of maderstcok file is different that a factory reset/data wipe. All that the factory reset/data wipe does is erase your downloaded apps, and personal data such as accounts (gmail, etc).

SysAdmin-X said:
I'm not quite sure what you mean by these ROMs.... The files being suggested are SBF files, which are used to return your phone to an "out of the box" state depending on which Verizon update you are running off of.
for your second question, yes the SBF of maderstcok file is different that a factory reset/data wipe. All that the factory reset/data wipe does is erase your downloaded apps, and personal data such as accounts (gmail, etc).
Click to expand...
Click to collapse
Sorry, I meant Roms as in Rubix, Apex, etc. I understand now though. Thanks again.

rocko73 said:
Sorry, I meant Roms as in Rubix, Apex, etc. I understand now though. Thanks again.
Click to expand...
Click to collapse
No problem. If you have issues or questions, check out my guide
http://forum.xda-developers.com/showthread.php?t=940986

If you sbf,or flash madertstock you will have to reactivate your phone. Its painless dial *228, press 1, provide last 4 of ssn if prompted, wait for process to finish it may take while do not pull battery.
Sent from my DROIDX using XDA App

I think I may have messed up...
Got Droid X Bootstrapper loaded, made a back up. Forgot to wipe, and installed Liberty 1.5, rebooted... Liberty Installed. Now on reboot all I get is Liberty and the wings going around in circles over and over again.
Ugh! Anyone got any ideas?

I think I might have fixed it. Got into Bootstrap recovery mode and was able to reload my back up.
This time, back up THEN WIPE! Grrrrrr

Segfalt said:
I think I might have fixed it. Got into Bootstrap recovery mode and was able to reload my back up.
This time, back up THEN WIPE! Grrrrrr
Click to expand...
Click to collapse
yes, first rule of thumb should always be to make a backup before changing anything such as theme/ROM... unless you feel you have nothing to lose =)

Now to run a back up again and then WIPE... forgot to wipe last time. So I'm sure it was trying to load both boot files. Looked like Liberty was going to work. But, it wound up in an endless loading screen with the wings spinning.