Officia Jelly Bean Update Notice-At&t Samsung Galaxy Note SGH-I717
- Thread starter Alerwisher
- Start date
It should be for any Note that has the I717 label. Since the Rogers Note is only the I717R version, it should apply.
I would check the Samsung site to verify.
Hoping that group messaging would have been resolved in 4.1.2. 4.2.2 has it working well. Overall performance is good - no multi window tasking on this version either. At least NFC is now working to transfer photos. Had to factory reset/wipe after upgrade (email and messaging crashing).
I had to reset to factory a couple times as mine starting rebooting on me. It's ok now...waiting on Note 3.
Sent from my SAMSUNG-SGH-I717 using Android Central Forums
Sent from my SAMSUNG-SGH-I717 using Android Central Forums
Well we didn't get Multi view and a few other things but we did get the following: write on calendar, handwriting emails, pop up browser, google now & a smoother interface.
After I got over the initial disappointment of not getting multi window, and after my phone stablized, I will say I'm glad I updated.
Sent from my SAMSUNG-SGH-I717 using Android Central Forums
After I got over the initial disappointment of not getting multi window, and after my phone stablized, I will say I'm glad I updated.
Sent from my SAMSUNG-SGH-I717 using Android Central Forums
How do you access Google Now? I know how to do it on my Nexus 7, but not on my Galaxy Note SGH-i717.
Long press home button and you will see three buttons at the bottom of your screen. It's the middle button. You can also place a shortcut (The blue Google icon) on you home screen. I placed the shortcut on the app bar so I always have easy access.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
If you disable voice talk, then long press the magnifying glass (one to the right), it will give you the option to set that for google (and that is google now).
I went to do the upgrade yesterday and when it got to the part where it was supposed to install the update, a little message popped up with something in a different language. When I clicked ok it just stopped the update. Any ideas?
This update eats battery up...not only that. My phone is now soooooo slow I want to scream. Can I revert to previous version or does anyone have advice? My phone is stock not rooted and everything updated via Kies....but it is not good for me at all 
Xingularity
Well-known member
- Sep 12, 2011
- 275
- 1
- 0
This update eats battery up...not only that. My phone is now soooooo slow I want to scream. Can I revert to previous version or does anyone have advice? My phone is stock not rooted and everything updated via Kies....but it is not good for me at all
Did you do a factory reset after updating?
Sent from my SAMSUNG-SGH-I717 using Android Central Forums
Please explain what you mean by "when your phone stabilized". I recently updated my Note to Jelly Bean, and it seems to run slower than before. Is this normal? Will it eventually run faster?
Yes it will return to normal function. After an update the media scanner has to read your media again. It usually takes 2 or 3 days to fully stabilize. My phone has had the update since the night before the official release and it works wonderfully now.
How to do the 4.1.2 Jelly Bean update without a hitch
I've owned a Samsung Captivate (SGH-i897), and a Samsung Infuse 4G (SGH-i997), and now an unusual situation has come-up whereby I'm going to be getting a brand new Galaxy Note (SGH-i717) so inexpensively that I can't pass it up and hold-out for the price of the Note II to come down once the Note III comes out. And that's cool, because the truth is that I kinda' like the Note better than the Note II. Go figure.
I'm 56 years old, and pushing 40 years in IT and high-tech management consulting; and so, as you can imagine, I always make sure that I know everything there is to know about any device I own. Even though I only found-out yesterday that I was going to get a new Note, I've already gotten up-to-speed on at least everything I need to know about doing an OS upgrade (it was easy, 'cause it's basically the same information I needed to know to OS upgrade both the Captivate and the Infuse), so I believe I can really help you folks, here in this thread, regarding OS upgrading the Note... yes, even though I haven't even gotten mine yet. Seriously. Trust me on this. I really do know.
The first and most important thing you need to know about any Samsung/AT&T OS upgrade is that the both Samsung and AT&T engineers do all their testing on phones exactly as they originally shipped from the factory; or, if there's already been an OS update, then they test on phones as shipped from the factory, and then OS updated before installing anything else on the phone. In other words, the never test on phones that have been in use for a while, and have had a bunch of apps and stuff installed on them. So that they always have a known starting point for all tests, all phones used for testing are always, always, always as shipped from the factory.
You wouldn't believe how important that is to know, because what it basically tells you is that before you go using Kies Mini to do an OS upgrade, you first need to get your phone back to the way it came shipped from the factory; or, if it's had previous updates, then back to the factory state for that particular previous update.
Some of you are complaining about your Note being slow after an update: That's because you didn't reset your phone back to factory state before doing the update. I've seen it a gabazillion times. Resetting the phone back to factory state immediately before performing an OS update also helps with the whole business of the phone "stabilizing" on account of the media scanner. I'm sorry... I don't mean to offend, but that whole business of taking a few days to "stabilize" is just hokum, anyway. Android phones don't work that way. Everything, regarding all aspects of the phone, is always pretty immediate. But even if it weren't; even if, in fact, there were some kind of weird three-day "stabilization" thing going on, factory resetting the phone immediately before doing an OS update would completely eliminate the need for something like that. Fortunately, since no three-day "stabilization" period is needed, regardless, it's all moot. Sorry. Again, don't mean to offend.
And when I say that one needs to factory reset immediately before doing an OS update, I mean immediately... as in, do the reset, and then immediately -- before configuring the phone, or installing anything on it, or using it -- do the OS update. No delays. Think of the factory reset, and the OS update as being, in effect, just two steps of the same process.
And by "factory reset," I mean a "GSM reset" (or what some call an "E2P Full" reset, on the Note), and not the kind of reset you can do by either pressing the right buttons in the phone settings area, or holding the power and volume rocker buttons. Those resets aren't "big" enough. You need to do a full "GSM" (or "E2P") reset. More on that in a moment; first, more preparation.
Before doing a reset, of course, you need to get everything off the phone that you might want to keep, because a GSM reset wipes the phone clean... and I mean really clean... exactly the way it was when it shipped from the factory. But since that step involves connecting the phone to the PC, first make sure that your Windows machine has the "Device(Install), USB Driver (Software) (ver.v1.5.14.0)" that's available on this web page (click on the "See All Downloads" link, then, scroll down a little and click on the "Software" link that's to the right of the "Manuals" link, and you'll see it there). Download and install it, then, again, reboot the computer, being patient to let it fully boot-up before doing any thing else on it... let the hard drive light settle down.
Now, back to the phone: If you have a good backup app on the phone, use it. Be sure to back-up ringtones, settings, emails, texts, contacts, side-loaded APK files... absolutely EVERYTHING that's on that phone, either in the internal storage, or the 13 or so gigabytes of the non-removable pseudo-external storage (part of the 16GB) that comes with the phone, and also any storage you may have on a 1, 2, 4, 8, 16 or 32GB truly external storage card. Connect the phone to the USB port of your computer and put it into file transfer mode and bygod get every last thing you can think of off of it, and onto your PC's local hard drive, in a backup folder of some kind, before you do the GSM reset!
Once you get the phone backed-up to your PC, disconnect the phone from the PC, and then reboot the PC. Wait for it to fully finish rebooting; don't rush it. Let the hard drive light calm down.
Then, if you have any version, at all, of KIES or KIES MINI installed on your PC, use something like REVO UNINSTALLER's strongest mode to fully uninstall all copies of KIES. Then reboot the machine again, again being patient and letting the hard drive light calm down so it's really and truly fully done booting up.
Make sure that you have -- if you still have it, and haven't lost it -- the original USB cable that came with the phone. If you don't, then at least make sure that whatever USB cable you use is either Samsung branded, or is guaranteed to be an absolute duplicate of the Samsung-branded USB cable; but do not plug it into either the phone or the PC yet.
Make sure that the battery in your phone is fully -- and I mean fully -- charged.
Just to play things safe, pause, and re-think through your phone backup procedure and make triple-net sure that you've bygod gotten every last thing that you could possibly need off of it. Remember that your Google Play store apps are all available to you to re-download once the phone's been updated; and the same should be true for Amazon apps. But if you've ever side-loaded one from some other site, then make sure you can either get at it again from said site, or make sure you back-up the APK file. Just make sure, one last time, that there's bygod nothing left on that phone that you're gonna' need, 'cause the GSM reset's gonna' blow it to smithereens! Just just take a moment.
Make sure, again, that the phone's battery is fully charged.
Make sure that the SIM card is in the phone.
Make sure that whatever external SD card you normally keep in the phone is, in fact, in the phone.
When you're certain that you can safely GSM reset the phone, here's how to do it:
Open the phone dialer like you're gonna make a call.
Dial this, exactly: *2767*3855#
The instant you dial that last pound sign (#), the phone will begin the GSM reset. DO NOT INTERRUPT IT. Set the phone down so you don't accidentally touch something. Just be patient while it does its thing!
When it boots back up, don't be too quick to start responding to it. Just let it sit on the table or desk for a little while and let it fully boot. After waiting a minute or so longer than you might have had I not just told you to, try to bypass all the questions the phone asks you when it's factory new... you know... your GMAIL address and whatever else. Just try to drop out of all that by pressing the "back" button however many times you need to to finally be dropped to the phone's centermost home screen.
Now, and only now, is your phone finally ready to have the Android 4.1.2 Jelly Bean OS update applied to it.
To do that, go to this web page...
How do I update my Samsung Galaxy Note to Android 4.1.2 Jelly Bean? : AT&T Cell Phones | Samsung
...and follow the instructions exactly... and I mean EXACTLY: Do not deviate one single bit from any part of it!
When you finish, your phone should reboot to a pristine, factory-new 4.1.2 Jelly Bean version. It should be fast, factory-fresh, and with no problems.
If the phone shipped from the factory with 4.1 Ice Cream Sandwich on it, so that this 4.1.2 Jelly Bean update is the first one you've tried using KIES, then it should go smoothly and work fine. However, if you bought the phone with 2.3 Gingerbread on it, and have already done one update to 4.0 Ice Cream Sandwich, then there's a possibility that your GSM reset won't really get the phone back to the same "factory" state as a phone that actually shipped from the factory with 4.0 Ice Cream Sandwich on it... especially if you didn't do a GSM reset first, before doing the earlier 4.0 Ice Cream Sandwish update.
If there are problems, yet everything happened as it was supposed to during the KIES installation and Jelly Bean update, then there's probably something wrong which re-performing all of the above steps probably won't fix... especially, again, if this 4.1.2 Jelly Bean update is actually the second one you've done to the phone.
If there was a problem during the KIES Jelly Bean update, then it's possible the phone is now too squirrely to either use, or even to re-try the steps.
Both those things said, if something's wrong, then it certainly can't hurt to at least try repeating the process by first unplugging the USB cable from the PC and then rebooting the PC, and letting it fully boot back up, letting the hard drive light setting down.
Then GSM reset the phone again.
Then retry all the steps on this web page...
How do I update my Samsung Galaxy Note to Android 4.1.2 Jelly Bean? : AT&T Cell Phones | Samsung
...making extra sure that you really get them right this time...
...and see if it makes a difference. It probably won't, but what the heck: you can't now hurt the phone anymore than it already is.
If retrying everything somehow magically makes everything okay, then count your lucky stars. However, since it probably won't, then here's what you need to know: AT&T has special device support centers located all over the country. Most people, almost no matter where they are in the US, are no more than an hour to maybe three hours drive from one. And boy-oh-boy do the tecnicians there know what they're doing! It's nothing like some halfway-technician at some AT&T store or dealer store fidding with your phone and maybe getting it right, and maybe not. The technicians at any of the official AT&T device centers are world class... best-of-breed.
All you have to do is find the one nearest you, and take your Note to it. Tell 'em the steps you took, and what happened; and ask 'em to please just redo it all for you, and get the phone properly reset and updated to 4.1.2 Jelly Bean.
Some centers will refuse to do updates; and, instead, will only put the phone back to the condition it was when it shippped from the factory. That's actually kinda' okay because at least it really and truly will be, as opposed to what the GSM reset does. It's a good place to start; and if that's all they'll do for you, then accept it and take the phone home and then re-try the above steps... including, yes, redoing the GSM reset, even though they already did the big brother of that at the device support center.
If you're lucky, though, the device support center people will completely fix the problem by first making the phone the way it was from the factory, then checking it out, then performing whatever updates it needs to finally get up to a pristine 4.1.2 Jelly Bean OS version. And then they'll hand it back to you. And I believe you'll pay them nothing for any of it! Gotta' like that.
To find your nearest AT&T device support center, go to this web page...
Warranty exchange locations - AT&T Wireless Support*
...and then scroll down to "Step 3." Find your state, and then download the list of device support center locations, and find the one nearest you. Forget everything else on that page. Just do what I tell you here.
It all seems like a lot, I know; but only by following my steps, here, and being really anally retentive about it all, will your OS update to 4.1.2 Jelly Bean go pretty much okay. The likelihood that you'll need to go to an AT&T device support center is small, but at least you know it's there and available to you if you do. And, trust me, it's the safety net! Whatever's wrong will positively get fixed there. Fear not.
Youj're free, of course, to listen to other people, but I wouldn't. I've been through this with two previous Galaxy-class (wow, that sounds like Star Trek, doesn't it?) phones; and I've posted stuff like this in other forums and had people doubt me and, eventually, they all come back and apologize and thank me for giving them the only procedure that actually works. So, act accordingly.
To make sure that you get it absolutely right, re-read this posting a time or two. Don't skip a single step... not a single reboot of either PC or phone. Do everything exactly as I've here described, in exactly that order, skipping nothing, rushing nothing, interrupting nothing.
If you do, the statistical probability that you'll come back here and write something like, "ohmygod, Gregg, it worked, flawlessly; my phone's fast as greased lightening; and everything's really cool!
When you restore things to your phone, be careful not to restore any system or OS files. Just restore data, music, movies, whatever. Import contacts, stuff like that.
If you've previously ROOTed your phone, then all bets are off. Who knows if any of the above will work; and don't ask me questions about it if you're working from a phone that's ever been rooted. You rooted it, so you're on your own. Only if your phone has never been rooted (although it's probably okay if it's been unlocked) will I answer your questions, here.
So... [sigh]... let's see... have I left anything out? I don't think so.
Good luck.
I've owned a Samsung Captivate (SGH-i897), and a Samsung Infuse 4G (SGH-i997), and now an unusual situation has come-up whereby I'm going to be getting a brand new Galaxy Note (SGH-i717) so inexpensively that I can't pass it up and hold-out for the price of the Note II to come down once the Note III comes out. And that's cool, because the truth is that I kinda' like the Note better than the Note II. Go figure.
I'm 56 years old, and pushing 40 years in IT and high-tech management consulting; and so, as you can imagine, I always make sure that I know everything there is to know about any device I own. Even though I only found-out yesterday that I was going to get a new Note, I've already gotten up-to-speed on at least everything I need to know about doing an OS upgrade (it was easy, 'cause it's basically the same information I needed to know to OS upgrade both the Captivate and the Infuse), so I believe I can really help you folks, here in this thread, regarding OS upgrading the Note... yes, even though I haven't even gotten mine yet. Seriously. Trust me on this. I really do know.
The first and most important thing you need to know about any Samsung/AT&T OS upgrade is that the both Samsung and AT&T engineers do all their testing on phones exactly as they originally shipped from the factory; or, if there's already been an OS update, then they test on phones as shipped from the factory, and then OS updated before installing anything else on the phone. In other words, the never test on phones that have been in use for a while, and have had a bunch of apps and stuff installed on them. So that they always have a known starting point for all tests, all phones used for testing are always, always, always as shipped from the factory.
You wouldn't believe how important that is to know, because what it basically tells you is that before you go using Kies Mini to do an OS upgrade, you first need to get your phone back to the way it came shipped from the factory; or, if it's had previous updates, then back to the factory state for that particular previous update.
Some of you are complaining about your Note being slow after an update: That's because you didn't reset your phone back to factory state before doing the update. I've seen it a gabazillion times. Resetting the phone back to factory state immediately before performing an OS update also helps with the whole business of the phone "stabilizing" on account of the media scanner. I'm sorry... I don't mean to offend, but that whole business of taking a few days to "stabilize" is just hokum, anyway. Android phones don't work that way. Everything, regarding all aspects of the phone, is always pretty immediate. But even if it weren't; even if, in fact, there were some kind of weird three-day "stabilization" thing going on, factory resetting the phone immediately before doing an OS update would completely eliminate the need for something like that. Fortunately, since no three-day "stabilization" period is needed, regardless, it's all moot. Sorry. Again, don't mean to offend.
And when I say that one needs to factory reset immediately before doing an OS update, I mean immediately... as in, do the reset, and then immediately -- before configuring the phone, or installing anything on it, or using it -- do the OS update. No delays. Think of the factory reset, and the OS update as being, in effect, just two steps of the same process.
And by "factory reset," I mean a "GSM reset" (or what some call an "E2P Full" reset, on the Note), and not the kind of reset you can do by either pressing the right buttons in the phone settings area, or holding the power and volume rocker buttons. Those resets aren't "big" enough. You need to do a full "GSM" (or "E2P") reset. More on that in a moment; first, more preparation.
Before doing a reset, of course, you need to get everything off the phone that you might want to keep, because a GSM reset wipes the phone clean... and I mean really clean... exactly the way it was when it shipped from the factory. But since that step involves connecting the phone to the PC, first make sure that your Windows machine has the "Device(Install), USB Driver (Software) (ver.v1.5.14.0)" that's available on this web page (click on the "See All Downloads" link, then, scroll down a little and click on the "Software" link that's to the right of the "Manuals" link, and you'll see it there). Download and install it, then, again, reboot the computer, being patient to let it fully boot-up before doing any thing else on it... let the hard drive light settle down.
Now, back to the phone: If you have a good backup app on the phone, use it. Be sure to back-up ringtones, settings, emails, texts, contacts, side-loaded APK files... absolutely EVERYTHING that's on that phone, either in the internal storage, or the 13 or so gigabytes of the non-removable pseudo-external storage (part of the 16GB) that comes with the phone, and also any storage you may have on a 1, 2, 4, 8, 16 or 32GB truly external storage card. Connect the phone to the USB port of your computer and put it into file transfer mode and bygod get every last thing you can think of off of it, and onto your PC's local hard drive, in a backup folder of some kind, before you do the GSM reset!
Once you get the phone backed-up to your PC, disconnect the phone from the PC, and then reboot the PC. Wait for it to fully finish rebooting; don't rush it. Let the hard drive light calm down.
Then, if you have any version, at all, of KIES or KIES MINI installed on your PC, use something like REVO UNINSTALLER's strongest mode to fully uninstall all copies of KIES. Then reboot the machine again, again being patient and letting the hard drive light calm down so it's really and truly fully done booting up.
Make sure that you have -- if you still have it, and haven't lost it -- the original USB cable that came with the phone. If you don't, then at least make sure that whatever USB cable you use is either Samsung branded, or is guaranteed to be an absolute duplicate of the Samsung-branded USB cable; but do not plug it into either the phone or the PC yet.
Make sure that the battery in your phone is fully -- and I mean fully -- charged.
Just to play things safe, pause, and re-think through your phone backup procedure and make triple-net sure that you've bygod gotten every last thing that you could possibly need off of it. Remember that your Google Play store apps are all available to you to re-download once the phone's been updated; and the same should be true for Amazon apps. But if you've ever side-loaded one from some other site, then make sure you can either get at it again from said site, or make sure you back-up the APK file. Just make sure, one last time, that there's bygod nothing left on that phone that you're gonna' need, 'cause the GSM reset's gonna' blow it to smithereens! Just just take a moment.
Make sure, again, that the phone's battery is fully charged.
Make sure that the SIM card is in the phone.
Make sure that whatever external SD card you normally keep in the phone is, in fact, in the phone.
When you're certain that you can safely GSM reset the phone, here's how to do it:
Open the phone dialer like you're gonna make a call.
Dial this, exactly: *2767*3855#
The instant you dial that last pound sign (#), the phone will begin the GSM reset. DO NOT INTERRUPT IT. Set the phone down so you don't accidentally touch something. Just be patient while it does its thing!
When it boots back up, don't be too quick to start responding to it. Just let it sit on the table or desk for a little while and let it fully boot. After waiting a minute or so longer than you might have had I not just told you to, try to bypass all the questions the phone asks you when it's factory new... you know... your GMAIL address and whatever else. Just try to drop out of all that by pressing the "back" button however many times you need to to finally be dropped to the phone's centermost home screen.
Now, and only now, is your phone finally ready to have the Android 4.1.2 Jelly Bean OS update applied to it.
To do that, go to this web page...
How do I update my Samsung Galaxy Note to Android 4.1.2 Jelly Bean? : AT&T Cell Phones | Samsung
...and follow the instructions exactly... and I mean EXACTLY: Do not deviate one single bit from any part of it!
When you finish, your phone should reboot to a pristine, factory-new 4.1.2 Jelly Bean version. It should be fast, factory-fresh, and with no problems.
If the phone shipped from the factory with 4.1 Ice Cream Sandwich on it, so that this 4.1.2 Jelly Bean update is the first one you've tried using KIES, then it should go smoothly and work fine. However, if you bought the phone with 2.3 Gingerbread on it, and have already done one update to 4.0 Ice Cream Sandwich, then there's a possibility that your GSM reset won't really get the phone back to the same "factory" state as a phone that actually shipped from the factory with 4.0 Ice Cream Sandwich on it... especially if you didn't do a GSM reset first, before doing the earlier 4.0 Ice Cream Sandwish update.
If there are problems, yet everything happened as it was supposed to during the KIES installation and Jelly Bean update, then there's probably something wrong which re-performing all of the above steps probably won't fix... especially, again, if this 4.1.2 Jelly Bean update is actually the second one you've done to the phone.
If there was a problem during the KIES Jelly Bean update, then it's possible the phone is now too squirrely to either use, or even to re-try the steps.
Both those things said, if something's wrong, then it certainly can't hurt to at least try repeating the process by first unplugging the USB cable from the PC and then rebooting the PC, and letting it fully boot back up, letting the hard drive light setting down.
Then GSM reset the phone again.
Then retry all the steps on this web page...
How do I update my Samsung Galaxy Note to Android 4.1.2 Jelly Bean? : AT&T Cell Phones | Samsung
...making extra sure that you really get them right this time...
...and see if it makes a difference. It probably won't, but what the heck: you can't now hurt the phone anymore than it already is.
If retrying everything somehow magically makes everything okay, then count your lucky stars. However, since it probably won't, then here's what you need to know: AT&T has special device support centers located all over the country. Most people, almost no matter where they are in the US, are no more than an hour to maybe three hours drive from one. And boy-oh-boy do the tecnicians there know what they're doing! It's nothing like some halfway-technician at some AT&T store or dealer store fidding with your phone and maybe getting it right, and maybe not. The technicians at any of the official AT&T device centers are world class... best-of-breed.
All you have to do is find the one nearest you, and take your Note to it. Tell 'em the steps you took, and what happened; and ask 'em to please just redo it all for you, and get the phone properly reset and updated to 4.1.2 Jelly Bean.
Some centers will refuse to do updates; and, instead, will only put the phone back to the condition it was when it shippped from the factory. That's actually kinda' okay because at least it really and truly will be, as opposed to what the GSM reset does. It's a good place to start; and if that's all they'll do for you, then accept it and take the phone home and then re-try the above steps... including, yes, redoing the GSM reset, even though they already did the big brother of that at the device support center.
If you're lucky, though, the device support center people will completely fix the problem by first making the phone the way it was from the factory, then checking it out, then performing whatever updates it needs to finally get up to a pristine 4.1.2 Jelly Bean OS version. And then they'll hand it back to you. And I believe you'll pay them nothing for any of it! Gotta' like that.
To find your nearest AT&T device support center, go to this web page...
Warranty exchange locations - AT&T Wireless Support*
...and then scroll down to "Step 3." Find your state, and then download the list of device support center locations, and find the one nearest you. Forget everything else on that page. Just do what I tell you here.
It all seems like a lot, I know; but only by following my steps, here, and being really anally retentive about it all, will your OS update to 4.1.2 Jelly Bean go pretty much okay. The likelihood that you'll need to go to an AT&T device support center is small, but at least you know it's there and available to you if you do. And, trust me, it's the safety net! Whatever's wrong will positively get fixed there. Fear not.
Youj're free, of course, to listen to other people, but I wouldn't. I've been through this with two previous Galaxy-class (wow, that sounds like Star Trek, doesn't it?) phones; and I've posted stuff like this in other forums and had people doubt me and, eventually, they all come back and apologize and thank me for giving them the only procedure that actually works. So, act accordingly.
To make sure that you get it absolutely right, re-read this posting a time or two. Don't skip a single step... not a single reboot of either PC or phone. Do everything exactly as I've here described, in exactly that order, skipping nothing, rushing nothing, interrupting nothing.
If you do, the statistical probability that you'll come back here and write something like, "ohmygod, Gregg, it worked, flawlessly; my phone's fast as greased lightening; and everything's really cool!
When you restore things to your phone, be careful not to restore any system or OS files. Just restore data, music, movies, whatever. Import contacts, stuff like that.
If you've previously ROOTed your phone, then all bets are off. Who knows if any of the above will work; and don't ask me questions about it if you're working from a phone that's ever been rooted. You rooted it, so you're on your own. Only if your phone has never been rooted (although it's probably okay if it's been unlocked) will I answer your questions, here.
So... [sigh]... let's see... have I left anything out? I don't think so.
Good luck.
Re: How to do the 4.1.2 Jelly Bean update without a hitch
Holy crap that is a lot of work, first for you...and next for us. So I like the "go to ATT" advice best. Does this mean to an ATT store, and will they ensure everything on my phone is saved to the SD?
Then another reply asked if I had done a factory reset after updating...was that in the instructions? It sounds as if it wouldn't be the proper step anyway, based on your instructions though.
My phone never "stabilized" and I haven't a lot of media on it, so I am not sure there is much hope without redoing it all. Which I am not sure I want to go thru by myself. UGH
Thanks for going to all this trouble!!
Holy crap that is a lot of work, first for you...and next for us. So I like the "go to ATT" advice best. Does this mean to an ATT store, and will they ensure everything on my phone is saved to the SD?
Then another reply asked if I had done a factory reset after updating...was that in the instructions? It sounds as if it wouldn't be the proper step anyway, based on your instructions though.
My phone never "stabilized" and I haven't a lot of media on it, so I am not sure there is much hope without redoing it all. Which I am not sure I want to go thru by myself. UGH
Thanks for going to all this trouble!!
Re: How to do the 4.1.2 Jelly Bean update without a hitch
Well, I've written it before, so at least some of it was just copy 'n paste.
And it's less work than you might think; but, whatever work it is is the kind of thing that technology, frankly, requires. The truth is that one must become at least a little bit anally retentive whenever they're doing some technological thing like this, else they have no right to expect good results. Forums like this are filled, for every Android phone model that's capable of an update like this, with posts by people who say it made their phone worse, or slow, or squirrely, or whatever; and, I promise you, that it was because they didn't break down and do what even I agree is sphincter-clenchingly stressful (for those not used to it) and irritatingly detailed steps to actually get some computer-related thing right. Half the tech guys out there making a living working on people's Windows and Mac computers aren't doing anything that the end-user couldn't have done if s/he had just had the patience and properly-anally-retentive attitude! [grin]
No. I never said store. I was clear in what I wrote about it not being a store. It's an "AT&T Device Support Center," which is an entirely different animal; and I provided the link to find the page where you can see your state on a list and download the PDF file which shows you where are the AT&T device support centers in your state. It may be right in your town, or it may be half your state's length's or width's drive away. And, trust me, they don't care about your data or anything else. That's your responsibility, and they become irritated if you even bring it up. These are hard core technicians, there to help as many people sitting in those waiting room chairs as possible, and as fast as possible; each of them with sometimes very serious problems. They're not there to pussyfoot around and/or hold the customer's hand. They're there to plug the customer's phone into some very special both testing and remediation equipment and figure out what it needs, and then do to it whatever that happens to be. They hand back to people basically reset and tested/checked-out phones that are pretty much as they came from the factory, more or less, and then they send you on your way.
They used to even refuse to do updates (and many of them still do), but there have been so many people have their updates fail, or have KIES fail, that some AT&T device support center managers have decided to help people with their updates, too. Still, it's by no stretch of the imagination anything like an AT&T either factory or dealer store. No one smiles or is really all that nice, frankly. They just fix what's wrong and that's the end of it. If your data or any other information gets lost in the process, then tough tomatoes.
So then, bottom line, you still have to do the work of backing-up the phone to the Windows PC. No one should ever dare do an Android OS update/upgrade without fully backing-up everything; or, also, without doing a factory reset... preferably the biggest "GSM reset" kind.
Certainly a factory reset -- preferably of the most serious "GSM reset" type that I described in my steps -- must be done just before (and I mean just before) performing the OS update via KIES. There are two other kinds of "factory" resets: One accessible from the phone's "settings" area, and the other which may be accessed by a certain way of holding-down both the power button and the volume rocker while the phone's powering-up...
...neither one of those methods I want anyone to do if they're following my instructions. What needs to be done is a true, harshest-of-the-reset-methods "GSM reset" doing the dial keypad presses that I described. So doing also sends a signal to AT&T's system which kinda' flushes-out a thing or two tied to both the phone's EIN number, and the account tied to the SIM card that's in the phone (if, in fact, there's one there), that could be slightly technically helpful when firing-up the phone under the new, updated/upgraded OS version. A GSM reset does not, though, change or hurt anything stored on the SIM card. It simply resets a couple of reallly minor -- and probably inconsequential -- things in the AT&T system tied to the phone's EIN, and also to its SIM if present. And, of course, it does those things in addition to basically wiping your phone and all of its both internal and external memory completely clean, and reformatting things, and resetting all apps back to original factory state, and making the phone think it just came fresh off the factory floor! That's what one needs to do before attempting any OS update/upgrade!
Now, as for doing one immediatelly after the OS update/upgrade using KIES... hmmm.... well, as long as you do it immediately after KIES is done, and you're sure that the phone's fully and correctly updated/upgrade, yet you haven't yet told the phone anything about yourself of your email address or your account or anything; and you've not yet transferred or keyed any date into the newly-updated/upgraded phone yet, then doing yet another GSM reset certainly couldn't hurt. It's not really necessary, though. Rebooting the phone, once KIES gets all the new OS files onto it, is part of the process; and when it finishes booting-up, it's ready for use. Believe it or not, powering-down the phone, then removing the battery from it, then waiting like a half hour, then putting the battery back in and powering it up again would almost be more beneficial; and for much the same kinds of reasons as I prescribed rebooting the Windows machine in preparation for the KIES update process.
Speaking of the battery, once the OS update/upgrade is done, the battery needs to be recalibrated in order for how much juice it allegedly does or doesn't have in it to be more or less accurate. It's a simple process which I can cover if anyone wants to do it. Let me know. But now I've digressed. Sorry.
Well, of course, the whole "stabilizing" thing -- especially it taking several days -- is just tantamount to witchcraft. There's no such thing. Just go ahead and get that one out of your head, right now. [grin]
If you've had what appears to be a failed update, then you're the perfect candidate for taking the phone to the AT&T device support center nearest you (even if it means having to cross over into a neighboring state) and just letting them bail you out of it. They don't like it when people come in with perfectly functional phones, and they ask the tecnicians to perform the OS update/upgrade for them. That, the device support center people don't like; and it's usually those people who are told that AT&T Device Support Centers don't do that. But if you've tried to perform your update, and the phone's now worse, and slow, and clearly something's wrong, they by all mean get that phone over to an AT&T device support center (not a store, but one of the hard-core, serious-technician-occupied device support centers) and have them get you squared away.
Only if the phone's actually broken, somehow, at the hardware level, will they say something to you like that your only choice is to replace the phone. If it's under warrantey, then they'll replace it right then and there, but, sadly, with a refurbished one. Fortunately, they're Samsung-, and not AT&T-refurbished, so, honestly, they're pretty much good as new... as good , at least, as your phone that broke was! Most of the time, though, the phone's fine, at the hardware level, but it just got goofed-up from either something like someone who didn't know what they were doing rooting it, or a failed KIES update/upgrade, etc. There are also some fairly serious viruses out there that could squirrel a phone pretty good under the right circumstances, but, honestly, even that's just so, so rare. And with two simple pieces of software -- one free, and the other free, too, unless you'd like real-time automatic monitoring and a few other features, then it costs a tiny bit of money to purchase -- I could show you how to protect your phone from all the nasties without you having to so much as break a sweat.
But if you're phone's currently a mess, then first things first: Yes, I suppose you could try to repeat the OS update/upgrade using my steps; but the thing is that if the reason it's messed-up is because KIES mini didn't really do a good job (and most of the time that's because there wasn't a propery GSM reset performed before KIES mine was employed to perform the OS update/upgrade), then it's possible that the files on your phone are a weird hybrid of those from the new updated/upgraded OS, plus also from the old, pre-update/upgrade OS. And that, then is why the phone's acting weird. If that's the case, then there's no pristine OS of either version on the phone to which to restore during the GSM reset. The phone, at that point, needs what only a technician at an AT&T device support center can do.
So you may as well just stop screwing around with it and get the phone over to it and let them do the voodoo that they do, and bail you outta' this mess. It may be the quickest and easiest thing to do, at this point. Life's short, remember. When a device manufacturer gives you instructions, and you're pretty sure you followed them, and the device is made worse, then it becomes said manufacturer's responsibility. In this case, of course, Samsung is the manufacturer; but because phones, in the end, are tied directly to a carrier's service, and even often bear its brand name, the carrier -- AT&T in this case -- effectively becomes the manufacturer, for purposes such as yours. Go go get in the car and take the phone to 'em and hold 'em accountable! That's what they're there for.
No problem. Happy to help... or to try, at least.
Good luck to you!
Well, I've written it before, so at least some of it was just copy 'n paste.
And it's less work than you might think; but, whatever work it is is the kind of thing that technology, frankly, requires. The truth is that one must become at least a little bit anally retentive whenever they're doing some technological thing like this, else they have no right to expect good results. Forums like this are filled, for every Android phone model that's capable of an update like this, with posts by people who say it made their phone worse, or slow, or squirrely, or whatever; and, I promise you, that it was because they didn't break down and do what even I agree is sphincter-clenchingly stressful (for those not used to it) and irritatingly detailed steps to actually get some computer-related thing right. Half the tech guys out there making a living working on people's Windows and Mac computers aren't doing anything that the end-user couldn't have done if s/he had just had the patience and properly-anally-retentive attitude! [grin]
No. I never said store. I was clear in what I wrote about it not being a store. It's an "AT&T Device Support Center," which is an entirely different animal; and I provided the link to find the page where you can see your state on a list and download the PDF file which shows you where are the AT&T device support centers in your state. It may be right in your town, or it may be half your state's length's or width's drive away. And, trust me, they don't care about your data or anything else. That's your responsibility, and they become irritated if you even bring it up. These are hard core technicians, there to help as many people sitting in those waiting room chairs as possible, and as fast as possible; each of them with sometimes very serious problems. They're not there to pussyfoot around and/or hold the customer's hand. They're there to plug the customer's phone into some very special both testing and remediation equipment and figure out what it needs, and then do to it whatever that happens to be. They hand back to people basically reset and tested/checked-out phones that are pretty much as they came from the factory, more or less, and then they send you on your way.
They used to even refuse to do updates (and many of them still do), but there have been so many people have their updates fail, or have KIES fail, that some AT&T device support center managers have decided to help people with their updates, too. Still, it's by no stretch of the imagination anything like an AT&T either factory or dealer store. No one smiles or is really all that nice, frankly. They just fix what's wrong and that's the end of it. If your data or any other information gets lost in the process, then tough tomatoes.
So then, bottom line, you still have to do the work of backing-up the phone to the Windows PC. No one should ever dare do an Android OS update/upgrade without fully backing-up everything; or, also, without doing a factory reset... preferably the biggest "GSM reset" kind.
Certainly a factory reset -- preferably of the most serious "GSM reset" type that I described in my steps -- must be done just before (and I mean just before) performing the OS update via KIES. There are two other kinds of "factory" resets: One accessible from the phone's "settings" area, and the other which may be accessed by a certain way of holding-down both the power button and the volume rocker while the phone's powering-up...
...neither one of those methods I want anyone to do if they're following my instructions. What needs to be done is a true, harshest-of-the-reset-methods "GSM reset" doing the dial keypad presses that I described. So doing also sends a signal to AT&T's system which kinda' flushes-out a thing or two tied to both the phone's EIN number, and the account tied to the SIM card that's in the phone (if, in fact, there's one there), that could be slightly technically helpful when firing-up the phone under the new, updated/upgraded OS version. A GSM reset does not, though, change or hurt anything stored on the SIM card. It simply resets a couple of reallly minor -- and probably inconsequential -- things in the AT&T system tied to the phone's EIN, and also to its SIM if present. And, of course, it does those things in addition to basically wiping your phone and all of its both internal and external memory completely clean, and reformatting things, and resetting all apps back to original factory state, and making the phone think it just came fresh off the factory floor! That's what one needs to do before attempting any OS update/upgrade!
Now, as for doing one immediatelly after the OS update/upgrade using KIES... hmmm.... well, as long as you do it immediately after KIES is done, and you're sure that the phone's fully and correctly updated/upgrade, yet you haven't yet told the phone anything about yourself of your email address or your account or anything; and you've not yet transferred or keyed any date into the newly-updated/upgraded phone yet, then doing yet another GSM reset certainly couldn't hurt. It's not really necessary, though. Rebooting the phone, once KIES gets all the new OS files onto it, is part of the process; and when it finishes booting-up, it's ready for use. Believe it or not, powering-down the phone, then removing the battery from it, then waiting like a half hour, then putting the battery back in and powering it up again would almost be more beneficial; and for much the same kinds of reasons as I prescribed rebooting the Windows machine in preparation for the KIES update process.
Speaking of the battery, once the OS update/upgrade is done, the battery needs to be recalibrated in order for how much juice it allegedly does or doesn't have in it to be more or less accurate. It's a simple process which I can cover if anyone wants to do it. Let me know. But now I've digressed. Sorry.
Well, of course, the whole "stabilizing" thing -- especially it taking several days -- is just tantamount to witchcraft. There's no such thing. Just go ahead and get that one out of your head, right now. [grin]
If you've had what appears to be a failed update, then you're the perfect candidate for taking the phone to the AT&T device support center nearest you (even if it means having to cross over into a neighboring state) and just letting them bail you out of it. They don't like it when people come in with perfectly functional phones, and they ask the tecnicians to perform the OS update/upgrade for them. That, the device support center people don't like; and it's usually those people who are told that AT&T Device Support Centers don't do that. But if you've tried to perform your update, and the phone's now worse, and slow, and clearly something's wrong, they by all mean get that phone over to an AT&T device support center (not a store, but one of the hard-core, serious-technician-occupied device support centers) and have them get you squared away.
Only if the phone's actually broken, somehow, at the hardware level, will they say something to you like that your only choice is to replace the phone. If it's under warrantey, then they'll replace it right then and there, but, sadly, with a refurbished one. Fortunately, they're Samsung-, and not AT&T-refurbished, so, honestly, they're pretty much good as new... as good , at least, as your phone that broke was! Most of the time, though, the phone's fine, at the hardware level, but it just got goofed-up from either something like someone who didn't know what they were doing rooting it, or a failed KIES update/upgrade, etc. There are also some fairly serious viruses out there that could squirrel a phone pretty good under the right circumstances, but, honestly, even that's just so, so rare. And with two simple pieces of software -- one free, and the other free, too, unless you'd like real-time automatic monitoring and a few other features, then it costs a tiny bit of money to purchase -- I could show you how to protect your phone from all the nasties without you having to so much as break a sweat.
But if you're phone's currently a mess, then first things first: Yes, I suppose you could try to repeat the OS update/upgrade using my steps; but the thing is that if the reason it's messed-up is because KIES mini didn't really do a good job (and most of the time that's because there wasn't a propery GSM reset performed before KIES mine was employed to perform the OS update/upgrade), then it's possible that the files on your phone are a weird hybrid of those from the new updated/upgraded OS, plus also from the old, pre-update/upgrade OS. And that, then is why the phone's acting weird. If that's the case, then there's no pristine OS of either version on the phone to which to restore during the GSM reset. The phone, at that point, needs what only a technician at an AT&T device support center can do.
So you may as well just stop screwing around with it and get the phone over to it and let them do the voodoo that they do, and bail you outta' this mess. It may be the quickest and easiest thing to do, at this point. Life's short, remember. When a device manufacturer gives you instructions, and you're pretty sure you followed them, and the device is made worse, then it becomes said manufacturer's responsibility. In this case, of course, Samsung is the manufacturer; but because phones, in the end, are tied directly to a carrier's service, and even often bear its brand name, the carrier -- AT&T in this case -- effectively becomes the manufacturer, for purposes such as yours. Go go get in the car and take the phone to 'em and hold 'em accountable! That's what they're there for.
Thanks for going to all this trouble!!
No problem. Happy to help... or to try, at least.
Good luck to you!
Similar threads
Trending Posts
-
Pixel 10 /pixel watch purchase- Started by newtda513
- Replies: 3
-
-
Who's ordering the Pixel 10?
- Started by mustang7757
- Replies: 88
-
What did you think of the live event and Jimmy Fallon?- Started by Snareman
- Replies: 21
Facebook
Twitter
Instagram