yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] Gnomepatrol:
Long Post

Started out with gummy 1.9.1 have been using gummy since 1.5 without any issues. Thursday of last week my phone started to lock up randomly. First thing i did was restart the phone after the lockups stopped. Was fine for a few hours then began to lock up again. Decided to reflash 1.9.1 via cwm then rebooted back in. Same lockup issues, but this time it was throwing force close errors. Tried another flash with a wipe data/cache same issue.

Frustrated at this point, headed to xda re-downloaded gummy and via odin reflashed the phone. Still no good, same errors. Decided to try a gb rom at that point, since nothing seemed to be working. Picked up humble, and proceeded to flash, noticed after that i needed to disable voodoo. Went back into cmw after flash disabled voodoo, then wiped cache/data and reflashed humble. Still received the same errors that i was getting with gummy.

Now after all that i decided to use the recovery threads that i had bookmarked in order to get a fresh start. Using the provided pit file i followed the directions and flashed pit and ed1/ed2/ee4 all three sent me to the recovery screen that you see in the pictures that i uploaded. I then went over to rootzwiki i think it was and followed the instructions for using samsungpst to no avail. I then tried out flashing ep1h to see if the gingerbread leak would work. Still no luck.

Which brings me to where i am now. I have just reflashed gummy 1.9.1 and am back to being able to get into the os, but it is completely unusable as it throws so many errors. I did notice it seems that it is trying to load apps that i had installed when my phone was working. Which seems odd since the data has been wiped and rewiped multiple times.

I feel a bit in over my head at this point, but don't want to give up just yet.

If i need to be clearer on anything let me know.

Thanks in advance for any help
[Verizon Droid Charge] anoninja118:
well it looks like you did everything right.. also can you tell what's force closing when it starts? is it apps, google programs, system programs? the only thing I see that might be causing the issue is the fact that you disabled voodoo in CWM... I only say this because it is a known issue that it does not work in CWM (at least not all the time), or at least falsely reports it being enabled/disabled so you may have flashed a nonvoodoo rom with lagfix enabled which leads to the semi-soft bricked phone you have here. I would only use the voodoo control app to check if you have voodoo lagfix enabled and to disable it
[Verizon Droid Charge] Gnomepatrol:
Everything force closes: keyboard to system to launcher. What is weird is i have seen tapatalk which doesn't make sense to me since i have done so many wipes and flashes.

Another note i have noticed that my phone seems to be double booting. It seems to be loading twice at the same time one slightly ahead of the other in both audio and boot animation. Is it possible that my phone is attempting to load 2 roms, just speculation on my behalf.

EDIT: Just threw a Process system is not responding at me. No clue what that means as far as an issue.

EDIT2: I think i was just able to send a text, but it is telling me i have no service yet it told me the text had been sent. I also had to receive it as well. This is just strange. :P

Edit3: As i got further in i keep seeing it change from the wallpaper i last had to the stock 1.9.1 wallpaper. Which further leads me to believe it is somehow loading the old flash and the newer ones. What is going on?
[Verizon Droid Charge] anoninja118:
sounds like a corrupt file you're flashing or its not flashing properly.. I think the main thing at this point would be to get you to stock, if you can make any backups and boot into CWM then wipe EVERYTHING data/cache/dalvik and proceed to try and odin a stock rom with PIT and repartition checked.. could also be an sd card problem that i've never heard of before, if you were desperate you could format/wipe your sd card and see if that changes anything (after backups of course)

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] Gnomepatrol:
Just reformatted the sd card and tried again still no good. I don't know much about how the android os works, so just purely speculating. Is it possible that somehow i have 2 roms flashed and they are both booting up with the phone? Not that it is going to help my issue just curious at this point.
[Verizon Droid Charge] anoninja118:
sounds like something weird like that is going on if 'downloaded' apps are force closing on a first boot after a wipe/flash... I have a little experience with linux (what android is built/based on) but this is beyond my skills to diagnose lol. If you knew ADB or could access a terminal emulator i would say to grab some logcats so someone could take a look at whats going
[Verizon Droid Charge] Gnomepatrol:
I'm at a loss. I wish i knew ADB or anything that could hep at this point. Onto day four of trying i guess.
[Verizon Droid Charge] anoninja118:
well if all else fails try and odin the stock EE4 for whatever good it'll do and take it in and try and get a new one lol

