yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] imnuts:
Initially, this post was meant to fix people's phones after a bad restore from CWM, but now I'm changing it to be more general and pretty much be a guide for how to fix your phone from nearly any problem. The original reason for this post is this error:

-- bootmode=7 from cmdline...
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation

--Movi_check already executed!!...

--movi_checking done!...
# MANUAL MODE #

It was caused by a problem with /data and this guide helped fix that. Now that several other things have come along (leaks, voodoo, etc.) people are having a host of random errors show up with their phones. This guide will hopefully get you back to a working phone regardless of what is wrong with it. Take note though, that following this guide will delete all data not on the sdcard. So, with that being said, here is how you can fix your phone.

1. Download one of the packages below as well as the PIT file.

2. Open up Odin, click PDA, and select the package you downloaded

3. Click on PIT and select the PIT file that you downloaded.

4. Get your phone into Download mode.

4a. Pull out the battery, hold down on Vol Down, and plug in the USB Cable while still holding the button.

4b. After you are in Download Mode, put the battery back into your phone. This increases the reliability of flashing with Odin

5. Make sure your phone is recognized in Odin

6. Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.

7. Press "Start" and flash the package.

8. After it is finished flashing, take the battery out, unplug the USB cable, put the battery back in, and start up what should now be a working phone.

Download descriptions. There are 3 files linked to below. The first is the PIT file, and required for this. The PIT file is the partition information table. It tells your phone where different packages go on the phone, as well as how big partitions are on the phone. Without this information, Odin cannot properly re-partition your device. The next two files are more or less the same and you will only need one of the two, not both (unless you want them just for fun). There is ED1, which is what the phone initially shipped with, and ED2, the update that was released just after the phone was. The ED1 package may be a little bit smaller for those that are concerned about download size as it is compressed. However, you will need 7-zip or similar to extract it after downloading. Also note that this cannot be done with Heimdall as Heimdall does not have the ability to re-partition your phone, thus, you need a Windows computer to be able to follow this procedure.

All packages are available here.
[Verizon Droid Charge] will2live:
Sweet, as always thanks for the work/effort on this stuff. At least now we don't have to be AS concerned atm if a restore was done in CWR and someone hoses there device.
[Verizon Droid Charge] papi92:
this work for anyone?
[Verizon Droid Charge] imnuts:
Updated this with what I believe to be the proper steps. I was in and out at work while papi was fixing his phone, and lost track of the exact files used, but some combination of the above Odin packages and the PIT should get you back to a working phone if you are having a problem.
[Verizon Droid Charge] davey11:
Good sh|t man ... phone was bound to have growing pains.
[Verizon Droid Charge] trebores1:
Unfortunately, I am trying to fix this very problem right now.

I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.

Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.

Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
[Verizon Droid Charge] hoppermi:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
[Verizon Droid Charge] trebores1:
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
[Verizon Droid Charge] trebores1:
And, yes - I was able to previously flash the ed2-debloat rom from CWM, but it wouldn't boot up... I may try that again while I'm waiting for the stock-ED1 root to finish downloading.
[Verizon Droid Charge] hoppermi:
Pretty sure that papi flashed this http://xdaforums.com/showthread.php?t=1085190 one the error message was gone, and he was good to go.
[Verizon Droid Charge] papi92:
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
[Verizon Droid Charge] trebores1:
Yeah, that worked. It got rid of the error and I can now boot into stock recovery.. but I'm stuck in a droid eyeball bootloop now. Not sure what else to do. I factory reset everything. I think it's time to just return to the VZW store.
[Verizon Droid Charge] papi92:
Don't return it. You got that far it can be restored. Try flashing altered beast thru odin o
[Verizon Droid Charge] papi92:
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
[Verizon Droid Charge] briaguya:
Same here. Flashing altered beast fixed the problem and let me cwm flash debloatedv4. (4.1 seems really buggy)
[Verizon Droid Charge] trebores1:
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?

I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.

