Database Users

How to remove clockworkmod recovery boot?

I just want to remove the clockworkmod recovery to regular or stock recovery? I found the info for EVO 4g and it said not to use for anything else. Could someone, please tell me how to remove clockworkmod recovery and change it back to stock?

First- this applies if you are on 2.2 ota- not 2.1 or leaked 2.2
The easiest way now might be simply starting from scratch. The 2.2 ota sbf was released last night so you can use it to restore your phone to factory state. You will need the SBF and the latest version of RSDLite. Google...
VRZ_MB810_2.3.15_1FF_01
and something should come up. It is a large file. 430mb or so. (unzipped)
Also google rsdlite 4.8 it is not a very large file. I have never done the sbf before- but there is a guide on the droid x rootzwiki...
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
WARNING!!! make sure you are using the FULL SBF for 2.2! there is a sytem sbf for 2.2 that you don't want and there is the 2.1 sbf that you definitely don't want.
There may be just a simple uninstall- but I don't know how. I am a newb. Maybe a veteran will chime in with some help?

Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.

Cyc323 said:
Thank uou.
I was able to do that lastnight. before I got home from work, I downloaded SBF file with myDX. It took me an hour. By 8:00 pm my phone was rooted again without clockwork mod.
Click to expand...
Click to collapse
Cool. Since I have never done it before- did you just follow the rootzwiki guide? And was it pretty straight forward? And- how long once you actually started RSDLite did the process take (assuming you used RSDL)?
thanks.

It wasn't painful. I used rsd lite 4.8. I searched for info on 4.8 but everything is on 4.7, even on rootzwiki . On 4.7 you are suppose to move an .ini file to another place. I saw a similar file but without the .ini extension. I thought maybe this is one of the improvement of 4.8 over 4.7. You also have to do the bootloader thing. The whole process took about less than 10 minutes. I was surprised that nothing on the phone was erased other than titanium backup. Wallpaper and Launchpro's settings were still intact.

[Q] Help with either update.zip to 2.3.40 or SBF?

I'll keep this short so I can get straight to the point. Was running Apex ROM on 2.3.15, and a new version is out for the OTA update that just came out, 2.3.40. Reverted back to stock everything, tried to apply the update.zip, and got an error that said "status 7." Did some reading, saw a suggestion to apply the clean Droid X image from 928droid.com. I did that, tried to update.zip, and it still wouldn't do it. I've cleared everything a couple times and keep getting the error.
So unless there's another route I can go to get the update applied (which I'd love to hear so I can avoid SBF'ing), it looks like I'll need to just SBF. Problem is, in the SBF guides I've seen, it says that the current SBF (the ~450MB one) will only work for the 30.03 bootloader, not 30.04... Well I have 30.04. So I really don't know what to do.
ANY help would be appreciated.

If you already have the 30.04 bootloader (refurb phone on 2.3.151?), you can use the system only SBF for 2.3.340.

It is a refurb that I just got with the 30.04 on 2.3.151. So I should just follow the instructions here as though I'm running the 2.3.20 leak even though I'm not?

Crap crap crap!
You can't use just the system only SBF for 340! No kernel means problems for you! Get your 2.3.151 back to bone stock and try Verizon's over the air update now that it's out. If that doesn't work I'm not sure where you go from where you are.

The OTA update doesn't work, it downloads it, goes to install it, then after getting about 1/4 of the way in it says it failed.

Try the 320 update.zip or the 320 full SBF from Team Black Hat, then do the system only SBF to 340. That should get you back to the right path.

Can you tell me where to get the 320 update.zip?
Right before the Status 7 error it says "Error in /cache/Blur_Version.2.3.15.MB810.Verizon.en.US.zip", if that matters to anyone reading.

You can look around the forums here or over at MDW, but I'm guessing all the links are long gone by now. The Team Black Hat app is a few bucks on the Market and has all the files you want, and to be honest it's worth it. Those guys do a lot for the community!

Wiped data and cache, then restored the backup from here - http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
After that I was able to update, no SBF's anywhere in the process.
Just thought I'd post because I've seen a handful of people having similar problems today.

err:a5,70,70,00,00 for droid x

ok so after the new ota update my phone was running slower so i flashed it back to VRZ_MB810_2.3.15_1FF_01.sbf or at least thought i did. well it says its finished in rsd lite but the phone is stuck on boot loader with error err:a5,70,70,00,00. Is there a rom i can use to flash to unbrick? would the vrz_a955_2.3.20_1ff_01.sbf work despite being for the d2? any help, ideas, or suggestions would be appreciated.

You must use the 2.3.32 sbf now, its on mydroidworld

thank you very much
since i cant post links just google "droid x 2.3.32 sbf" and its the 1st result
downloading now

ouch.. you went backwards. Never good to go backwards on a DX due to the locked bootloader. A full SBF of 2.3.340 may be your only hope. Unfortunately not available yet.. Is clockwork mod gone too? If not you can try the kernel/system updates that TBH just produced. Here is the link
mod edit from Sleuth
Thanks to mob87, I now understand that the 2.3.32 full SBF can be used. Once complete, install clockwork mod then flash the 4 TBH update.zip files (bootloader, kernel, system, baseband) from the above link to restore your phone to the full 2.3.340 OTA.
Whew. Nice to know we have a safety net on 3.2.340.
end mod edit

yup i am stuck at the bootloader screen
boatloader
30.04
err:a5,70,70,00,00
mem_map blank
service req'd
battery ok
ok to program
transer mode:
usb
this is all i see
im hoping this works
Droid X: 2.3.32 Full SBF
Team Black Hat does not normally release full sbf files, but today we have received permission to release one. Please do know, that this is not the normal operating procedure and will most likely not be repeated in the future.

