Ashley & Reefboy,
Any chance you bought your phones on eBay and you received a phone that was rooted and because of that the update will not install. I ask because from what you say it sounds as if your phone is refusing to install GB 2.3.6?
Go to settings>about phone and go to bottom of the page. Do your settings EXACTLY match the photo? The photo shows the STOCK EE4 Froyo 2.2.1 settings. If thet don't match that may be why the install is failing.
BTW, do NOT reformat the SD card.
JerryF
I bought mine new from Costco and it does match your attached image exactly.
Don't format SD card? ooops... I formated sd card, wiped cache, and basically any thing I thought may give me a chance. All for not. Still no success. I called verizon and I should be talking with Samsung tomorrow. Tech support said I did everything they would have had me try. If Samsung can't help then I believe they will be giving me a new phone.
12/4/2011
Reefboy & Ashley too,,
I still have a feeling that it is the file you downloaded that is causing your problem. Read this again and double check that the original name of the file you downloaded was update_EE4B_to_EP4D.zip and that you renamed it to update.zip. Also, after you drag it to your root directory in your phone check there to see that it does NOT say: update.zip.zip.
Some folks have ended up with the .zip in there twice. The safest way to rename this file is to delete the _EE4B_to_EP4D part leaving behind ONLY the update.zip. The give it one more try.
JerryF
__________________________
This is for the Samsung Charge phone from Verizon. My battery was charged to 98%. I did NOT have the phone plugged into the charger. To do this your Samsung Charge phone you MUST be running STOCK on Fro yo 2.2.1 EE4. This update does NOT root your phone.
I went to the URL shown below and downloaded the Gingerbread update file named update_EE4B_to_EP4D.zip to my PC. The file size was 117,613 KB in my PC but after it was copied into the root folder of my Samsung Charge phone the file size was 114.9 MB.
http://forum.xda-developers.com/showthread.php?t=1364298
After you go to this URL you want to choose the FIRST URL that ends in HAG3RFTBY6 and download that file to your PC. It is named "update_EE4B_to_EP4D.zip"
Next, while it was still in your PC, change the name of the file to: update.zip
Then using the USB cable copy the file update.zip from your PC to your Charge phone's SD Card root file. Do not copy it into a another folder. That's where all my Music, Photos, Videos and so forth are stored. After you copy it there you should go to the APP My Files to confirm that update.zip is there in the root folder on your SD card. The file size is now 114.9 MB.
Next I pressed three buttons at the same time (this was tricky and a bit difficult). I probably tried 8-10 times before it worked. What it was doing is turning off the phone but I kept trying. The three buttons are: Volume Up Button, Home Button, and the Power Button. One user gave me the suggestion to Hold Volume Up + Hold Home + Hold Power until you see the Samsung logo, then release the Power button. Finally release the other two buttons (Volume Up + Home) several seconds later.
In my case the screen that came up was a RECOVERY screen. It said recovery at the top. You will see a choice of about five things you can do. On that list of choices I touched UPDATE.ZIP and then I pressed the HOME Button at the bottom of the phone. The update started and the screen that came up had an picture of an open box with an arrow coming out going down toward a Droid. Now we know there really is a little Droid doing the update work! There also was a BAR showing the progress which was slow at times.
It took all of 15+ minutes and then the phone rebooted itself and finally just turned off. The little Droid was probably exhausted by then! I waited a couple more minutes after the screen went blank (black) and then pressed the power button. The phone started and it's working very well on Gingerbread 2.3.6. You might be advised to reboot the phone again for a second time.
I am having the same problems, I have that exact screen above and for some reason the over the air gingerbread update wont work for me, I think I am going to go see what they can do at the verizon store.
There was bound to be some issues that were going to crop up during this update. Not all phones are setup the same, sometimes it can be the combination of apps you have on the phone that could cause an update to fail.
I do have instructions on how to take the phone back to stock EE4 which would of course get the phone back to a pristine stock factory state which you could then re-run the update on which at that point the update should complete successfully.
But, I do warn people... these instructions aren't for the faint of heart or people who are scared of bricking their phones. I'm giving these instructions in hopes that it will help someone be able to fix their phones on their own without having to resort to taking it to a Verizon Store.
JerrF,
That is exactly what I did the first time. just renamed the first part and did nothing with the zip. I also verified the name of the file. All subsequent attempts have been with OTA. Are you saying that you think my first attempt is what is keeping the OTA from working correctly?
What is surprising me though is that I've formatted and wiped every option in the recovery screen. Would think that would have wiped away anything if the first manual attempt was the cause.
I appreciate your coninued input and suggestions!
JerryF,
I tried again and wrote down the error log. As I stated earlier I bought this new and watched them update to the last update OTA after starting it the first time. I've never rooted it or done anything that I imaginge would of / could of caused a problem.
Install from sdcard…
Finding update package….
Opening update package…
Verifying update package…
Installing update…
Verifying current system…
Updating modem…
Assert failed: stealth_update_cdma_bp(“/tmpt/modem_delta.bin”,”modem_delta.bin”)
E:error in /mnt/sdcard/update.zip
(status 7)
Installation aborted
Does this give anyone enough of a clue as to what is going on and if it can be overcome?
I tried taking out my SIM card SD card and Battery again but again no luck after the update installed still 2.2 so I'm going to try to do a factory reset and clearing the cache and hopefuly that will work
AshleyBabby,
From what I've done (exactly what you are hoping to do) I wouldn't get your hopes up. I have been unsuccessful. Verizon is supposed to conference call me this afternoon with Samsung to see if they can push something out other wise the service support lady sounded as though they may have to exchange phones.
Reefboy
It might be that your first manual update attempt could be holding back the OTA if you still have the file UPDATE.ZIP in your root folder on the phone. Go look and check to see if it's still there and at the same time look to see that it only has one .zip extents and not two. Delete it from your root directory.
You said, "just renamed the first part and did nothing with the zip" The wording of this statement makes me believe that you did NOT rename the file properly. Right now at this moment I think that is the problem. In the previous post to you in this thread I suggested how to rename the file. Try that! Update.zip in my phones root folder was 114.9MB. It had only one .zip and it did not have a yellow folder symbol next to it. It had two overlapping white sheets of paper as its symbol because it in a file, not a folder. SEE the atached photo.
Can you be a bit more specific such as: is the file in your phone named only UPDATE.ZIP nothing more & nothing less and there are not two .zips or not two dots before the zip..
I think you should redo the manual update.
JerryF
Start a new topic or ask questions in the open forum.