When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.

Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
[Verizon Droid Charge] papi92:
You need to wipe data. You have too. And yes I got stuck at Samsung logo after. I had to flash stock ed1 rooted then wipe data
[Verizon Droid Charge] imnuts:
To find out if lagfix is disabled run mount from a root terminal app, or adb shell mount if you're hooked up to your computer. If anything shows up as ext4, lagfix is still enabled. If it is all rfs/vfat/not ext4 then you're ok.
[Verizon Droid Charge] trebores1:
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!

Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
[Verizon Droid Charge] hoppermi:
Did you activate another phone? I know someone w/ a TB who reactivated his Fascinate then wanted to switch back and his sim wouldn't work. Had to get a new one.
[Verizon Droid Charge] rj57:
Bauserman did look better than I have seen in the past. Am in Columbus now.

Did you flash a kernel? If not, try Imnuts latest novoodoo.

Sent from my SCH-I510
[Verizon Droid Charge] rj57:
Also, if you have adb, you could take a look at at your root file system to see if the files are there.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
I had flashed PBJ in the past. And don't believe i have adb, or not that I know of.

I flashed CWM and then flashed Gummy 1.9.1 It loaded to CWM (aqua green). I rebooted system and finally got the setup app. But I also has about 10 force close msgs for various apps.

UPDATE: Serious lag on keyboard and everything else I try to do. Force close msgs continue to pop up.
[Verizon Droid Charge] rj57:
My guess is that you have a corrupt /system and or /data partition. If you can, format both in CWM and then reflash Gummy.

If you don't have the format options, the latest CWM has them under mounts and storage.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
I formatted /data. I tried to format /system and got this msg:

E:format_volume failed to unmount "/system"

Error formatting /system!
[Verizon Droid Charge] rj57:
Go ahead and try to flash gummy again and see what it does. Sounds like the may be a permissions issue with /system

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
It let me format /system and I reflashed gummy. It booted into CWM and I wiped cache, dalvik, and data before rebooting. It went into the setup app, but I'm hit with multiple force close msgs for various apps before I've done anything.

Can I fix this by uninstalling the apps and then restoring them? Or is this going to be a persistent issue?

I'm also seeing an incredible lag.
[Verizon Droid Charge] rj57:
OK with everything that you have done, corruption may not be the issue.

Does the CWM that you are using have a Fix Permissions option under Advanced? If so, try to run that. If not, you could flash Imnuts 8/17 CWM and run the fix permissions.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
It does have fix permissions. What data size do I want to select? The options are:

128M

256M

512M

1024M

2048M

4096M

I was not able to complete the setup app before. It force closes as do most of the apps I try to run.
[Verizon Droid Charge] rj57:
Ok something is not right here. Are you on the 4.0.0.8 (Blue) CWM?

Mine just does it without asking for a data size.

Just looked at imnuts source on github and it looks like it was probably broken prior to 8/4. Your probably best to flash the 8/17 CWM (4.0.1.4 Orange). The fix permissions definitely works on that one.
[Verizon Droid Charge] zagoric:
mine says CWM Voodoo Lagfix Recovery v4.0.0.8 and it is blue. I'll look for the other one you mentioned.
[Verizon Droid Charge] rj57:
This is the one that I was referring to http://xdaforums.com/showthread.php?t=1112804
[Verizon Droid Charge] zagoric:
Thanks. I found that and flashed it. From there it would only load into download mode or recovery. I was able to fix permissions and flashed gummy 1.9.1 again. I hung on the Samsung logo at this point. I 've let it sit there for well over an hour twice now, so I don't think it is an issue of it loading.
[Verizon Droid Charge] rj57:
Try the following

1.) Boot into recovery

2.) In mounts and storage, format system, cache, data, and datadata

3.) flash your kernel

4.) flash Gummy

5.) run fix permissions (This needs to be done after the ROM has been flashed)

6.) reboot

