OTA Available after activation - Thunderbolt General

Did anyone besides be get notified of an OTA after they activated their T-Bolt? Did you install it? I didn't for fear it will ruin our current root exploit even though it's not permaroot.

I didn't get it yet, I wish I did though, don't want anything to be wrong if I can't get OTA updates. Hopefully I'll get it later today.
Update: Tried to manually update, phone said I had the latest software.

you can go to settings and check for update.
Crap i just did it again and now it says i don't have one.

I have not been notified but I was told to expect one in the next few days. I was told it contains the fixes for battery life issues.
Sent from my Xoom using Tapatalk

Related

AT&T to Push JH7 Starting Today...

*UPDATE*
Designgears has captured the OTA update and packaged it up for anyone who is having trouble with the download applying.
http://forum.xda-developers.com/showthread.php?t=790080
Software Updates and Maintainence Releases
1.09/21/2010 - Firmware Over the Air (FOTA) software update changing software version from I897UCJF6 to I897UCJH7. A 12MB download is being pushed to Samsung Captivate owners starting on 09/21/2010 and will continue Tuesday through Friday at 15K customers per day until complete. This is NOT an operating system update. This update includes the following software updates:
•Preinstalled software - QuickOffice for Android will allow users to edit various Microsoft Office documents.
•Messaging - Exchange 2003 support, MMS and other messaging enhancements.
•Voice - Improved calling experience.
•Media - media scanning time improvements.
Note:
This firmware update is not intended to resolve all device reset or freezing issues, which may be caused by:
•Corrupted files
•Device memory becoming filled and leaving insufficient room to run applications.
•Use of incompatible 3rd party applications on the Samsung Captivate.
http://www.wireless.att.com/answer-center/solutionDisplay.jsp?solutionId=KB110797
scroll to the very bottom of the link
No gps fix?
Sent from my SAMSUNG-SGH-I897 using XDA App
Mention of GPS strangely absent.
been running JH7 since it came out with SRE.
WTF is this? JH7 doesn't fix GPS nor does it come close!
(battery life is AMAZING THOUGH!)
Well, since GPS is not mentioned, I doubt this is meant as the fix for GPS issues...
But it IS a good sign that AT&T is actually working on our device, since they are releasing this FW to the public.
Very odd. They guaranteed a GPS fix by end of Sept. We already have used JH7 and it doesn't fix our GPS. I can't imagine them putting out another update before the end of September...
Is it possible that the update from AT&T will somehow include more file update or be different from the JH7 version that we have? Beyond that, I can't understand how they are finally releasing an update but NOT fixing the biggest issue. Especially since they apparently fixed it on the Vibrant and know how to fix it.
Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.
swedishcancerboi said:
Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.
Click to expand...
Click to collapse
Check the GPS....
actually, before I get too crazy, let me verify something:
I had JF6, I made a backup image using ROM Manager/Clockwork Mod. I then applied the JH7 found here, had problems (no sideloading), and restored the image. I am ASSUMING that put me back on Baseband JF6, but I don't remember checking afterwards.
Is it possible that the JH7 I have is left over from my manual update? I don't wanna lie to everything thinking I got the official push and really didn't.
swedishcancerboi said:
actually, before I get too crazy, let me verify something:
I had JF6, I made a backup image using ROM Manager/Clockwork Mod. I then applied the JH7 found here, had problems (no sideloading), and restored the image. I am ASSUMING that put me back on Baseband JF6, but I don't remember checking afterwards.
Is it possible that the JH7 I have is left over from my manual update? I don't wanna lie to everything thinking I got the official push and really didn't.
Click to expand...
Click to collapse
You can flash back to JF6...
I will do it if need be but it will have to wait until tonight.
My GPS works fine and I have none of the other issues that this is supposed to fix, so I couldn't tell you whether the update will fix those or not.
swedishcancerboi said:
Looks like I got it. I definately have to test Exchange now. Maybe it'll work properly.
Click to expand...
Click to collapse
Did you have to look for updates on your phone or was it sent auto? Were you running stock when you got it?
Rhiannon224 said:
Did you have to look for updates on your phone or was it sent auto? Were you running stock when you got it?
Click to expand...
Click to collapse
They are pushing it, but you should be able to get it if you search for updates and your phone meets the criteria...
I'm running a backup now. I'm need to test a few things. I just happened across this thread and had a quick look at my basband number and it shows JH7. I *should* be stock. But that assumes that when I restored back to my original image, it also restored JF6
I'll get back with you. I don't feel like I'd be one of the lucky ones to get the update first (unless it goes by purchase date, I did get mine early).
LOL...fail. I went to check for update, said no update and that I can not check for another 24 hours. WTF? why cant I check for updates when I want.
Noob question: Is it necessary to un-root and un-lagfix before attempting to download or install this update?
Sent from my SAMSUNG-SGH-I897 using XDA App
iceman4357 said:
LOL...fail. I went to check for update, said no update and that I can not check for another 24 hours. WTF? why cant I check for updates when I want.
Click to expand...
Click to collapse
Me too, lol, I'm already running JH7 that was leaked. According to the AT&T site they are looking at your firmware version and that's how they determine who's getting it.
Hmmm, debating if this update is even worth it. Doesn't fix GPS, and it's not Froyo
OTA update process usually takes days or weeks. It pushes in batches so that only limited number of phones will download the update so that the update server don't get overloaded. No, maunally check for update does not speed the process up at all or change your position in the queue. Basically, you have to wait for your turn.
Sooner or later someone will figure out the URL to download the update directly. Only when that happens, you can go and download the update and manually put that file to internal SD card, boot the phone into recovery mode and apply the update.
If that's too much work for you, wait for your turn.
Ikonomi said:
Noob question: Is it necessary to un-root and un-lagfix before attempting to download or install this update?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
same question here. Anyone know if I'll lose root/non-market apps if I apply this update?
One thing I did notice about the leaked version was the new YouTube app styling. I kinda liked it. Came in handy at the gas pump.

