Anyone knows when the update is going to arrive? This device had had only two leaks, and yet still not official firmware even thought the other devices in the galaxy tab 2 line have received their 4.1.1 update.
Nope. On the Samsung website the answer to that question is that they don't/won't "speculate" when a release may come out.
LeftyGR said:
Nope. On the Samsung website the answer to that question is that they don't/won't "speculate" when a release may come out.
Click to expand...
Click to collapse
What's taking them so long? I mean I've been waiting for like3 months and my device is the only one not getting the update. Guess I'll stick with CM10.1
yup, we covered this last week here http://forum.xda-developers.com/showthread.php?t=2046567
ALWAYS assume your question or comment has been asked and do a good search before starting a repetitive thread.
Also if your on CM 10.1 your not gonna even get the update (and why would you want to use an OLDER version anyway) unless you use Triangle away to reset the flash counter and revert to stock.
daniel644 said:
yup, we covered this last week here http://forum.xda-developers.com/showthread.php?t=2046567
ALWAYS assume your question or comment has been asked and do a good search before starting a repetitive thread.
Also if your on CM 10.1 your not gonna even get the update (and why would you want to use an OLDER version anyway) unless you use Triangle away to reset the flash counter and revert to stock.
Click to expand...
Click to collapse
I'm not talking about OTA or not. I'm only talking about the jb update for this device. I obviously know I won't get the update on CM but I can revert back to stock as I want the stock jb for p3113.
Related
I am l little crazy about this ,sorry ,anyone who can tell the date,thank you!
knowing AT&T, you may never see an update, unfortunately.....they are notorious for that.
hp420 said:
knowing AT&T, you may never see an update, unfortunately.....they are notorious for that.
Click to expand...
Click to collapse
At&t does not push the update, Google does. As far as I've read only the 9020t (T-Mo) version has started to receive OTA updates. Google's announcement stated that the entire roll out will happen over the next month so it could be mid-January before all NSs get on official OTA.
There are ICS ROMs, based on the 9020t OTA, in the development section that work fine on the 9020a, just use a 9020a radio.
I know its a dumb question but I really want to know if its possible (guess just desperate to get JB on my phone).
I have m200 Nexus S korean version, and I've been waiting for an update for the last 2 weeks. Had a luck last week but it was only until July 25 and its gone.
Got so excited on that date, but luck was really on my side; battery low, applied update just to get an error (the famous red exclamation mark after reboot).
So now, I'm wondering, is it possible to use i9020t flash rom on my phone?
Your response will be GREATLY appreciated.
nhelven said:
I know its a dumb question but I really want to know if its possible (guess just desperate to get JB on my phone).
I have m200 Nexus S korean version, and I've been waiting for an update for the last 2 weeks. Had a luck last week but it was only until July 25 and its gone.
Got so excited on that date, but luck was really on my side; battery low, applied update just to get an error (the famous red exclamation mark after reboot).
So now, I'm wondering, is it possible to use i9020t flash rom on my phone?
Your response will be GREATLY appreciated.
Click to expand...
Click to collapse
jb release for your device?
leap_ahead said:
jb release for your device?
Click to expand...
Click to collapse
yeah there was, seems just for 1 day though and never came back
http://forum.xda-developers.com/showthread.php?t=1797383
I just spoke with Acer concerning the US release of Jelly Bean for the US A700.
The Acer representative stated that "the Jelly Bean update is still being tested". He went on to say that when it will be available as an OTA update when it officially releases (duh). No time frame for release was given...
Angus66 said:
I just spoke with Acer concerning the US release of Jelly Bean for the US A700.
The Acer representative stated that "the Jelly Bean update is still being tested". He went on to say that when it will be available as an OTA update when it officially releases (duh). No time frame for release was given...
Click to expand...
Click to collapse
In other words...."Dude... I don't know diddly..... why you calling me asking this?" "Of course we are going to give you some stupid excuse. What did you want us to say?"
Welcome to Acer....
Heck, they still haven't put out, Ahem...... JB KERNEL SOURCE for the 701! And...... They know it is against GPL. Hear that ACER? Non GPL compliant.
JB isn't being tested. It's ready and has been. They just have a schedule (to wait for issues from other OTA's). Just be patient.
MD
I thought under GPL they had like 180 days to post source? I know there are a few vendors that push it to the end.
Sent from my HTC One X using Tapatalk 2
My guess is that they've pushed the JB update to a small group of guinea pigs... I mean users... to find major issues before a wider release.
Update is likely still in "Beta" form and not ready for general release.
JasonJoel said:
I thought under GPL they had like 180 days to post source? I know there are a few vendors that push it to the end.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Generally, they should push it upon release.
In the case of 501 HC, they pushed it about 9 months afterwards. Fortunately, there wasn't a lot of differences in the kernel source, so devs could make modified kernels.
A lot of this, has to do with "branded" 501 models. Although it has nothing to do with the kernel source.
I will say, Acer did a lot by allowing unlocked bootloader. Kudo's Acer. However, they put a super-brick bug in the kernel/bootloader source. Which means, when you flash a certain amount of times, your tab may brick itself.
So far, we have found a couple of things. But I am sure there are more. Guess Acer likes to have more repairs. Costing them money.
But the bugs will be found. They always are.
MD
Lies....
I've triggered the update twice today by upgrading my software from 1.029 to 1.057... If your not on 1.057 then chances are your not getting it for now.
Last few posts here for reference.
http://forum.xda-developers.com/showthread.php?t=1907933
Itchiee said:
Lies....
I've triggered the update twice today by upgrading my software from 1.029 to 1.057... If your not on 1.057 then chances are your not getting it for now.
Last few posts here for reference.
http://forum.xda-developers.com/showthread.php?t=1907933
Click to expand...
Click to collapse
Thanks for the info. My firmware is even lower than the ones you mentioned above - I'm still on 1.017.
I wonder why the tab isn't updating to a newer version?
1.057 Necessary for JB in United States
Angus66 said:
Thanks for the info. My firmware is even lower than the ones you mentioned above - I'm still on 1.017.
I wonder why the tab isn't updating to a newer version?
Click to expand...
Click to collapse
At 1.017, you appear to be on the original ICS release of Android for the A700- that's old! Is that by choice? If not, there's definitely something weird about this.
I was the one who got frustrated with no update from 1.029, and messed around with trying to update to 1.057 and found that it worked. I passed that along to bidniss in the other thread on this forum, and via Itchee, et. al. word appears to be getting out now.
I started out rooted with CWM 6.0.1.4 on Build # 1.057, knowing that you can't get an OTA update in that state. So I unrooted and re-locked bootloader by flashing stock 1.029 (because stock 1.057 wouldn't work to unroot). It seemed kind of screwy to me that when I checked for an update from 1.029 it told me I was "up to date". Even if JB was NOT yet available I should have been prompted to update to 1.057, I would have thought. That's why I decided to install the stock 1.057 on my own. Lo and behold, the minute I did it I was prompted for the JB update!
It seems if you fall behind in updates, Acer is not too friendly about helping you get caught up?
I've only had my A700 for a little over 1 week, and I've not been offered any OTA update. I've been checking manually 20 - 50 times a day and I keep getting the "your device is up to date" message...
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
dweezle said:
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
Click to expand...
Click to collapse
I'd recommend finding a comfortable place to sit and wait because you will probably be there a looong time.
dweezle said:
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
Click to expand...
Click to collapse
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
http://ezandroidapps.info/samsung-galaxy-s3-and-s4-will-get-android-4-3-jelly-bean-update/
SlimSnoopOS said:
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
That's sound advice there. I'm not OTAing nothing until the devs say it's okay or they make a flashable zip.
dweezle said:
http://ezandroidapps.info/samsung-galaxy-s3-and-s4-will-get-android-4-3-jelly-bean-update/
Click to expand...
Click to collapse
Ahh, there's no mention of an update specifically for Verizon. When OEMs state an update for phone models and do no specify the exact ones, they always mean their international variants. International varants are not tied to carriers and therefore do not need to go through a certification process before being pushed to handsets. If there's an ota coming at all for any US variant, it would't be on Verizon for another few months. It would foreseeably go T-Mobile/Sprint then AT&T/Verizon a month or two later.
Also, any site that has as many grammatical or syntax errors for sentence structure should not be viewed as a reliable source. Try here for example, the info is more clearly detailed and presented.
Yeah wouldn't hold my breathe, If Samsung release in Oct the soonest verizon could/would roll anything out would be jan/feb and pretty sure looking at past performance from verizon the s3 will reach end of life around the same time. meaning no update
I am reaping the benefit of a lot of generous, and smart, people who have kept my Moto Xoom alive and kicking way past what most would consider it's end of life. One of the reasons I chose the S3 was because of the large numbers that were sold. I assumed that the community support would outstrip any "official" support from either Samsung or Verizon. What are chances that someone will cobble together a great 4.3 ROM for the i535, after the release of 4.3 by Samsung?
nujackk said:
Yeah wouldn't hold my breathe, If Samsung release in Oct the soonest verizon could/would roll anything out would be jan/feb and pretty sure looking at past performance from verizon the s3 will reach end of life around the same time. meaning no update
Click to expand...
Click to collapse
Normally I'd agree with you whole heartedly but as PrDog stated they want us to buy that watch. So it just might be sooner than we think.
Sent from the S3 of The Afro Samurai
TheAfroSamurai said:
Normally I'd agree with you whole heartedly but as PrDog stated they want us to buy that watch. So it just might be sooner than we think.
Sent from the S3 of The Afro Samurai
Click to expand...
Click to collapse
I would be extremely surprised and happy if it did, but sincerely doubt it.
SlimSnoopOS said:
Ahh, there's no mention of an update specifically for Verizon.
Click to expand...
Click to collapse
I did the same thing as you, I looked for the word "verizon" and didn't find it ! Heh, I'm running Android 4.3 on my S3 already, albeit w/o Touchwiz....
dweezle said:
What are chances that someone will cobble together a great 4.3 ROM for the i535, after the release of 4.3 by Samsung?
Click to expand...
Click to collapse
For reasons beyond my knowledge level, ports from international versions of the S3 don't get done for the VZW, ATT, and so on variants of the S3. I know the non-US models have a different CPU (and chipset ?) so that could be the reason. Proprietary drivers and libraries that hook into the kernel are NOT "free" or open-source. It's not as simple as just re-compiling the Samsung-released kernel as important pieces of the puzzle are missing and it won't work without those pieces....
So as some of you may know the S4 had it's exploit fixed and since then we haven't been able to get away from Touchwiz based roms.
Before I go get the G3 I just wanted to be 100% clear that even the latest firmware hasn't fixed Bump, and I will be able to do other AOSP roms. From my quick research it seems like it's fine, but I only have 20 minutes left to get it friday instead of monday, so I figured I would just ask to be safe.
failedjedi said:
So as some of you may know the S4 had it's exploit fixed and since then we haven't been able to get away from Touchwiz based roms.
Before I go get the G3 I just wanted to be 100% clear that even the latest firmware hasn't fixed Bump, and I will be able to do other AOSP roms. From my quick research it seems like it's fine, but I only have 20 minutes left to get it friday instead of monday, so I figured I would just ask to be safe.
Click to expand...
Click to collapse
AT&T released firmware Build number: KVT49L.D85010f to patch root exploit. Read this thread
http://forum.xda-developers.com/att-lg-g3/general/d850-software-update-t2937550
When Android Lollipop rolls out to G3 in the near future, rooting will be harder to accomplish. Same for other brands.
hwong96 said:
AT&T released firmware Build number: KVT49L.D85010f to patch root exploit. Read this thread
http://forum.xda-developers.com/att-lg-g3/general/d850-software-update-t2937550
When Android Lollipop rolls out to G3 in the near future, rooting will be harder to accomplish. Same for other brands.
Click to expand...
Click to collapse
But that is recent enough that a phone bought today will not come with it out of the box, so I'm not worried about that.
And in theory I can just flash a bumped lollipop build later anyway right?
I just want to make sure it's not in the same current state as the S4 where you have to have touchwiz and match roms to bootloader version and what not.
I know there isn't too many roms yet with bump being fairly new, but as long as I stay on the current build I should be fine going forward no?
And I guess on that note, the stock rom isn't nearly as bad touchwiz is it?
failedjedi said:
But that is recent enough that a phone bought today will not come with it out of the box, so I'm not worried about that.
And in theory I can just flash a bumped lollipop build later anyway right?
I just want to make sure it's not in the same current state as the S4 where you have to have touchwiz and match roms to bootloader version and what not.
I know there isn't too many roms yet with bump being fairly new, but as long as I stay on the current build I should be fine going forward no?
And I guess on that note, the stock rom isn't nearly as bad touchwiz is it?
Click to expand...
Click to collapse
Yes, yes and Lg is better than TW imo.
hwong96 said:
Yes, yes and Lg is better than TW imo.
Click to expand...
Click to collapse
Cool, I went for it, thanks for the quick clarifications. I can read all about everything now while I impatiently wait for UPS friday.
with LG phones you can always downgrade the software to a version where you can root.
I am sure there will be a way to get official lollipop while keeping custom recovery and root.
Once again, LG locked the door but forgot to close it before locking like what they did on the G2. So we were still able to upgrade while keeping custom recovery and root by mixing and matching partitions from upgrade and previous versions.