• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Can't get Infuse to update to GB

OK. I'm new to this site.

I've never updated or attempted to update my phone.

Currently i'm having issues with my infuse. It started happening yesterday.
Basically when i turn the screen off or i guess powering it down, then when i turn the phone on to put in my password and touch the "ok", my screen freezes and i have to take the battery out. Basically resetting it.

I figure if i can update to gb it may help. Well i hope.

So, from what i can get from your earlier posts, DL the keis mini from samsungs website, then do the hard reset by putting in that number code, plug in the usb from my pc and start the upgrade?

Again i've never attempted this so hopefully maybe you can clear it up again.

Thanks.
 
Also, would it be easier to go onto samsungs website and use their tutorial?

Or will it cause problems like others had with their updates?
 
So, from what i can get from your earlier posts, DL the keis mini from samsungs website, then do the hard reset by putting in that number code, plug in the usb from my pc and start the upgrade?

Also, would it be easier to go onto samsungs website and use their tutorial? Or will it cause problems like others had with their updates?

No, you're right about the tutorial (actually, I call them instructions). As I recall... er... wait... lemmee look it up, to be sure... stand-by...

[moments pass]

...okay, it's these (click here) instructions that you follow...

...and I mean FOLLOW... as in EXACTLY; do not miss a single syllable or deviate from a single part of it. Not one!

But here's the thing that's not in those instructions: You need to do the GSM reset first! And only then immediately -- and I mean immediately (after the GSM reset) -- follow those instructions, to the letter.

If you do that, and there are no errors and/or nothing freezes or anything, then a more or less perfect Gingerbread upgrade should result.

Be sure to back-up anything you need from your 2.2 Froyo installation to your Windows machine's hard drive first. Simply syncing things like contacts with your GMAIL account should be enough to cover that, but you may have ringtones, browser bookmarks, and other stuff that you'd like to back-up; and I think I covered, earlier in this thread, what I consider to be the best back-up app for that purpose. If not, just ask.

A caveat: KIES Mini apparently only works on 32-bit Windows. Since I had used my wife's 32-bit Vista machine when I upgraded my phone (my 64-bit Win7 machine was in my briefcase and I was too lazy to fire it up), everything went well; and so I didn't even realize, 'til I read others commenting about it, that KIES Mini doesn't run well -- or maybe not even at all -- on 64-bit Windows. So, if your machine is even remotely new, then it'll almost certainly be 64-bit, and so you'll likely need to go find a machine with 32-bit Windows on it... likely a Vista or maybe even an older XP machine. There are some Win7 machines out there which are, for some reason, 32-bit, but good luck finding one. If you find a 32-bit Win7 machine it'll likely be an older one that originally shipped running XP, and then got upgraded. And that would work fine... but I'm just sayin' that finding a 32-bit Win7 machine will be a challenge. If all else fails, a local, mom-and-pop computer repair store/shop will likely have a 32-bit Windows XP, Vista or maybe even Win7 machine sitting around; or, alternatively, it will likely have a 32-bit copy of Win7 on an installation DVD that it could install on a virtual machine for you or something. Be prepared to pay a fee, of course... hopefully an only small one.

If Samsung had used its head, it would have made a Linux version of KIES Mini available as part of an ISO file which included a bootable Linux distribution so that all a person would need to do is download the ISO, burn it, bootably, to a CD using readily-available freeware; then just leave the CD in the drive and turn off the machine, then back on again, allowing it to boot from the CD into Linux, which would then go straight into a fully-automated routine that just walks the user through the process, easy as pie. Then, at the end, the CD gets removed, and the machined turned off, then on again, whereupon it would reboot back into normal Windows. Then no one would have to worry about 32-bit versus 64-bit because a 32-bit copy of Linux will boot as 32-bit, even on 64-bit hardware. Actually, so will a 32-bit copy of Windows, but most people with 64-bit machines don't have the installation CD for that lying around.

Of course, if Samsung had really used its head, it would have... oh... I dunno... how 'bout MADE A 64-BIT VERSION OF KIES MINI, TOO, maybe! Did anyone at Samsung... you know... think of that?

<sarcasm>Yes, it's a bleeding edge concept, I know... far too much to ask of Samsung; but I'm just sayin'.</sarcasm>

Hope that helps!


_____________________________
 
I have a 6 or 7yr old pc lol. Im still on win xp pro. 32 bit.

I made sure i backed everything onto my pc. Basically copied everything and pasted to my pc hd.

So assuming i mess up and there is an error. Do u have to do the gsm reset and start all over again
I've read that people still had problems when upgrading to gb. But i assume if u follow samsungs direction.

Also do u need to take out ur sd card?

Thanks

No, you're right about the tutorial (actually, I call them instructions). As I recall... er... wait... lemmee look it up, to be sure... stand-by...

