yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] rj57:
Ok, there is a parted procedure on the Vibrant (a very similar phone) forum that looks to be exactly what we want to do.

http://xdaforums.com/showthread.php?t=1230059

Do not use the PDA file in the post, you will need to flash the EE4 with no PIT first and then reflash with EE4+PIT after it boots into recovery from the first flash.

Also, you will need to adb push parted to the bin or sbin directory. If parted doesn't work by itself (it should) download and push the files per this post:

http://xdaforums.com/showpost.php?p=17627819&postcount=10

1.) Flash CWM and boot into CWM (Do not flash a kernel unless we can't perform the next step)

2.) adb push parted /sbin/

3.) adb shell

4.) chmod 0755 /sbin/parted

5.) parted /dev/block/mmcblk0 (interactive mode)

6.) print (you should see the partition list)

7.) rm 1

8.) rm 2

9.) rm 3

10.) print (you should see no partitions)

11.) quit

12.) exit

13.) flash EE4 by itself (No PIT)

14.) let it reboot to recovery

15.) pull battery

16.) flash EE4+PIT (put battery back in after you get into download mode)

17.) reboot it and hopefully this does the trick
[Verizon Droid Charge] TrypWyr:
I feel like we are so close...

EDIT: Also, I tried running on stock kernel with CWM, no luck, so I installed GummyCharge.zip so I could get su without rebooting. Same thing tho...

# su
su
# chmod 0755 /sbin/parted
chmod 0755 /sbin/parted
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM02G (sd/mmc)
Disk /dev/block/mmcblk0: 1959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 32.8kB 1256MB 1256MB primary ext2
2 1256MB 1686MB 430MB primary linux-swap(v1)
3 1686MB 1959MB 273MB primary ext2

(parted) rm 1
rm 1
rm 1
(parted) rm 2
rm 2
rm 2
(parted) rm 3
rm 3
rm 3
(parted) print
print
print
Model: MMC SEM02G (sd/mmc)
Disk /dev/block/mmcblk0: 1959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 32.8kB 1256MB 1256MB primary ext2
2 1256MB 1686MB 430MB primary linux-swap(v1)
3 1686MB 1959MB 273MB primary ext2

(parted)
[Verizon Droid Charge] rj57:
ok, we really need to do this with CWM being the only thing that we flash over the EE4 flash. When you boot into CWM, you should have a root shell, even though thinking about it, /sbin is read only which means that you can not just push the parted file to it.

A solution may be to mount system if it is not already mounted. system can be mounted in mounts and storage in CWM.

This is what we need to do:

1.) Flash EE4 to the phone.

2.) Let it boot to recovery

3.) pull battery

4.) flash CWM in Odin

5.) boot to CWM

6.) go to mounts and storage and mount system

7.) adb shell and check that you can cd /system/xbin/

8.) exit adb shell and adb push parted /system/xbin

9.) pick up at step 4 of my earlier procedure and use /system/xbin/ instead of /sbin/

10.) at step 5 you will need to /system/xbin/parted /dev/block/mmcblk0 (interactive mode)

finish the rest of the original procedure
[Verizon Droid Charge] TrypWyr:
Same. The "rm" command seems to work, or at least no errors, but when I "print" everything is still there.
[Verizon Droid Charge] rj57:
Also, I have used the first package on this thread a while back when I borked my phone coming off of Gummy 1.8. Just flashed it, let it boot to recovery and wiped and formated. Rebooted fine for me.

http://xdaforums.com/showthread.php?t=1116867

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] rj57:
Make sure that cache and data are not mounted. Go to mounts and storage to unmounted them

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] rj57:
If that doesn't work install Imnuts 0807 novoodoo kernel and do the first parted procedure that seemed to work on rm

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] TrypWyr:
Nope, nothing with imnuts kernel. And definitely un-mounted, otherwise I get an error when running the rm command.

Now here's an idea: my wife just got back from travelling, and she has a nice working Charge without voodoo (didn't want her to deal with conversion times, and she's not a speed demon). Anything I might be able to do with it to help mine?
[Verizon Droid Charge] rj57:
What kind of error did you get with the email command? also, I looked at your previous posts on a bigger screen and it looks like we never did remove anything with parted. Have you tried to push all of the files from the following post to the /system/xbin directory? http://xdaforums.com/showpost.php?p=17627819&postcount=10

Using the above post, don't worry about getting su. if you have a # prompt, you got root. Also, use the instuctions from my previous post to run the parted rm operations instead of the ones in the linked post.

