Database Info

Firmware Update 2.1-update1

Samsung just released the first firmware update today... i installed it but cant find any info online anywhere about what all it changed/fixed? anyone have more info on this?

There's a post in general about it coming soon. I haven't gotten it yet, anyway to extract it and host it? just in case they release it in phases. According to the other post, you can install it via OTA, Store, or home computer, so it should be available to the masses soon.

Always the same first question... Does it kill root?
Sent from my SPH-D700 using Tapatalk

Same usual first question: Does it kill root?
Roger
Sent from my SPH-D700 using Tapatalk
Sorry about the double post. Got an fc and then didn't show.

I got the update a bit ago. Phone rebooted to install...there was an error but I didn't get to see what it was. Phone rebooted again and is going fine now. Titanium backup still shows root. I went to about phone and it shows 2.1_update 1. I read media hub was supposed to be enabled but mine still says check later...I'm wondering if my phone didn't actually update. I will see what others say about their updates.
Oh and my specs...one click rooted with andromeda kernel and adw launcher...pretty much stock other than that
Sent from my Epic 4G using Tapatalk Pro

i have had 2.1 update one since i first got my phone... :-( i was soo excited about an update ... I want the puzzle unlock

Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.

done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.

done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App

JojoSteez said:
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.
Click to expand...
Click to collapse
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App

rufflez2010 said:
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's what I figured...I could flash back to stock I guess, but might be moot if the phone can't find the update again. It was pushed to me to begin with and now it's like it never happened...

rufflez2010 said:
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I still have dg27 so it seems my update just failed. It's gotta be the custom kernel then. hmm...what to do, ha

Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.

JojoSteez said:
Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.
Click to expand...
Click to collapse
Let us know if battery life is any better.
Sent from my SPH-D700 using Tapatalk

Samsung's build number is always easy to read.
A, B, C, D, ... : month.
January, February, March, etc. G means July, therefore.
27 means July 27th: the date of kernel/firmware build.
So DI07 means September 07, which is fairly new.

http://community.sprint.com/baw/message/213524
Here is a Sprint Admin talking about it. It is an official release as of today. He has all the fixes listed too.

it is a 2.1 exploit through adb actually so this shouldnt be of any worries to us

Just got a pop up on my phone about the update. Accepted it and told it to apply. Phone rebooted, then showed an error when trying to apply the update. Hit the Home button and phone rebooted. No further notifications now about the update. Went in and manually checked and it tells me none are available. So,..I guess you only get one shot at the update and then you're skipped??

anyone that is rooted with stock kernel able to update and keep root?

wait what update? i checked for an update but there wasnt one.

Gingerbread Update

I have a G2x and am running the latest nightly. I have two questions I'd like answered
1. Can my phone still get an automatic update from T-mobile even though my phone is rooted. I noticed when I had FROYO there was an option in my setting to check for "system updates" but that went away on CM7
2. If I don't get an automatic update from T-mobile is there any advantage for me download the update or will the developers eventually integrate the changes into there ROMS?

1, no. Not if you're on CM7, I don't think. Rooted stock, I think so.
2, the developers probably will integrate.
I'd stay rooted and custom.

Doesn't anyone read the forums before posting at all anymore? This has been covered/talked about since the leak happened like 4 to 5 days ago. Geez LOOK AROUND!

Goldbatt said:
I have a G2x and am running the latest nightly. I have two questions I'd like answered
1. Can my phone still get an automatic update from T-mobile even though my phone is rooted. I noticed when I had FROYO there was an option in my setting to check for "system updates" but that went away on CM7
2. If I don't get an automatic update from T-mobile is there any advantage for me download the update or will the developers eventually integrate the changes into there ROMS?
Click to expand...
Click to collapse
1. If your phone is rooted then you will NOT get an OTA update NOR will you be able to manually update your phone. Must remove the root first.
2. This totally depends on you on what you want. Look around the forum and see if the new update is right for you with all its pros & cons.

My phone ran the manual update just fine and was rooted. Lost root, of course, after the update though.

Lightning Blue said:
My phone ran the manual update just fine and was rooted. Lost root, of course, after the update though.
Click to expand...
Click to collapse
was this using the LG updater tool?

J360 said:
was this using the LG updater tool?
Click to expand...
Click to collapse
Yeah, I wasn't going to try OTA over 2G

mhsamma said:
1. If your phone is rooted then you will NOT get an OTA update NOR will you be able to manually update your phone. Must remove the root first.
2. This totally depends on you on what you want. Look around the forum and see if the new update is right for you with all its pros & cons.
Click to expand...
Click to collapse
I thought having a custom recovery was the issue, not root. You must have the stock recovery.

I am running EB 1.05 rooted Faux kernel. Ran update check and got prompted to download update.

OTA 2.3.5 Question

I have went back to stock on the 22nd of this month. I still have not got the ota yet. Is that normal? should I wait a few more days?

lawranceomega said:
I have went back to stock on the 22nd of this month. I still have not got the ota yet. Is that normal? should I wait a few more days?
Click to expand...
Click to collapse
The OTA will roll out to all devices over a few weeks - you can't just "check in" and get it. It's flagged by IMEI/ESN. Once you're flagged a subsequent check in will result in OTA notification.

krohnjw said:
The OTA will roll out to all devices over a few weeks - you can't just "check in" and get it. It's flagged by IMEI/ESN. Once you're flagged a subsequent check in will result in OTA notification.
Click to expand...
Click to collapse
FYI the check in code is *#*#checking#*#*

*#*#checkin#*#*

Overstew said:
*#*#checkin#*#*
Click to expand...
Click to collapse
You must have replied as I was editing. Thanks

Its still wrong ^^
MBeattie said:
You must have replied as I was editing. Thanks
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

Thanks guys!

I noticed the original poster is on T-Mobile. Keep in mind that so far, the 2.3.5 update is only for the Nexus S 4G on Sprint. No announcement official or unofficial has been made regarding a 2.3.5 update for any other Nexus S variant other than the 4G one for Sprint.

i hope they dont start fragmenting their OS further...even at the nexus s flagship level...that would suck.
-gk

Has anyone tested updating OTA with a rooted phone on 2.3.4? I assume this will set the phone back to stock but wanted to make sure it wouldn't brick it...

gkrawiec said:
i hope they dont start fragmenting their OS further...even at the nexus s flagship level...that would suck.
-gk
Click to expand...
Click to collapse
it was a update primarily for the Nexus S 4G. its not fragmentation.
if you REALLY want 2.3.5 then just download a ROM with it.

Jagar123 said:
Has anyone tested updating OTA with a rooted phone on 2.3.4? I assume this will set the phone back to stock but wanted to make sure it wouldn't brick it...
Click to expand...
Click to collapse
It won't brick anything. At worst it will change the permissions on the su binary and you'll have to flash it through recovery again or format /system (the incremental updates don't really do that though) to extract the new system packages.

krohnjw said:
It won't brick anything. At worst it will change the permissions on the su binary and you'll have to flash it through recovery again or format /system (the incremental updates don't really do that though) to extract the new system packages.
Click to expand...
Click to collapse
Unfortunately it looks like it's bricked my phone... I got the triangle exclamation point and it wont go anywhere...
*EDIT*
After taking out my battery and rebooting it looks to have gone back to 2.3.4 pre update. Yay

Jagar123 said:
Unfortunately it looks like it's bricked my phone... I got the triangle exclamation point and it wont go anywhere...
Click to expand...
Click to collapse
thats not what a BRICK IS! if your screen shows something. ITS NOT BRICKED. stop using the wrong term, its fixable.
root and get clockwork if it isnt there anymore, wipe and flash a ROM.

Quick question...not ssure if answered already but after the update, are there supposed be more signal bars showing? I have read in other forums that some who updated saw more signal bars (not necessarily more signal strength but more bars as opposed to the 4 that we have pre update).
Thanks aand how has tthe experience been with the update? I used the recovery method rather than wait for sprint to push it to us and honestly, I have noticed very little difference in coverage
Sent from my Nexus S 4G using XDA App

[Q] New OTA? Or am I just way behind somehow?

I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.

2.3.3 was all the rage about a month or so ago.
Sent from my LG-P999 using xda premium

Well, sure, but all news says that T-mobile stopped doing OTAs some time ago (started late July, stopped August 10). So why on earth is my phone just getting it now? I even do a manual check every so often and never got it. I didn't do anything special today that I can recall.

you should update it. you dont have nothing to lose. ifd your still rooted it will unroot but then you can flash nvflash recovery and go back to any rooted roms you want

epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
No idea why you're just getting it now, but its the same one thats been out for a while now.

hmichaelkim said:
No idea why you're just getting it now, but its the same one thats been out for a while now.
Click to expand...
Click to collapse
T-Mobile removed the 2.3.3 update from their servers long ago. If you are getting something else it is new most likely. You can do an OTA if you are rooted as long as you have not modified any system files other than adding su and superuser.apk to get root..

epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
So what was the update?
Sent from my HTC Desire using XDA App

What happens?
Sent from my LG-P999 using XDA Premium App

Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).

I'm on froyo to and rooted but no clockwork mod recovery. I tried to check for an update and it said some kind of error i dont remember.

epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Check in the /cache directory for the zip file for tthe update. If you can, before you install it can you save a copy of the zip to a separate area on your sdcard and thn upload it to a file sharing site so others can download it? Once you install it, it gets deleted from the /cache directory but if you save it elsewhere those copies will be saved.

epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Yes, you need to be on stock recovery and your phone's system partition must be stock. LG stores some OTAs very differently than other vendors.
Do a backup of your phone first to preserve the OTA image. It might be in the cache but it might be elsewhere. If you wouldn't mind giving me a link to the system and cache images I can try to find the OTA and see what it is for.

I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.

Lenin809 said:
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Click to expand...
Click to collapse
Did you flash roms and then restore an old backup? That backup could have had the OTA on it and you did not notice it before. T-Mobile pulled the OTA months ago (was available less than two weeks). Doesn't seem likely it was pushed to you recently.

Rogers System Update - (1.94.631.3)

I've been checking for updates on my one x almost everyday for a month now, and an update just went out.
It's a system update (1.94.631.3) 67Mb.
Still not sure what its updating.

Try it and let us know!
Sent from my HTC One XL using xda app-developers app

I'm currently on version 1.73.631.1.
I can download the update and run the installer.
It gets halfway through the update then shows a phone with an error icon on it.
phone resets and im still on the old version.

Berserk87 said:
I'm currently on version 1.73.631.1.
I can download the update and run the installer.
It gets halfway through the update then shows a phone with an error icon on it.
phone resets and im still on the old version.
Click to expand...
Click to collapse
Are you unlocked/rooted? Or pure stock?

I think I'm going to wait a bit before installing this update...
for the record I'm on 1.73 still... not sure what's in this update

That's odd.. from other X & XL 4.0.4 releases they have used a 2.x.x.x release code and I'm surprised they would release another 4.0.3 version with 4.0.4 out.

I called HTC.
They couldnt tell me how to fix the error or what the update includes.
I was told to factory reset and try it again, which I did. The update still failed and I have to resetup my phone now...

Custom Recovery Screen
I downloaded the update successfully on my rooted One X (with stock ROM). When I hit install, it restarts the phone and goes into the custom recovery screen... I don't really know what to do from there though... anyone got any ideas?

Berserk87 said:
I called HTC.
They couldnt tell me how to fix the error or what the update includes.
I was told to factory reset and try it again, which I did. The update still failed and I have to resetup my phone now...
Click to expand...
Click to collapse
Need to relock bootloader, restore recovery and return OS to stock.
Basically relock bootloader and flash original RUU.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
ComposMentis said:
That's odd.. from other X & XL 4.0.4 releases they have used a 2.x.x.x release code and I'm surprised they would release another 4.0.3 version with 4.0.4 out.
Click to expand...
Click to collapse
Only Singapore has gotten 2.x aka 4.0.4.
All other regions were recently updated to things like 1.88(previous Singtel), 1.89(Telstra), 1.91(Telus), 1.92(o2 Germany) and now 1.94(Rogers). There is probably a 1.90 and 1.93 somewhere. Eg maybe 1.93 is the soon to be released AT&T and maybe Vodafone Germany is at 1.90?

Only thing I can think that might mess it up, is that my phone was rooted, but i've done a factory reset already.
So the only other thing I can think of is that the update fails because my phone shows "tampered" from rooting.

You need to install a ruu(the correct rogers one). That will remove tampered warning.

I just downloaded the update. It's def worth doing it. My phone was rooted as well but had no issues with update. Multitasking issue for me seems to be fixed, well a million times better than it was anyways (Seems i spoke too soon on the multitasking, its a bit better, but after a couple apps its back to normal) no more reloading every time you go back to something. Also I used to find it slow going into text messages etc, and the contact list was slow to update especially when scrolling through, totally eliminated now. So much faster and less bogged down feeling.

lurker82 said:
I just downloaded the update. It's def worth doing it. My phone was rooted as well but had no issues with update. Multitasking issue for me seems to be fixed, well a million times better than it was anyways (Seems i spoke too soon on the multitasking, its a bit better, but after a couple apps its back to normal) no more reloading every time you go back to something. Also I used to find it slow going into text messages etc, and the contact list was slow to update especially when scrolling through, totally eliminated now. So much faster and less bogged down feeling.
Click to expand...
Click to collapse
Any tricks to the update?
did you download over wifi?
plugged in during update?
use htc sync?

twistedddx said:
You need to install a ruu(the correct rogers one). That will remove tampered warning.
Click to expand...
Click to collapse
I don't think that removes the tampered flag.
Sent from mobile

Installing a RUU does remove the tampered flag. so run the stock ruu, flash the update then unlock the bootloader again then push the custom recovery. flash a root for cmw then you will be rooted again. If you want a custom rom from it, then do a system dump after the upgrade.

OTA Link
Here's the link for the OTA download for anyone who wants to go through it: http://fotadl.htc.com/OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
It contains hboot 8960_1.11.0000_20120607 and an updated radio, the version of which I'm not sure of.

Oh. Didn't actually try an ruu myself.
Sent from mobile

TelusHTCHero said:
Here's the link for the OTA download for anyone who wants to go through it: http://fotadl.htc.com/OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
It contains hboot 8960_1.11.0000_20120607 and an updated radio, the version of which I'm not sure of.
Click to expand...
Click to collapse
Where did you get that and how do I flash it?
I would also like to keep root if possible.

I assume people catch the link while the phone tries to download it.
You can't manually flash a fota. You need to apply all the patch files against the original firmware intended to be updated.
It's a long tedious process, only a smart dev will be able to pull it off.
It was done to get 4.0.4 but is it worth the effort for this? This is likely equal to all the other regions recent 4.0.3 updates.

Why are you guys so eager to flash this? I'm sure there are better custom roms. This will update your hboot so beware. If s-off is achieved you'll be **** out of luck.
Sent from my HTC One XL using xda app-developers app