[moments pass]

...okay, it's these (click here) instructions that you follow...

...and I mean FOLLOW... as in EXACTLY; do not miss a single syllable or deviate from a single part of it. Not one!

But here's the thing that's not in those instructions: You need to do the GSM reset first! And only then immediately -- and I mean immediately (after the GSM reset) -- follow those instructions, to the letter.

If you do that, and there are no errors and/or nothing freezes or anything, then a more or less perfect Gingerbread upgrade should result.

Be sure to back-up anything you need from your 2.2 Froyo installation to your Windows machine's hard drive first. Simply syncing things like contacts with your GMAIL account should be enough to cover that, but you may have ringtones, browser bookmarks, and other stuff that you'd like to back-up; and I think I covered, earlier in this thread, what I consider to be the best back-up app for that purpose. If not, just ask.

A caveat: KIES Mini apparently only works on 32-bit Windows. Since I had used my wife's 32-bit Vista machine when I upgraded my phone (my 64-bit Win7 machine was in my briefcase and I was too lazy to fire it up), everything went well; and so I didn't even realize, 'til I read others commenting about it, that KIES Mini doesn't run well -- or maybe not even at all -- on 64-bit Windows. So, if your machine is even remotely new, then it'll almost certainly be 64-bit, and so you'll likely need to go find a machine with 32-bit Windows on it... likely a Vista or maybe even an older XP machine. There are some Win7 machines out there which are, for some reason, 32-bit, but good luck finding one. If you find a 32-bit Win7 machine it'll likely be an older one that originally shipped running XP, and then got upgraded. And that would work fine... but I'm just sayin' that finding a 32-bit Win7 machine will be a challenge. If all else fails, a local, mom-and-pop computer repair store/shop will likely have a 32-bit Windows XP, Vista or maybe even Win7 machine sitting around; or, alternatively, it will likely have a 32-bit copy of Win7 on an installation DVD that it could install on a virtual machine for you or something. Be prepared to pay a fee, of course... hopefully an only small one.

If Samsung had used its head, it would have made a Linux version of KIES Mini available as part of an ISO file which included a bootable Linux distribution so that all a person would need to do is download the ISO, burn it, bootably, to a CD using readily-available freeware; then just leave the CD in the drive and turn off the machine, then back on again, allowing it to boot from the CD into Linux, which would then go straight into a fully-automated routine that just walks the user through the process, easy as pie. Then, at the end, the CD gets removed, and the machined turned off, then on again, whereupon it would reboot back into normal Windows. Then no one would have to worry about 32-bit versus 64-bit because a 32-bit copy of Linux will boot as 32-bit, even on 64-bit hardware. Actually, so will a 32-bit copy of Windows, but most people with 64-bit machines don't have the installation CD for that lying around.

Of course, if Samsung had really used its head, it would have... oh... I dunno... how 'bout MADE A 64-BIT VERSION OF KIES MINI, TOO, maybe! Did anyone at Samsung... you know... think of that?

<sarcasm>Yes, it's a bleeding edge concept, I know... far too much to ask of Samsung; but I'm just sayin'.</sarcasm>

Hope that helps!


_____________________________
Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
 
So assuming i mess up and there is an error. Do u have to do the gsm reset and start all over again

I've read that people still had problems when upgrading to gb. But i assume if u follow samsungs direction.

Also do u need to take out ur sd card?

If you follow the instructions to which I linked you, and you execute them immediately after doing the GSM reset, it's quite unlikely that you'll "mess up" or that there'll be "an error."

If the update does get goofed-up, though, and crashes in some way before it completes, then whether you can recover, and begin again, will depend on how much of the update took. If the phone ends-up with some kind of mixture of 2.2 Froyo and 2.3 Gingerbread on it, then a GSM reset will probably not work; will reset the phone to a weird hybrid state which KIES Mini may or may not be able to update on its second try.

Fortunately, a screw-up like that is rare as... well... its astronomically rare. So I just don't think you need to worry about it. However, if that worst case happens, it's still recoverable; it's just that you'd have to take the phone to an A&T support center and have them restore the phone to a pristine copy of 2.2 Froyo. The support centers won't do a 2.3 Gingerbread update (er... well... unless maybe you find a tech who's got a big heart, and is working without his/her supervisor around or something), and so you'd need to have them put it back to factory state, the way it came in the box; then drive home and do the 2.3 Gingerbread update using KIES Mini.

But, honestly, that's almost certainly not gonna' happen... at least as long as you, seriously, just follow the instructions to the letter. It's not rocket science. You'll be fine.

The reason I made such a big deal out of it, and talked about the persnicketyness of it all and stuff is because people don't take it seriously. They think that they can just plug the phone in, as is, to the 32-bit Windows machine, without any GSM reset, and do the 2.3 Gingerbread update. And that, for sure, won't work. Period.