I don't think that there is anything that you can get off of your wife's phone to help.

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] TrypWyr:
What "email" command?

I pushed just the file "parted", was under the assumption that the other files were different commands and not needed for parted to work. I definitely used "rm" to remove the partitions, but it's like it didn't actually finalize or something, but I don't see anything in the parted manual saying that anything like that is needed.

I will try again and push all the files, see if that helps.
[Verizon Droid Charge] rj57:
Looks like email was SwiftKey way of saying parted.

I took a look at the sdparted script in the zip file and it looks like they take a different approach with parted.

The script is issuing an mklabel command to nuke the partition table and then a mkpartfs to create the new partitions and filesystems. That should be everything that stock recovery needs to properly format the partitions on mmcblk0.

The script may be a good blueprint on how to go about recreating the new partitions

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
I got to this point:

5.) parted /dev/block/mmcblk0 (interactive mode)

6.) print (you should see the partition list)

Instead of getting the partition list I get this:

(parted) print

print

print

Error: /dev/block/mmcblk0: unrecognised disk label

Can anyone point me to the right direction?

I would really appreciate this, oh yeah that's my work phone I just killed lol

TIA
[Verizon Droid Charge] Poloasis:
Guys I need help, I manage to get parted going and not able to make any partition including msdos. I get this:

Error: SEGV_MAPERR (Address not mapped to object)

Aborted

Can anyone point to the right thread/site how to re-create the internal partitions, don't mind reading 300 post or it's a return to VZ store.

Thanks guys.
[Verizon Droid Charge] rj57:
OK, THIS IS TOTALLY UNTESTED BUT FOLLOWS THE STEPS IN THE SDPARTED SCRIPT IN THE ZIP FILE. IT HAS THE POTENTIAL TO KILL YOUR INTERNAL STORAGE PERMANANTLY. DO NOT DO THIS UNLESS YOU HAVE FIRST TRIED THE PROCEDURE IN THE OP MULTIPLE TIMES. THIS IS A LAST RESORT METHOD

1.)Flash CWM over EE4+PIT

2.)Reboot into CWM (3 Button Method)

3.)Go to Mounts and storage and mount system

4.)Execute the following adb commands

adb push parted /system/xbin/

adb shell chmod 0755 /system/xbin/parted

adb shell /system/xbin/parted /dev/block/mmcblk0 print > MMC-Repart-log.txt

adb shell umount /data >> MMC-Repart-log.txt

adb shell umount /preinstall >> MMC-Repart-log.txt

adb shell umount /cache >> MMC-Repart-log.txt

adb shell /system/xbin/parted -s /dev/block/mmcblk0 mklabel msdos >> MMC-Repart-log.txt

adb shell /system/xbin/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat32 64 2453503 >> MMC-Repart-log.txt

adb shell /system/xbin/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat16 2453504 3293183 >> MMC-Repart-log.txt

adb shell /system/xbin/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat16 3293184 3825663 >> MMC-Repart-log.txt

adb shell /system/xbin/parted /dev/block/mmcblk0 print >> MMC-Repart-log.txt

adb shell reboot

5.)Hopefully it boots up a bit better. If not post MMC-Repart-log.txt

Edit: my bad on umount commands - fixed

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] rj57:
Have you tried the procedure in the OP?

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] TrypWyr:
Tried with all files present, same issue.

Reading the sdparted script itself is a little over my head... What do you think would happen if I ran the script? Probably nothing good, eh?
[Verizon Droid Charge] rj57:
Did you look at what I put up a few posts up. Running the script as is would make a mess at best.

Different filesystems setup, disk size eetc

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
It's boot looping with Droid anim no sound

Here is the MMC-Repart-log.txt:

Error: /dev/block/mmcblk0: unrecognised disk label

umount: can't forcibly umount /dev/block/mmcblk0p1: No such file or directory

umount: can't forcibly umount /dev/block/mmcblk0p2: No such file or directory

umount: can't forcibly umount /dev/block/mmcblk0p3: No such file or directory

Error: Input/output error during read on /dev/block/mmcblk0

Error: Input/output error during write on /dev/block/mmcblk0

Error: /dev/block/mmcblk0: unrecognised disk label

Error: /dev/block/mmcblk0: unrecognised disk label

Error: /dev/block/mmcblk0: unrecognised disk label

Error: /dev/block/mmcblk0: unrecognised disk label

