Sprint's Samsung Epic 4g Official Froyo EB13

How did your update to EB13 go?


  • Total voters
    0
Status
Not open for further replies.
I updated with the update.zip method to the SD card. The update worked flawlessly, but after install I kept getting Android Force close issues. They would happen continuously. I have a stock, unrooted Epic.

I was able to download a SMS backup tool and I went ahead and did a factory data reset via the phone. Reninstalled all my apps and all is good now.
 
So there is no way around it. I guess I will just have to get used to it. That sucks. Wish we had more permissions in changing some features in the firmware.
 
The problems I've noted so far include auto rotation not working properly and my WeatherBug Elite wall paper not scrolling properly.
Get Terminal Emulator from the Market and once you open it, type this stuff exactly as written:

Type: su then hit enterand allow the app root
Then type: /system/bin/sensorcalibutil_yamaha and hit enter then just folow directions. Exit app turn off screen, turn it back on and then it should fix the lag
 
Get Terminal Emulator from the Market and once you open it, type this stuff exactly as written:

Type: su then hit enterand allow the app root
Then type: /system/bin/sensorcalibutil_yamaha and hit enter then just folow directions. Exit app turn off screen, turn it back on and then it should fix the lag

Terminal Emulator does require root access
 
p.s. use the old one click root method for dk28 i tried the one for eb13 that includes cwm3xxx & bricked the hell out of my phone twice
It's all about comfort level and understanding. It's not something that everyone will have a problem with. If you don't use the EB13 CWM3xx one click root method, then you are limited to RFS .
So to anyone out there who read this comment about only using the 2.5.5 root method, this WILL NOT brick your phone if you do it correctly. Just make sure you understand the procedure before you start. Run through the steps in your head. You WILL be fine. EXT4 is such a difference, I can't even tell you. To have waited for this update for so long, and then stay at RFS would be really...dissapointing..to put it lightly :)
 
Problems after updating

Has anyone else noticed these things?

-The market went back to the old version. Its not all shiny and new with the new layout (that cover flow look to it)

-The camera absolutely blows now. It seems like the HD 720p video recording went way downhill. I don't know if its a frame rate cap or what but its bad.


Anything else that others are experiencing? I haven't found anything about these two issues in the forums as of yet so I'm not sure if I'm alone.

BTW I did the manual update.
 
That could be my problem too. I tried to apply the update to my rooted DI18 but it failed. It's one click rooted with CW2.5.1.0 installed. I got the recovery mode when I did the three finger salute. Then when I apply the update.zip it fails, apparently stalling on ASPHALT5_DEMO according to some of the error text. It said there's a problem with the zip file, but I checked it and it's all there. Is there any hope to get it off eclair DI18?
 
Last edited:
So I downloaded the zip file directly to my sd card. Rebooted with volume down, camera and power button. Tried to run the zip and it says it isn't signed. I erased the file from my sd card and retried it 5 times. Same result every time. Any help?
 
once I rebooted the phone once after the update the market returned to the newer version.


i noticed the same choppy camera but haven't recorded anything yet. just looked through the viewfinder while moving around.
 
how do you reboot? If I knew that I would download the update myself.

reboot? turn the phone off, turn it back on. And updating manually isnt hard at all. Download the update.zip file (same one u will get in the OTA) from Samsung website and move it to the SD Card. The process took me 5 minutes and ive never done a manual update. Trust me, im skeptical of anything that isn't OTA. Everything works perfect!
 
Camera and multimedia force closing

I used the update.zip from the samsung website. Everything installed OK but now my camera and music player instantly force close. Was running stock Android (never rooted). Whenever I activate the camera or the music player the vibrates and force closes the application. Everything else seems to be working well so far.

I downloaded the update.zip file to my PC and copied it to the root directory (no folder) of the sdcard. Did the upgrade without any issue, all apps, contacts pictures, etc. were OK.

Please advise if you got this problem and found a way around it. I already backed up all my contacts, messages, pictures and videos. I don't mind having to restore them manually. My only concern is that the phone itself would stop working (network settings, phone number, etc.). Should I just leave it as it is and wait for the OTA update? Go back to 2.1 DI18 (If so, how?)?
 
Yeah, after going to the market once after the update, it downloaded a new market behind the scenes automatically. I wouldn't have noticed, except that Lookout told me it was scanned Market.

I didn't see the change until I rebooted my phone either.
 
From what I've read the OTA is the exact same file as the one you and I tried, so waiting for it won't help. I guess we're stuck until someone can figure this out. At least yours installed.
 
I used the update.zip from the samsung website. Everything installed OK but now my camera and music player instantly force close. Was running stock Android (never rooted). Whenever I activate the camera or the music player the vibrates and force closes the application. Everything else seems to be working well so far.

I downloaded the update.zip file to my PC and copied it to the root directory (no folder) of the sdcard. Did the upgrade without any issue, all apps, contacts pictures, etc. were OK.

Please advise if you got this problem and found a way around it. I already backed up all my contacts, messages, pictures and videos. I don't mind having to restore them manually. My only concern is that the phone itself would stop working (network settings, phone number, etc.). Should I just leave it as it is and wait for the OTA update? Go back to 2.1 DI18 (If so, how?)?

Take out your sd card and put it into your computer.
Copy complete contents to your computer.
Format sd card.
Copy all your files back to sd card.
remount sd card into phone.

This has worked for many.
 
  • Like
Reactions: cartman#AC
I just upgraded and one thing I have not been able to get to work is Bluetooth with the Voice Mail application. I thought Froyo would fix this, so that when I'm driving with my bluetooth headset, I can listen to my messages through the headset. Had anyone else tried this gotten it to work? Maybe it's an issue with my headset?
 
It's all about comfort level and understanding. It's not something that everyone will have a problem with. If you don't use the EB13 CWM3xx one click root method, then you are limited to RFS .
So to anyone out there who read this comment about only using the 2.5.5 root method, this WILL NOT brick your phone if you do it correctly. Just make sure you understand the procedure before you start. Run through the steps in your head. You WILL be fine. EXT4 is such a difference, I can't even tell you. To have waited for this update for so long, and then stay at RFS would be really...dissapointing..to put it lightly :)

whats the right way to do the ext4 so it dont brick cuz it bricked me twice
 
My only issue is just a carry over from when I installed the old "unoficial" update. My camera now has black bars on the sides and doesn't fill up the whole screen. So, no matter what settings I change, my pictures are quite smaller than before.

I uninstalled and went back to stock and waited for this release, hoping it would fix my issues. It, however, has not.
 
I want to know if im the only one with this problem.

My epic works perfect the only thing i haven't found a solution is that my Gallery is super slow in Froyo, (it works perfect on 2.1) it seems I'm the only one with this problem. I had hope the Official Froyo will fix this but it didn't. Can someone please help me with this?
 
Status
Not open for further replies.

Forum statistics

Threads
957,497
Messages
6,973,327
Members
3,163,834
Latest member
Vresbudsbenz