yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] sikimk:
i have to thank you imnuts you have saved my ass numerous times.

your a great developer, keep up the good work my friend.

i used this and it worked perfectly using the ED1 package.

---------------------------------------

OG Droid(cyanogenmod 7)

Droid Inc (cyanogenmod 7.0.1RC1)

Droid X (Deodexed Gingerbread)

Samsung Fascinate (Rooted GingerRom)

Samsung Droid Charge (Infinity Rom Beta)
[Verizon Droid Charge] Makaveli315:
YES!

Thank you soooo sooooo much rj57! I tried this one this time (CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.md5) and it worked! My phone is now back to original factory settings! Thank you and the devs so much, now I just hope to god that I successfully get GC2.0FE on my phone w/o another panic attack lol. THANK YOU!
[Verizon Droid Charge] flyinj54:
Stressed out

Hello. I have been going through and reading all the threads to and tried misc flashes to try to fix my phone. My situation is I flashed my phone to gummy 2.0 rc1.5 ep1w build and everything was working fine for a week or so until I launched google maps from then on out force closes etc. I decided to reflash my phone with humble 4.0. Before doing this I did create a disable-voodoo folder in my voodoo directory and rebooted and the heard the woman begin to disable this function. After that it locked up for about 45 minutes at the samsung screen. So I pulled the battery and tried to flash the humble 4.0. Everything seemed to have went fine and booted the phone and right past the animated boot screen I just got a black screen. I tried the charge.pit and flashing ed1 from the forums with no sucess. After flashing I am getting a bootloop on the droid eye. I tried using cwm to clear cache, davilk, factory reset and reload charge.pit and ed1 without prevail. At this point I have flashed this ed1 back on with charge.pit then flashed cwm and cleared all and flashed humble again. Still getting bootloops. Not sure what to do from here. At one point I was able to get into the operating system but immediatley I recieve a fc on every app on the phone which locks me up and causing me to reboot into a bootloop again. Not sure where to go from here. Any help or direction would be appreciated. thanks
[Verizon Droid Charge] timefornothing:
The First post by imnutz worked perfectly for me thanks so much
[Verizon Droid Charge] id1dave:
Same ole' bootloop

Ran into the same issue that TrypWyr, zagoric, and others had earlier on in this thread. Boot loop on stink eye or stuck at Samsung depending on what I flashed. Couldn't get EE4+PIT to work (or ED1, ED2, etc). Was running PBJT voodoo kernel (8/7) on stock fine for weeks when for no reason that I could tell I looked down and had the red eye.

Reflashed kernel, tried wiping various caches, formatting, factory resets, etc. Finally went to this procedure and could not for the life of me get it to work. Tried everything in this thread including every ODIN combo, and even the samsung flashing util (minus the adb - had trouble setting that up without a working phone to put in usb debug mode). Was able to ALMOST get in with gummy 1.9.1 but couldn't ever make it all the way.

Anyway, new phone is on the way. Would certainly appreciate if someone could figure this one out as I am reluctant to touch the new one knowing there might not be a way back (that doesn't involve soldering).

PS - Thanks to those who took the time earlier to troubleshoot and post their steps.

PPS - Like others, this is what I get after flashing EE4+PIT (booted straight into recovery):

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:
as I mentioned earlier when trying to troubleshoot, this error is with the /cache partition and as of yet is not fixable or recoverable... so I hate to say it but you've got a bricked phone there :( my advice would be to flash stock EE4 with PIT for whatever good it'll do then get verizon or samsung to replace it
[Verizon Droid Charge] flyinj54:
Replaced

Thanks for the help. I ended up with a new phone which was not the route that I had hoped to take. I am not a little afraid of using the voodoo lagfix and converting to ext4 file system. My problems seem to have all came after trying to disable lagfix and convert back to rfs. Since that day I had a mess on my hands. After hours and hours of trial and error I was unable to fix this issue and decided it was probrably best to just replace the phone. Unfortunently there doesnt appear to be roms without the voodoo preinstalled in the flash. Im sure things would be just fine flashing without the ext4 file system conversion if their were any roms that I could do this with. Ive learned alot through all of this thats for sure.
[Verizon Droid Charge] anoninja118:
Eclipse for froyo by Nitroglycerine is a pretty nice rom that doesn't include a kernel... also on Rootzwiki Imnuts and TSM put out a sweet TW4 based EP1W rom (that I'm running right now and it's awesome) that you can download and flash that is rom only or rom+kernel
[Verizon Droid Charge] id1dave:
Yep. New one arrived today.

I really appreciate all of the work that the devs and knowledgeable users do taking their time to help out ppl in this thread. There is a definite issue here with this phone though, and I would certainly be grateful (along with many others I'm sure) to the dev who managed to figure it out.

I have 4 days to return the old phone so in that time I am happy to test whatever if it will help someone to troubleshoot and figure this thing out.
[Verizon Droid Charge] rj57:
I'm game for this. I think that there are a couple of things that will need to be checked in adb to see if the cache and data partitions have any hope of recovery.

This check will require adb which will be accessible if the phone is sitting on the CWM menu.

You will need imnuts' CWM from here and the attached parted program which will need to be unzipped to your android-sdk\platform-tools directory

To do the check,

1.) Perform the steps in the OP here using the ED1 package or pentafive's EE4 package from here.

2.) Let the phone boot as far as it will, and then power down.