Note that CWM will be downgraded if you flash a PBJT kernel that is older than the 7/30 version. I would recommend using the latest PBJT if you can get it onto your SD card.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
This may show you how limited my knowledge is, but PBJ is the kernal, correct? CWM has nothing to do with this other than I will flash PBJ through CWM?
[Verizon Droid Charge] rj57:
PBJ is the kernel CWM is the recovery utilities.

I just checked my instructions and you will want to mount data and datadata before formatting them. after formatting, unmount them. all of the options are under the mounts and storage in CWM. Also run fix permissions right after flashing Gummy and before you reboot
[Verizon Droid Charge] zagoric:
Will do. Do you know the date of the latest PBJ I should look for?

What if I can't get PBJ onto the sd card? I haven't been able to get my cpu to read the phone as storage.

Because of this I've been flashing gummy via odin, as well. If I need to continue doing this, when do I fix permissions? On initial reboot after flash?
[Verizon Droid Charge] rj57:
go ahead and download this kernel for later. http://xdaforums.com/showthread.php?t=1104634

If you are currently using a voodoo kernel, get the voodoo one, otherwise get the novoodoo one.

Good news is that once you get to at least setup, you should be able to get this onto your SD card and it will update your CWM to the latest.

Fix permissions should be done before you boot while you are still in the new CWM as you will have your CWM downgraded when you flash the kernel that you have on your SD card.
[Verizon Droid Charge] zagoric:
I had voodoo before. Would it have been erased when flashed the PIT file?
[Verizon Droid Charge] rj57:
The PIT file should have given you fresh partitions. However if you flashed a voodoo kernel after the PIT, it should have converted the partitions back to ext4 (voodoo). If lagfix is disabled, then the partitions should still be nonvoodoo. Did you hear the robot lady on first boot?

Also, how are you flashing Gummy? From the Odin or from CWM?
[Verizon Droid Charge] zagoric:
I haven't flashed any kernals since flashing the PIT file, so I assume I am still in non-voodoo. Would I have heard the voice when going back to non-voodoo? I did not hear a voice. This would let me know if the PIT file took hold or not.

I'm flashing gummy via ODIN since I was getting a could not mount sd card msg at one point and reformatted the sd card in an attempt to correct. I haven't been able to read the phone as storage since, so I can't get any files on there to flash via CWM yet.

So I should flash the non-voodoo now? At what point would I be able to go to voodoo? And can I flash the kernal via ODIN? I'm getting the E:Cant mount /sdcard msg.
[Verizon Droid Charge] anoninja118:
no you do not hear the voice if voodoo isn't activated... even when it is you only hear it once when its converting the partitions for the first time

you could try fixing permissions in CWM under the 'advanced' section, you could also go to 'mounts and storage' and mount /system and /sdcard if they're not mounted... or you could look for that sd card fix and flash that too