and im in the middle of a snow storm and my net keeps going in and out, normally have 20 down and pulling .5 down right now so a hour to dl a simple 200mb file, life is great right now.

Sleuth255 said:
ouch.. you went backwards. Never good to go backwards on a DX due to the locked bootloader. A full SBF of 2.3.340 may be your only hope. Unfortunately not available yet.. Is clockwork mod gone too? If not you can try the kernel/system updates that TBH just produced. Here is the link
Click to expand...
Click to collapse
2.3.32 sbf works fine if you updated to the OTA so no need for a 2.3.340 sbf

got both downloading now, thank you for you help, now if only i could get some dl speed, lol, i hate snow.
so 2.3.340 would be pointless? the reason i ask is it only has 5 minutes left and the happy_holidays_from_tbh.zip has 27 minutes.
by the way you guys are great and i truly appreciate your help. i cant contribute much but i will give what i can. still a n00b and am learning more and more.
i see now that dl is done 2.3.340 is a update and i cant load the stupid phone so i cant get to bootstrap so im stuck for another 12 mintues till the 2.3.32.sbf is done.

2.3.32
sw update
in progress..
tick tock tick tock

at least i no longer have a brick got the M now and waiting the droid eye, there it is, back in biz. thanks for all the help from everyone. do i need to do anything else now?

You aren't on the official OTA now. If you want to be flash all the patches posted on mydroidworld

mob87 said:
2.3.32 sbf works fine if you updated to the OTA so no need for a 2.3.340 sbf
Click to expand...
Click to collapse
Good to know we have a safety net for 2.3.340. Previous post updated with method. Thx!

[Q] Update to 2.3.340 fails after reboot

I got a DX a few months ago, rooted it, etc. About a month ago I decided to go ahead deodex it. Installed CWM and did a backup first, then deodexed. During the process the instructions said to copy the guava.odx file out of the modded fileset, so I did. Everything seemed to work OK, rebooted, been fine since.
Early this week I got the update notice for 2.3.340, so I restored the CWM backup, downloaded the update, and tried to install. The phone rebooted and began installing the update. A few seconds into the install I see what looks like a yellow triangle around the progress bar, and it bails out. Once it finishes rebooting I get a message that the update failed.
I haven't removed any bloatware apps, so I don't think it's that. I suspect it's either 1) that I'm rooted, althoughs others here have updated while rooted; or 2) that guava.odx is missing and I'm not sure where to put it back.
Any ideas on my next step? Grab the 2.2 SBF and start over?
THanks.

jjalenak said:
...Installed CWM and did a backup first, then deodexed... ...Any ideas on my next step? Grab the 2.2 SBF and start over?
THanks.
Click to expand...
Click to collapse
Um - sorry. I did read the post wrong.
I am rooted and was able to install. So I don't think that is it. After you rooted - but before you made your back up - did you mess with any system files or remove any bloat ware? You need to have all of that stuff to successfully install the OTA.

I don't remember messing around with anything. I had originally thought I'd remove the bloatware, but ended up not doing that.
Where would I find the stock 2.2 SBF? I can restore that, then update and re-install all of my apps, etc. Can someone also provide the instructions on how to install the 2.2 SBF?
Thanks.

Head over to mydroidworld.com and check out their thread on the update. You can flash it via cw recovery along with the baseband, bootloader, etc.
Sent from my DROIDX using Tapatalk

A full SBF (2.3.320) via RSD cures all then start all over ***MAKE BACK UPS !!!** Then do 2.3.340 via phone.
If you want to really do it right copy your SD to you PC format the SD with your phone and only add back to the SD files you need and know that way you get rid of any old data files that may haunt your phone.

So I hit MyDroidWorld and found the 2.2 SBF thread. Downloaded the file along with the RSD Lite version. Update the Moto USB drivers to the latest 4.8 drivers, and installed RSD Lite. Plugged my X in, making sure it was set for PC mode and Debugging - but it doesn't show up in RSD Lite. What now? Or did I manage to overlook a crucial step?
Thanks.

Found that I had to put the phone into 'bootloader' mode. Did so, and the phone now shows up in RSD Lite. I can select the .SBF file, but the 'Start' button remains grayed out.
<sigh>
It shouldn't be this difficult, should it?
Do I have the wrong .SBF file? The bootloader shows 30.03, so I think that's the correct one for the 2.2 SBF....
Thanks.

Found an approach to flashing the 2.1 SBF here - http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
This seemed to work (RDS List showed 'Passed' as the final status), but when I go to reboot it is giving me an error. Here's what's on my screen -
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
Help! What do I need to do next?

Apparently needed the 2.2 SBF. Flashed it and the phone has re-booted successfully. Whew. What a pain in the a.....!
Thanks.
PS - RSD Lite has a status of 'Please manually power up this phone.', progress is 'Executed; 100%', Result is 'In Process...'. THe phone is powered up, although I do have this odd little blue triangle in the status bar next to the signal strength. If I click 'Close' in RSD Lite I get a message "Application is currently busy. Closing application may DAMAGE the attached device.". Needless to say I'm a little unsure about this. Is it OK to unplug the USB cable and close RSD Lite?
PPS - OK, needed to *228 it. Still not sure about close RSD Lite though...
PPPS - Success! Went ahead and unplugged the USB cable, then closed RSD Lite. Did the 2.3.340 OTA, rebooted, and everything appears to be OK. Need to get my root access back, but that shouldn't be too bad.

[Q] [URGENT] [HELP REQ] Err: A5,70,39,00,27

Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?

AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.

bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.

I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App

http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...