3.) Flash imnuts' CWM package in Odin

4.) Boot into CWM using the 3 button method

5.) In CWM's Mounts and Storage menu, mount system

6.) adb push the parted program to /system/xbin/ using the following commands

adb remount
adb push parted /system/xbin/
adb shell chmod 0755 /system/xbin/parted

7.) get data for the /dev/block/mmcblk0 partitions

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

8.) Post the results that should be in the MMC-Parts.txt

If there are 3 partitions, it definitely may be worth trying out the stock newfs_msdos, fsck_msdos, and fat.format programs in the /system/bin/ directory.
[Verizon Droid Charge] davidhite:
Thanks RJ57.

I am also very interested in seeing a solution. My cache partition seems to be bunged (won't convert to rfs when lagfix is disabled) so I'm afraid to change anything at this point for fear of creating a brick.

All I have done is install PBJ Voodoo 0602 over stock EE4 and disabled lagfix.

This is from the rfs_formatter log:

format cache:

Cluster size(4096) is too small to format this to FAT16.

If you want to format this to FAT16, retry to format after enlarge the cluster size. Otherwise, retry to format the device with FAT32 type.

fat 34 max 65524 num_clusters 66198

create_pbr[382]: failed to calc_fat_sectors!

make_tables[683]: Cannot create PBR!

make_tables[731]: Releasing allocated memory

fat_format[963]: Failed to make table!

fat.format 1.0, 2010.07.01

Fail to format
[Verizon Droid Charge] rj57:
The error that you are seeing is "normal " in a very loose definition of normal for the rfs conversion. The problem is that the lagfix scripts are using some screwy fat.format settings. This issue is present on all of the Voodoo kernels for Charge.

I personally wouldn't run on the pseudo rfs that is set up by the conversion. My experience is that it can become very unstable after time.

You are probably best going back to ext4 or to stock using the procedure in the OP. (ED1 package)

Assuming that you are relatively stable, going to stock is relatively low risk compared to doing it after you start bootlooping or getting lots of persistent FCs. The biggest risks are a bad odin setup, inattention to detail when doing the procedure, and panic flashing if something goes wrong.

I have done the procedure successfully about 15 times on 7 different phones. A couple of times were tricky but I have yet to personally see one like the ones that people are having an impossible time with.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] id1dave:
Here's the results:

Model: MMC SEM02G (sd/mmc)

Disk /dev/block/mmcblk0: 1959MB

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

Partition Table: msdos

Number Start End Size Type File system Flags

1 32.8kB 1256MB 1256MB primary ext2

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

3 1686MB 1959MB 273MB primary ext2

What next, captain?
[Verizon Droid Charge] rj57:
With the phone sitting in CWM like before, try the following adb commands. Dont worry if the umount commands fail. We just need to make sure that the partitions are unmounted before trying to put a new file system on them. Each one of the newfs_msdos commands could take some time as they should create a new file system and format it

adb shell umount /data
adb shell umount /preinstall
adb shell umount /cache

adb shell /system/bin/newfs_msdos -F 32 -S 512 -c 32 -s 2453440 /dev/block/mmcblk0p1
adb shell /system/bin/newfs_msdos -F 16 -S 512 -c 32 -s 839680 /dev/block/mmcblk0p2
adb shell /system/bin/newfs_msdos -F 16 -S 512 -c 32 -s 532480 /dev/block/mmcblk0p3

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

