Database Users

Wont install 2.3.20

I have unrooted reset all the factory software. Everytime I try to install the update it gets about 25% and errors and reboots. It says Failed to update.

Anyone have this issue?

Nowhere near enough info provided. Are trying to update via sbf, if so what OS. Trying to use the update manager from phone to upgrade via ota? Trying to flash the update.zip through recovery?
Sent from my DROID2 using XDA App

trying to update using the update manager via OTA.

I had this issue. I had Koush's Bootstrap (clockworkmod) installed, and I'm assuming that interfered with the process. Even when I unrooted and uninstalled, I think the recovery was still modified.
I was able to SBF 2.3.20.

I am sure this is going to be a stupid question but what is sbf and how do I do it?
I am new to droid but not new linux. Thanks for all the help so far.

hector12t said:
I am sure this is going to be a stupid question but what is sbf and how do I do it?
I am new to droid but not new linux. Thanks for all the help so far.
Click to expand...
Click to collapse
System Boot File. Check this section out on how to SBF. It explains the Mac, Windows, and Linux instructions.
http://forum.xda-developers.com/forumdisplay.php?f=741

[Q] ClockworkMod errors?

Here is my problem. I've been running Sonofskywalker3's 4.01 DL30 rom for a couple of days (loving it). I installed an app that broke my "back" button. I booted into recovery (the stock one) and did a full wipe reinstall. Then I was stuck in a boot loop.
I used Odin to flash a DL09 tar from here. Then I rooted using this method.
Every time I tried flashing a ROM I got an error about not having signed files. I installed ClockworkMod from here using the Red install listed near the bottom.
Now I can boot into ClockworkMod 2.5.0.4 (green) from ROM Manager and at one point I was able to manually boot into the RED ClockworkMod by manually holding down both volume buttons at boot up, applying the sdcard:update.zip in the stock recovery (2e).
I tried to flash the DL30 ROM again from ROM Manager (Sonofskywalker's ROM). I just get errors saying "Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1) (Device or resource busy).
I thought it might be the SD Card so I tried a different SD Card and exact same error. I even got the same error with the RED ClockworkMod
Is there a way I can flash something with Odin and get it to work? Right now I'm in the phone (not bricked) but I don't have vibrate (really weird). Any help would be greatly appreciated. Thank you.
Current Phone Specs:
Hardware version: i500.04
Model Number: SCH-I500
Firmware version: 2.1-update1
Baseband Version: S:i500.04 V.DL09
Kernel version: 2.6.29
Build Number: SCH-I500.DL09
ROM Manager v3.0.0.7
Current Recovery: ClockworkMod 2.5.0.4

Odin (complete dl01) may be looking for you
Sent from my SCH-I500 using XDA App

Grimis said:
Odin (complete dl01) may be looking for you
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
+1 this is the fix for all soft bricks. so just keep that file on your desktop like i do.

Same here
I am having the same issue. I have flashed DL01 and still cannot flash CWMrecovery that worked before. My issue will never push out the update.zip. I remember my CWM was 2.5.1.0 (green) before 2.2. Anyone else have this issue? I think I'm doing something wrong since this is happening to two different Fascinates or 2.2 leak changes something deeper that our odin cannot correct.
*** I resolved my issue: my root did not take. After I rooted, I was able to flash from Rom Manager ***

Where do I get the DL01 file? Can someone post a link? I'll be home soon and I can try it out.
Sent from my SCH-I500 using XDA App

phantom27-ck said:
Where do I get the DL01 file? Can someone post a link? I'll be home soon and I can try it out.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=867648
Check out this thread for DI01

namoh21 said:
http://forum.xda-developers.com/showthread.php?t=867648
Check out this thread for DI01
Click to expand...
Click to collapse
Thank you. I had actually just found it and came back here to post it and found that you had beat me to it. I actually just flashed DJ05 and then had to re-root. I'm about to try rom manager again but I think it might have just been that I wasn't completely rooted (crossing fingers).

Now I'm getting this error:
E: failed to verify whole-files signature
E:signature verification failed
Installation aborted
I guess it's on to DI01...

Try flashing CWM through Odin now. When I got the same error I flashed the tar file via Odin and then it worked perfect
Sent from my SCH-I500 using XDA App

OK... Trying that now. I'm trying the RED one. Is that right?

Ok... It looks like it's working... (fingers crossed)

Well... It worked... mostly...
When I am in ROM Manager and it reboots it gets messed up and ends up at the stock recovery. Then I run sdcard update.zip and it goes to clockworkmod and starts flashing the new ROM. It starts off with an error saying that there are some missing bitmaps or something, but then it works.
Not perfect but close enough (I guess.)

That's pretty much the way it is working for all of us I think. I know JT addressed the missing bitmap error in one of the new CWM threads. Glad it worked!
Sent from my SCH-I500 using XDA App

I need help please

I gained root and installed ClockworkMod Recovery. When I booted every process crashed so I selected wipe data/facory reset. Well now I only have the ClockworkMod Recovery and it will continuously load the 2 slash screens.
Before I cause anymore damage can anyone tell me how to go back to how it was from the factory?

You need to sbf from the bootloader if you didn't hose that by installing clockworkmod because it sounds like you didn't use koush's bootstrap to install it the way the D2 needs to have it installed. Please let me know if I'm wrong.
There are two tutorials for flashing the sbf one in windows and one in Linux but both have information worth knowing. I'd link them but I'm on my D2.
EDIT:
Windows.
Linux.
but you should read through BOTH of them before flashing.
Sent from my DROID2 using XDA App; Edited from a PC
p.s. I don't mean to criticize but a more informative thread title would be nice. If you had "Bootloop after ClockworkMod install" for a thread title that means more to me than "I need help".

Thank you that is a start. I really shouldn't have attempted this...

I got a critical error after I selected the sbf.

http://iamthewalcs.com/SBF Files and Update files/SBF File/Droid 2 Global FULL SBF.zip
I try to download that file but when I try and open it is says invalid.

Problem Solved I had to format everything first then do the steps listed.

[Q] Go back from GBread?

Before I tackle this upgrade I was wondering if there was a way to get back to my froyo via SBF then root then clockwork restore. Or will it brick it?

You can go back to 2.2. Just
1. sbf back to .340
2. You will bootloop, boot into stock recovery and wipe data/cache.
3. Boot into 2.2 and root.
4. Install bootstrap.
5. Restore backup/install new rom.
Sent from my DROIDX using Tapatalk

i sbf back to 2.3.340 adn i cant go in to recovery to make a data factory reset i hit sear and the recovery menu wont apear.please help

That shouldn't happen. Did you use the _full_ sbf and not the system only? Do you have the correct Motorola drivers? Have you sbf'd before using the same computer/phone?
Sent from my DROIDX using Tapatalk

vladimirtm said:
i sbf back to 2.3.340 adn i cant go in to recovery to make a data factory reset i hit sear and the recovery menu wont apear.please help
Click to expand...
Click to collapse
You have to press both volume and up button when you see the exclamation point not the search button

i did factory reset but im still stuck in moto logo

That's for the new recovery, the old recovery required you to press the search button. It sounds like the sbf didn't complete properly.
Sent from my DROIDX using Tapatalk

Did you have to press the volume up and down buttons to get into recovery? If so, you're still on the new recovery and you'll need to sbf to get back to the old one.
Sent from my DROIDX using Tapatalk

Make for certain you are using the full 2.3.340 SBF file located here
http://www.mydroidworld.com/forums/droid-x-discussion/6367-new-full-sbf-droid-x-2-3-340-a.html
Otherwise it will not boot. You can tell if you have the red M logo you still have the leaked GB bits. If you use the system only SBF file it will not work. If the full 2.3.340 SBF file worked, you will have a white M logo when you power on the phone.

This thread does not belong in Development, Moved to General. Development Questions are not Development Forum Material. Development Sections are for Development Project Threads only.
Thank you have a Nice Day.

problems getting back to froyo
I am hitting problems sbfing back to froyo 340 from gingerbread. My drivers are installed and rsdlite 4.9 is recognizing the droid x perfectly fine as well. The sbf process starts fine, but fails due to a group 31 checksum error.
ERROR: Flash failure: Interface AP-OS: Error verifying Code Group 31 checksums. File: 0x56E0, Phone: 0xB9A8 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
The strange part is that now when i reboot, it always goes back to the way my phone was before i attempted to flash it. Any apps I install just get installed. Icons that were moved get put back.
Any suggestions?

can't install roms on droid x

Hey, I'm helping my friend install a new rom on his Droid X because the GB update messed his phone up. The Recovery version is 2.xxxx. I have Team Liquid's rom which won't install and it says
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
I thought maybe the download was bad so I downloaded OMGB and the same thing happens.
I can install roms without a problem on my Thunderbolt but I know nothing about this phone. It took me a bit just to figure out how to get into Recovery. No longer can I get into Recovery with Rom Manager or Quick Boot. If I tried to use those apps it just ends up rebooting the phone.
Any ideas why this is happening? Should I install the latest version of Recovery (CWM)? I downgraded the Recovery because I thought the new version was preventing Rom Manager and Quick Boot from booting into Recovery mode. Thanks in advance!!
Edit: I downloaded the Droid 2 Bootstrap app and now I managed to get into Recovery but installation failed again. It says
"Installing update..."
"assert failed: run_program("/tmp/check_kernel")"
"==0"
"E: Error in /sdcard/update.zip"
"(Status 7)"
"Installation aborted."
Any ideas?

Sbf and try from there
Sent from my DROIDX using XDA App

Sbf to. 602 and root using petes root tools, goolge will help since I can't post links
Sent from my DROIDX using XDA App

I'm a lil confused as what you mean when you say the GB update messed his phone up. If it was a OTA update that messed the phone up, then i would simply suggest getting rid of root and going back to Verizon because it could be an issue with that phone in itself.
Now if the GB update was caused by you guys trying to do certain things than follow directions of above poster StayFrosty777 (Cool name btw dude lol).
Also make sure that you download a custom rom that is on the build. I'm unsure of whether he actually has GB or if still on Froyo. If he is still on Froyo you will need to flash a Froyo rom, flashing a rom such as Liquid 3.0 which is based on GB, will not work on Froyo.