yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] juttschallenger:
Ok so now I'm able to get the phone to boot all the way up to the setup screen but when I click next, I get the sim card error message. Went to vzw and got a new sim but still have the same problem.

I flashed AbeastA4 and I seen the wallpaper changed and the menu but stuck with the sim card issue.
[Verizon Droid Charge] juttschallenger:
Trebores1

I am now at the same place you were. Getting the simcard error. Went to vzw and got a new one and it still didn't work. So now I am running Abeast4 and I can see that its on the phone but I can't get past the setup screen with the SIM error. What did you do after you got the error?
[Verizon Droid Charge] hamlet2424:
Mine was giving the same error. I tried using Odin to put stock rom to go back and now the phone is just dead. The phone won't turn on and not able to get into download mode. I tried a jig wire to force to download mode and that didn't work (tried the wire on a galaxy to make sure its working which it is). Any advice on what i can do?
[Verizon Droid Charge] binglejellsx2:
So now a noob question. will these steps get me out of a frozen Samsung logo? Last thing I did before it stopped working was in terminal emulator: su then reboot recovery. Here's my story.

I used imnuts odin file to root / flash the cwm / voodoo lagfix on ED2. I wanted to see if I could boot into recovery manually by holding vol up+home+pwr, but the Samsung logo was stuck. So then I held power until the logo disappeared. It quickly reappeared and booted fine. I had a OTA update prompt, and to get ready for it I added a "disable-lagfix" folder in sdcard/Voodoo to get back to RFS. I went into terminal emulator and typed "reboot recovery" since the hardware button combo didn't work. Been stuck there since.

Any help (I can't believe I'm actually making one of these posts)? What I really want to know is if I can Odin or Heimdall over my system, or if I have to find a way to get it back to RFS first.

Edit: I can get into download mode. I just want to confirm whether or not it is ok to proceed with the first steps in the OP.

Edit 2: Got my phone working again! Besides the wrong button combo to try to get into CWM (I found out it's supposed to be vol down+vol up+pwr), I don't know what caused it to freeze at the Samsung logo. Short fix story: I found a PC and installed the AB Rom through Odin.

Long fix story: I'm using a Mac only, so I tried, unsuccessfully, all kinds of things with Heimdall (command-line only since I couldn't figure out how to get the front-end). Because of this I was unpacking all the Odin files and peeping inside. I noticed the AB Rom had factoryfs.rfs, zImage, and recovery.bin versus the VoodooChargeKernel.tar.md5's zImage only (it's what I used to root). I figured it wouldn't hurt to use the AB Rom to install CWM, but it failed with Heimdall. I borrowed someone's Mac that ran Windows and used Odin. I've since disabled the Voodoo lagfix and once it booted everything else seemed to be working fine.
[Verizon Droid Charge] Mikey450GT:
Which package did you flash?
[Verizon Droid Charge] trebores1:
I can't find a fix.. I know this is unpopular here - since this is all "at your own risk" but I exchanged the phone.
[Verizon Droid Charge] trebores1:
I flashed the second file in the first post - almost-everything. I couldn't get the first file to flash.
[Verizon Droid Charge] Mikey450GT:
I couldn't either. Now I can't even get my phone to load up or show a charging symbol when its plugged into my computer or the wall....I don't think that's a good sign LOL :confused:

EDIT: It kept failing on me, so I tried it out not selecting the re-partition in Odin and it passed somehow! I got stuck at the bootload screen, attempting to load stock ed1 rooted from odin to see. Hopefully from here I can set the system to disable the lagfix and get back to having a phone! I will keep everyone posted to see what I find out. I knew I shouldn't have done recovery but I wanted to change roms and I'm so used to doing it on my old Evo....
[Verizon Droid Charge] Ronbo85:
Yes I know the 2 numbers are same except for 1 digit. No this phone is clean I already check with verizon, as a matter of fact when I log into my verizon account it shows that the charge is activated. When I went to activate the charge I submitted my IMEI but I could not get a network connection on the charge so I just threw my sim card back in my thunderbolt and when I log into my vzw account it shows I am still using the charge. Thanks for the reply anyway

_____________________________

sent via VZW T-Bolt/Bamf ROM
[Verizon Droid Charge] juanito157:
"md5 hash value is invalid" is the error message I receive when trying to follow your instructions.. please help

Thank you