Thanks for anything you can recommend.
[Verizon Droid Charge] rj57:
Can you try to odin ee4+ the pit again to see if it will repartition?

Also, what did parted print show before you rm d the partitions?

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] TrypWyr:
Whoops, no, I didn't see that post!

Followed the instructions to the letter, copied and pasted all the commands. Here's my command list:

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push parted /syste
m/xbin/
2418 KB/s (346680 bytes in 0.140s)

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 0755 /
system/xbin/parted

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted /dev/block/mmcblk0 print > MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell umount -f /d
ev/block/mmcblk0p1 >> MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell umount -f /d
ev/block/mmcblk0p2 >> MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell umount -f /d
ev/block/mmcblk0p3 >> MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted -s /dev/block/mmcblk0 mklabel msdos >> MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat32 64 2453503 >> MMC-Re
part-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat16 2453504 3293183 >> M
MC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted -s /dev/block/mmcblk0 unit s mkpartfs primary fat16 3293184 3825663 >> M
MC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /system/xbin
/parted /dev/block/mmcblk0 print >> MMC-Repart-log.txt

C:\Program Files (x86)\Android\android-sdk\platform-tools>

And here is the output:

Model: MMC SEM02G (sd/mmc)

Disk /dev/block/mmcblk0: 1959MB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 32.8kB 1256MB 1256MB primary ext2

2 1256MB 1686MB 430MB primary linux-swap(v1)

3 1686MB 1959MB 273MB primary ext2

umount: can't forcibly umount /dev/block/mmcblk0p1: Invalid argument

umount: can't forcibly umount /dev/block/mmcblk0p2: Invalid argument

Error: You requested a partition from 64s to 2453503s.

The closest location we can manage is 63s to 63s.

Error: Can't have overlapping partitions.

Error: Can't have overlapping partitions.

Model: MMC SEM02G (sd/mmc)

Disk /dev/block/mmcblk0: 1959MB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 32.8kB 1256MB 1256MB primary ext2

2 1256MB 1686MB 430MB primary linux-swap(v1)

3 1686MB 1959MB 273MB primary ext2
[Verizon Droid Charge] rj57:
ok, the partitions didn't remove using mklabel, just like rm didn't seem to work.

let's try to just do a mkfs command over the existing partitions, wouldn't normally do this but here goes. For testing, we are just going to do the data partition and see what we get.

after we get parted pushed to /system/xbin and chmod 0755 it, do a '/system/xbin/parted print' in adb to verify that we are starting with the 3 partitions.

next execute this command in adb '/system/xbin/parted mkfs 1 fat32'

finally execute '/system/xbin/parted print' in adb to see if partition 1 changed.

As always post your result
[Verizon Droid Charge] Poloasis:
Odin EE4 and then EE4+Pit multiple times to no end.

Never were able to bring the partition with parted, when the phone got stuck on Samsung logo, I was never able to see them much less rm partition them.

Hopeless?
[Verizon Droid Charge] rj57:
Your partition table is totally gone. A little different than the issue that TrPWyr is having.

It looks like the partition editing functions of this parted program are not working in some cases. It reads fine though.

There is a MBR file at the link below that you may be able to use with cat or dd to write a new partition table to /dev/block/mmcblk0

you will need to extract the zip file to your platform-tools directory and adb push it to /sdcard/

Then you will need to execute this command from adb:

cat /sdcard/charge-pt.mbr > /dev/block/mmcblk0

or

dd if=/sdcard/charge-pt.mbr of=/dev/block/mmcblk0 bs=1 skip=0 count=512

Then try to flash the EE4+PIT and then CWM, if it bootloops

Next you will need to start the manual parted procedure and see if you can see the partition table.

The zip is at the following post:

http://xdaforums.com/showpost.php?p=17654744&postcount=269

If you get a write error, when you cat it, the internal storage is likely toast.
[Verizon Droid Charge] Poloasis:
I will go ahead with you recommendation and post results shortly.

Thanks again bud.

---------- Post added at 09:17 PM ---------- Previous post was at 08:23 PM ----------

I have push charge-pt.mbr to the /sdcard:

adb push c:charge-pt.mbr /sdcard and got this:

3 KB/s (512 bytes in 0.157s)

Should I be on adb shell to run the following because when I run

cat /sdcard/charge-pt.mbr > /dev/block/mmcblk0

I get this error

cat: can't open '/sdcard/charge-pt.mbr': No such file or directory