you can flash voodoo or non-voodoo whatever one you want at any time you want just remember if you do flash the voodoo kernel and want to flash something else thats not voodoo (I don't even think there is anymore except for absolute stock as even GB kernels support it, so mainly for going to stock) you would need to odin EE4 with the PIT file... and I don't think there are any odin packages for kernels, they need to be flashed in CWM
[Verizon Droid Charge] zagoric:
Will it be a problem then to flash a rom before the kernal. I looks like I'll have to have a rom installed to get the cpu to read the phone as a drive.
[Verizon Droid Charge] anoninja118:
nope no problem with rom first, matter of fact most roms cone with kernels so you'll be set... most are voodoo, though you can change them later if you want

blazing through on my 4G Droid Charge
[Verizon Droid Charge] rj57:
OK when you flash gummy through odin, you are putting a new CWM, voodoo kernel, and gummy on all at once. You should have heard the robot lady.

At this point, you need to do the pit and stock EE4 to try to get the phone to a known state. Make sure that you unplug the usb cable before booting the first time.

If you get into a bootloop or go straight to recovery, do the format internal sd card and then flash the EE4 odin only. Make sure that the repartition box is unchecked and no pit file is in the pit section.

Hopefully, you will then be able to boot to setup.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
No, I haven't heard the robot since this started. I only heard it the first time I installed PBJT.

I went straight to recovery from flashing PIT and EE4. I tried to format internal sd-card and I get an error saying:

E:Can't mount /devbock/mmcblk0p1

(Invalid argument)

E:copy_dbdata_media:Can't mount SDCARD:

your storage not prepared yet, please use UI menu for format and reboot actions.

The problem with going back to EE4 is that I get a bootloop there. I can only access setup from gummy and then the sdcard is unreadable and I don't have the sdcard fix on there anymore.
[Verizon Droid Charge] zagoric:
I took my girlfriend's phone and loaded the necessary files to her sd card and then put that in my phone and followed the above procedure. I heard the robot voice, but I'm in a bootloop. Should I just flash PIT and EE4 (where i get a bootloop) and try to get Verizon to replace?
[Verizon Droid Charge] rj57:
The pit definitely is not doing it's job for some reason.

What version of odin are you using?

I have been using Odin3 v1. 3 and it hasn't failed to get me out of trouble yet.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
I'm using Odin3 v1.82

I'll try to redownload the PIT file and find Odin 1.3, but I'm starting to lose hope.
[Verizon Droid Charge] rj57:
The PIT in the OP is good.

Here's a link for Odin3 v1. 3

http://www.multiupload.com/O6JOYLCPQ7

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
Tried again with odin 1.3 and got the same result.

The PIT file must be working, because I'm flashing voodoo after and I get the voice.
[Verizon Droid Charge] zagoric:
If I send it back to Verizon and the below msg shows in recovery are they going to know I messed with it and void my warranty?

bootmode=7 from cmd line

E:Can't mount /dev/block/mmcblk0p1

(Invalid argument)

--Movi_check Start..!!

checksum configuration need_checksum [0]

Not need checksum confirmation

-- Movi_check already executed!!...

-- movi_checking done!...

E:Can't mount /dev/block/mmcblk0p3

(Invalid argument)

E:Can't mount CACHE:recovery/command

#MANUAL MODE#

E:Can't mount /dev/block/mmcblk0p3

(Invalid argument)

E:Can't mount CACHE:log/recovery.log

E:Can't open CACHE:log/recovery.log

E:Can't mount /dev/block/mmcblk0p3

(Invalid argument)
[Verizon Droid Charge] anoninja118:
yes because to me it looks like you tried to push a rom to the phone which failed... have you tried odin just CWM, booting into it and wiping data/cache/dalvik? I can't think of why its not letting anything flash right

blazing through on my 4G Droid Charge
[Verizon Droid Charge] anoninja118:
^^^^^^ this seens to be your problem right here, when you odin with EE4 and PIT (with repartition box checked of course) you need to let the phone boot once and format itself don't go into recovery and wipe anything especially not in stock recovery

blazing through on my 4G Droid Charge
[Verizon Droid Charge] anoninja118:
imnuts also says to make sure 'Re-Partition' is checked in odin because it sounds like the phones not getting properly repartitioned

blazing through on my 4G Droid Charge
[Verizon Droid Charge] zagoric:
Yes, I've done this before flashing any roms.

When I say I go into recovery, I meant the phone goes there on its own in the initial boot after flashing EE4 and PIT. I'm sure I've let it reboot from there without wiping anything, but I'll redo it now to make sure. And I've always had re-partition checked when using the PIT file.
[Verizon Droid Charge] zagoric:
I did it again and got another bootloop when I rebooted from stock recovery without wiping anything.
[Verizon Droid Charge] anoninja118:
well according to imnuts something is wrong with the partitions, they're not being done right in odin... sorry if its repetetive but could you list all the details of what you're doing as well as all the files you're using? it could be maybe your PIT file is bad and isn't working right
[Verizon Droid Charge] rj57:
Did it only take 12 minutes to odin the PIT and EE4 package?? The times that I have done it, it took a good 15 - 20 minutes to flash and then @10 minutes to get past the Samsung on the first boot. Which EE4 Package are you flashing? I have used the one from this thread without problems http://xdaforums.com/showthread.php?t=1172182
[Verizon Droid Charge] zagoric:
No worries. Thanks for the help. I've been flashing the PIT from the OP along with the CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5 and even CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.md5 for stock. I also tried an ED2 but I got an error msg with that one. I get bootloops with either of the stock files.

From stock, I've flashed a few versions of CWM, mostly 4.0.0.8 and also the one from 8/7 (can't recall the version but it is mentioned within the last few pages).

