yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] will2live:
Heya all need some input and advice. Here is the situation I'm sitting at. I've got a device that is needing to be returned to VZW after getting a replacement for a hardware defect on mine it won't even go into download mode. No matter what I try it is just a black screen like the device is completely dead no Samsung logo or anything and fyi it was running EP1W so I need to get it back to EE4.

What happen was I was in the middle of a flash last night taking it device back to stock as I just received a replacement unit. So before sending it back I wanted to get EE4 back on it obviosuly. Well in the middle of the flashing the dam power went out at the house for no reason as there was no bad weather. Anywhoo once it came back on I was going to try reflashing obviously but as I mentioned above its like the device is toasted as nothing happens no matter what I try.

Is there any hope of reviving it, or should I not worry about it and just send it back to VZW seeing as I got my refurb now anyways and this was a defect. My only concern is I don't need to get hit retail on it if they see it has a different OS on it then what it should. However I'm not even sure what is on it because I don't know where the flashing process was when the power went out. Any input or advise is greatly appreciated as I do need to get this thing in Fedex very soon. I'm half tempted to just send it back as is seeing as it won't even power on or do anything now, but I really do not need to get hit with paying for it if they figurer out if was flashed and had a different SW build on it.
[Verizon Droid Charge] rj57:
A couple of things that you can try to get it into Download mode.

1.) There is a usb jig mentioned earlier in this thread somewhere that might work.

2.) Try getting it into download mode by plugging into the wall charger and holding down the volume button down right after you plug it in. No need to remove the battery. I found this by accident the other day and have since verified that Odin can see the phone when I plug it into my computer.
[Verizon Droid Charge] ercDROID:
I am in the same boat as some others. My wifes phone was running gummy 1.9.1 for a month and all of the sudden just wouldn't get past the boot animation. It was stuck in a boot loop. I tried all methods discussed in this thread without success. I've been trying for 8 hours and am not getting anything done. I can get into download mode. I brought in the newest CWM through odin. I used odin for the stock EE4 and PIT file. Now if I reboot I can't get past samsung logo. Why would this just happen for no reason. Only thing new is Imoseyons kernel was flashed 2 weeks ago. Please help if you can! I have a baby due in 2 weeks and really can't afford to shell out 600 on a new phone and I need my wife to have her cell on her. Hopefully somebody can save this phone!
[Verizon Droid Charge] trparky:
http://www.toms-world.org/android

Click on "Show Instructions to Flash Your Droid Charge Back to Stock" and follow the instructions provided. After clicking the link you will have to scroll down the page. Reply back if it works for you.
[Verizon Droid Charge] anoninja118:
see my convo with zagoric a few posts up, I was trying to help him with the exact same problem... if it gets into download mode its not a hopeless cause, however nothing flashing is the big issue and I noticed that error message you posted in the other thread is related to /cache partition... I suggested to the other guy zagoric to pm a dev like Imnuts or Kejar, maybe even Danalo as they can assist further hopefully... also have you tried flashing anything else? I've heard that the new GB leak odin package MIGHT fix it as one person said it did who had kinda the same problem, as always YMMV but as I said as long as it can get into download mode there's a chance to revive it

blazing through on my 4G Droid Charge
[Verizon Droid Charge] ercDROID:
I have tried everything. Just tried the gingerbread leak odin. Just on a boot loop at the animation. Every time I odin something it is successful. I'm gonna try a few more things then after that I'll stop until someone has another suggestion.
[Verizon Droid Charge] ercDROID:
If I flash back to to verizon EE4 full odin and can get my phone to only have the boot animation loop and show no other errors would verizon know that i did something? I'm just ready to take it back if possible.
[Verizon Droid Charge] anoninja118:
that sounds like it should be fine, at least if its bootlooping on stock they won't suspect anything.. say it happened after a factory reset you pulled the battery or something and now it just bootloops

blazing through on my 4G Droid Charge
[Verizon Droid Charge] ercDROID:
Out of curiosity, could this problem be related to the flash on gummy 1.9.1 and imoseyons latest that I did weeks ago? Just odd that it happened so long after I set up my wifes phone.
[Verizon Droid Charge] anoninja118:
could be, I think zagoric was on the same setup and after a while got borked like yours... though idk why, you two are the only ones I've heard of with the problem

blazing through on my 4G Droid Charge
[Verizon Droid Charge] TrypWyr:
Well, add a third, I am getting the same errors as Z above.

I was running GummyCharged FE 2.0, PBJT kernel, murdercharged theme. Phone shut down on me this afternoon (thought the battery was just dead), but then wouldn't boot past the animation. Wiped the cache/dalvik to see if I could at least get in and get backups. Was able to get in and get a backup of my SMS and some of my apps, getting FC's all over the place. Good enough.

Rebooted and wiped data/cache/dalvik. Still getting force closes... strange. Finally tried the ol' PIT+EE4, no luck. I get the errors on first boot, then boot-loop.

Man, I really hope someone finds a fix for this one... I'm at a loss. Nothing will fix, even tho they Odin fine.

Help me Obi-wan, you're my only hope...
[Verizon Droid Charge] will2live:
Should be fine and I wouldn't worry about it as they are pretty much clueless over there anyways. They will try resetting it and so forth to find out its toasted.

Lets put it this way if you look back a page and saw my issue I sent it back as is to them as nothing would work to save it. And seeing as you only get 5 days to return a device when getting a replacement I ran out of time with messing with it so I had no choice but to send it back. That said haven't heard a word about it after sending it back and I didn't even know what software was partially installed on it when it was sent back.

---------- Post added at 08:17 AM ---------- Previous post was at 08:14 AM ----------

Appreciate the input but like I just posted I ran out of time and had to send it back as is. FYI I did try your #2 thought as I have a buddy who works for Samsung and he suggested the same and still nothing. He had a few other thoughts as well and none of them would work either.
[Verizon Droid Charge] braveally:
11 pages deep and no luck

I'm working my way through this thread now and nothing so far has worked. Background: I was running Humble 1.6 and had recently loaded the v6supercharger script. Everything was working fine over the past two days then all of the sudden my phone is frozen on the dial pad. I restarted the phone and booted into the error seen on the original post. Every combination I have tried so far is not working:

Pit + EE1

Pit + ED2 (corrupt file)

Pit + EE4

Pit, then EE1

Pit, then EE4

All in Odin and Samsung PST. Gonna continue working through the thread but not feeling this right now. Please help me.

I have however moved from the bootloop at the samsung logo to bootlooping at the animation, which some have identified as a sign of progress I think. I have no problems getting into download mode either.
[Verizon Droid Charge] rj57:
How long are you letting it go when it is at the animation? It can take a while after flashing the pit and stock. I would give it up to 30 minutes before giving up on the boot especially if the animation isn't frozen.

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] rj57:
Also, if you have adb, there are a couple of things that can be checked if the phone is setting at the stock recovery.

The following adb commands can be used to capture some useful information for troubleshooting.

adb shell mount>mounts.txt

adb shell ls -l>rootfs.txt

adb shell dmesg tail>dmesg.txt

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] braveally:
Will do

Ok, will do. About to leave to work so I will let it do its thing. Hopefully it can recover while I am on my way. when I get there it should be okay i will post the result. Not getting any sound on the animation which is why I thought it was a bad flash.

What more can I do to investigate this? When should I just go to Verizon?
[Verizon Droid Charge] braveally:
Hour of animation looping, no luck

So I let the animation loop on my trip to work, which was roughly an hour today (kind of long actually) and I have had no progress. Just my phone looping and getting more and more hot. What's next?

---------- Post added at 12:10 PM ---------- Previous post was at 11:23 AM ----------

So I let the animation loop on my trip to work, which was roughly an hour today (kind of long actually) and I have had no progress. Just my phone looping and getting more and more hot. What's next?
[Verizon Droid Charge] rj57:
Sounds like something may be awry on the data partition. It appears that it is mounting ok as you are getting to the boot animation

What were you running for the kernel and ROM prior to Humble?

Also, which kernel were you running when your phone died?

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] braveally:
Phone History

Prior to this I was running the previous version of Humble on the PBJ (no overclock) kernel. Prior to that I was just running a rooted EE4 on the same kernal. I odined to Humble 1.6 and using the included IMoseyON 13.6 Lean Kernel.

Also, not sure how to access adb.

I would really love to fix this and not turn into Verizon but I am about half an hour away from doing just that.
[Verizon Droid Charge] rj57:
I suspect that the root cause may be a borked swap file on the data partition. Not sure if it can be fixed at this point.

I am pretty sure that flashing anything by itself will not fix it as you have tried all of the standard flashes.

Are you familiar with using adb from the android SDK?

If so, you might be able to flash CWM, boot into CWM, and connect to the phone with an adb shell to get more info as to what is happening.

BTW, I disabled my swap a few days ago after I started getting reboots when running poweramp over Bluetooth. Cleared my reboots immediately.

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] braveally:
Unfortunate

That's sad. Any idea how this could have happened? I forgot to mention that I recently installed the v6 supercharger script. I highly suspect it had something to do with it. Any insight into how I could avoid this in the future? I will probably take it back later, I have flashed it to stock nearly a dozen times so I guess they won't find anything wrong. What are the chances they will let me get a bionic?
[Verizon Droid Charge] rj57:
V6 SuperCharger doesn't really do anything that could cause permanent damage. It's actually one of the safer mods that you can do. About the worst you can do is to misconfigure and have a very laggy phone.

As far as totally avoiding the risk, the only way is to never mod or update your phone.

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] TrypWyr:
So from what I can tell, there's something wrong with the internal memory partitions. This apparently should be fixed by flashing the charge.pit file, but that doesn't seem to be working.

Very possible that I'm being naive here, but I came across this on an HTC Incredible forum... any idea if their fix could be adapted to the Charge?

http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

I really don't want to try and take my phone back to Verizon... not to mention that I don't want to replace the Invisible Shield! ;-)
[Verizon Droid Charge] rj57:
This error that has been coming up in the recent cases seems to be where it all starts falling apart.

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

(Invalid argument)

This is the data partition that won't mount and it looks like the init script is going into la la land at this point.

It will likely take some troubleshooting with adb to get to the bottom of this and possibly correct the issue.

You usually can get into adb from recovery unless things are really hosed.

My theory is that you will need to:

1.) flash Imnuts' CWM

2.) Boot to CWM

3.) connect the usb to a PC with adb installed.

4.) Mount data from CWM

5.) start adb shell on the pc

6.) cd to /data in the adb shell

7.) list the directory with ls -l

8.) look for various files like zipalign* and swap.

9.) if you see a file named swap, delete it using rm swap.

10.) flash the pit and EE4

11.) reboot

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] TrypWyr:
Yup, there was a swap file. I deleted it, Odin'ed PIT+EE4, same issue. Went back in using adb shell after Odin'ing CWM, swap file is back (normal, I assume?).

I saw a few zipalign files too, did those need to be deleted as well?

EDIT: Looking around in adb shell, found something interesting... when I run mount, I get the following list:

mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
/dev/block/stl7 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p3 on /cache type ext4 (rw,noatime,barrier=0,data=writeback)
/dev/block/mmcblk0p1 on /data type ext4 (rw,noatime,barrier=0,data=writeback)

Could this problem just be caused by the partitions still being stuck on ext4 rather than rfs? How can I convert them back??
[Verizon Droid Charge] rj57:
Actually, all that stuff is from the Gummy 2 ROM and imoseyon kernel. None of it is stock.

This is strange. I would try to wipe data, cache and then flash gc2 from CWM.

If you can boot to gc, install voodoo control from market, and then disable voodoo.

Alternatively, you can put a file in the Voodoo directory on the sd card named disable_lagfix

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] TrypWyr:
Installed GC 2.0, PBJT voodoo kernel. It started the disabling, then went into GC. Force closes all over the place, then it reboots and does the conversion again.

I then flashed EE4+PIT again, CWM, checked the "mount" output, still showing ext4.

I'm at a real loss here... looks like tomorrow might be a trip to Verizon. I really appreciate all your help, rj57. If you have any more ideas, I'm game, but it's not looking good, eh? :rolleyes:
[Verizon Droid Charge] braveally:
Good info here, but getting a new phone

Wish I had the time to try the methods in the last few post, although it seems a bit over my head. I am studying java and android development but haven't played around with adb enough to fell comfortable. Maybe in a few weeks. I did however go to Verizon after work today, and it was actually a bit funny.

The rep looked at my phone and tried to ask some questions to disqualify my warranty "Did you root your phone? Did you make any other changes?" I played dumb like I never heard of a root. Then I watched as he tried to boot into recovery, incorrectly (only held the vol up button), telling me that he could just do a factory reset and it should fix it (despite me trying to do that a dozen times).

Then he asked another rep if he had "those programs" to factory reset my phone. Hmmm... Didn't quite sound like company policy. But it ended with them sending me a new phone, so all is well now. Thanks for all your help. This thread should be a sticky.
[Verizon Droid Charge] rj57:
Basically what needs to be done is to completely wipe the /data, /system, /cache, and /datadata partitions. This can be done from CWM under mounts and storage using the format options. You will need to mount each of the partitions and then format them.

Then reboot into CWM and verify that the partitions are empty using adb.

If they are empty, flash the pit and EE4. A good flash will take @15 minutes to complete.

When it reboots, if it is stuck at the Samsung logo, let it sit there for at least 20 minutes, before intervening. The first boot after a successful stock restore has taken @10 to 15 minutes to get to the boot animation when I have done it. The reason for the extra time is that the partitions are being set up.

If it goes straight to samsung bml recovery, you will need to format the internal sdcard (last option) and then reboot. Give it some time and if it fails, do one more pit and EE4 flash

_____________________________

GummyCharged 2.0 FE

Imoseyon lean kernel 1.2.0 noswap, no OC

V6 SuperCharger
[Verizon Droid Charge] TrypWyr:
No luck... mounted the partitions in CWM, formatted. Rebooted, back into CWM. ADB shows all partitions empty but CACHE and DATA. EE4+pit, got the e3 screen. Tried to wipe internal SD card, unable due to CACHE mounting errors.

It all seems to come back to these mmcblk0p1 and 0p3 files. It's like they are corrupted and stuck on etx4, but will not format or reset.

I don't suppose it would be possible to get a copy of these from a working Charge, then "adb push" them to mine, overwriting the bad ones?

EDIT: Perhaps "file" isn't the right term here... I'm a little fuzzy with Linux terminology.
[Verizon Droid Charge] rj57:
I guess that we need to find out why formatting cache and data in CWM isn't actually formatting the data and cache partitions.

I did some experimentation in the cache partition on my phone and have a couple of things to try in adb when you are in CWM.

1.) in CWM, go to mounts and storage.

2.) format /data and /cache

3.) mount /data in CWM (mounts and storage)

4.) go into adb shell and cd /data

5.) do a ls -l to list the files in the data directory

6.) if there are any files, execute rm -R /data/*

7.) note any errors if any (there should be some if it fails)

8.) if there are no errors, ls -l /data/* to see if it is empty

9.) if it is empty, repeat step 2 for data

10.) run the following command in the adb directory:

adb shell cat /tmp/recovery.log>recovery_log.txt

this will create a test file of the logging on the recovery session and may assist in further debugging.

11.) wipe cache

12.) exit adb shell

13.) Power off in CWM

14.) Flash EE4 and the PIT in Odin
[Verizon Droid Charge] TrypWyr:
No such luck. I wiped the cache, used "rm" to delete all items, confirmed the directory was empty. Rebooted, everything was back the way it was before.

Tried running the command "adb shell cat recovery.log>recovery_log.txt" and all I get is "access is denied".
[Verizon Droid Charge] rj57:
Ok just to verify. You are checking the repartition box in Odin when you flash EE4 and the PIT? correct? and you have the battery in after you put the phone into download mode?

The access denied error that you got when running ADB shell sounds like you don't have root, which you wouldn't if you booted out of CWM without installing a kernel.

The recovery log will be useless at this point as it doesn't persist between recovery sessions.

Something else that may help is if you copy and paste the contents of the Odin message window so that I can see if anything looks abnormal.
[Verizon Droid Charge] TrypWyr:
Sorry, been busy with family stuff...

I'm really at a loss with this one. My main concern is that this issue seems to be happening quite a bit and no one has a solid fix for the Charge. Every thread I find about it usually ends with the OP getting a replacement phone, or the thread just ends with no responses:

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

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

http://xdaforums.com/showpost.php?p=14175238&postcount=281

http://forums.androidcentral.com/introductions/90953-cwm-stuck-droid-charge.html

http://www.chargeforums.com/forum/d...ricked-really-could-use-some-help-please.html

The problem seems to be with the CACHE partition but the PIT file isn't reverting it to the original state, i.e. RFS. I've tried formatting manually, flashing everything I can think of with Odin as well as PST, all convievable combinations of ROMs, Kernels, and CWM versions. And most definitely being sure to click "repartition" in both Odin 1.3 and 1.85. ;) With SIM, without SIM, with battery, without battery.

All that said, there is a fix. The problem? It's not for this phone:

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

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

We need to get a hold of this legendary "original.mbr", only for the Droid Charge instead of the Fascinate...

Like I said, the fact that there's not a current fix for this, even though it's a software issue (well, firmware, perhaps?), makes me real concerned about getting another Charge and keeping the one my wife has... maybe just not use voodoo lagfix?

rj57, I truly appreciate the help! Unfortunately I've been without a phone for almost a week now and that's not gonna work. It looks like without this MBR, I am SOL.

Verizon Store, here I come!

:rolleyes:
[Verizon Droid Charge] rj57:
That looks like an interesting approach. A person should be able to get the Charge equivalent of the Fassy's original.mbr using the dd command on a rooted non-voodoo EE4 phone. The command would be something like this to put the file on your sd card:

dd if=/dev/block/mmcblk0 of=/mnt/sdcard/charge_mmc_partition_table bs=1 skip=0 count=512

The Samsung PST program that trparky mentioned, may work if you have a 32 bit Windows PC. I have not been able to get it to find my phone on any of my Windows 7 64 bit PCs. so I stick with Odin on my PC or Heimdall on my Ubuntu workstation. I have an old XP laptop that seems to work ok with PST Lite though.

As far as Voodoo goes, I don't think that is necessarily the root cause of your issue. There are other things like bad Odin flashes, bad nandroid restores, or running an unstable configuration that are more likely to cause problems.

I do run a nandroid backup prior to trying a new ROM and do keep known good ones that I have restored without issue. That way, if I get into trouble, I can usually get back to a good place pretty quickly.:)
[Verizon Droid Charge] trparky:
I've been able to get it to work fine on my 64-bit system. It detects the phone and everything.