PS. currently my phone only shows a picture of a phone a hazard sign in the middle and a pic of a pc on the right
[Verizon Droid Charge] Ronbo85:
yes you are in download mode and it sounds like your using odin, the file your trying to use is corrupt try redownloading it

sent via VZW T-Bolt/Bamf ROM
[Verizon Droid Charge] kj1060:
I am coming from the Infinity Rom and I was getting a "unable to mount sd card". I have downloaded the ED2 files multiple times and every time I have received "Samsung_Charge_ED2_Full.tar.md5 is invalid." I don't know what to do now. Any help would be greatly appreciated.
[Verizon Droid Charge] rj57:
Use the ED1 file or the EE4 file that pentafive posted.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] kj1060:
I'll try the EE4, but I get a bad link with the ED1 file every time I attempt to use it. Any possibilities of someone providing a direct download vs. file sharing website? Thanks for the help.
[Verizon Droid Charge] trparky:
CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5.7z | FTP Download (Faster Speeds)

MD5: B1FF17D01A9EAF2A85E928B7B340804F

Extracted File MD5: 7ECF9ED3FD74461C8895D0D30BCF6C41

You will need a decompression tool that supports 7zip compression. PowerArchiver 2011 is one such program.
[Verizon Droid Charge] kj1060:
Thank you I will attempt this later. Just one last question, can't I just use 7zip to decompress or extract it?
[Verizon Droid Charge] trparky:
Yes, you can. I just gave an example of a program that can extract it if you don't already have one.
[Verizon Droid Charge] kj1060:
Thank you all for the help. I have successfully gotten back to stock and everything seems to be running fine.
[Verizon Droid Charge] blueis300:
Thanks for this great thread. I wanted to see if I could root. I did and need to go back to stock. I loaded , it asked to update and appears good so far.
[Verizon Droid Charge] Andrwmorph:
I had the same problem and I ended up calling for a replacement as well. I couldn't find any method to fix the partitions. Just wanted to say thanks to everybody in the thread for trying to fix the issue.

FYI:

I was running http://rootzwiki.com/showthread.php?6656-9-29-11-ROM-KERNEL-Infinity-Rom-RAW-BETA with imoseyon's 2.5.0 voodoo kernel. I flashed the version of Infinity Rom that automatically did the ext4 conversion. It was very stable for 1-2 weeks then I started getting weird FCs and the phone would forget accounts, etc.
[Verizon Droid Charge] gmarsz:
Has ANYONE ever recovered from this?

Ok, spent the last week or so going through this thread and others... even went through all the same steps with the adb to no avail. Sure learned a ton of what can be done and would think with that sort of power we could recover from this... yet I'm stuck with FC's no matter what ROM, and can't disable vodooo/switch back from EXT4/or delete anything for that matter from /data. (identical situation to OP)

I've had the phone for 2.5 months so I'd have to send it back to samsung (again, first time was a mysterious internal camera lens fracture that I still had to pay for).

Needless to say, if anyone comes up with another option, even if it requires physically cracking this thing open, I'm game. Otherwise I have a shiny boot looping paper weight.

THANKS for the comp sci lesson though
[Verizon Droid Charge] hindustani8:
Samsung Fascinate

I am getting e:can't mount /cache error on my Fascinate. I was running CM7.1 and it was working fine. I did a battery pull and it went in reboot cycles. I am able to get into cwm recovery mode. Would this instruction work for Fascinate? Is there a better way to fix the problem?

EDIT: I charge my battery to 100% and tried restarting the phone...that fixed the problem.
[Verizon Droid Charge] gmarsz:
MBR anyone?
[Verizon Droid Charge] laidback1987:
Recovery

Im on gummy charged gbe is there anyway for me to go back to stock phone software thought cwm sorry if this has beeln answered already the inky reason I want to go back to stocm is because I get horrible battery life with gummy charged
[Verizon Droid Charge] jkbucksot:
Thanks imnuts,

had to use this to get back after breaking some things due to flashing errors. worked like a charm
[Verizon Droid Charge] itkujo:
Hey guys so I was trying to use the PIT file did what the instructions said then once it was done I pulled the battery out then unplugged then I tried to turn back on and nothing not sure if the battery is dead but the phone wont even show the charging screen......
[Verizon Droid Charge] anoninja118:
I'm pretty sure you're supposed to unplug it from the pc before pulling and reinserting the battery but I doubt it would cause issues if not done exactly in that order, will it power on?