A little help, because I have my hopes high lol
[Verizon Droid Charge] rj57:
You need to be in adb shell to run the cat

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
I was, just wasn't sure since I got the error, this is what I got:

~ # cat: can't open '/sdcard/charge-pt.mbr': No such file or directory

After running the command...any ideas?
[Verizon Droid Charge] rj57:
Looking at what you adb pushed, it looks like you may have a 512 byte file in /. You pushed to /sdcard instead of /sdcard/ Do an ls -l and see if there is a file called sdcard

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
C:\>adb shell

~ # ls -l

ls -l

drwxr-xr-x 3 root root 0 Jan 1 00:00 acct

drwxrwx--- 2 system cache 0 Jan 1 00:00 cache

dr-x------ 2 root root 0 Jan 1 00:00 config

lrwxrwxrwx 1 root root 17 Jan 1 00:00 d -> /sys/kernel/debu

drwxr-xr-x 3 system system 0 Jan 1 00:00 data

drwxrwxrwx 2 root root 0 Jan 1 00:00 datadata

-rwxr-xr-x 1 system system 118 Jul 30 2011 default.prop

drwxr-xr-x 9 root root 13440 Jan 1 00:00 dev

drwxrwx--x 2 system system 0 Jan 1 00:00 efs

drwxrwxrwx 2 root root 0 Jan 1 00:00 etc

-rwxr-xr-x 1 system system 2737 Jul 30 2011 fota.rc

-rwxr-xr-x 1 system system 141364 Aug 12 2011 init

-rwxr-xr-x 1 system system 1613 Jul 30 2011 init.goldfish.rc

-rwxr-xr-x 1 system system 21637 Aug 12 2011 init.rc

-rwxr-xr-x 1 system system 351 Jul 30 2011 init.smdkc110.rc

drwxr-xr-x 3 system system 0 Aug 17 2011 lib

-rwxr-xr-x 1 system system 704 Jul 30 2011 lpm.rc

drwxrwxr-x 6 root system 0 Jan 1 00:00 mnt

dr-xr-xr-x 68 root root 0 Jan 1 1970 proc

-rwxr-xr-x 1 system system 10487 Aug 16 2011 recovery.rc

drwxr-xr-x 4 system system 0 Aug 17 2011 res

drwxr-xr-x 2 system system 0 Jan 1 00:00 sbin

lrwxrwxrwx 1 root root 11 Jan 1 00:00 sdcard -> /mnt/sdcard

drwxr-xr-x 12 root root 0 Jan 1 1970 sys

drwxr-xr-x 3 system system 0 Aug 17 2011 system

drwxrwxrwt 2 root root 60 Jan 1 00:00 tmp

drwxr-xr-x 4 system system 0 Aug 17 2011 voodoo
[Verizon Droid Charge] rj57:
OK, redo the adb push to /sdcard/ note trailing slash. Big difference from /sdcard

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
Ran this:

C:\>adb push c:charge-pt.mbr /sdcard/

71 KB/s (512 bytes in 0.007s)

Then ran

cat /sdcard/charge-pt.mbr > /dev/block/mmcblk0

I get this error

cat: can't open '/sdcard/charge-pt.mbr': No such file or directory

I know I may be keeping you from bed, but when ever you want to pick this tomorrow, I'm cool and very appreciative for your help.
[Verizon Droid Charge] rj57:
If you are on the latest CWM (orange) you may need to mount the external sdcard (mounts and storage menu) Once mounted, you can retry the push then cat.

I'll check in the morning

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak

---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------

And you could always push it to /system/xbin/ and adjust the path on the cat command
[Verizon Droid Charge] mlm2588:
This was a life saver on my soft brick just now... What you guys do is truely amazing and a huge help. Thanks a ton
[Verizon Droid Charge] Poloasis:
Ok, this is the result from the following command I ran last night

C:\>adb push c:charge-pt.mbr /sdcard/

71 KB/s (512 bytes in 0.007s)

CC:\>adb shell

~ # cat /sdcard/charge-pt.mbr > /dev/block/mmcblk0

cat /sdcard/charge-pt.mbr > /dev/block/mmcblk0

cat: write error: I/O error

~ # dd if=/sdcard/charge-pt.mbr of=/dev/block/mmcblk0 bs=1 skip=0 count=512

dd if=/sdcard/charge-pt.mbr of=/dev/block/mmcblk0 bs=1 skip=0 count=512