blazing through on my VZ Droid Charge 4G
[Verizon Droid Charge] HemiDroid03:
Ok so I'm getting the message from the OP right, NOW I downloaded ED2 and the PIT file BUT when I go to flash I get a FAILED message with something about the MD5 HASH not matching or whatnot... DRIVING ME NUTS!! HELP!?
[Verizon Droid Charge] vegasjones:
Just worked like a charm for me. I had a random boot loop after using Humble 1.5 for the past week. Got back to ED1 with this. Weird thing is that I went to do a system update, and it said my phone is up to date. Anyone know if I have to wait for this after restoring or if I can do in manually?
[Verizon Droid Charge] hazard209:
Go into settings > about phone. Scroll to the bottom. If you see EE4 under the baseband version and the build number then your set.

Just a bad download man. They happen. Redownload and try again.
[Verizon Droid Charge] muzhik:
used ed1 file, worked 100%

ed2 fails at check sum in odin 1.3v
[Verizon Droid Charge] Syn Ack:
Worked perfect if you do step by step and use ED1 and the PIT file.
[Verizon Droid Charge] diverbelow:
How do you fix a bricked Droid Charge?

I flashed the EP1Q and boot looping so flashed back to EE4 and now my phone will not turn on or go in to Download mode. I did notice that while trying to get in to the Download mode, the lights on the physical buttons are VERY dim.
[Verizon Droid Charge] rubadub234:
we're in the same boat. I did the same thing. You posted in My Droid World right? Waiting for your replacement? I'm nervous about returning it because with my luck, id get billed the full retail price.

i found some stuff about using a jig? to force the dl mode. think they sell them on ebay, but not sure if it will work on a Charge

http://droidangel.blogspot.com/2011/05/how-to-make-samsung-galaxy-s-download.html
[Verizon Droid Charge] diverbelow:
I saw that too, and there is a posting on XDA that talks about using a jig but it says, "If your phone screen is always black, that is it does not display the white Galaxy S/Samsung/AT&T logo when you switch it on, then sorry, this jig will not help you. " and I think the phone is SOL.
[Verizon Droid Charge] rubadub234:
of course lol

i contacted mobiletech world to see if they can unbrick it. They had a couple videos with them unbricking a galaxy II, so im hoping they can come through
[Verizon Droid Charge] diverbelow:
I saw those videos too. I also sent a tweet to @Samsungsupport and asking them but have not heard back. If mobiletech can unbrick it, please let me know.
[Verizon Droid Charge] rubadub234:
you got it, fingers crossed
[Verizon Droid Charge] rubadub234:
sent you a pm
[Verizon Droid Charge] kvswim:
Redownload the file. Also, I would reccomend using the stock EE4 odin so you don't have to upgrade back to EE4 OTA.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] kvswim:
Use the EXT4 formatter (mount everything in cwm first). Then restock using the EE4 Odin+the PIT file. Then flash your rom of choice (in odin). I had the same problem you did. This worked for me.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] bobthesalesclerk:
Link to the .pit file is down. If anyone can put it back up asap please do. My phone is kinda broke right now and I need it for work :)

Will make multiple accounts and hit thanks with all of them :)
[Verizon Droid Charge] landshark68:
Mediafire was down so I had to upload it to multiupload:

http://www.multiupload.com/1DQXFE41QF
[Verizon Droid Charge] bkott425:
I think I bricked my phone but not sure. It won't turn on, the only thing it will do is go in to download mode. I've tried flashing with the samsung PST and it always fails and I've tried odin and always fails. It also stopped showing up as a adb device. Any ideas?
[Verizon Droid Charge] imnuts:
If it goes into download mode, it is not bricked. However, to fix it, you need to give more info than what you provided. Where does it fail? Have you tried different cables/USB ports? Flashing with the battery in or out? What are you flashing? What does your phone show when you try to boot it up normally?
[Verizon Droid Charge] diverbelow:
It is not bricked since you can get in to Download mode. In my case, the screen would not turn on or get in to Download mode.
[Verizon Droid Charge] bkott425:
ok It finally flashed in Odin with alteredbeast but now it's stuck in Manual mode. It won't let me Flash and repartition with the stock in odin or samsung pst. any ideas?
[Verizon Droid Charge] bkott425:
it's fails when setting the pit file when following the steps at the begining of this thread. When I tried to flash the rom without the pit it fails at param.lfs.
[Verizon Droid Charge] imnuts:
If it is pausing when attempting to set partitions, it is a drop in communication. Have you read my previous post? Are you flashing with the battery in or out? Have you tried different cables? Different USB ports? Different computer?
[Verizon Droid Charge] bkott425:
battery and sim is out. Used different cable, computer and different usb ports, same reaction. It will only let me flash rooted gb2.4.3 and altered beast but both just boot to manual mode.
[Verizon Droid Charge] sl1ckmcg33:
I had to use p3droid post. Odin seemed to not work. Got the Samsung PST and flashed back to stock. One hangup was the whole battery thing when trying to connect to PST. I'll find the link in a sec.

http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
[Verizon Droid Charge] Seppe1976:
Battery needs to be put back in

read over the instruction and see that the battery needs to be back in the phone
[Verizon Droid Charge] imnuts:
Flash with the battery in, it could very well solve your problems.
[Verizon Droid Charge] bkott425:
ok it decided to flash alteredbeast and finally get past the manual. I guess my droid was done being mad at me. Back in business :D
[Verizon Droid Charge] jdougal11:
I didn't want to start a new thread so I'll post in here. I'm having issues flashing any sort of ODIN Rom. Any advice on fixing this situation would be greatly appreciated.

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> humble151.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> param.lfs

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<ID:0/003> Removed!!

<OSM> All threads completed. (succeed 0 / failed 1)

This has occurred with GummCharged, Humble, and AC's Beats and usually disables the phone from rebooting. So far I have been successful in reflashing the debloated ROM from ODIN.
[Verizon Droid Charge] imnuts:
Flashing with battery in or out?
[Verizon Droid Charge] rubadub234:
For those of you sitting on a hard brick,(no bootloader, no nothing) I just heard from MobileTechVideos. They are making some progress...fingers crossed he can fix it

Yes I have spent hours trying to map points. It will be a challenge if at all possible. I found an island of 10 pads that are what I believe to be the JTAG points but I’m not totally sure either. Mapping the points is always an absolute challenge. I will be talking with the RIFF JTAG team tomorrow to see if they have any samples of this board. Once the points are mapped, I should be able to purchase a working Charge, read the full 512NAND then flash the bootloader zones to yours to revive it.

However this is all very very tough work as the Charge doesn’t have the standard JTAG map that many Cortex A8 Samsung models have that I had originally been hoping to see!

Needless to say it’s been a project. I’ve been here since 7-12PM researching with this board... ;)