blazing through on my 4G Droid Charge
[Verizon Droid Charge] rj57:
Which PDA package (ED1, ED2, or EE4) did you use? Or did you flash the PIT by itself?

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] JihadSquad:
Which Odin do I use? 1.3 or 1.82?
[Verizon Droid Charge] blueis300:
Ive been 1.82 for everything.
[Verizon Droid Charge] shrike1978:
Either should work, but I use 1.82.
[Verizon Droid Charge] JihadSquad:
<OSM> MD5 hash value is invalid

<OSM> Samsung_Charge_ED2_Full.tar.md5 is invalid.

<OSM> End...

What do?
[Verizon Droid Charge] dwitherell:
Usually that means the download was corrupted in some way - I would try to download the file again and see if that resolves the issue.
[Verizon Droid Charge] JihadSquad:
Downloaded the ED2 MD5 from android central and it worked fine.
[Verizon Droid Charge] Roninrc51:
Bricked my phone :(

Any ideas .. Teaching my son about using odin and cwm, he formatted my phone in cwm and now it gets stuck at initializing in odin. Have tried numerous attempts with pit file and using PST nothing works. Both programs see my phone on com14 but neither seem to be able to flash to it.
[Verizon Droid Charge] anoninja118:
when you say formatted in CWM what exactly does that mean or what did he do? and it was CWM right and not the stock samsung recovery (which look similar and have similar options)? also seeing as you got CWM on the phone that means Odin was working fine before... if it connects fine and Odin recognizes it but stalls on the flash I'm inclined to say its what you're flashing, on that note what are you trying flash? sorry for the questions but I'm trying to troubleshoot before calling it a brick :)

edit: oh I forgot to ask also are you flashing with the battery in? leaving the battery out is the culprit in most of these cases (and remember to uncheck the auto reboot box when flashing with the battery in)
[Verizon Droid Charge] Bfitz26:
please help no one is responding to my thread it q and a so i figured id throw a link up and hopefully some one can give me a light in the right direction also will verizon swap my phone out if i have the error code on it??

here is the link: http://xdaforums.com/showthread.php?t=1339283

thanks in advance...
[Verizon Droid Charge] duuurp:
So my phone was giving me trouble and I decided to go to the new gb leak, boot looped.

I come here grab the pit and ED1 .tar, odin them and now I'm still stuck in a boot loop. Anyone got any advice?

EDIT: After reading this entire thread, it looks like I"m having the same issue with the partitioning as everyone else. Oh well I guess I'm bricked. If there is a fix and I just missed it please let me know. Otherwise I guess I'm going back to my ****ty flip phone

Just to be clear. I was on EP3h with a voodoo kernel, but I can't remember which. Phone was fine for a few weeks, then bam constant reboots and force closes.
[Verizon Droid Charge] anoninja118:
EE4 and PIT? with repartition checked too

blazing through on my 4G Droid Charge
[Verizon Droid Charge] duuurp:
Yeah tried EE4 as well, re-ran both a few times just to make sure. Nothing...
[Verizon Droid Charge] anoninja118:
have you tried Odining CWM and booting into it then trying to flash a rom from there? I think I have a .zip of stock EE4 I can link to when I get home

blazing through on my 4G Droid Charge
[Verizon Droid Charge] blueis300:
Is this what you need?

http://www.filesonic.com/file/3519795694/ee4.zip
[Verizon Droid Charge] duuurp:
yeah I tried installing eclipse through CWM. I'll try EE4 tomorrow.
[Verizon Droid Charge] syntrix:
Nothing in the first post worked for me today.

A few pages in, there's a link to another forum with a stock rom and the samsung utility. It wouldn't flash at first, but second try it worked, yay!!!!

I forgot to unvoodoo going back to stock :D
[Verizon Droid Charge] droidiam:
Thanks so much, you saved my charge from having to be shipped back to mobiletechvideos for $40 again! lol
[Verizon Droid Charge] Kryptonian_Knight:
for me on odin it just stops at "factoryfs" or "movinand" and iv tried with and with out the battery and diff usb port, im trying to flash EP4 deodexed rooted gb.

on reboot it goes to the samsung and then to recovery and repeats every time i try to reboot
[Verizon Droid Charge] trparky:
Did you remember to convert back to RFS by disabling Voodoo Lag Fix first?
[Verizon Droid Charge] kennethlongshaw:
you guys are life savers
[Verizon Droid Charge] boricuastock:
No luck

I have tried everything on here. I was running BlackHat deox-debloat 2.3.5 and was upgrading to 2.3.6 and on reboot I got a ton of Force Closes and could not use the phone. I have tried the Pit with EE4 and ED1 with not luck. I tried the samsung flash utility as well. Everything ends up the same.

--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 will always boot. But I get a mass of force closes and my data is still there. So for some reason it is not working. It will force close all my old apps and then the system hangs. I tried to do ADB and wipe system and data and nothing seems to work.

Any suggestions. I have tried on win7 32 and 64 bit. I am out of ideas... Please help anyone.
[Verizon Droid Charge] syntrix:
Follow the samsung util and file on the other site to the letter.

It's the only thing that worked for me and others here.

Otherwise something is bad in hardware, and might need a warranty swap.
[Verizon Droid Charge] thelandon:
Not good... I used the PIT file from the OP and flashed in Odin (using PDA) the stock EE4 tar. Now, my phone is hard-bricked. It won't go into download-mode. It won't power-on either. The weird thing is, Odin said: 1 passed/0 failed.

I've flashed 50 ROMs easily between the Charge, Incredible, and Revolution. I'd like to think that I know what I'm doing. However, that certainly isn't the case today. :/

I know this is poor form, but unless someone can help out, the only thing I can think to do is to take it back to Verizon and say that it failed during the OTA to 2.3.6.
[Verizon Droid Charge] beatingU:
Pure Awesome

I thought my phone was done... wouldnt even turn on and imnuts is the bomb! it worked and i got my phone back. Those of you who download the first EE1 make sure you extract it somewhere you can go back and put it in Odin. thats where i messed up. Odin took about 5 minutes to completely download to the phone but its working just like when i bought it.

I cant thank you enough, this site is great, THANKS
[Verizon Droid Charge] SFniner415:
was on gummy gbe 1.8.5. last night everything kept force closing and i couldnt use my phone at all. flashed ed1 with pit and finally got back into the phone but everything keeps force closing still. even the setup wizard. is my phones internal memory seriously injured? i did nothing out of the ordinary. the phone just started flippn out last night.

Edit: Phone restarted itself after all the force closing. phone is up and running now.

Edit 2: restarted phone. once it starts up i get a ton of pop ups with unexpected errors on a million things. then it goes back to the droid eye and now its been on the eye for 10+ minutes. wtf is wrong with my phone. i didnt get the OTA either when it did load up the first time.
[Verizon Droid Charge] syntrix:
I'm seeing that you missed a lot of steps, as described.
[Verizon Droid Charge] SFniner415:
like.....?

So this is what i get. when i flash ed1 & pit it gets passed the droid eye and i get about 20 unsespected error things like "setup wizard crash" and a bunch of other stuff. then it goes back to the droid eye and i had it sit 30+ minutes hoping it would load up.

when i flash ee4 it just gets stuck at the eye. i had it sit 20+ minutes and nothing. any help would be great. i have 3 hours before i leave the country.
[Verizon Droid Charge] papa54:
dont et the ed2 o straiht to the EE4 Odin file it will place yer phone riht where it should be.. look over my typos seems the letter after <F> before the <H> has opne bye bye .. chane boards tomorrow ..

think about that EE4 Odin update its quicker, has all necessary files just as if you had updated from the ED2..
[Verizon Droid Charge] boricuastock:
This is exactly what is happening to mine. I tried an upgrade to 2.3.6 as well from 2.3.5 and I got all the messages. Having done this a hundred times I just tried taking it back to ED1, etc. and they all failed. I followed all the steps posted here. I could not get it fixed. I am having to send it in to Samsung for them to fix. Verizon wouldn't do it because I didn't originally buy it from them otherwise they would have changed it out.
[Verizon Droid Charge] rudolphe:
This just totally saved me from a disaster... I spent two hours trying to fix it prior to finding the damn pit file.

Big thumbs up....

Now I have to tell Verizon not to send me out a new phone.
[Verizon Droid Charge] pizzle11:
brick fixed

i had to plug into back usb plugs also, but i used the .pit and ed1 and it worked great, thanks. trying the deodex/debloat all in one again, it seems to be working this time since i restored the phone back to ed1. i first tried flashing the deodex/debloat all in one 2.3.6 right over the top of the bloated version and i guess you can't do that? it got stuck at the cp_modem.

To some this may be rambling but if i found a thread (i'm sure ones out there) that told me to flash the old rom before the new on top of new, it would have saved me a few hours.

Hopefully this helps someone.
[Verizon Droid Charge] junksecret:
Just a quick note, I was running the leaked EP4D with CWR & Voodoo and wanted to return to stock to accept the OTA update to EP4. After the last few posts of problems I was a bit worried but I got the stock EE4 HERE & used the PIT file and instructions from this thread.

I disabled Voodoo Lagfix first using Voodoo control from the market and the downgrade to EE4 went flawlessly.

I'm going to try and get the OTA now.

Thanks to the OP and all the rest for the help!
[Verizon Droid Charge] diablospeed:
i have tried everything here and read through all 44 pages... i am still not able to get any mobile data. at least the good thing is I can go back to VZ and get a replacement. i'm sure I effed up something when i flashed this thing like 500 times in the past 4 months.
[Verizon Droid Charge] diablospeed:
maybe imnuts can help here... i went to verizon today because it doesn't matter what ROM i put on the phone ( i even went to ed1, which upgraded to ee4, then ep4 via OTA), I cannot receive 3g data on those radios. i have no issues with the lte radio finding the /data directory. i re-partitioned and added the PIT file when I went to ed1 and flashed the stock image, but I was never able to obtain mobile data. i am getting a replacement from verizon, but I want to understand what happened. Here are the steps i followed:

i was running humble 5 rc2 with the 4.0 kernal for the last 3 weeks. i wanted to play around and let the OTA happen, so I flashed the stock ee4 back to the phone only after i disabled lagfix and allowed the phone to be factory reset. all cache's were cleared before I flashed in ODIN. once i was done, the data issue surfaced, so i attempted to go back to ed1. I flashed that ROM and included the PIT file. still nothing.

question: is there a PIT file available for the GB stock roms that will fix the issue with the phone not seeing the /data directory?
[Verizon Droid Charge] sf_love:
semi-bricked

After getting my system update I decided to try to get root access to my phone but I don't think the voodoo thing I was using was compatible with the gingerbread update so now my phone is in a phone coma, stuck in a loop with the samsung logo turning on and off.

And, judge away, I know this is a dumb question- I'm not sure if I'm 'flashing' it properly because I'm not sure what that means in the context of my phone. So here's what I did, can anyone tell me where I've messed up and/or how to fix it? I'd like to not have to factory reset it because I'm not sure where my pictures are saved- I think my SD card filled up and they're stored on my phone (yes, that is my biggest/only concern for resetting my phone and one that could have been avoided, I know. )

1. I downloaded Odin and VoodooChargeKernel4.tar.md5. I loaded the md5 into the PDA field of the odin utility and hit start. It seemed to install without issue, but when it restarted I got stuck in the samsung logo loop

So I poked around my phone a bit, got to the recovery mode or whatever but none of the options there said flash anything, just like upload from SD card, but there were no files to be loaded from so that was useless.

2. I downloaded a clockwork mod thing- 0817_charge_recovery.tar.md5 and installed that the same way and it seemed to work too- when I rebooted in recovery mode the background changed to the banana guy instead of the droid thing and had a lot more options, and it said CWM-based recovery. So I tried to apply update from sdcard, hoping that there was some magic module that would get my phone going properly again, but it just said there were no files so installation was aborted. I proceeded to do a backup, just for funnsies. That worked, but I don't know what that's good for. Rebooting my phone still leaves me in the samsung logo loop of despair :eek: !

Oh and it has also decided that it won't charge because the temperature is either too high or too low. Seriously, that's what the error says. Doesn't say which, just that it is apparently uncomfortable and cannot be expected to charge in such horrible conditions. whatever.

I'm really about to lose it-hysterical crying and/or a very unladylike string of cusswords is imminent if my phone continues this nonsense. if anyone can help me get my phone back in working order I would really appreciate it. If you can do it without clearing my phone's data you'll be my hero and have my undying gratitude and affection, but first priority is definitely getting my phone functional! (and if you could tell me what exactly I'm supposed to do to 'flash' my phone in the instructions that would be great).
[Verizon Droid Charge] justin251:
I can't get any of this to work on my charge.

The ED1 and ED2 go all the way to 99% and then FAIL pops up.

I'm trying to fix my phone with an MEID problem. The MEID is unknown.
[Verizon Droid Charge] diablospeed:
this does not sound good. MEID errors could mean the phone is reported as lost/stolen.

---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------

if you are just trying to get it back to stock then ODIN the ed4 files on the device first.. once it is up and running you should try to root again.
[Verizon Droid Charge] justin251:
Deleted post