All the bad stories you've heard about 2.3 Gingerbread not working, or sucking, or being worse than 2.2 Froyo...

...every last one of them was from the 2.3 Gingerbread update being performed on a phone that wasn't reset first. The AT&T and Samsung engineers tested the 2.3 Gingerbread update on pristine, out-of-the-box copies of 2.2 Froyo. By the time a phone's been in use for a while, the 2.2 Froyo installation is all different from how it came out of the box... just different enough that the 2.3 Gingerbread update/upgrade just doesn't end-up quite right; and so the phone, then becomes squirrely.

I have been prescribing doing the GSM update immediately prior to doing the 2.3 Ginbread update because I'm trying to get people to put the phone back the way it came new, from the factory: a pristine 2.2 Froyo installation, as if the phone's just out of the box. And the reason is because every test that the AT&T and Samsung engineers did on the 2.3 Gingerbread update was done on a factory-new, never been used 2.2 Froyo installation. They had to do it that way, else they'd have no known starting point and so wouldn't know what went wrong if the 2.3 Gingerbread update failed. I've done that kind of testing in my career. You always have to start from a known point, else you're just blind when troubleshooting.

That's why the 2.3 Gingerbread updates done to factory-new and pristine 2.2 Froyo phones, restored to that state even after a year or two of use by doing a GSM reset, always work; and 2.3 Gingerbread updates done to 2.2 Froyo phones that have been in use for a while, without first being GSM reset, nearly always have glitches. Some people have only a glitch or two, and they're so mintor that they're happy. Others report nearly nightmarish results. And for a few, said nightmarish results are so nightmarish, and the phone's so goofed-up, that even trying a GSM reset, once it's that bad, won't work. Fortunately, a quick trip to the nearest AT&T support center (and I'm not talking a dealer, but an AT&T corporate support center), and the kind of restoral of the phone to 2.2 Froyo that only those guys can do, will put things right back where they need to be.

The other thing to remember is that a lot of these guy out there are rooting their phones; then they try to do the 2.3 Gingerbread update, and they wonder why it fails. Rooting so goofs around with the deepest bowels of the phone that godonlyknows what'll happen if either a GSM reset, or a 2.3 Gingerbread update is attempted. Then those idiots get into forums and leave out that they so messed with the phone's little brains before they tried the 2.3 Gingerbread update that it's a wonder the thing even boots. Don't be misled by those idiots.

And never root a phone. Yes, in the hands of a master, a rooted phone can do amazing things; but at what cost? Who has time for all the fiddling you have to do; and all the researching what the symptoms and error messages mean? The only people who get anything out of rooting phones is young people who find it fascinating, and learn stuff from it, and get a charge out of mastering it and doing cool stuff with it. I was like that too, once; started-out when I was in grade school and my parents came home to find the big console TV in the living room all torn apart and in a gabazillion pieces. I was so proud -- and learned a ton -- when I put it back together and it actually worked. And that sense of conquering the technology stayed with me for the first 15 or so years of my now nearly 40-year-long IT career.

But I just want stuff to work, now; and don't give a rat's youknowwhat how the technology achieves it. I know I can spend a Saturday with virtually any technology and figure it out and master it and awe people. So what? Who do I see about getting that Saturday back?

Never root a phone. Keep it the way Samsung and AT&T shipped it; that way you can hold them accountable when it doesn't do what they promised; and you can also always restore the phone to the way they shipped it to you with such as a GSM reset so you can get to the same starting point that they used when they created and tested the 2.3 Gingerbread update/upgrade that you're getting ready to perform. Again... I can't stress this enough: NEVER ROOT A PHONE! That way you'll never be one of the idiots in the forums asking why their phone's doing such-and-such instead of spending quality time with your family, or walking your dog on the beach, or...

...well... just read the message on my website.

The GSM Reset and then the immediate 2.3 Gingerbread update should be done with whatever SD card in it that you intend to use in it once you've got 2.3 Gingerbread up and running, and you're beginning to restore stuff to your phone, and reinstall apps, etc.

Also, try to use the USB cable that came with the phone. Others will likely work, but every now and then I'll hear about somebody who thought s/he could save a buck by buying some super-cheap cable that comes from such as one of Amazon's resellers who just puts it into a Glad-brand sandwich back, with a hand-written label on it. Some of those cables don't even have continuity on all the pins. If you no longer have the cable that came with the phone, at least use one that's made by one of the big-name makers... Belkin, maybe... or anything with an AT&T or Samsung label on it. Sorry I forgot to mention that earlier... though I already might have, earlier in this, or one of the other threads I've got on this subject floating around out there on the various forums.

Just be cool. Take it one step at a time. Don't rush things. Follow the instructions. Everything will be fine.

And I trust you'll report back and let us know how it went.

Lookin' forward to it.


Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
 
I was curious how long does it take to upgrade to GB?

It's been like almost 20 minutes and stuck at 42%.

I felt something wrong was going to happen:(

If you follow the instructions to which I linked you, and you execute them immediately after doing the GSM reset, it's quite unlikely that you'll "mess up" or that there'll be "an error."

If the update does get goofed-up, though, and crashes in some way before it completes, then whether you can recover, and begin again, will depend on how much of the update took. If the phone ends-up with some kind of mixture of 2.2 Froyo and 2.3 Gingerbread on it, then a GSM reset will probably not work; will reset the phone to a weird hybrid state which KIES Mini may or may not be able to update on its second try.

Fortunately, a screw-up like that is rare as... well... its astronomically rare. So I just don't think you need to worry about it. However, if that worst case happens, it's still recoverable; it's just that you'd have to take the phone to an A&T support center and have them restore the phone to a pristine copy of 2.2 Froyo. The support centers won't do a 2.3 Gingerbread update (er... well... unless maybe you find a tech who's got a big heart, and is working without his/her supervisor around or something), and so you'd need to have them put it back to factory state, the way it came in the box; then drive home and do the 2.3 Gingerbread update using KIES Mini.

But, honestly, that's almost certainly not gonna' happen... at least as long as you, seriously, just follow the instructions to the letter. It's not rocket science. You'll be fine.

The reason I made such a big deal out of it, and talked about the persnicketyness of it all and stuff is because people don't take it seriously. They think that they can just plug the phone in, as is, to the 32-bit Windows machine, without any GSM reset, and do the 2.3 Gingerbread update. And that, for sure, won't work. Period.

All the bad stories you've heard about 2.3 Gingerbread not working, or sucking, or being worse than 2.2 Froyo...

...every last one of them was from the 2.3 Gingerbread update being performed on a phone that wasn't reset first. The AT&T and Samsung engineers tested the 2.3 Gingerbread update on pristine, out-of-the-box copies of 2.2 Froyo. By the time a phone's been in use for a while, the 2.2 Froyo installation is all different from how it came out of the box... just different enough that the 2.3 Gingerbread update/upgrade just doesn't end-up quite right; and so the phone, then becomes squirrely.

I have been prescribing doing the GSM update immediately prior to doing the 2.3 Ginbread update because I'm trying to get people to put the phone back the way it came new, from the factory: a pristine 2.2 Froyo installation, as if the phone's just out of the box. And the reason is because every test that the AT&T and Samsung engineers did on the 2.3 Gingerbread update was done on a factory-new, never been used 2.2 Froyo installation. They had to do it that way, else they'd have no known starting point and so wouldn't know what went wrong if the 2.3 Gingerbread update failed. I've done that kind of testing in my career. You always have to start from a known point, else you're just blind when troubleshooting.

That's why the 2.3 Gingerbread updates done to factory-new and pristine 2.2 Froyo phones, restored to that state even after a year or two of use by doing a GSM reset, always work; and 2.3 Gingerbread updates done to 2.2 Froyo phones that have been in use for a while, without first being GSM reset, nearly always have glitches. Some people have only a glitch or two, and they're so mintor that they're happy. Others report nearly nightmarish results. And for a few, said nightmarish results are so nightmarish, and the phone's so goofed-up, that even trying a GSM reset, once it's that bad, won't work. Fortunately, a quick trip to the nearest AT&T support center (and I'm not talking a dealer, but an AT&T corporate support center), and the kind of restoral of the phone to 2.2 Froyo that only those guys can do, will put things right back where they need to be.

The other thing to remember is that a lot of these guy out there are rooting their phones; then they try to do the 2.3 Gingerbread update, and they wonder why it fails. Rooting so goofs around with the deepest bowels of the phone that godonlyknows what'll happen if either a GSM reset, or a 2.3 Gingerbread update is attempted. Then those idiots get into forums and leave out that they so messed with the phone's little brains before they tried the 2.3 Gingerbread update that it's a wonder the thing even boots. Don't be misled by those idiots.

And never root a phone. Yes, in the hands of a master, a rooted phone can do amazing things; but at what cost? Who has time for all the fiddling you have to do; and all the researching what the symptoms and error messages mean? The only people who get anything out of rooting phones is young people who find it fascinating, and learn stuff from it, and get a charge out of mastering it and doing cool stuff with it. I was like that too, once; started-out when I was in grade school and my parents came home to find the big console TV in the living room all torn apart and in a gabazillion pieces. I was so proud -- and learned a ton -- when I put it back together and it actually worked. And that sense of conquering the technology stayed with me for the first 15 or so years of my now nearly 40-year-long IT career.

But I just want stuff to work, now; and don't give a rat's youknowwhat how the technology achieves it. I know I can spend a Saturday with virtually any technology and figure it out and master it and awe people. So what? Who do I see about getting that Saturday back?

Never root a phone. Keep it the way Samsung and AT&T shipped it; that way you can hold them accountable when it doesn't do what they promised; and you can also always restore the phone to the way they shipped it to you with such as a GSM reset so you can get to the same starting point that they used when they created and tested the 2.3 Gingerbread update/upgrade that you're getting ready to perform. Again... I can't stress this enough: NEVER ROOT A PHONE! That way you'll never be one of the idiots in the forums asking why their phone's doing such-and-such instead of spending quality time with your family, or walking your dog on the beach, or...

...well... just read the message on my website.

The GSM Reset and then the immediate 2.3 Gingerbread update should be done with whatever SD card in it that you intend to use in it once you've got 2.3 Gingerbread up and running, and you're beginning to restore stuff to your phone, and reinstall apps, etc.

Also, try to use the USB cable that came with the phone. Others will likely work, but every now and then I'll hear about somebody who thought s/he could save a buck by buying some super-cheap cable that comes from such as one of Amazon's resellers who just puts it into a Glad-brand sandwich back, with a hand-written label on it. Some of those cables don't even have continuity on all the pins. If you no longer have the cable that came with the phone, at least use one that's made by one of the big-name makers... Belkin, maybe... or anything with an AT&T or Samsung label on it. Sorry I forgot to mention that earlier... though I already might have, earlier in this, or one of the other threads I've got on this subject floating around out there on the various forums.

Just be cool. Take it one step at a time. Don't rush things. Follow the instructions. Everything will be fine.

And I trust you'll report back and let us know how it went.

Lookin' forward to it.


Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
 
Well i waited about an hr and half and it was stuck at 42%. Not sure what could have caused this.

Maybe it was the hardware issue i had been having lately with my phone.
 
If I was helpful to you, please click the Thanks button.

I'm sorry... helpful to whom, for what, and how? Are you sure you posted in the right thread? I don't see your participation in this one, anywhere...

...er... well... except, of course, for that to which I'm now replying.

So, then, was it simple mistake? Or are you doing what I've seen in other forums like this wherein you hope that the person helped won't notice who's posting the "Thanks" button request, and will just click on the button of the one who asked for and/or suggested it?

Sorry to be so cynical, but I've seen every trick in the book. My apologies if I've misjudged.

But helpful to whom, for what, and how, in this thread?

Just askin'.
 
I was curious how long does it take to upgrade to GB?

It's been like almost 20 minutes and stuck at 42%.

I felt something wrong was going to happen.

---------------

Well i waited about an hr and half and it was stuck at 42%. Not sure what could have caused this.

Maybe it was the hardware issue i had been having lately with my phone.

Sometimes hardware breaks, it's true. Maybe that's what's going on with your phone.

You could try the GSM reset again... maybe even do it twice, pulling out the battery and just letting the phone sit for a few minutes inbetween them.

Also try it with and without the SD card inside (a bad SD, card, by the way, can make a phone really nutty).

At this point, you've got little to lose so you can safely experiment a little.

Ultimately, though, to safe yourself a bunch of time and frustration, you probably need to go to an official AT&T wireless support center and have them first make the phone exactly the way it came from the factory. Don't let 'em just do their own GSM reset. Ask them, instead, to plug the phone into one of their machines that forcibly wipes everything clean, and reinitializes everything, and then reinstalls 2.2 Froyo onto the phone, exactly as it came from the factory. Once, when I did it, they actually installed an every-so-slightly older 2.2 Froyo than came on my phone; but the tech insisted that that version was more stable. So these guys really know what they're doing.

Once a clean, good, pristine, AT&T-installed 2.2 Froyo's on the phone, then ask him to test the heck out of it and make sure the hardware's okay.

Then -- this may sound strange -- but then ask him to repeat the process of wiping everying, reinitializing everything, and re-installing a factory-new copy of 2.2 Froyo onto the phone.

While you're there, either talk him into giving you, or buy one if you have to, a new battery. The battery plays a role, believe it or not, in the 2.3 Gingerbread update; if it's squirrely in any way, it can screw-up the update. When you get the phone home, put the new battery in and charge it all the way up, and make sure it's that way when you next try the update.

To learn where is your nearest wireless device support center, go to this web page (click here) and then scroll down to "Step 3." Don't worry about all the warranty info on the page; just pick your state, download its PDF file, and then open said PDF file, and find the center nearest you. Sadly, some states have only one center, so you may have some driving to do. But it's usually worth it, though, because those guys tend to really know what they're doing.

You might even be able to talk 'em into exchanging the phone for you. I've seen that happen, even with a phone that was way out of warranty, but the customer was an old and long-standing one whose two-year contract was just barely halfway through. So, who knows.

Or, what the heck, maybe it's time to move on to a new phone. Even if your two-year contract isn't over, AT&T will quite often let you sign-up for, in effect, a whole new two year contract, and pick a nice either free, or one-cent, or otherwise super-cheap phone. If you've got the money, you should get a Samsung Note (not necessarily the Note II, though if you want that one, instead, fine; but the regular Note is amazing... huge, better/faster, and so effectively a blurring of the line between a phone and a tablet that you may stop carrying around your tablet (or may not buy one, if you don't already have one). It's a fantastic phone.

Even though our two-year contract still has 8 months left on it, Mary-Anne and I want to move over to the shared data family plan because we can get a net 2GB/month increase over what we have now, but for over $20/month less. While we're at it, I'm thinking very, very seriously of finally pulling the trigger on getting that Note; and giving Mary-Anne the Infuse; and then doing a GSM reset on her Captivate and just putting it in the drawer as a backup phone in case either one of ours craps out. The chances that we'll do that are high, actually. Maybe you should consider something like it.

Or if you don't want the Note, fine... there are others. Click here. I see that a refurbed Galaxy SIII can be had for only thirty bucks. Never be afraid of the refurbs. They're not merely checked-out by AT&T; they're factory refurbed by Samsung or one of its authorized refurbishers, and, seriously, anything even close to being marginal is replaced, and then everything is thoroughly checked-out. The only thing potentially bad about refurbs is that they've usually got at least a year of usage history on them; and so anything that checked-out during refurb, and so wasn't replace, could finally die just as it would have if the phone had never been refurbed. But, seriously, refurbs, if they're really good deals, like this SIII, are usually a pretty good value; and, in a sense, are far better checked-out and verified than brand new phones. As long as a refurb is really a refurb, by the factory or one of its authorized centers; and as long as they really did replace things, and not just test, reset, clean-up and rebox, then they're pretty reliable.

There are obviously other phones there...

...including the Note, for $199, on which I've so got my eye.

Start with doing a little experimenting; GSM reset the phone again, and be sure to reboot the Windows machine, too, just before doing the update (and let it fully boot-up... wait 'til the hard drive light settles down). Re-try the update (making sure the battery's fully charged, even though, yes, the phone gets juice from the USB cable). Make sure the USB cable's the one that came with the phone, and that it has no shorts or anything in it.

If it fails again, then repeat it all, but with the SD card out of it. In fact, as long as the SD card's out of it, put said card into the Windows machine and reformat it. Can't hurt.

When you're finally done screwin' around with it (or if you're ready now), find the nearest AT&T support center and go there and do what I earlier herein wrote. Then go home, charge-up the new battery, do your own GSM reset, reboot the Windows machine, connect the phone to it, and try it again.

If that fails, too, then I'm not sure I know what to tell you..

...other than at that point you'd be in the sort of place where I would, were I your official support person, be asking you to box it up and send it to me.

Did you purchase the phone new or used? If used, how did you purchase it... off eBay or something? If so, you know, it could have been dropped in the toilet or something, and be water damaged. If I could look inside it, I could tell you in two seconds. If so, though, that could explain why it's squirrely, and why it might even pass testing at the support center, yet still be squirrely when you got it home. Water damage to integrated circuits can produce all manner of oddities.

It might also have been dropped, and something's shorted inside such that it just happens to test okay at the service center, but gets squirrely elsewhere.

There could be heat issues, too. Sometimes only certain precise conditions of heat, after the phone's been on for a certain amount of time (which maybe couldn't be replicated in the service center) can suddenly make something inside one of the chips or other components, or on one of the tracings or solder joints, open-up a little... become intermittent.

While any of those things, in the hands of someone like me, for example, who's got a whole workshop full of cool tools and test equipment, can find; at some point one has to ask: At what cost? For no more than a new phone costs, you might want to just punt and go get one.

That said, if the service center's close enough to you, it would probably be a trip worth taking. Take the cable with you, too, and have 'em check that out; or buy a brand new one with AT&T labeling (it'll be expensive, but probably worth it).

And don't forget to get a new battery... not an aftermarket one, but, rather, the actual Samsung-brand battery exactly like the one that came with the phone! You wouldn't believe how these advanced batteries, some of which actually have little circuits inside, can goof-up a phone. Truth be told, that could be all that's wrong with it. I'm serious.

Short of sending me the phone or something, I don't know how much more helpful, at this point, I can be. I'm sorry it hasn't worked-out for you. There's obviously something wrong...

...although, having said that, I've seen these things fail, too, because of something wrong on the Windows PC. Maybe a bad USB port; or some USB management software running. Maybe something running downn in the System Tray; or a service that's conflicting with KIES Mini. The list of possibilities on that score is potentially endless!

Also... oh, yeah... I forgot... this is important: Make sure that no earlier version of KIES Mini -- or, especially, the full version -- is installed on your machine. If more than one KIES Mini is installed, or if an earlier version was on it, but you thought you properly uninstalled it, then use REVO UNINSTALLER's most aggressive mode to bygod get every version, including the most recent one you just tried to use, off that machine. Then reboot. Then reinstall the new KIES Mini. Then reboot. Then do the GSM reset, then try the update.

Whew! I know it's a lot of screwing around, but whoever wrote KIES Mini either at or for Samsung must have been high or somethiing, because that whole family of software products is a freakin' mess.

Anyway... see what part of anything I've just written helps... and let us know.
 
No i wasn't trying to be smart ass about it. I really meant thanks for trying to help out. No ones at fault. Not blaming you or no one else.

I had to stop the keis program. But it bricked my phone ( i guess it's the right term). I went to an att device support center.
They ended up grading my phone to GB.

Since i backed up all my files to the pc and i want to upload it back to my phone. But now i'm having another issue (cant seem to catch a break damn samsung phone lol), my usb cord is having problems connecting with my pc. I touch the mass storage to connect with my pc, but almost immediately it will disconnect.
When i did connect the first time it was fine but the second time it wont connect. I took the battery out and see if that would help but its being a pain in the ass.

the usb cord is the original one that came with the phone.

When i bought the phone it was brand new.

Any ideas?




I'm sorry... helpful to whom, for what, and how? Are you sure you posted in the right thread? I don't see your participation in this one, anywhere...

...er... well... except, of course, for that to which I'm now replying.

So, then, was it simple mistake? Or are you doing what I've seen in other forums like this wherein you hope that the person helped won't notice who's posting the "Thanks" button request, and will just click on the button of the one who asked for and/or suggested it?

Sorry to be so cynical, but I've seen every trick in the book. My apologies if I've misjudged.

But helpful to whom, for what, and how, in this thread?

Just askin'.


Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
 
I did fix the usb connection by going into settings/application/usb settings and setting it as mass storage.

But it seems i have to down load all the apps again. I was hoping to save my text messages and backing it up to my sd card as well as my contacts but not sure if i can. I thought i backed it up but i guess i'll have to tinker with it more after work tonight.

IF you got any ideas that would be great. :D

I'm sorry... helpful to whom, for what, and how? Are you sure you posted in the right thread? I don't see your participation in this one, anywhere...

...er... well... except, of course, for that to which I'm now replying.

So, then, was it simple mistake? Or are you doing what I've seen in other forums like this wherein you hope that the person helped won't notice who's posting the "Thanks" button request, and will just click on the button of the one who asked for and/or suggested it?

Sorry to be so cynical, but I've seen every trick in the book. My apologies if I've misjudged.

But helpful to whom, for what, and how, in this thread?

Just askin'.


Gregg L. DesElms
Napa, California USA
gregg at greggdeselms dot com
 
No i wasn't trying to be smart ass about it. I really meant thanks for trying to help out. No ones at fault. Not blaming you or no one else.

Wait a minute, user "tvfreakazoid," when I was asking "helpful to whom," I was talking to user "sarahard7," who asked for somone whom s/he did not specify to click on his/her "thanks" button if he had helped anyone. I was not talking to you. Please pay attention to who's post is whose by looking over on the left side of each post and noting said post's owner's username.

Or are you saying that you're logging-in, here, under both the "tvfreakazoid" and the "sarahard7" usernames? If so, then that's probably a violation of this site's terms of service (TOS). Most forums require that everyone be "present" with only one (1) username/identity. I'm guessing that this forum's rules are similar.

So, then, assuming that it was not actually you to whom I was addressing my "helpful to whom" words, you needn't have apologized for anything. Again, note the any given post's username, over on the left. Anyone who's registered around here may post in any thread... as it appeared user "sarahard7" did... either accidentally, or because s/he was "thanks button clicke trolling." Only s/he knows.

Bottom line, @tvfreakazoid: I wasn't, when I wrote "helpful to whom," addressing you... er... I mean... unless you're also user "sarahard7," which I'm guessing you're not.

I had to stop the keis program. But it bricked my phone ( i guess it's the right term). I went to an att device support center. They ended up grading my phone to GB.

"Bricking" a phone is usually something that only screwing-up the rooting of a phone can accomplish; though, if you think about what KIES Mini is doing, it's much the same sort of thing. And so, yes, I suppose "bricking" could happen from an effectively aborted-in-the-middle 2.2-Froyo-to-2.3-Gingerbread update. I'm a little surprised that the device support center people were willing to do the 2.3 Gingerbread update, but with all the trouble it's been having, maybe they've loosened that policy. I haven't been to a center in quite a while.

I'd sure like to know precisely what the technician, there, did, though. If s/he recovered from the bricking and did the 2.3 Gingerbread update in the same process (as opposed to first restoring the phone to 2.2 Froyo factory condition, and only then performing the 2.3 Gingerbread update) then it's entirely possible that you've still got yourself an oddball, hybridized, pretty-much-2.3-Gingerbread-but-with-2.2-Froyo-remnants phone. And that can cause all manner of weirdness. AT&T techs sometimes take shortcuts, too; and those who learned what they know through mostly just rote, without really having a good engineering both background and mindset, sometimes make the same kinds of rookie mistakes as reinstalling-Windows-is-the-answer-to-everything PC technicians in places like Best Buy.
The only road to a proper 2.2 Froyo-to-2.3 Gingerbread upgrade is to start from a phone that's in fresh-from-the-factory, pristine, 2.2 Froyo state. Period. No amount of wishing otherwise will change that.

On most phones, a simple GSM rest achieves that state; and then if everything is just right about the phone and its battery, the Windows PC and its Internet connection and the KIES Mini installation on it, and the cables between them, then the upgrade to 2.3 Gingerbread, if done exactly/precisely as per instructions, and immediately after the GSM reset, will go flawlessly.

That's really the net bottom line of all of this. Anyone who deigns to perform the 2.2-Froyo-to-2.3-Gingerbread upgrade by any other means is introducing into the mix a state of things that's inconsistent with what AT&T and Samsung engineers did when they developed the 2.3 Gingerbread update/upgrade, and tested and re-tested it until they finally got it right. And don't forget that they originally got it wrong, and withdrew their first release of the 2.3 Gingerbread update for the Infuse 4G. Their testing of the update between the first and second releases always began with a factory-state 2.2 Froyo phone. Always. Beginning anywhere else is inviting trouble.
Sometimes, sadly, even AT&T technicians need to be reminded of that. The guy I go to at the device support center nearest me is the assistant manager, and I could tell that he really got it. So my experience with my only two trips, ever, to that office have been excellent. But almost every technical support office for every type of high-technology product, around the world, has a technician (or two) who isn't(aren't) careful; and who shotcut things. I worry that that's what's happened to you and your Infuse today. I'm not saying it did, but I sure wish I knew precisely how the technician did whatever s/he did on your phone today.

Since i backed up all my files to the pc and i want to upload it back to my phone. But now i'm having another issue (cant seem to catch a break damn samsung phone lol), my usb cord is having problems connecting with my pc. I touch the mass storage to connect with my pc, but almost immediately it will disconnect.

When i did connect the first time it was fine but the second time it wont connect. I took the battery out and see if that would help but its being a pain in the ass.

the usb cord is the original one that came with the phone.

When i bought the phone it was brand new.

Any ideas?

Yeah... print-out this posting. Take it and the phone with the SD card in it, your cable, and whatever battery you're using back to the AT&T device support center. Demand to speak with the manager, and then show this posting to him/her, and demanding that s/he read it (asking him/her to ignore, of course, the first section, where we settled the "sarahard7" issue); then demand to be handed-off to his/her absolutely, hands-down best technician (which the manager often also is)... even if it means your coming back if s/he's not working that day. And then, once your phone is in his/her hands, demand that s/he:

  1. Restore the phone to original, as-shipped-from-the-factory, 2.2 Froyo state by the most destructive means possible. If there's a way to wipe it so clean of all previous stuff on it before so doing that it's as if the phone just came off the factory line, just before installing anything onto its chips, then have him/her do that first. This phone needs every trace of anything and everything ever on it to be gone; and then a pristine 2.2 Froyo, exactly like it ships from the factory, installed onto it.
  2. Then run the phone through the most aggressive and complete hardware diagnostics of which the center's capable. Do it twice, and get the phone heated-up, but good by the first time, for the second time.
  3. Assuming both those things go well, then and only then perform the 2.3 Gingerbread update.
  4. Then run the phone, again, through the most aggressive and complete hardware diagnostics of which the center's capable. Do it twice, and get the phone heated-up, but good by the first time, for the second time.
If the phone survives all that and the technician believes, to the depths of his/her soul, that the phone's basically perfect...

...then have him/her do, on one of the Windows PCs there, on the counter, in front of your eyes, whatever you're doing which is failling on yours, at home, and see if it works. If it does, yet still fails in the manner you're describing when you get the phone home, then it's likely that your Windows XP machine has been the problem, all along. If so, then that's a whole different diagnostic and repair road that you must go down; but at least it shows that the phone's fine.

Let me know how all that goes.
 
Back
Top Bottom