Post the results that are in MMC-Parts2.txt
[Verizon Droid Charge] id1dave:
Ok, so the MMC-Parts2.txt is showing the exact same thing as the first MMC-Parts.txt. Not sure that the commands were working since it didn't take a long time to run each as you had mentioned.

Here's the adb session and the responses I got when running:

C:\Program Files\Android\android-sdk\platform-tools>adb shell umount /data

umount: can't umount /data: Invalid argument

C:\Program Files\Android\android-sdk\platform-tools>adb shell umount /preinstall

umount: can't umount /preinstall: No such file or directory

C:\Program Files\Android\android-sdk\platform-tools>adb shell umount /cache

C:\Program Files\Android\android-sdk\platform-tools>adb shell /system/bin/newfs_

msdos -F 32 -S 512 -c 32 -s 2453440 /dev/block/mmcblk0p1

/system/bin/newfs_msdos: warning, /dev/block/mmcblk0p1 is not a character device

/system/bin/newfs_msdos: Skipping mount checks

/dev/block/mmcblk0p1: 2452192 sectors in 76631 FAT32 clusters (16384 bytes/clust

er)

bps=512 spc=32 res=32 nft=2 mid=0xf0 spt=16 hds=4 hid=0 bsec=2453440 bspf=599 rd

cl=2 infs=1 bkbs=2

C:\Program Files\Android\android-sdk\platform-tools>adb shell /system/bin/newfs_

msdos -F 16 -S 512 -c 32 -s 839680 /dev/block/mmcblk0p2

/system/bin/newfs_msdos: warning, /dev/block/mmcblk0p2 is not a character device

/system/bin/newfs_msdos: Skipping mount checks

/dev/block/mmcblk0p2: 839424 sectors in 26232 FAT16 clusters (16384 bytes/cluste

r)

bps=512 spc=32 res=1 nft=2 rde=512 mid=0xf0 spf=103 spt=16 hds=4 hid=0 bsec=8396

80

C:\Program Files\Android\android-sdk\platform-tools>adb shell /system/bin/newfs_

msdos -F 16 -S 512 -c 32 -s 532480 /dev/block/mmcblk0p3

/system/bin/newfs_msdos: warning, /dev/block/mmcblk0p3 is not a character device

/system/bin/newfs_msdos: Skipping mount checks

/dev/block/mmcblk0p3: 532288 sectors in 16634 FAT16 clusters (16384 bytes/cluste

r)

bps=512 spc=32 res=1 nft=2 rde=512 mid=0xf0 spf=65 spt=16 hds=4 hid=0 bsec=53248

0

C:\Program Files\Android\android-sdk\platform-tools>adb shell /system/xbin/parte

d /dev/block/mmcblk0 print > MMC-Parts2.txt

Thoughts?
[Verizon Droid Charge] rj57:
Ok, it looks like we may be close. Did a quick search on the newfs_msdos errors and it looks like we may get past them by mounting the partitions before running newfs_msdos.

In CWM, go to mounts and storage, and mount /cache and /data

Then run the previous newfs_msdos commands for mmcblk0p1 and mmcblk0p3

Finally, run the parted command to get the partition list so we can see if it changed
[Verizon Droid Charge] davidhite:
Thanks rj57,

I'll try taking it back to ext4, then flash back to ED1 after it has been stable for a couple of days.

Do I need to use the PIT file when I flash back to ED1?
[Verizon Droid Charge] rj57:
You will need to use the PIT when going back to stock with ED1. You will want to follow the directions in the OP precisely.

Take your time and don't panic if you see it bootlooping a couple of times on the first boot. You will quite likely see the movicheck stuff come up and it may even hang there for up to 5 minutes before going on and formatting the internal storage.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] pacino12:
About to unroot and return back to Verizon.

Hey guys and gals,

I'm about to use this process to unroot my Droid Charge and return it back to stock condition in order to return it back to Verizon (due to a faulty charging port). Before I go ahead with this process I want to make sure that I'm doing everything correctly.

1. I am currently running Gummy Charged 2.0.

2. I will be either be using ODIN 1.3 or PST Lite to complete the process. (Which program is better to use?). And what boxes should I check (or uncheck) before I flash the files.

3. I am guessing I don't need to flash the PIT file since my phone is operating correctly.

