I am still stuck on firmware 1.58 due to S-ON and I thought AT&T was rolling out an update to Android 4.4.4 but my phone can't find it.
Does anyone know why or how to update the firmware to something newer if I have S-ON? Thanks.
AvatarOfFrost said:
I am still stuck on firmware 1.58 due to S-ON and I thought AT&T was rolling out an update to Android 4.4.4 but my phone can't find it.
Does anyone know why or how to update the firmware to something newer if I have S-ON? Thanks.
Click to expand...
Click to collapse
download the HTC Sync software and try doing a manual update. or you can just wait until the OTA gets pushed.
AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.
jshamlet said:
AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.
Click to expand...
Click to collapse
HTC hands over technically approved code to AT&T they can load their bloatware crap on it. AT&T takes code informs everyone update will role out the next day, loads bloatware...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OTA pulled Back technical difficulties.
jshamlet said:
AT&T canceled the KitKat OTA because it was messed up. Not sure on the details, but I believe battery life was significantly worse.
Personally, I dumped AT&T's image and switched to the Developer Edition, and I've never looked back. However, if I needed to run AT&T's crap, I'd avoid their KitKat OTA and pray that they finally get around to releasing a Lollipop OTA instead.
Click to expand...
Click to collapse
Can I switch to the developer edition if I have S-ON?
AvatarOfFrost said:
Can I switch to the developer edition if I have S-ON?
Click to expand...
Click to collapse
No.
Related
First Off, im not sure if this should be in Q&A or android development. But, here i go..
I have seen alot lately about the leaked ota update, and all these fancy 2.2 leaks, which apparently requires a radio flash of some kind. Now before i do this, i have some questions..
If i do this, will i be able to use old nandroid backups of 2.1? and if i am rooted, how do i go about flashing the leaked ota? Im asking because im hearing alot of posts of people bricking phones.
Also, if i ignore this update, and theoretically a 2.2 update is released tommorow, will i be able to just update rooted? im sure i would lose root but could i do it? or do i really need to use PB31IMG and restore my phone?
Thanks for the reply.
Gentle warning, due to admitted OP confusion. Good rule: if you really have to start a thread, when in doubt choose General or Q&A (if one is available). Thanks
mikerulez121 said:
... im not sure if this should be in Q&A or android development....
Click to expand...
Click to collapse
it should be in Q&A.
Unfortunately, Incredible has no Q&A section yet so General is used for that. For now.
Ok, ill keep that in mind. I take it the thread has been moved. but anyway, anyone have any input on the whole radio update dillema?
If a new OTA is released and the radio is slightly different you'd need to RUU. I am not sure how the OTA prompt would go and what would happen if you tried to apply the ota BUT I know you can always RUU down and flash the newest OTA after SU busybox etc is added with no problems.
So basically, theres no way im upgrading the radio unless i RUU and apply the ota. Alright. Guess Ill wait for an official OTA. but will a 2.2 rom break unrEVOked 3.1?
mikerulez121 said:
but will a 2.2 rom break unrEVOked 3.1?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No one knows because the official update is not out. No one knows if the radio will be different than the leaked one, or if the hole used to root is plugged. The people who do know (HTC/Verizon), don't appear to be on this forum.
I want to flash my AT&T Galaxy S3 SGH-I747 with the new Android Version
My version is : 4.1.1
I'm not an expert and I want to update my smartphone
Please help my to do this (Instructions and file sources)
Thank you.
I suppose KIES tells you that your current Firmware 4.1.1 is up-to-date, right...?
Do you have an unlocked phone...?
abdestar said:
I want to flash my AT&T Galaxy S3 SGH-I747 with the new Android Version
My version is : 4.1.1
I'm not an expert and I want to update my smartphone
Please help my to do this (Instructions and file sources)
Thank you.
Click to expand...
Click to collapse
aldana said:
I suppose KIES tells you that your current Firmware 4.1.1 is up-to-date, right...?
Do you have an unlocked phone...?
Click to expand...
Click to collapse
Unless you're prepared to learn about rooting and flashing a new rom on your phone, just wait a few weeks and the phone will offer you an upgrade some point after they officially release it.
If you're prepared to learn about rooting and flashing your phone - the instructions are in post 1 of the thread under Android development.
AT&T released 4.1.2 the begining of August 2013 but KIES keep teeling that 4.1.1 is the latest.
rdoac said:
Unless you're prepared to learn about rooting and flashing a new rom on your phone, just wait a few weeks and the phone will offer you an upgrade some point after they officially release it.
If you're prepared to learn about rooting and flashing your phone - the instructions are in post 1 of the thread under Android development.
Click to expand...
Click to collapse
aldana said:
AT&T released 4.1.2 the begining of August 2013 but KIES keep teeling that 4.1.1 is the latest.
Click to expand...
Click to collapse
Missed that. I went straight from 4.1.1 when I got the phone to romming it. Can it update OTA instead of using KIES?
I still say wait a couple of weeks, the 4.3 is a much more advanced update and is in the pipeline soon so Samsung can sell you a Galaxy Gear in time for Christmas.
Those SGH-I747 (AT&T) devices, cannot do OTA because the devices tries to connect to AT&T Servers; see images below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rdoac said:
Missed that. I went straight from 4.1.1 when I got the phone to romming it. Can it update OTA instead of using KIES?
I still say wait a couple of weeks, the 4.3 is a much more advanced update and is in the pipeline soon so Samsung can sell you a Galaxy Gear in time for Christmas.
Click to expand...
Click to collapse
My HTC is the A & T and would like to see if my firmware is up to date! I used the var get all command as in the photo below but is not showing up! and enjoy and tell me what I most need updating! I'm using the ARHD and is taking to start the device but the rest is perfect! If you have to install an updated firmware please help me! and excuse my poor English!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hboot 3.16 = 1.x firmware, which won't work for any of the more recent Sense ROMs.
You can only officially update the AT&T version to hboot 3.17 (2.x firmware) which doesn't really help matter much as far as the current ROMs.
My suggestion is s-off by sunshine, which will allow you to flash 3.x or 4.x firmware as needed by the particular ROM.
Or wait until AT&T gets rolling with some OTAs (don't hold your breath).
redpoint73 said:
Hboot 3.16 = 1.x firmware, which won't work for any of the more recent Sense ROMs.
You can only officially update the AT&T version to hboot 3.17 (2.x firmware) which doesn't really help matter much as far as the current ROMs.
My suggestion is s-off by sunshine, which will allow you to flash 3.x or 4.x firmware as needed by the particular ROM.
Or wait until AT&T gets rolling with some OTAs (don't hold your breath).
Click to expand...
Click to collapse
Actually, AT&T finally released 4.4.4 yesterday.
xunholyx said:
Actually, AT&T finally released 4.4.4 yesterday.
Click to expand...
Click to collapse
Files were released in error for a short time, but then subsequently pulled: http://forum.xda-developers.com/showpost.php?p=58313915&postcount=156
In any case, if the OP is trying to run the current ARHD, which needs 4.x software. So Android 4.4.4 update (firmware 3.x) still won't help, and he will still suffer long boot times.
If you are stuck with AT&T, this should give you a sense of how long you can expect to wait for Lollipop...
redpoint73 said:
Files were released in error for a short time, but then subsequently pulled: http://forum.xda-developers.com/showpost.php?p=58313915&postcount=156
In any case, if the OP is trying to run the current ARHD, which needs 4.x software. So Android 4.4.4 update (firmware 3.x) still won't help, and he will still suffer long boot times.
Click to expand...
Click to collapse
Yeah, I an article about it being pulled this morning.
So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
wase4711 said:
So, yeah, this is one of those "tester" phones that I recieved to do a review about, and there are a few things I am not clear about now that the Pixel XL has been out for awhile..
- I haven't gotten any OTA updates at all, and still on October security files; am I missing anything?
-not sure which "factory" version I should use as a fall back in case of a disaster
-not sure if I have to "upgrade" to a different build before I root and flash TWRP
Its actually kind of nice just keeping the phone pure stock so far, but I know its only a matter of time before the custom roms and tweaks start to show up, and, we all know how important it is to have a "fall back" plan, in case of a disaster..
Thanks to anyone who has the same situation, and has figured out how to move forward.. :good::good:
Still using my Shamu as my DD, but would like to get the Pixel XL to that point too!
Click to expand...
Click to collapse
I got the same build number when i bought phone from best buy. I was able to unlock bootloader and root.
Edit: just unlock bootloader and then flash full factory image using adb and fastboot tools..
i've unlocked the bootloader, but not rooted or twrped yet, since there is really nothing to flash yet..
which image did you flash?
thanks
I downloaded the play services update from all mirror and it now gives the option to check for updates, you'll find the appropriate play services in my screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel XL using XDA-Developers mobile app
I have the same version of play services as in your screenshot, and when I go into dev options/about/check for updates, it says no updates available...weird
still no update for me, very strange
Is it just me or is this by design? Very weird
Not just you, not sure what googleeeee is smoking lately
wrecklesswun said:
Is it just me or is this by design? Very weird
Click to expand...
Click to collapse
Where is it reporting as SD1A.210817.015.A4? In Settings/About? Any other details such as what country you're in and what carrier you're using? Anything else you can tell us - are you rooted or applied OTA or factory image manually?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine is exactly what I flashed
USA, in Settings About, Build Number, Fi, Rooted, Flash three time manually from here
https://dl.google.com/dl/android/aosp/raven-sq1d.211205.017-factory-bf3da4b2.zip
Here
this build appears to be raven-sd1a.210817.015.a4
https://dl.google.com/dl/android/aosp/raven-sd1a.210817.015.a4-factory-bd6cb030.zip
wrecklesswun said:
Here
Click to expand...
Click to collapse
Are you using a custom kernel?
Can you check the hash of the full .017 firmware zip you downloaded and compare it to the hash shown on the website? (I check it after every time I download a full image zip, or an OTA zip)
minus case insens they match
BF3DA4B26554D84F99EAAD9837330C7D757F7D31442397EF89A98307D169D96A
bf3da4b26554d84f99eaad9837330c7d757f7d31442397ef89a98307d169d96a
no custom kernel
curious to know which is the one to apply for google FI or t-mobile or ATT (you'd think i'd know this working for TMO
wrecklesswun said:
curious to know which is the one to apply for google FI or t-mobile or ATT (you'd think i'd know this working for TMO
Click to expand...
Click to collapse
It was always my impression to use the one that makes sense for the region and carrier you use, i.e. US Carrier, but at least one knowledgeable person in the P6P section said the A1 is the correct one. I haven't had problems with the US Carrier one on AT&T (.017). My wife's phone isn't rooted and she hasn't gotten the December OTA. I mainly leave well enough alone on her phones since some things I've done on all her old phones (which is always the same phone as what I have, to make it easier for me to give her tech support) have given her unwanted surprises.
Oh yeah - you could always try the Official Google Android Flash Tool and see if you get any different results.
so is the 16.a1 correct or 17 for us carriers?
wrecklesswun said:
so is the 16.a1 correct or 17 for us carriers?
Click to expand...
Click to collapse
I don't have any better answer than my reply #12. Since the .017 says "US Carriers" on the page with the list of firmware, that's the one I use.