Related
EDIT: Yes I know that this has been a long standing issue...but I never heard of it until it happened to me!!! So no need to come in and comment like 4 or 5 others felt the need to do with "lol this is old news u r teh dumbz hurr" I just wanted to bring this up to any new captivate owners like myself :]
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
this wasnt a post about me getting my hopes up for a 2.2 update lol. This was a warning to those who dont about that fail update thats messing up a ton of phones. ;D
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
I didn't received any ota from att but last year I forced update my phone and it works fine with me though without any issue. I think its the same ota update but I manually force to update my phone lol
Sent from my SAMSUNG-SGH-I897 using XDA App
leo5111 said:
blackberry,iphone captivate, whatever. i have learned NEVER EVER do OTA update download it from phone authors site or whatever no matter what phone it is OTA is spelled BRICK....
Click to expand...
Click to collapse
I'm of the assumption that a OTA bricks less than 0.1% of the devices that attempt an update. Granted that may be a large number if the number of devices are large..but not much of a chance to brick in the big picture
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
HaiKaiDo said:
And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
That thread started in September, that's ancient in tech years.
bradleyG said:
I think this is a known issue. Many phones had this happen with the release of JH7. It was provably just the JH7 update that got pushed to your phone. I wouldn't get my hopes up
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 Still betting on St. Patty's Day release, office pool ya know.
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
+100 Mine got the OTA fine and it was even rooted on edge service. Meh, who can tell why some did brick and others didn't. For sure I'll never do another OTA again. I love my 1007 build too much to return it.
HaiKaiDo said:
If for some reason you have a hankering for some stock 2.1 from your captivate like I did for whatever random reason tonight......if you see an an OTA (Over The Air) Update for your captivate....DO NOT DO IT!!!!!! I say this because I did this tonight thinking that MAYBE this was some form of a 2.2 silent update push..or hell just some bugfixes would have been nice...so i went ahead and downloaded it, it prompted for a restart so it could flash it......and when it attempted to flash...it got about 50% and failed! Well at this point im thinking...awesome...ATT at its finest. So it said it was going to reboot back to android, I waited patiently...waited.....it hot about 3 minutes with phone in hand and screen off when i feel 2 *buzz* buzz* ! I think to myself HOORAY! its okay ....well i was wrong...that was my Captivates last words so to speak. I have tried plain powering on the phone....trying to go into recovery, trying to go into download mode even using a JIG to get back into download mode.....nothing the screen is blank completely, seems as if its not even getting power. :\ I am now the sad owner of a Captivate shaped door stop /facedesk .....Thankfully i yelled at the ATT people on the phone tonight enough to get a replacement phone lol! I am greatfull for this and felt as if i should pass this along to you guys until this gets sorted out. And no im not the only one thats had this problem
http://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Bricked/td-p/2008787/page/2
thats just one of many threads where this has happened. I dunno if this is new or old news...but Still i thought that i should put this out here.
Bryan
Click to expand...
Click to collapse
August called it wants its omg failed update back
Sent from my SGH-I897 using XDA App
Razzman said:
JH7 pushed to mine flawlessly when i got my phone last month, no issues at all.
Click to expand...
Click to collapse
Yup... This, but then my phone was new and unmodded at the time.
Thx for the info
viperrepiv said:
Thx for the info
Click to expand...
Click to collapse
No problem
I know its easy to flame. But we were all new once.
smokestack76 said:
I know its easy to flame. But we were all new once.
Click to expand...
Click to collapse
Join Date : March 2010
New
cappysw10 said:
Join Date : March 2010
New
Click to expand...
Click to collapse
July 2010 for you. You are new as well
Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...
Go to verizon, swap it for a new one. Warranty case for sure.
bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\
chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\
Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.
I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.
I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App
Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App
bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!
Why isn't there more angst about T-Mobile US releasing our version of the Sensation update?
Forums for other phones I've had would be exploding long before now that TMO is awful in all sorts of ways.
Has everyone just given up? Any idea of our prospects? Or have I missed something obvious?
samnada said:
Why isn't there more angst about T-Mobile US releasing our version of the Sensation update?
Forums for other phones I've had would be exploding long before now that TMO is awful in all sorts of ways.
Has everyone just given up? Any idea of our prospects? Or have I missed something obvious?
Click to expand...
Click to collapse
Personally I don't want to see ANY TMOUS OTA. I doubt it would give us S-OFF which is want I want to see first. I think most of us are waiting on developer S-OFF and then developer ROMs/kernels/radios and could care less about carrier OTA.
digiholic said:
Personally I don't want to see ANY TMOUS OTA. I doubt it would give us S-OFF which is want I want to see first. I think most of us are waiting on developer S-OFF and then developer ROMs/kernels/radios and could care less about carrier OTA.
Click to expand...
Click to collapse
+1
an OTA could ruin your chances at using a developer S-off method
I think it's awesome that there aren't seeing more threads about "when are we gonna get our update in the us....waaaahhhh"
It does nothing for us actually getting one, and as the above posters stated, it would probably leave us worse off. Although, those threads we aren't seeing, have pretty much been replaced by "s-off threads" so there's really been npthing gained
digiholic said:
Personally I don't want to see ANY TMOUS OTA. I doubt it would give us S-OFF which is want I want to see first. I think most of us are waiting on developer S-OFF and then developer ROMs/kernels/radios and could care less about carrier OTA.
Click to expand...
Click to collapse
Yeah, I'm not in that group. I don't need another hobby. Besides, HTC is unlocking the phone soon. But I get your point, which I'd overlooked, that most here are only waiting on the devs, not HTC or TMO. Thanks.
I agree... I just want S-off .... no tmobile ota is needed for me.
swellthekitty said:
I think it's awesome that there aren't seeing more threads about "when are we gonna get our update in the us....waaaahhhh"
It does nothing for us actually getting one, and as the above posters stated, it would probably leave us worse off. Although, those threads we aren't seeing, have pretty much been replaced by "s-off threads" so there's really been npthing gained
Click to expand...
Click to collapse
Actually the "outrage" did prompt TMO to push out a Vibrant Froyo update sooner, and they said they would do better. So I think posting can have an impact, but I see why it's not a high priority around here at this point.
swellthekitty said:
I think it's awesome that there aren't seeing more threads about "when are we gonna get our update in the us....waaaahhhh"
Click to expand...
Click to collapse
Agreed. And us veterans know we wouldn't take the update anyway.
I'll take an update for bug fixes and speed improvements in a heartbeat. I don't know what you guys are smoking, but I don't want any of it. If we had root and s-off then my song would be a little different, but the sad truth is that we don't. Plus, as I've said before this device is pretty awesome for a non-rooted device. Just make sense run a little snappier like the evo3d and I'm a happy panda.
Paging Dr B said:
I'll take an update for bug fixes and speed improvements in a heartbeat. I don't know what you guys are smoking, but I don't want any of it. If we had root and s-off then my song would be a little different, but the sad truth is that we don't. Plus, as I've said before this device is pretty awesome for a non-rooted device. Just make sense run a little snappier like the evo3d and I'm a happy panda.
Click to expand...
Click to collapse
It's not that we wouldn't want bug fixes, it's that there have been a number of other devices that lost their root and s-off exploits from OTAs. For me, it's just not worth the risk when those bug fixes will be available later via custom ROMs.
in my past experience t-mobile is notoriously bad with ota's ( my previouly phones were the g1 and the mytouch 3g and, had a vibrant for like a month then solid it. ) so i pretty much given up ota with tmobile
Because not everyone likes to whine, and almost everyone doesn't like seeing other people whine.
I'm hoping if there is an OTA, it will enable video-chat on gtalk, the nexus S has this and I thought all gingerbread devices should be able to.
Ndokami said:
in my past experience t-mobile is notoriously bad with ota's ( my previouly phones were the g1 and the mytouch 3g and, had a vibrant for like a month then solid it. ) so i pretty much given up ota with tmobile
Click to expand...
Click to collapse
Might be true. I'm new to tmo, but from what I've read and seen, they're not half as bad as att. They sucked when it change to updates, which weren't even ota, had to dl a program and update via home pc.
I couldn't care less. Don't need an OTA. Phone is solid stock. I just want S-Off.
Solid stock? Only of you dont have touchscreen issues. And i cant believe all of you guys dont have it... My 5th sensation will be here tomorrow, 1st 4 had the touchscreen issue. An OTA for touchscreen issues is very very very important. This phone has a ton of bugs.. my experience is the dev community doesn't normally fix the type of issues the sensation has. Who the ef cares if they have an s-off phone if you have to press 14 times for a 7 digit number.. Or cant scroll contacts or home screens with out opening whatever you touch 1st during the swipe. Completely unacceptable. I guess thats why they dont mind replacing my phone every week.... Since thats how long it normally takes for the touchscreen to ef up. I didnt pay etf at sprint to leave the evo for a supposedly way better phone that is slower than the evo once the touchscreen takes a poop. S-off is coming, we know this, HTC says so. Bug fixes are more important to me, we need an OTA like last month!
I'm waiting on an XDA OTA update to really fix this bad boy
Damonkashu said:
I'm hoping if there is an OTA, it will enable video-chat on gtalk, the nexus S has this and I thought all gingerbread devices should be able to.
Click to expand...
Click to collapse
Good luck with that LOL the new MyTouch 4G Slide has 2.3.4 and still isn't compatible with gtalk video... so blah
nugzo said:
Solid stock? Only of you dont have touchscreen issues. And i cant believe all of you guys dont have it... My 5th sensation will be here tomorrow, 1st 4 had the touchscreen issue. An OTA for touchscreen issues is very very very important. This phone has a ton of bugs.. my experience is the dev community doesn't normally fix the type of issues the sensation has. Who the ef cares if they have an s-off phone if you have to press 14 times for a 7 digit number.. Or cant scroll contacts or home screens with out opening whatever you touch 1st during the swipe. Completely unacceptable. I guess thats why they dont mind replacing my phone every week.... Since thats how long it normally takes for the touchscreen to ef up. I didnt pay etf at sprint to leave the evo for a supposedly way better phone that is slower than the evo once the touchscreen takes a poop. S-off is coming, we know this, HTC says so. Bug fixes are more important to me, we need an OTA like last month!
Click to expand...
Click to collapse
Still don't understand these touchscreen issues. I've had mine since 2 days after launch and zero problems. I wish I could see it first hand.
Sdobron said:
Still don't understand these touchscreen issues. I've had mine since 2 days after launch and zero problems. I wish I could see it first hand.
Click to expand...
Click to collapse
Also had mine since launch with no touchscreen issues.
Coming from the vibrant there where baseband zips shortly after a new one was out. Is there a way we can do this? Im hearing the only way to get it right now is by updating via the updater. So can anyone zip it up? I know it may take time just wonder if its being worked on...
smashpunks said:
Coming from the vibrant there where baseband zips shortly after a new one was out. Is there a way we can do this? Im hearing the only way to get it right now is by updating via the updater. So can anyone zip it up? I know it may take time just wonder if its being worked on...
Click to expand...
Click to collapse
Its been mentioned several times that there should be one in a day or so after testing is complete. TheDude has it covered.
I am going to download the newest leak in Rom form (already rooted) and then flash the basebands later. Too many people have made errors or had issues with using the LG tool.
jcbofkc said:
Its been mentioned several times that there should be one in a day or so after testing is complete. TheDude has it covered.
I am going to download the newest leak in Rom form (already rooted) and then flash the basebands later. Too many people have made errors or had issues with using the LG tool.
Click to expand...
Click to collapse
Thanks just as long as someone is on it I can wait. I also am on the rooted one just waiting for a flashable zip...
smashpunks said:
Thanks just as long as someone is on it I can wait. I also am on the rooted one just waiting for a flashable zip...
Click to expand...
Click to collapse
No idea who "TheDude" is, but he appears to be some sort of legend. He was all over the forums last night getting much respect. He wanted to thoroughly test everything, and I mean everything before he released it into the wild.
jcbofkc said:
No idea who "TheDude" is, but he appears to be some sort of legend. He was all over the forums last night getting much respect. He wanted to thoroughly test everything, and I mean everything before he released it into the wild.
Click to expand...
Click to collapse
if i'm not mistaken "TheDude" is one of the top dogs on team cyanogen.
smashpunks said:
Coming from the vibrant there where baseband zips shortly after a new one was out. Is there a way we can do this? Im hearing the only way to get it right now is by updating via the updater. So can anyone zip it up? I know it may take time just wonder if its being worked on...
Click to expand...
Click to collapse
Haha! I too posted this! Again coming from Vibrant, the new modem would be up in minutes after leak.
Guess we were spoiled then and now we must be patient.
Apparently there are two versions of our phone. I think DW and DWP (you can check your serial # to see which one you got) so I guess the new baseband might not work for the DWP for some reason.
So the devs don't want to cause mayhem and have a bunch of problems with people flashing it that aren't suppose to.
Which is why they are testing it before release!
....
htc2364 said:
Haha! I too posted this! Again coming from Vibrant, the new modem would be up in minutes after leak.
Guess we were spoiled then and now we must be patient.
Apparently there are two versions of our phone. I think DW and DWP (you can check your serial # to see which one you got) so I guess the new baseband might not work for the DWP for some reason.
So the devs don't want to cause mayhem and have a bunch of problems with people flashing it that aren't suppose to.
Which is why they are testing it before release!
....
Click to expand...
Click to collapse
I have the dw one... Hopefully thats good.. Yea vibrant stuff was posted so fast you could take a **** come back and flash...
Also wonder if the different versions would be why some get reboots and others don't?
Anyways I'm happy to wait for the safety of no bricking.
I'm pretty sure TheDude is the guy in the Big Lebowski
TheDude was a much lauded Developer when the G1 first came out. I moved on from the G1 sometime last year and haven't kept up with him since but he, JesusFreke, and Cyanogen were top dogs when all this stuff was still in its infancy.
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?
Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.
The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box
ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S
3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.
I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.
I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny