I am wondering if the coming 2.3.6 OTA update for the Sprint E4GT will screw with a returned-to-stock nonrooted phone but has the EG31 modem update installed.
I saw that the EK02 update in the developer forum cannot be loaded on a phone with EG31, hence, my concern.
Temporary problem, possibly, permanent problem, highly unlikely.
A full update will leak eventually or they could simply ship a full modem.bin in the OTA.
It won't be a permanent problem considering Sprint corporate repair centers are using EG30 Rev5 (EG31) to flash phones that have firmware issues. I believe there will be a version of EK02 pushed to devices sporting both EG30 and EG30 Rev5 that will unite the firmware versions. That way future updates will be universal.
Well thanks both of you for easing my tormented mind. Now I just have to summon my patient s.
crzchn said:
Well thanks both of you for easing my tormented mind. Now I just have to summon my patient s.
Click to expand...
Click to collapse
Thanks button dude.
Related
I see that we've managed to get our hands on a copy of the EG30 Modem, Huzzah! See: http://forum.xda-developers.com/showthread.php?t=1381632
That's all well and good, but has anyone gotten the OTA update notification after flashing back? I used Odin to head back, hoping to get the official OTA. (I had previously unrooted and flashed the .tar file to go back to stock with the EG31 modem.
Looking on Sprint's site for the update (Here) I noticed that my baseband version is: S: D710.0.10S.EG30
And the Sprint website lists the official build as being: S: D710.0.5S.EG30.
Does this mean I'm still SOL on an OTA? (I don't seem to get the notification and a manual check doesn't pull anything up for me)
Or can I flash the update from recovery now that I'm on a version of EG30?
Thanks!
Sprint website has a typo. The version you have is what it should be.
They pick the MEIDs to get the update in a pseudo-random fashion.
Oh ok. Good to know. I'll just be more patient then. Thanks.
Can you provide any more insight into the selection process?
Can someone give a laymen definition of what is what?
I think some are kernels, some are modems, and some are updates, but I can't find anywhere describing what is what...
What is the following:
EG30
EG31
EG12
EK02
Maybe just a little history of what is what would help some of the newbies coming online.
Bielinsk said:
Can someone give a laymen definition of what is what?
I think some are kernels, some are modems, and some are updates, but I can't find anywhere describing what is what...
What is the following:
EG30
EG31
EG12
EK02
Maybe just a little history of what is what would help some of the newbies coming online.
Click to expand...
Click to collapse
EG30, EG31, and EK02 are all software versions for your phone.
The 1st letter is the year (E=11, F=12, ...)
The 2nd letter is the month of build (A=Jan, ..., G=Jul, ..., K=Nov, L=Dec)
The last 2 #s are the day of month.
The most important parts of these software releases are:
1) modem/radio
2) Kernel
3) ROM
Sprint/Samsung will usually include new versions of all three for each release.
While in theory you could experience incompatibilities mixing and matching different versions of the 3 parts, in practice, so far, it hasn't been an issue. This statement is regarding the stock versions. Sometimes custom kernels can make changes that make mix and matching not work.
EG12 - this is what is stored on the modem partition of the shipped EG30 phone, that partition is UNUSED. Often it is confused for EG30 because when people first pulled the modem from the modem partition, this is what showed up. Later on people realized that was a dormant partition that doesn't reflect the running modem.
EG30 - this is the software version that shipped with the phone Modem/Kernel/ROM. For the longest time we had no true "factory restore" for EG30. We had pulled the EG30 Kernel/ROM from the phone so you could restore to those, but we couldn't pull the EG30 modem (thus you couldn't restore to the EG30 modem). Right around the time of the EK02 release Przekret graciously leaked an EG30 ODIN tar update that include the EG30 Modem/Kernel/ROM.
EG31 - for the longest time we didn't have any way to do a true factory restore. sqush 7 graciously leaked a factory restore that Samsung sent to the maintenance machines at Sprint. At first we thought this was EG30, but after looking at the files we realized there were slight differences. It include the EG31 modem/baseband. It included the EG30-Rev5 Kernel and ROM, which to reduce confusion, we've been referring to as EG31 Kernel and ROM.
EK02 - this is the recently released first official Sprint OTA update for the E4GT. This is the same as the "leaked" EK02 that kingsway8605 obtained a week earlier from Sprint. It has only been released as an OTA patch update. That means it doesn't include the full Modem/Kernel/ROM. It only includes the "differences" from the EG30 release. It is meant to be applied on top of an stock EG30 installation. That is why you must be on truly stock EG30 to apply the EK02 update successfully. Some enterprising folks applied the EK02 update on top of EG30, then pulled the results off the phone to create "full" EK02 updates. Those are floating around and don't require you to be on EG30 (they are also much larger downloads) Caveat is the EK02 modem is still a patch release that must be applied on top of EG30. The modem on the phone is essentially write-only right now. The running modem can't be read or we would have a full EK02 modem pulled.
From another pretty new guy....Thanks for the excellent explanation.
Yea, excellent info. I must have changed something in my install that is causing the update to fail.
Only thing I can remember doing is deleting skype and manually updating to the beta.
Bielinsk said:
Yea, excellent info. I must have changed something in my install that is causing the update to fail.
Only thing I can remember doing is deleting skype and manually updating to the beta.
Click to expand...
Click to collapse
Based on what you wrote in the other post, it doesn't sound like it is something you changed. It is unlikely you would have modified that file and that is the first file being checked by the updater, so the install virtually didn't start at all.
More likely it is something else, possibly running in CWM?
sfhub said:
Based on what you wrote in the other post, it doesn't sound like it is something you changed. It is unlikely you would have modified that file and that is the first file being checked by the updater, so the install virtually didn't start at all.
More likely it is something else, possibly running in CWM?
Click to expand...
Click to collapse
replying in other thread.
So I recently found out I'm unable to install OTA Android updates to my phone if it's rooted.
So what can I do once ICS is released for the GS2? Will there be a download online that I can just flash with ODIN? Or are people going to be forced to unroot if they want the official ICS stock?
Most likely samfirmware aka sammobile will release an odin .tar, so you'll be good to go with odin.
Sent from my SPH-D710 using Tapatalk
saj1jr said:
So I recently found out I'm unable to install OTA Android updates to my phone if it's rooted.
Click to expand...
Click to collapse
That's not true. You will be unable to install OTA patch-style updates if you have modified one of the files being patched. If you rooted with Auto Root and that's all you did, you will be able to install OTA patch-style updates even without unrooting (though the update will disable root)
saj1jr said:
So what can I do once ICS is released for the GS2? Will there be a download online that I can just flash with ODIN? Or are people going to be forced to unroot if they want the official ICS stock?
Click to expand...
Click to collapse
I'm sure there will be an ODIN update within a few days or maybe even the same day. You can also flash EK02 and let the OTA update upgrade you (or if you've just rooted with Auto Root, just let the OTA update run), though you are probably better off waiting for an update from XDA, because the updates from here will attempt to keep your rooting and upgrade options as open as possible.
I'll also probably have an OTA compliance check for the next official update so you can tell immediately which files are not in compliance with what the update expects. I have one for EG30 to EK02 as part of the Auto Root package, so it would be similar in functionality.
First rule: Never take an OTA update if you care about rooting.
Any file made available from sprint or samsung will have a rooted/safe version posted in the dev section within a few hours of release.
I know samsung is pretty nice to us rooters but you never know when that might change.
lafester said:
First rule: Never take an OTA update if you care about rooting.
Any file made available from sprint or samsung will have a rooted/safe version posted in the dev section within a few hours of release.
I know samsung is pretty nice to us rooters but you never know when that might change.
Click to expand...
Click to collapse
Is there a way to block OTAs? I'm running Calkulin's 2.8 if that matters.
Relax427 said:
Is there a way to block OTAs? I'm running Calkulin's 2.8 if that matters.
Click to expand...
Click to collapse
There is a thread on blocking them in the wiki, provided here for your ease.
http://forum.xda-developers.com/showthread.php?t=1388778
If you are worried about the OTA messing something up, it'll download and ask to install, but if you've made any changes to your ROM, including installing CWM, then it will fail the integrity check and won't install, so nothing will change.
I don't understand the OP's dilemma. Just wait a couple of hours after the OTA update and get a rooted version of the update... no problem!
It won't be out for a few more months anyways. It isn't even being tested yet. I doubt an initial build is even at Samsung. They are working on the the Galaxy S2 right now(the GSM overseas version). And, I am sure Sprint will sell some other phone with ICS stock before they update ours.
Can you get OTA on AOKP? I switched back to EL29 Gingerbread. But it keeps saying no firmware update is available so I'm just wondering if they would of missed me or something.
I want the update they send out to the phones just incase of anything, such as modems and connection issues.
hrffd said:
Can you get OTA on AOKP? I switched back to EL29 Gingerbread. But it keeps saying no firmware update is available so I'm just wondering if they would of missed me or something.
I want the update they send out to the phones just incase of anything, such as modems and connection issues.
Click to expand...
Click to collapse
Any of the custom ROMs built on FF18 will contain the same thing that OTA had - it has been checked against the leak already.
And no, you cannot pick up OTA on AOKP - stock (rooted/unrooted) only.
If you were still running AOPK, no you wouldn't see it. But since you flashed back to EL29 you will get the OTA. From what I've read the OTA is rolling out in waves. Your region may not have had it rolled out yet.
Why don't you just flash the rooted OTA from the dev section??? Again from what I've read there were no changes made to the OTA from the leaked version of FF18. And word to the wise, if you were to take the OTA you would have to root all over again.
If your having radio or signal issues try flashing a couple different modems till you find one the works for your area.
Sent From My Galaxy10.1 Class Starship....
So has anyone actually received the ICS update over the air or is everyone just getting it from here? Just asking because me & a couple of my friends have been checking like on the hour for the past few days and haven't gotten the update. They have returned their phones to stock and my wife's E4GT has been stock since day one. She doesn't trust rooting anymore after all the problems we had with the original Epic.
Sent from my EVO using Xparent ICS Tapatalk 2
I didnt bother trying. But friend of mine with the same phone got it on launch day by the time i got the chance to even tell him there was going to be an OTA he laughed and sent me the screen shot of the update message.
I reverted to FF18 to update PRL and Profile and pull a couple APK's now that we know the leak was the OTA and it was back to CM9 for me.
Mind you if your looking to be rooted, the only root method is to flash the FF18 tar (one click of course available) which is going to overwrite the firmware data with the same firmware data so unless you want to test unrooted there isn't much point in wasting time with the OTA. Also keep in mind it has not been found in the available kernel code that FF18 is safe to factory reset, etc on. Might be in compiled binaries like the eMMC driver but not worth the risk. Grab TWRP or Agat's kernel or something if your going custom. A rooted cwm zip is now available in addition to the stock ota update.zip thats on googles servers.