4. Would you recommend using the ED1 or ED2 file? Also does the EE4 file replace the prior two mentioned files? Should I just flash EE4 along with the PIT?

Any help you can give me before I go about doing this would be greatly appreciated!!!
[Verizon Droid Charge] anoninja118:
1. that shouldn't be a problem

2. Odin is what I would recommend, version doesn't seem to matter but some people prefer the 1.82 (I use 1.3 and never have problems)... also only use PDA and PIT buttons, put the battery back in for the flash so uncheck auto reboot box and only check the repartition box if you have the PIT file, leave all others alone

3. no you will need to do it with the PIT file since Gummy and the voodoo kernel convert your file systems to ext4, you need them to be stock which is rfs so PIT will repartition them

4. ED1/ED2 are just previous incarnations of froyo, EE4 is the most recent and up to date so yes use EE4 with the PIT file
[Verizon Droid Charge] id1dave:
Sorry for the delay. So i've been hanging for over an hour on the "adb shell /system/bin/newfs_msdos -F 32 -S 512 -c 32 -s 2453440 /dev/block/mmcblk0p1" command. Does that seem right??
[Verizon Droid Charge] rj57:
That seems a little on long side. You could do A CTRL C, to stop it. Pretty sure that it isn't working.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] rj57:
It looks like the internal sdcard is stuck in a read only state which would explain why the PIT is failing to partition it.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] id1dave:
Haven't been able to make it work using the newfs_msdos command. Either hangs indefinitely or errors out like in my previous post.

Anything else I should try before sending the old one back?
[Verizon Droid Charge] rj57:
I am pretty much out of ideas. Nothing is going to work if you can't get changes written to the partitions. You probably will want to do one last flash with EE4+PIT and let it boot as far as it will. Wouldn't want CWM to come up if they turn it on.
[Verizon Droid Charge] majorhunadadun:
Is this the fix if you can't get your sd card to mount in cwm??
[Verizon Droid Charge] juanzr1:
So if I flash back to ed2 we will be able to update to the official gingerbread?
[Verizon Droid Charge] rj57:
I would flash the ED1 package+PIT per the OP and let it do the OTA to EE4. Several people have had corruption issues from the ED2 download.

You will be full stock and should be able to take any VZW OTA updates.
[Verizon Droid Charge] nismology:
It seems to me like the ED1 file in the OP might be corrupted. I've tried downloading it at least 10 times using different browsers and using both the newest winrar and 7-zip to extract it...no dice. Also is there an MD5 hash associated with it that anyone could post just in case I get a download that works?
[Verizon Droid Charge] rj57:
Here is the MD5 hash for my copy of CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.7z 9375107184CE56088B86F3D0CC798425

The MD5 hash of it's contents, CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.md5 is A833E8629FE5C336A84D488ED446982B

I have used this file several times without issue
[Verizon Droid Charge] barrettcook2000:
So I ran into a little bit of a problem. My Charge is currently stuck in clockwork and will not reboot. It seems to only reboot back into clockwork. Once there, I cannot flash anything at all. It just says E:can't mount /sdcard and I have no idea how to fix it.

On top of that the phone will go into download mode, but Odin cannot see the phone. Again, I am clueless at this point. Any ideas?

Odin 1.3

CWM 4.0.1.4
[Verizon Droid Charge] rj57:
Take a look at the known issues section of imnuts post

http://xdaforums.com/showthread.php?p=14479482

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] braveally:
Thanks

So I borked my phone trying to disable lagfix in GummyCharged (switching over to Humble 4.2). I was afraid of my previous experience where nearly everything in this thread didn't work. Glad to say it was a different experience this time around. Flashed the pit and EE4 stock and i'm back in business! Thanks again for this incredible thread.
[Verizon Droid Charge] Ronbo85:
First thank you for the very useful info here.

I have ended up here after working with the guys in the "unbrickable mod" thread for the charge hoping to find some help. Here's the story...

I bought this phone second hand and have no idea what the background to it is other than im sure its the victim of a flash gone wrong. It was totally dead when I got it other than when connected to a charger the battery would get a little warm as usual when charging, no display, no, connect to pc, or boot whatsoever. The phone appeared brand new, mint, never wet or apart.

I sent it to Adam for the unbrickable mod and he ended up sending it to mobiletech videos for jtag. I got the phone back and it works perfect but.... the MEID is all zeros.