Also, this is the type of work that’s required in working towards a world’s first when no documentation on JTAG exists for this model.
[Verizon Droid Charge] Syn Ack:
Thank you.... I'd love to test it out but Verizon replaced my phone for free, getting it in the mail today.
[Verizon Droid Charge] Happy!:
I have tried this, booted up and EVERYTHING is force closing. Any suggestions?
[Verizon Droid Charge] Syn Ack:
Then your phone is broken like mine..... I had to get mine replaced by Verizon..... :(
[Verizon Droid Charge] jstoneky:
Are the ED1 and 2 Links here Stock, or Stock Rooted?
[Verizon Droid Charge] blarrick:
Try flashing the ee4 package instead of the ED1/ED2 that's in this post. Worked for me.
[Verizon Droid Charge] jmcdade:
Help

please!! need help!! I booted into recovery and went to backup and restore thinking i had backed up my phone. I selected something that started with 2005. and ended with image. now my phone will only startup and boot into recovery.I have tried to reflash via odin and cmr using gummy charged 1.9.1
[Verizon Droid Charge] anoninja118:
you might need to odin CWM (if you can't get into it) and wipe data/cache/dalvik if you're stuck in a restore bootloop like that... the phone is probably trying to restore a corrupted backup and can't so its bootlooping, worst case scenario you may need to odin back to stock EE4 and start over

blazing through on my 4G Droid Charge
[Verizon Droid Charge] jmcdade:
thanks for the info but i just tried to odin the stock ee4 using it with the pit file but it keeps failing. any ideas??
[Verizon Droid Charge] hazard209:
Put your battery back in after going into download mode and before starting Odin.
[Verizon Droid Charge] jmcdade:
thanks but i have tried that. every time i use the pit file my phone wont even power on.I reflashed gummy charged 1.9.1 and then i can get back to recovery mode but thats it every time i reboot it brings me back. please someone help i need this phone for work tommorow. i reflashed imnuts kernel with recovery that i was using to see what restore i flashed that started this and to help understand better this is what i did. I went into backup and restore and select -2005-01-01.00.01.40/ and now im stuck. thanks for everyones help
[Verizon Droid Charge] hazard209:
What Odin file are you using to go back to stock?
[Verizon Droid Charge] jmcdade:
help
[Verizon Droid Charge] hazard209:
No. Like are you using ED1 or ED2 listed in this thread? Are you using Pentafive's EE4?
[Verizon Droid Charge] jmcdade:
is that not a good odin to use ??
[Verizon Droid Charge] jmcdade:
ohh sorry..im using the stock ee4 from the stock unrooted thread.
[Verizon Droid Charge] jmcdade:
I downloaded the file from the stock unrooted thred and when i try to flash using odin i dont have the option to select the file. when i select pda it takes me to all my .tar files and the stock file is listed .tar.z7
[Verizon Droid Charge] hazard209:
Ok. Try this EE4 Odin file, here. It may be the same one you're using but try redownloading it. You may have just got a bad download (they happen). Also redownload the PIT file.

I'm just going to post a complete walkthrough, give it a try.

Power down your phone, remove the battery, open Odin on your computer, connect phone to computer (If you're on a desktop, use a back USB port! On a laptop? Make sure that it is plugged into the AC adapter and use the USB port closest to where the adapter connects with the computer), hold volume down, after Odin recognizes the phone reinsert the battery. Check re-partition in Odin and uncheck the other 2 boxes. Load the PIT file in the PIT section and load the Odin file into the PDA section.

EDIT: Make sure to unzip the file so that it's an .tar.md5 file! Use 7zip to extract it!
[Verizon Droid Charge] jmcdade:
do i need to unzip that stock ee4 file before flashing with odin becase i cant get it into the pda slot

sorry didnt see your edit...but thanks very much!!!!!!
[Verizon Droid Charge] hazard209:
Look at the edit I made at the bottom of my last post.
[Verizon Droid Charge] jmcdade:
hazard209 thank you very much for everything i just got my phone up and working!!!!im so glad that everyone on here is so helpful..without this site and its members my charge would be stock and could have even been a brick...THANKS !!!!!
[Verizon Droid Charge] quantim0:
Deleted asked in two threads
[Verizon Droid Charge] Endless2232:
Hey guys, I flashed the ep1q modems and have not had service all day. Redownloaded and flashed again, but flash failed during the CDMA modem phase. Now everything i flash fails at this part. Followed these instructions and phone boots up fine now (got caught in a boot-loop from hasty flashing), but still no service. Any help?
[Verizon Droid Charge] trparky:
Try flashing the EE4 radios back to the phone using ODIN. You can download the EE4 modems at http://bit.ly/oBzUOI.
[Verizon Droid Charge] Clarkkent434:
I can say that unbrickable mod fixes all these issues on this thread with bricking.
[Verizon Droid Charge] trparky:
In this case, I don't think he needs to do something that drastic yet. He has working phone in the sense that it boots, if it boots and you can get into Download Mode then you can do just about anything including flash ClockWork Recovery MOD or do other things in ODIN to flash new OS ROMs or modem firmwares.
[Verizon Droid Charge] Endless2232:
I'll give it another try, and let you know how it goes.
[Verizon Droid Charge] Endless2232:
To be more specific, here is the process i took today to try to fix the problem (Repeat of last night). Tried to flash EP1Q modems through odin: Failed during cp_modem. Tried to flash EE4 modems: failed during cp_modem. Redownloaded EE4 modems: same failure. FLashed the pit file and re-partitioned phone: successful. Flashed the ED1 package in OP: I get a progress bar until completion of lte modem, then progress bar goes away, screen says VIA reset done. Odin acts like it's fllashing the modems, then fails after about 1 minute. Tried different full odins, same result. Hope being more specific helps things.
[Verizon Droid Charge] GoBlue13:
Are you putting the battery back into the phone after you get it into download mode and before pressing start. If not try it and see if that helps.

Sent from my Droid Charge running GummyCharged FE 2.0
[Verizon Droid Charge] rj57:
Did you flash both the PIT and Odin package at the same time?

If not, then you likely have a problem on your hands. Not sure if you can safely redo it by flashing both after doing the PIT by itself. Maybe someone has more insight on this.

I have used Imnuts procedure on a couple of phones with Pentafive's EE4 full Odin with no issues. Good luck.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
I've tried this using ODIN and Samsung PST. I've tried flashing: CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.7z

CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5.7z

and Samsung_Charge_ED2_Full.tar.md5

I was getting a boot loop earlier and/or a msg that the SD card would not mount.

Then I was getting only a boot loop. Now it is loading to recovery sating it can't mount /dev/block/mmcblk0p3

This has been going on for a day and I don't know what I did to start this whole problem. It was working fine and then after a few hours without any use this started. It hasn't been the same since. Any help is appreciated.
[Verizon Droid Charge] anoninja118:
well ED2 is retarded and can give you problems, the other two should've worked given you unzipped them with 7zip... sounds like you've got a soft brick there, you need to use Odin (version shouldn't matter) and try and flash the EE4 stock rom with the PIT file
[Verizon Droid Charge] zagoric:
Yes, ED2 kept giving me a msg that the file was not working. The others were unzipped when I plugged them into Odin and Samsung PST. I'll look for a EE4 stock and try that.
[Verizon Droid Charge] zagoric:
Are you recommending an EE4 stock other than CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5 or should that do it?
[Verizon Droid Charge] anoninja118:
that's the one

blazing through on my 4G Droid Charge
[Verizon Droid Charge] zagoric:
I've tried that one (along with PIT) with both Odin and the Samsung PST and I load into recovery stating it cannot mount /dev/block/mmcblk0p3 or else it goes into bootloop.

Any other ideas?
[Verizon Droid Charge] anoninja118:
how exactly are you doing this in Odin? and does it pass and finish and bootloop when you start it?

blazing through on my 4G Droid Charge
[Verizon Droid Charge] zagoric:
I put the file in Odin in the PDA loader and check the PDA box. I put the PIT in the PIT loader.

I check the re-partition box and uncheck Auto Reboot and F. Reset Time.

I get a green pass. Once I get the pass and it has finished, I take out the battery and unplug from the CPU (I've also tried unplugging and then removing battery), reinstall battery and restart. It loads to recovery. I'll clear data and cache and restart. That's when it goes into bootloop.

Thanks for taking the time to help me with this.
[Verizon Droid Charge] anoninja118:
everything sounds right there except leave the f.reset time box checked

blazing through on my 4G Droid Charge
[Verizon Droid Charge] rj57:
Looks like you are doing the odin part correctly.

Is it booting straight to recovery when you do the first boot after disconnecting the cable? If so, are there any messages other than the # MANUAL MODE #?

Or does it look like it is booting normally and sticking at the Samsung label?

One thing that I noticed on both times that I did this procedure is that the phone took a good 5 minutes or so to get past the Samsung on the first boot. It then took another 5 minutes to finally finish booting and get to the setup program.
[Verizon Droid Charge] zagoric:
Okay. I ran it again with the f.reset box checked and got the same result as before. I'm at a loss here, but I'll admit my knowledge is limited.
[Verizon Droid Charge] zagoric:
It boots straight to recovery on the 1st boot after flashing. I'll do it again and post the message. From recovery, I reboot system and it then goes into bootloop.
[Verizon Droid Charge] zagoric:
On the first boot after flashing, I get:

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:
hmm this is strange.. you could odin CWM, boot straight into it and wipe data/cache/dalvik then try flashing sonething else to see if that works

blazing through on my 4G Droid Charge
[Verizon Droid Charge] rj57:
I had this set of errors once when going from GC 1.8.5 to stock. I finally ended up doing the format internal sd option in BML recovery and then re-flashed the odin package again. Everything was fine after that.

Sent from my SCH-I510
[Verizon Droid Charge] zagoric:
Should I run the PIT file with CWM or run CWM by itself?