dd: writing '/dev/block/mmcblk0': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 23.550663 seconds, 0B/s

~ #

C:\>adb push charge-pt.mbr /system/xbin/

8 KB/s (512 bytes in 0.056s)

C:\>adb shell

~ # cat /system/xbin/charge-pt.mbr > /dev/block/mmcblk0

cat /system/xbin/charge-pt.mbr > /dev/block/mmcblk0

cat: write error: I/O error

~ #

C:\>adb shell

~ # cat /system/xbin/charge-pt.mbr > /dev/block/mmcblk0

cat /system/xbin/charge-pt.mbr > /dev/block/mmcblk0

cat: write error: I/O error

~ # dd if=/system/xbin/charge-pt.mbr of=/dev/block/mmcblk0 bs=1 skip=0 count=512

dd if=/system/xbin/charge-pt.mbr of=/dev/block/mmcblk0 bs=1 skip=0 count=512

dd: writing '/dev/block/mmcblk0': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 23.551062 seconds, 0B/s

~ #

I've mounted /sdcard/and /system/sbin/ before I run the commands.

And yes I flashed the latest orange cwm.

Let me know what you think.

Thanks
[Verizon Droid Charge] rj57:
I don't know of any way to get around the i/o errors. The likely scenario is that the internal sd card is bad.

At this point, I am pretty sure that you have a hardware failure.

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak
[Verizon Droid Charge] Poloasis:
Thought so to, I'll try to get it replaced and again thanks allot for you help, learned allot.
[Verizon Droid Charge] Poloasis:
VZ would get me a replacement "used phone" in about two days witch I couldn't wait because I got in trouble to be without a phone for two days "Network Admin" so I moved to the dark side and got the Bionic "at least until the Prime comes out" and no, I didn't pay anything for it "Business account" lol.

It's a fast phone because of the dual core, but the screen compare to SuperAmoled+ is crap.

Anyway wanted to say a big thanks to rj57 for the help.
[Verizon Droid Charge] Makaveli315:
PLEASE HELP ME PLEASE... After doing everything your directions say to do step by step, it won't boot up anymore. It just goes into "Android system recovery <3e>" of " Samsung Recovery Utils For BML" and it gives me the options to "reboot system now, apply sdcard:update.zip, wipe data/factory reset, wipe cache partition, and format internal sd-card". Please help me, I've tried to wipe cache and then reboot but still it just goes back to the bootloader. Thank you!
[Verizon Droid Charge] rj57:
I am assuming that you performed imnuts' procedure at the OP in this thread. Is that correct?

Also what happened leadin up to you needing to fix your phone? And what were you running before you got to this point?

Which PDA package did you use? ED1, ED2, or EE4? I would at least try it with the ED1 and EE4 package from pentafive's thread at the link below?

http://xdaforums.com/showthread.php?t=1172182

Also, you could try to format the internal sdcard in recovery.

If none of those work, you will need to have adb set up from the android sdk so that we can determine the state of your internal sdcard.

Also, just a note don't panic and start flashing everything. Impatience can be your worst enemy in trying to recover your phone.
[Verizon Droid Charge] Makaveli315:
First off, I'd like to thank you for replying so quickly considering I'm going nuts right now but anyways I did imnuts' procedure however I used my stock backup (file name "stockrootedED1-20110517.tar.md5") that I created a while back right before I rooted my Charge. Anyways, what lead me to try and unroot my phone was... well you remember about a month after the Charge was released that you were only able to root it with the downgraded firmware? Well I wanted to have the most up to date version of my firmware and when It would pop up every other hour I decided to just get it but when it tried updating, it would try but quickly just reboot.. Also when I'd try to flash a ROM like "Gummy Charged 2.0FE" it would do the same thing (like the bootloader is corrupted or something.) So therefore I just tried unrooting it and then rerooting it to be able to have the update and flash a ROM but now I'm here very stressed out and frusturated but I really appreciate you spending some time to help me resolve my situation. I uploaded a picture of what my phone shows now on Photobucket (Link is below) to better help you understand my position right now.
[Verizon Droid Charge] rj57:
It looks like you have an issue with your data that is probably fixable.

Try these steps and see if one of them will let you boot.

1) format the internal sdcard and reboot

2) Try the ED1 in the OP

3) Try the EE4 that I referenced above

_____________________________

Bloat frozen EE4

CWM 4.0.1.4

PBJT Voodoo 0730

V6 SuperCharger

Loopy Smoothness Tweak