Random OTA update

I'm downloading a new software update . I had already installed the last update.
edit
When I say last update I meant the one with the GPS fix.
What else could this be besides froyo ?
edit
Something funny happen, the update didnt install and now I cant check for another one.
edit
I changed the date on my phone so now I'm trying the update again.
edit
It keeps failing, so I dont know what this is .
wrong.........
i tried 4 times, wasted many of my limited data, never get updated. Att sucks.
pobinghun said:
i tried 4 times, wasted many of my limited data, never get updated. Att sucks.
Click to expand...
Click to collapse
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)
i just got my brand new phone in the mail yesterday, im just gonna wait till it tells me there's an update before I download any updates..
link12245 said:
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)
Click to expand...
Click to collapse
It sure does show up under data used, so I assume that it will be counted against you data plan.
Is your phone rooted? Showing symptoms associated with.
AGAIN
Yeah I have no idea what this update is ? This is like the 5th time it failed on me, so forget it.
I am rooted.
When I got the update, I had just gotten the phone. The update went through just fine, the day after I rooted my phone. So maybe rooting had something to do with it. I don't see how that could effect it but maybe.
I think it's time you detach the umbilical cord to the OTA update Update using Clockwork. (Just a suggestion).

Update rolling out Soon

I spoke to a rep the other day regarding Jelly Bean. Long Story short he said it is rolling out to their systems now (computer support info) so we should have it very very VERY soon.
Sent from my SCH-I535 using Tapatalk 2
Your title gives the impression that it'll be JB
Edit : you edited your post.
Sent from my SCH-I535 using xda premium
blestsol said:
Your title gives the impression that it'll be JB
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
First mistake is assuming the reps have a clue about what they are talking about. They are lucky to dress themselves for work every morning. If I had a nickel for every time a rep told me an update is coming, I'd be a thousandaire.
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I think when he says a small update he is describing his post as a small update to here. No the actually Verizon update.
Of course the next Verizon update will be JB. They do not need to make our phone ready for JB, it is ready and the leak we have also says it is pretty ready to go.....
Yes to Jellybean. Sorry for the confusion.
Sent from my SCH-I535 using Tapatalk 2
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I'm familiar with your posts in other threads. Carry on.
Sent from my SCH-I535 using xda premium
Never trust verizon reps....
I know a bunch of people who work for Verizon corporate.
I tell THEM when builds/phones are coming. I just updates their store model M to JB on Friday. They had no idea
Sent from my SCH-I535 using Tapatalk 2
Delete.
Sent from my Galaxy Nexus using xda app-developers app
The leak seems more stable than the ICS official to me...
I think these delays are more of a marketing strategy of sort rather than a real technical time to get it ready.... I might be wrong but...
Well VZW is going to have to do something either right before or same day the Note 2 comes out.
Sent from my SCH-I535 using Tapatalk 2
It seems more of a marketing strategy because t mobile released theirs after the note 2 was released.
Sent from my SCH-I535 using xda app-developers app
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Well that depends, what's their definition of "soon".
Terry_blair said:
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
I laughed to his face and told him I would never be doing business with his store again.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
Click to expand...
Click to collapse
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
ooofest said:
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
Click to expand...
Click to collapse
Well I had been manually checking for like a week, however, I wasn't receiving an update that had been out for months. The phone was 2 updates behind!
The new phone with my same SIM updated instantly after it was set up. I didn't even have to manually check. And then it updated again. So I honestly believe there was something wrong with the phone. Very strange to not get an update that had been out for months, you know?
Sent from my SCH-I535 using xda app-developers app

[Q] Just got Shield (32GB), It has 4.4.2, says OTA "1.21" available...

Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....

New firmware BQG1

Anyone else get an update yesterday?
Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.
The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i dont notice anything new.
I cannot install the update on any of my rooted phones (which isn't a huge surprise to me). However, the update has been out for a few days, and I haven't seen anything about the update here on the forum until today. I'm hoping someone posts an update method for those of us with rooted phones.
Does anyone know can we use BT firmware from S6 onto S7? I have problem connecting my car hands free system, thought no such problem with S6
BQG1 improves network speed.
Averix said:
Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.
Click to expand...
Click to collapse
Got the BQG1 update on 7/29 and after stabilizing for an hour ran speed test via WiFi. I had noticed a drop to around 140Mbps on my Comcast service with the last update and couldn't figure out why. With BQG1, my downlaod speed is back up to 230Mbps and running very smooth. Don't know what VZ did, bit it works!
Hope that helps.
neyenlives said:
The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i don't notice anything new.
Click to expand...
Click to collapse
I wanted to give a quick update.
Following suggestions I found on a few threads here, I went ahead and updated all three of my rooted phones to firmware QH1 on Friday, and they are all still rooted.
I used ODIN to re-flash the stock firmware (using HOME-CSC to keep my apps and settings intact. I downloaded the firmware from one of the links I found here on XDA.
I then re-rooted using the procedure in the OP.
I had two issues (that I can think of):
1. A few of the settings (lock screen settings, specifically - maybe one or two others?) were cleared in the process - and I had to set them up again.
2. One of the phone (the one *I* use, of course), rooted okay, but SuperSU was missing after the reboot. Installing it from the Play store appeared to break root. So I just re-rooted it again.
Other than those issues, I think everything else went pretty smoothly.
I hope this is helpful to others.

Categories

Resources