[HOW-TO]Fix your phone

Search This thread

lowery23

Senior Member
Apr 20, 2009
94
17
Thanks for the info. I had to get the pit and ED2 downloads from another location but after doing that I followed your instructions and my friend's Charge now boots again. Previously it just sat on the Samsung screen.
 

spc_hicks09

Inactive Recognized Contributor
Jan 23, 2011
3,899
1,858
Marion, OH
www.facebook.com
Anyone have links for the files to restore the Droid Charge to the latest OTA? Trying to fix my wifes phone which has been on Gummy for almost 4 years. Any help is greatly appreciated!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 43
    Initially, this post was meant to fix people's phones after a bad restore from CWM, but now I'm changing it to be more general and pretty much be a guide for how to fix your phone from nearly any problem. The original reason for this post is this error:
    Code:
    -- bootmode=7 from cmdline...
    -- Movi_check Start..!!
    checksum confirmation need_checksum[0]
    Not need checksum confirmation
    
    --Movi_check already executed!!...
    
    --movi_checking done!...
    # MANUAL MODE #
    It was caused by a problem with /data and this guide helped fix that. Now that several other things have come along (leaks, voodoo, etc.) people are having a host of random errors show up with their phones. This guide will hopefully get you back to a working phone regardless of what is wrong with it. Take note though, that following this guide will delete all data not on the sdcard. So, with that being said, here is how you can fix your phone.

    1. Download one of the packages below as well as the PIT file.
    2. Open up Odin, click PDA, and select the package you downloaded
    3. Click on PIT and select the PIT file that you downloaded.
    4. Get your phone into Download mode.
    4a. Pull out the battery, hold down on Vol Down, and plug in the USB Cable while still holding the button.
    4b. After you are in Download Mode, put the battery back into your phone. This increases the reliability of flashing with Odin
    5. Make sure your phone is recognized in Odin
    6. Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
    7. Press "Start" and flash the package.
    8. After it is finished flashing, take the battery out, unplug the USB cable, put the battery back in, and start up what should now be a working phone.

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

    All packages are available here.
    3
    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.
    2
    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?

    Sent from my SCH-I510 using XDA App

    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.
    1
    Updated this with what I believe to be the proper steps. I was in and out at work while papi was fixing his phone, and lost track of the exact files used, but some combination of the above Odin packages and the PIT should get you back to a working phone if you are having a problem.