The IMEI is there and matches the sticker. It works on the wifi but obvioulsy there is no vzw network connection and it wont activate. When I got it back MTV had put the humble rom on it so last nite I reflashed it to stock from post #1 here just as a try but no luck on the MEID.

Ive seen all kinds of stuff searching around about this issue on other phone some say its fixable but as far as this phone Im stuck.

Also please note I am trying to REPAIR this as I know this topic is touchy
[Verizon Droid Charge] rj57:
There is a strong possibility that the phone has a bad ESN. If the previous owner filed a lost phone claim with Asurion, the ESN would definitely be bad. In this case, you would not be able to activate the phone even if you manage to get the MEID into the phone.

On both of the Charges in my household, the MEID is the same as the IMEI with the last digit dropped.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] barrettcook2000:
Thanks for the link. Couldn't do anything though because Odin couldn't see the phone. As it turned out Odin couldn't see my fascinate either. That gave me the solution to the problem. Seems that there is an issue with trying to use an LG cable with a Samsung device. Plugged in the Samsung cable, Odin sees the phone and I am back in business. Seems strange to me, but it worked.
[Verizon Droid Charge] laidback1987:
phone not working

i have been having problems since flashing back to stock my phone will turn on and it will go into android system recovery and it wont go any further than that please someone help here is what it says i have the droid charge

it says something about manual mode at the bottom and it doesn't go any further help
[Verizon Droid Charge] rj57:
Does it have any mount errors?

Also, what led up to the restore to stock? And what ROM/Kernel were you running?

I know that is just more questions, but is kind of important to get an idea of what is going on with the phone.

_____________________________

Rooted and Bloat frozen Stock EE4

V6 SuperCharger
[Verizon Droid Charge] trebores1:
No. I didn't activate a new phone.. did he have to get a new phone or a new sim?
[Verizon Droid Charge] trebores1:
So, my sim card issues are unrelated to the problem in this post. So ultimately, imnuts instructions work - thanks.

It seems that I screwed myself up by checking Phone EFS clear in Odin at some point in my futzing around. I'm working on fixing that.. apparently it can be fixed.

Anyway, thanks to everyone in this thread for helping.
[Verizon Droid Charge] memtenn:
Sim card after CWM RESTORE

A noob problem. I rebooted my phone out the bootloop but now my sim card doesn't work any suggestions? Should I just go get another one. I did use odin but I only had the partition box checked. Thanks in advance...
[Verizon Droid Charge] papi92:
Pull your sim out. Reboot. Then turn phone off put sim in. Anytime you factory reset or odin I suggest you don't have the sim card in
[Verizon Droid Charge] memtenn:
I reset it without the sim twice and it still wont read the sim. I will go to Verizon today and get another one.
[Verizon Droid Charge] stranula:
Verizon will replace the sim card for free, they don't seem to have them bug free yet. When I had to replace my Droid Charge, I activated my old phone (ENV Touch) and this deactivated the sim card, so when I got my replacement Droid Charge it wouldn't activate. Took it to Verizon store, and the guy messed up 2 sim cards trying to get my phone activated again.
[Verizon Droid Charge] juttschallenger:
I ran CWM trying to restore to a backup and ended up bricking the phone. Now I can't get out of the stock restore screen.

Been tying to run many different roms and nothing is working. I have followed the steps to a T. Is there something else that I can do here?

Another thing, I have wiped cashe and data and has a blank sd card it in. Don't know if that matters.

Could really use some help here.
[Verizon Droid Charge] juttschallenger:
Well now the phone will boot to the droid eye and it boot loops. Battery pulls do not work. How do I get it to boot the whole way? So close yet so far away.
[Verizon Droid Charge] trebores1:
Jutts - this sounds similar to what was happening to me. Maybe try what i posted a page back. It only worked when i flashed everything exactly in the order i posted.
[Verizon Droid Charge] juttschallenger:
Looked over your post and followed the steps perfect. Still stuck on boot loop. One thing that comes up after I run the PIT and Almost file, the phone boots into CWM after you put the battery in. I then reboot from there and back to the same ol Driod eye. Did you have the sim and sd card in during?
[Verizon Droid Charge] trebores1:
Sorry that didn't work. I had both the sim and sd card in when i fixed it.
[Verizon Droid Charge] juttschallenger:
I even tried to install a rom from CWM but still stuck on eye. Iv'e tried every ed rom out there. Seems like nothing works.