I can get to setup most of the time when I flash gummy FE 1.9 or 1.9.1 are the one's I've used for the most part, but I've also tried GRE. I have tried to flash via CWM, but have even tried the ODIN versions of Gummy EE4 (Rooted) and GummyCharged_FE_1.9.1_FullOdin.tar.md5. Although I can reach setup the phone is not functional. It will access google and pull my contacts (or at least some of them) and I can make calls, but I get force closes for programs that I am not trying to access (it seemed like they were google based apps mostly).

Let me know if this helps or if you need more info.

EDIT: I've also tried both ODIN3v1.82 and Odin3_v1.3
[Verizon Droid Charge] zagoric:
Correct. I think it even took less time than that. The files I've been using are in the above post. I've been using that file, but I'm not sure if I got it from the same post. Looks familiar though.
[Verizon Droid Charge] anoninja118:
here's the PIT http://dl.dropbox.com/u/34782489/charge.pit

and have you tried flashing an odin of anything else to see if it works? like Gummy or one of the GB leaks or something?
[Verizon Droid Charge] zagoric:
Yes, see the post before the one you quoted. It's on the previous page.
[Verizon Droid Charge] anoninja118:
oh ok my bad lol I switch from pc to phone a lot so it looks different and I may miss stuff... anyway this is a very interesting situation here, I pm'd imnuts and he said your specific error message (/dev/block/mmcblk0p3) is most likely related to the /cache partition however a proper flash with stock rom and PIT should fix it fine
[Verizon Droid Charge] zagoric:
Are there any other known fixes?
[Verizon Droid Charge] anoninja118:
I poked around and I couldn't find anything else that'll help, seems the EE4/PIT odin method is the 100% surefire way to fix it but you're the first I've heard of that it doesn't work... you may need to get a replacement but idk what to do about that recovery screen it boots into, it looks pretty obvious that you did something 'questionable'

edit: maybe you could pm one of the devs like imnuts or kejar and they could troubleshoot

blazing through on my 4G Droid Charge
[Verizon Droid Charge] zagoric:
I'll reach out to one of them. Thanks for the help.
[Verizon Droid Charge] dantomacedo:
I had the same issue (phone stuck in the samsung logo) after flash the smaller file ED1, then I flashed the stock "EP1F rooted droid charge gingerbread..." file and It is back, I have a working phone again...
[Verizon Droid Charge] da2zoe:
I've been doing a lot of reading on this topic and can't seem to find the answer(s) I'm looking for. There are threads for return to stock and fix your phone in many places but I cannot seem to find how or why you would choose ED1, ED2 or EE4. I know these have to be flashed with Odin or the PST to work and ED1 and ED2 would be followed by an OTA to get to EE4.

So this is my question: Do they all work the same when you need to fix your phone if it's started having problems? This thread only references ED1 and ED2. P3droid has a thread for returning to stock but is just EE4. Also, I've read that the PIT file isn't really necessary if you go back to ED1 - seems odd - but if that's true then I'd like to know why because it's on every thread I've ever found for returning to stock. It was the same when I had my Fascinate.

I don't have any issues with my phone and don't need this process for now (knock on wood) but I get a little flash happy at times and would like some input should I ever need it. Thanks in advance for any input. :)

(I'm a new enough poster on this particular site so I can't put a link in my post yet, but this is the thread by P3 I'm talking about: ...mydroidworld.com/forums/droid-charge-discussions/8448-droid-charge-ee4-full-factory-odin-return-stock.html#post93408)