Firmware update 11-14-2011 screwed up my Tab

[foxbat121]

For those of you failed update, is your Tab rooted?

Even if you manage to get wi-fi to work, even though your tab says it is running 3.2, some of your system binaries are probably still old because of failed update process. That's also the reason why wi-fi won't connect properly.

Basically same story as the first AT&T Captivate (Galaxy S) update for some owners. Samsung never learns.

 

[ByteMaster0]

Static IP works like a charm, but autorotate of course is AWOL. Two different Samsung reps are confirming the issue, saying "Our engineers are working on it."

Consequently, enabling static IP does get rid of the "Update failed" as it then connects to the servers to verify the new version installed.

 

[ByteMaster0]

For those of you failed update, is your Tab rooted?

Even if you manage to get wi-fi to work, even though your tab says it is running 3.2, some of your system binaries are probably still old because of failed update process. That's also the reason why wi-fi won't connect properly.

Basically same story as the first AT&T Captivate (Galaxy S) update for some owners. Samsung never learns.

Non-rooted. It only got to 53% in the upgrade - which on its own took more than 30 minutes just to reach there.

 

[sreymj]

The upgrade is seamless through Kies. No issues at all.

 

[ratamovic]

Nope it wasn't rooted.
In tablet logs, I can see that it fails to obtain an IP address:

D/ConnectivityService(  287): ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR
D/WifiStateMachine(  287): DHCP request started
D/HierarchicalStateMachine(  287): handleMessage: X
D/WpsStateMachine(  287): InactiveState{ what=39 when=-21ms obj=android.net.wifi.WifiStateMachine$StateChangeResult@40e75980 }
D/WpsStateMachine(  287): InactiveState{ what=39 when=-22ms obj=android.net.wifi.WifiStateMachine$StateChangeResult@41039240 }
W/PowerManagerService(  287): Timer 0x3->0x3|0x1
[B]D/WifiStateMachine(  287): DHCP request failed: Timed out waiting for dhcpcd to start[/B]
D/HierarchicalStateMachine(  287): handleMessage: E msg.what=16
D/HierarchicalStateMachine(  287): processMsg: ConnectingState
D/WifiStateMachine(  287): ConnectingState{ what=16 when=0 }
[B]E/WifiStateMachine(  287): IP configuration failed[/B]
I/wpa_supplicant( 2948): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor(  287): Event [CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 2948): Wireless event: new AP: 00:00:00:00:00:00
I/wpa_supplicant( 2948): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Indeed a static IP seems to work... of course if you have a router! And of course my Live Wallpaper is still gone :'(...

 

[urabob]

For those of you failed update, is your Tab rooted?

Even if you manage to get wi-fi to work, even though your tab says it is running 3.2, some of your system binaries are probably still old because of failed update process. That's also the reason why wi-fi won't connect properly.

Basically same story as the first AT&T Captivate (Galaxy S) update for some owners. Samsung never learns.

No Root and now No Wi-Fi on my 32 gig Tab. I wish I had gone the Kies route like sreymj.

 

[AFPoster]

Samsung Galaxy Tab 10.1 wi-fi edition. Installed with 38% battery life went perfect, booted perfectly and runs smooth. Found Allshare that I've been harping to Samsung to finally release or remove from features offered on their site. Glad to see we got it but Twonky is a better alternative.

 

[ccm435]

The upgrade is seamless through Kies. No issues at all.

Have others had success doing it through Kies? I haven't updated yet, but would like to soon if there was a way that worked for sure.

-cm-

 

[treno]

Glad to know this before I updated 12 at work - would have had some very unhappy council members. Hope it gets resolved soon.

 

[jimmyk0789]

I just changed the saved Wi-Fi info from DHCP to Static. Just press and hold on the saved Wi-Fi info and select "Modify network config".

You'll need to set up the static IP on your router. That process varies from router to router, so you will have to look that up online.

i used my phone to tether to im not sure if wifi tether has static wifi

 

[anon(549921)]

My Tab is saying there is an update but Kies isn't showing it, anyone know how to kick Kies into showing the update?

 

[foxbat121]

I think Samsung has pulled the updates. Neither my tab nor Kies now shows any updates.

 

[cordoni]

these are the photos i promised my girl friend dropped a bowling ball on my phone last night because she said i was flirting with her best friend and now my tablet isn't working :'(

thank good the nexus is coming out soon i hope

You mean ex-girlfriend, right?

Sent from my CM7 Thunderbolt, AOSP.

 

[iamkevski]

for those who applied the update, can you share what your firmware version is now reading? I opened Kies and it downloaded a pretty substantial update, then installed it, and now my firmware is reading as PDA:KME / CSC:KME (XAB) but my tablet doesn't look like anything was applied. Still on 3.1 and looks like the old build info on the tab.

 

[jtnave]

Mine updated fine via USB and Kies. The jitteryness has stopped and so far, it seems more responsive. Saw the same thing when the Transformer got 3.2.

 

[anon(549921)]

Neither my Tab or Kies show an update as being available now

 

[foxbat121]

for those who applied the update, can you share what your firmware version is now reading? I opened Kies and it downloaded a pretty substantial update, then installed it, and now my firmware is reading as PDA:KME / CSC:KME (XAB) but my tablet doesn't look like anything was applied. Still on 3.1 and looks like the old build info on the tab.

The updated firmware should show KMM. KME is the old 3.1 update with a small 3.5MB update. Basically, IIRC, when 3.1 was released, there are also a lot of problemes and failed updates. Samsung pulled the update and later re-released it as KME. And for those already updated, a smaller updated (3.5MB) was also released to bring it to KME. Look like history is repeating itself. We will see a newer update package to KMM.

 

[Cowchip]

And what does this update to 3.2 do for us?

 

[iamkevski]

The updated firmware should show KMM. KME is the old 3.1 update with a small 3.5MB update. Basically, IIRC, when 3.1 was released, there are also a lot of problemes and failed updates. Samsung pulled the update and later re-released it as KME. And for those already updated, a smaller updated (3.5MB) was also released to bring it to KME. Look like history is repeating itself. We will see a newer update package to KMM.

Great info, thanks!

 

[PaulQ]

When I plug in using Kies, the main screen boldly says "Your device does not support software upgrading via Kies."

How are you guys getting Kies to work? I installed version 2.1.0.11095_121 that I downloaded from the web site tonight.

Won't it be important to use Kies to fix this bad update?