Hello all,
like many users i've forced the mango update on my Omnia 7.I ended up with firmware version 2424.11.8.2.
However, i read that most of the users that got the update the "normal" way got firmware version 2424.11.8.5, so i rolled back to NoDo and updated again - still i get 2424.11.8.2.
So my question is - is my firmware ( 11.2 ) mango, or do i need to update my phone manually somehow?
Anyone knows what's the difference between 2424.11.8.5 and 2424.11.8.2 ?
My samsung now app doesnt auto-refresh also..could this be related to the firmware ver?
When you say "forced" the update, what do you mean?
Also, when you rolled back and then re-installed, did you need to do anything special to re-install?
Bocko92 said:
Hello all,
like many users i've forced the mango update on my Omnia 7.I ended up with firmware version 2424.11.8.2.
However, i read that most of the users that got the update the "normal" way got firmware version 2424.11.8.5, so i rolled back to NoDo and updated again - still i get 2424.11.8.2.
So my question is - is my firmware ( 11.2 ) mango, or do i need to update my phone manually somehow?
Anyone knows what's the difference between 2424.11.8.5 and 2424.11.8.2 ?
My samsung now app doesnt auto-refresh also..could this be related to the firmware ver?
Click to expand...
Click to collapse
2424.11.8.5 is the Mango update with Samsung drivers and 2424.11.8.2 without.
If you wanna enable Internet Sharing feature you need firmware 2424.11.8.5, this you can also do manually with Cab sender... just search here in the forum.
I flashed back to a branded T-Mobile rom for getting firmware 2424.11.9.4, with my unbranded Samsung rom I couldn´t update the firmware.
GoodDayToDie said:
When you say "forced" the update, what do you mean?
Also, when you rolled back and then re-installed, did you need to do anything special to re-install?
Click to expand...
Click to collapse
I mean i used the cable trick (google it) to get the update b4 it was available for my phone through zune.
After i rolled back i installed in the normal way - didnt use tricks, zune said there's an update, so i updated.I guess this is the official update for my phone.But i dont get it, why it comes without samsung drivers..
Unbranded phone
As I understand it if you have an unbranded Omnia 7 then you will only have 11.8.5 and that does not give you tethering. For me to get tethering I need the firmware update that only seems to come from the carriers themselves which leaves me in the lurch.
I do not want to faff about with unlocking them especially as I have 3 unbranded phones I guess I will just have to wait and see what Microsoft push out to us plebs. You can of course install the firmware if you phone is unlocked and you will find plenty of instructions on how to do this.
Hello Xda! I hope you've all had a wonderful christmas eve and an even better new year! I've joined this site after headhunting and reading numerous posts touching different topics regarding one subject and one subject alone: Samsung Galaxy S2.
Now, on to the issue at hand. After tweaking and modifying my firmware, in hopes of getting Cyanogen 7 to run along with the ICS theme for it and having failed, my Sg2 has never been the same, of one simple reason: I haven't found the exact stock firmware that fits my phone. When I write "fits my phone" I actually don't refer to the fact that they aren't working as they indeed are, but no-one that's up to date.
The problem could've been easily fixed if Samsung Kies actually worked with my Windows 7 64-bit, which it doesn't, and please, don't point me in the direction of other posts such as "untick debugging mode", "reinstall Kies", "install those drivers by searching 'this' and 'that' on Google", because trust me, I've tried everything. It worked for a couple of days, but now as I really need it, and want to get out of the hellhole I call "KE2", it doesn't seem to want to help me, at all. "This device is not supported by Kies".
Now, I've visited another thread here on xda, more or less this one: http://forum.xda-developers.com/showthread.php?t=1075278 and dabbled myself through numerous versions until I finally settled for XWKE2 - Generic NEE and successfully managed it to run on my phone with Odin.
Since my phone is operator locked and I'm paying for it monthly via a Swedish operator known as Telenor I'm not able to update the firmware via About phone -> Software update either.
As I said, Kies isn't able to update my phone to 2.3.5/ KE7 (or whatever version is the newest) and I'm thusly stuck with XWKE2 & 2.33.
The most major problem I have is that I don't know which firmware to download from the topic I provided above, and I'd really like to know which one to actually download in order to have the most up-to-date version.
I'd immensely appreciate any help!
Model number
GT-I9100
Android Version
2.3.3
Baseband version
I9100XXKDJ
Kernel Version
2.6.35.7-I9100XWKE2-CL187606 [email protected] #2
Build Number
GINGERBREAD.XWKE2
Turned on my tab this morning before work and after a few minutes a pop up displayed a message indicating a firmware update was available. Didn't do anything 'cause I'm rooted and customized and wasn't sure CWM would remain to get me back to where I was. Looked here expecting to see everyone talking about it and disecting it and am suprised to see nothing. Maybe this is old news and I missed it? I keep this site up on a browser tab 100% but it is still possible. I searched and went back a few and didn't see anything. Anyone else getting this?
i saw the update late last night, and tried to do it, but it kept giving errors when i tried to install it both from kies and ota. My firmware wasnt listed in the stock firmware list so i used odin to put in stock firmware, amd now the update isnt showing.
The update was 150mb and said something about updating the market.
Heres hoping i didnt delay ics for myself
On my end both kies and the built in updater are telling me there is no update so maybe something strange happened on their end? Or maybe they are getting ready to release it
150MB? doesnt sound like ICS. I would expect it to weigh in over 400MB. Hopefully Im wrong. Maybe its some "prep" update to fix someting for the coming ICS.
What build number are you on? The latest for the P6210 is LA3. Since you can't update with a custom recovery in place you may be behind a version or two and thats why Kies is telling you an update is available. To get any update, including ICS, you will have to put the stock recovery back, this is all covered in Gary's post for rooting and installing CWM Recovery. No device I know of will accept a carriers or manufacturers update with a custom recovery in place.
My GT-P6210 is stock, and neither Kies nor the device shows a firmware update. Kies says current firmware is PDA:LA3/CSC:LA3 (XAR).
I'm not sure what firmware I was last night. I did a search for the firmware version it said I had, but I was only able to find one or two references to it.
I am currently on LA3 and not seeing any updates available.
Yeah, I feel like an idiot. I upgraded to LA3, couldn't use Gary's kernel (and I had to have it for my project) so I downgraded with my nandroid. I used Kies to get the upgrade, was not prompted, and forgot about it. So...sorry, fellas! False alarm. Feel free to ignore my future outbursts.
The P6210 I purchased earlier this week came with LB2. Is this newer or older than LA3?
LA3 is the third firmware build in Jan 2012. LB2 would be the second build in Feb of 2012 (so LB2 would be newer.)
Gary
garyd9 said:
LA3 is the third firmware build in Jan 2012. LB2 would be the second build in Feb of 2012 (so LB2 would be newer.)
Gary
Click to expand...
Click to collapse
I supposed it is not possible to extract the ROM file out of the tablet, as I didn't get any response here.
Could LB2 be for Canada only (since ikeny's P6210 was bought there)? Would that explain why U.S. customers aren't seeing it as an available update?
Sun_Cat said:
Could LB2 be for Canada only (since ikeny's P6210 was bought there)? Would that explain why U.S. customers aren't seeing it as an available update?
Click to expand...
Click to collapse
Could be. But interestingly, there is no "English (Canada)" or "French (Canada)" in the language selection. Hopefully it's not any hardware differences.
[Update] In the other thread about the IR port, it's been pointed out that the Canadian version does not include the IR port. I don't get Samsung, it's like they think the fragmentation problem is not bad enough (GTab 7, 7.7, 8.9, 10.1, 7.0+... ), they want to introduce more different variants (P6200, P6210; now P6210 with IR and without IR). No wonder why it is taking so long to release ICS for all these devices !!!
garyd9 said:
LA3 is the third firmware build in Jan 2012. LB2 would be the second build in Feb of 2012 (so LB2 would be newer.)
Gary
Click to expand...
Click to collapse
Kies wont' display my firmware version, which is annoying. Can I find out from the device itself? Navigating to About Device shows no "firmware" but mentions "Kernel Version: 2.6.36-P6210UEKJC-CL567728 [email protected] #3" with "Build Number: HTJ85B.UEKJC P6210UEKJC". What the <bleep> does *that* mean??
bittersound said:
"Build Number: HTJ85B.UEKJC P6210UEKJC". What the <bleep> does *that* mean??
Click to expand...
Click to collapse
KJC:
K == 2011 (K is 2011, L is 2012, M will likely be 2013)
J == October (10th letter of the alphabet, 10th month of the year..)
C == 12th revision (1,2,3,...8,9,A,B,C,D)
hmmm, not as recent as LB2 then
I guess I could always take it to an authorised service centre for an official firmware upgrade...
A couple of quick questions:
1). My GT7+ build number is P6210UELA1 and it's rooted with Gary's method. Will the firmware update remove the root?
2). What does this firmware fixed? The only problem I have are:
- Lag after using the device for certain time (moving screen, etc.)
- Apps that are tablet-optimized is not shown as such (Mint, TripAdvisor) and shown in "phone" mode.
1. AFAIK, none of garyd's root options are compatible with standard firmware updates. Someone please correct me if I'm wrong.
In order to upgrade your firmware, you'd need to restore your tablet to stock first and then upgrade to the latest firmware.
2. AFAIK, the issues you are experiencing will not be remedied by updating the firmware.
Thanks for the information. Do you know if I can re-root once I downloaded the latest firmware? I.e. download latest firmware, lose root, with new firmware re-root.
k_t_b said:
1. AFAIK, none of garyd's root options are compatible with standard firmware updates. Someone please correct me if I'm wrong.
In order to upgrade your firmware, you'd need to restore your tablet to stock first and then upgrade to the latest firmware.
2. AFAIK, the issues you are experiencing will not be remedied by updating the firmware.
Click to expand...
Click to collapse
Yes.
Before I recently switched to an older firmware (so that I could use garyd's custom kernel), I had updated to the latest LA3 and rooted using p6210_CWMR_20120107.zip from [GT-P6210][CWMRecovery][ROOT] ClockworkMod Recovery and Root (07-Jan-2012). My tablet was running fine.
OK, after having waited and waited (and then waited some more) for an official update to my GT-6800, it's still running Honeycomb and all attempts to upgrade either directly from Tab or via Kies result in either "no update available" or ""Your device's current firmware version is not supported to update firmware via Kies" - it's time to risk the brick bug and do a manual upgrade.
This raises a few questions:
- What's the best method to update - 'Mobile ODIN' or is there a better way?
- Should I go to ICS 4.0.4 first and then update to 4.1.2 or can I go direct?
- My Tab has been confirmed as vulnerable to the brick bug - what measures can I take to minimise risk?
- And why the hell have I not got an official OTA or Kies update after a year of it being available? My tab reports firmware of:
PDA:LA2 / PHONE:LA1 / CSC:LA2 (XSG)
.. do I have some sort of weird development version that isn't supported for official upgrade or something? AFAIK the Tab was untouched before I got it and unrooted (it was advertised as 'brand new' and certainly seemed so when I unboxed it so I doubt someone has been on there and rooted it, plus I did a root check and it ain't showing as rooted). It was bought via eBay from a UK supplier but is definitely a grey import as it came with a two-prong European type power adaptor and not the 3-pin UK plug.
Kaiser Wilhelm II said:
OK, after having waited and waited (and then waited some more) for an official update to my GT-6800, it's still running Honeycomb and all attempts to upgrade either directly from Tab or via Kies result in either "no update available" or ""Your device's current firmware version is not supported to update firmware via Kies" - it's time to risk the brick bug and do a manual upgrade.
This raises a few questions:
- What's the best method to update - 'Mobile ODIN' or is there a better way?
- Should I go to ICS 4.0.4 first and then update to 4.1.2 or can I go direct?
- My Tab has been confirmed as vulnerable to the brick bug - what measures can I take to minimise risk?
- And why the hell have I not got an official OTA or Kies update after a year of it being available? My tab reports firmware of:
PDA:LA2 / PHONE:LA1 / CSC:LA2 (XSG)
.. do I have some sort of weird development version that isn't supported for official upgrade or something? AFAIK the Tab was untouched before I got it and unrooted (it was advertised as 'brand new' and certainly seemed so when I unboxed it so I doubt someone has been on there and rooted it, plus I did a root check and it ain't showing as rooted). It was bought via eBay from a UK supplier but is definitely a grey import as it came with a two-prong European type power adaptor and not the 3-pin UK plug.
Click to expand...
Click to collapse
First... KIES and the OTA upgrade system both suck. However, it's not their fault in this case: your XSG tab has the latest firmware available for that country code (XSG means your tab is from the UAE).
But save yourself from the trouble anyway. You're under HC, so the brickbug-trigger isn't set on your kernel. This means you can consider yourself safe. AFAIK JB is also brickbug-safe, so going straight from HC to JB is probably your best bet. If you do it like that, your tab will never be running under a kernel that does the secure erase that triggers the bug.
If you're not rooted and you don't intent to, just use Odin (PC Odin, not the Mobile Odin). That will factory reset your tablet, which is probably the best for stability.
Ok. I got an AT&T Galaxy Note 8 back in early-mid 2018. The first thing that happened when I booted it up and connected to a wifi hotspot was that it downloaded the latest update.
That was the last update I received.
I am trying to install Android P onto my device through Odin (Using 3.13.1B PatcheD). I tried OTA first, but when checking for updates, it says that my phone is up to date. I am currently on build U4CRD7.
I called AT&T and they told me that I have to contact Samsung to download the update, and also that it could be a hardware issue (?) and to possibly send it in to Asurion. After that, I called Samsung, and they told me I had to take it to the closest Best Buy. Now, I don't have a way to travel the ~30 miles to the closest one. So, I decided to try Odin. (I have used Odin before, so I am somewhat familiar with it)
I downloaded firmware version U7DTC1_USC from a post here on the forums. I placed all files in the correct areas, went to download mode, tried flashing, and failed. I've gotten three different fails. I changed cables and ports and failed. I tried downloading firmware version U7DSK3 and flashing that one, thinking I might have skipped too many updates (if that is a thing... I've read conflicting information). Failed.
The last failure was a "Complete(Write) operation failed"
Besides taking an expensive rideshare to the nearest Best Buy, is there something that I am missing in trying to update this phone? Could it be a hardware issue? Have I missed too many updates? Do I need to progressively update my phone? (I don't need answers to all these questions, just the most relevant answer please)
If I have posted this in the wrong area, I am sorry. This is my first post on XDA, and I usually don't post in forums anywhere, I just lurk and look for answers to my questions. I haven't been able to find a matching problem.
Edit:
More digging and I found this in another thread.
MrMike2182 said:
...You need to manually update it yourself to the next update version which I think is ... using Odin and then it'll be able to do it on it's own.
Click to expand...
Click to collapse
In further replies, he suggests updating to the firmware version that I am currently at. What is an "update version?" Do I need to just go one firmware update up? Do I need to go one BL version up?
Phone successfully updated
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
G-Man Cometh said:
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
Click to expand...
Click to collapse
Your problem was simply because you were trying to use the patched version of Odin and should have just used the newest updated version of Odin. There's no reason to use the patched Odin to flash the normal firmware. People use the patched Odin when they're flashing modified firmware.
Edit: By the way, if it's an AT&T device and you're using say a T-Mobile or Verizon sim card it will not update unless you put an AT&T sim card back in it. It's apparently picky like that. For instance let's say it had AT&T firmware on it and you have a Verizon(or other) sim card in it, the phone is expecting to find and download the AT&T firmware for updates the problem is that Verizon(and others) do not carry AT&Ts firmware they only have their own versions of firmware that's the reason some people don't get updates.