HTC Customer Support Fail - Thunderbolt General

Before the MR2 update came out I sent their customer support an email complaining about the random reboots and data connectivity being crap and about gingerbread and they gave me the typical generic answer we are aware of the issue and working on giving thunderbolt owners gingerbread soon and they were sorry for the problems with my reboots. So far since the MR2 update I have had no reboots and my data connectivity has been better but after hearing the Droid Incredible 2 got gingerbread today and the fact this phone came out after the thunderbolt I sent them another email in regards to this and the fact we have heard litterally nothing on their end about any status with the gingerbread update or when we could possibly see it and they responded
The Thunderbolt update is available to be pulled to the device. To pull the update go to Menu> Settings> System updates> Firmware update. If you are unable to update the device please wait for the FOTA update.
Sorry for the inconvenience.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number xxxxxxxxxxxxxx.
Sincerely,
Brian
HTC
He was refering to the MR2 that just came out, nothing about my question on gingerbread or how the Incredible 2 got it before the thunderbolt. Fail

smh I didnt know Droid Incredible 2 came out after the TB. Smh its like htc or Verizon dont give a **** about this phone

Perhaps you would have gotten satisfaction if your message was properly punctuated, clearly written, and presented in some organized fashion?

My message to them was accurate, and clear and I pretty much asked them about gingerbread and how the Incredible 2 was able to get it before thunderbolt when the incredible 2 came out after the thunderbolt. I also mentioned how they haven't mentioned anything in regards to the thunderbolt or given us at least a status update. From other forums I've read they just give the standard We are excited about the Operating System 2.3 Gingerbread update coming for Android, and while HTC will definitely have some phones running this Operating System, we do not have a specific time but it will be soon and what I posted was the response I got back from them.

What does it matter? #FOOL
Sent from my ADR6400L using XDA Premium App

bob miller said:
My message to them was accurate, and clear and I pretty much asked them about gingerbread and how the Incredible 2 was able to get it before thunderbolt when the incredible 2 came out after the thunderbolt. I also mentioned how they haven't mentioned anything in regards to the thunderbolt or given us at least a status update. From other forums I've read they just give the standard We are excited about the Operating System 2.3 Gingerbread update coming for Android, and while HTC will definitely have some phones running this Operating System, we do not have a specific time but it will be soon and what I posted was the response I got back from them.
Click to expand...
Click to collapse
Ah, I see. I assumed that your OP was verbatim. I couldn't really read it, as it had one period for about 15 different sentence fragments.
As a beleaguered technical support engineer, I had sympathy and could understand how some core points would have been ignored.
Not intended as flamebait. Your response above was more digestible.

brisdaddy1207 said:
What does it matter? #FOOL
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
And this contributed what exactly to this conversation? and you do realized this is a forum and not twitter?

Related

*false alarm* New AT&T Update

EDIT: FALSE ALARM, AT&T thinks I need an update.
I looked around the forum to see if I could find something about this and couldn't, maybe I missed it.
I have Cog 2.3B6 (Froyo), and I just got a text message from at&t saying:
AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You.
What update could this possibly be, official Froyo?
Edit: Also when I was reading my message, my phone was also trying to connect to DM, whatever that means. Not sure if it's related or not.
Probably just jh7.
Sent from my Captivate
any update?
didn't think you would get a notice rooted on custom rom.
Ahh. You got my hopes up...
Just checked.. nada. Running Jh7 stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lots of people with custom roms get that. AT&T's notification sytem sees that you are not on what they consider to be the latest version.
Ahh ok, thought it might be a false alarm. Thanks.
OP can you edit your post title so everyone doesn't come here and flame you... There should be some kind of MOD editing of these type of update posts that turn out to be false alarms. It think there are an average of 4 or 5 of these a day.
tahoeski said:
OP can you edit your post title so everyone doesn't come here and flame you... There should be some kind of MOD editing of these type of update posts that turn out to be false alarms. It think there are an average of 4 or 5 of these a day.
Click to expand...
Click to collapse
For sure. For the last time, most developers have it on good notice that this won't happen until Q1 2011.
If it drops before that, I'll eat my words but until then stop it.

At&t Message

*note I am posting in my BIL's account because I am on his computer*
I am currently running the original leaked FROYO rom that was posted here. Today I got a message from at&t saying they were providing a free update to my phone....
Got any ideas what this might be?.... I had already installed jh7 before...
Yeah, this happens... They sent that out with the last update for 2.1, and if you bought your phone sometime afterwards, you'll eventually get a (few) texts about it...
When Froyo is released, I'm sure you'll hear all about it, so don't worry about that text.
I've just learned to ignore that text message, I figure if Froyo comes out for the Captivate I'll probably read about it somewhere else first.
I got the same message from ATT
Froyo 2.2 Rooted I897UCJ16
In my case there was a time where I saw a sync Icon next to the Wifi Icon on top right which was bit unusual I thought. However when I pulled the tab to see what it was, nothing showed up but icon remained.
The text came from 1111487602 and it came to my SIM Card Phone # directly which a puretalk prepaid sim
malicenfz said:
I've just learned to ignore that text message, I figure if Froyo comes out for the Captivate I'll probably read about it somewhere else first.
Click to expand...
Click to collapse
Just as I am learning to ignore the daily new thread posting about it.
polarbee said:
Just as I am learning to ignore the daily new thread posting about it.
Click to expand...
Click to collapse
Haha!
Sent from my SAMSUNG-SGH-I897 using XDA App
Yup So have I lol. I have blacklisted the number cause I got it 4 times in the same day and I was like Yeah ok....Not gonna happen lol.
Thread closed

[Q] disappointment after disappointment

First off I would like to say hi and thanks to everyone on here, this forum rocks! But I honestly feel my Mesmerize has been a bigger disappointment to me than my Behold I had with T-Mobile! I switched to US Cellular and this phone cause they have better coverage where I live, and I wanted a phone I could customize so i wouldn't have the same thing as everyone else lol. I did the 2.2 update as soon as it released, toyed around with some of the other firmwares on here and what not before it was available, but started having the problem where my phone wouldn't notify me of incoming calls. So i used the files on here to go back to 2.1 using Odin and rooted for future possibilities, I receive every call now. But onto my questions lol, I was wondering if anyone on here has found a way to fix the incoming call problem on 2.2 that i had? How can I get voodoo onto my phone the way it is right now? I have tried every way described on here and through searching, keep finding dead links, phone will not update zip from sdcard on reboot, have tried numerous files that way! If you guys could post some links that would help me out with my problems, to files, and what not, that would be greatly appreciated. Sorry for the long winded post, just tired of searching everywhere and not getting anywhere, thanks!
Honestly, there *is* a thread that covers what you're after; it's bde's How to Customize your Mesmerize thread found Here. I should probably get on him to update the "First get Stock Froyo on your phone" link, because it does have an old link last time I checked. That's about the only one that I know of, every other link works.
Above all, make sure to always wipe your cache (any "Wipe ..." option you can find, one is under Advanced, except for Battery Cache) once you get Clockwork Mod (CWM) Red Recovery installed before you flash a ROM. It really does make things flash better, fewer FCs, and so on. There are times when you can get away without it, but in that event it's best to assume things will be glitchy unless they aren't. From the brief information you gave, I'd suspect that's what happened to your phone.
Best advice anyone here will give you: Read read read. Following that, read some more. Some people can only learn by doing, sure, but become as intimately familiar with the processes and terms as you can.
I suspect I'll do this a lot, but check out the Glossary in my signature, and read through the whole post. It should give you all the little "this goes here, but doesn't work there" kinds of pointers you need, all in one place.
Good luck! Hopefully from here on out, you can really enjoy your Mesmerize, and welcome to the forums!
Hi, thanks for the reply. I do need to read through the glossary post you put up a little more thoroughly, just kinda glanced so far LOL. I also have checked out that link as well, but honestly I won't go back to froyo, not worth the missing calls to me when my phone is how I make a living at the moment. Just mostly interested in finding a lagfix and the voodoo sound for 2.1.
Sent from my SCH-I500 using XDA App
mikef509 said:
Hi, thanks for the reply. I do need to read through the glossary post you put up a little more thoroughly, just kinda glanced so far LOL. I also have checked out that link as well, but honestly I won't go back to froyo, not worth the missing calls to me when my phone is how I make a living at the moment. Just mostly interested in finding a lagfix and the voodoo sound for 2.1.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Missing calls has never been a problem with froyo as far as I'm concerned. Uscc did realease their official version not long ago, getting 2.2 by that means should be flawless.
Sent from my SCH-I500 using XDA App
The US Cellular froyo upgrade is what i used and had all the problems with not being notified of my incoming calls, its a very well known problem from what I have found out by searching on google, took my 4-5 times of calling me before my phone rang, and he is with US Cellular as well
Sent from my SCH-I500 using XDA App
As a quick note, the missed calls thing is actually a Samsung issue that is known and is/was an issue on both 2.1 and 2.2 that is being worked on and a new firmware release is coming soon from what I have seen. I'm hoping to have more on that soon.
Sent from my SCH-I500

2.3.6 update

For some reason my phone keeps saying up to date & I have no idea if I just got a bad unit. Can anyone tells me how to get it to update? I'm still under my 30 days but time is ticking on me. Please help
Sent from my SAMSUNG-SGH-I727 using XDA App
Stevieboy02008 said:
For some reason my phone keeps saying up to date & I have no idea if I just got a bad unit. Can anyone tells me how to get it to update? I'm still under my 30 days but time is ticking on me. Please help
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
when you go into phone info does it still say 2.3.5. are you using CWM?
Nope my phone is stock. No root. Yes it says 2.3.5
Sent from my SAMSUNG-SGH-I727 using XDA App
Stevieboy02008 said:
Nope my phone is stock. No root. Yes it says 2.3.5
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
i have heard they pulled the update.....but silver posted a Zip file that you can flash to get the update in the dev section.
others have the same issue
Oh OK. I went to the AT&T store last night & their demo phones have it so I felt left out. LOL thanks for all the help. I'm new to android development but that's my 4th android phone from a long line of iPhone users used them all till the 4S. Can't seem to like them again
Sent from my SAMSUNG-SGH-I727 using XDA App
the2rrell said:
i have heard they pulled the update.....but silver posted a Zip file that you can flash to get the update in the dev section.
others have the same issue
Click to expand...
Click to collapse
that is correct, for an unknown reason they pulled the update. It was only available for like 5 days =(
nobody knows the changes in 2.3.6 and nobody knows why they pulled the update either =(
Those who are not aware of the fact that the AT&T Samsung Galaxy S II Skyrocket is delivered with Android 2.3.5 will be surprised when they receive an update notification that will allow them to upgrade their smartphones to version 2.3.6.
Although the carrier is still mum about the update, AndroidCentral reports that lots of Galaxy S II Skyrocket owners started to receive it in the last 24 hours.
No word on what's changed after the update, but those who upgraded noticed that it keeps root and boot-up seems a bit faster.
In addition, the speed of the new radio firmware on HSPA has been improved, and several changes on the camera interface have been included as well.
What's certain is that Android 2.3.6 fixes a Google Voice Search bug. Other than that AT&T may have squeezed several tweaks and possibly a few more performance improvements.
CosminVasile · 268 followers
@
AT &T
FILEDUNDER:
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
AT&T аnԁ Samsung hаνе јυѕt voiced thаt аn over-thе-air ascent fοr Android 2.3.6 hаѕ started pulling out tο AT&T’s Samsung Galaxy S2 Skyrocket. Thе refurbish іѕ approaching tο finalise thе Google Voice Search issue.
Galaxy S2 Skyrocket users аrе anticipating thаt thеу сουԁ irrevocably υѕе Google Voice Search аftеr thе update.
If уου haven’t perceived аnу notifications јυѕt уеt, уου mау wish tο try out fοr thе refurbish manually. Tο ԁο ѕο, јυѕt daub οn Software Update underneath Settings аnԁ click οn Try out fοr Updates. Updates wουԁ customarily rυn fοr mins depending οn уουr download speeds, ѕο уου mіɡht wish tο take the lay fοr thіѕ one.
Nеіthеr Samsung nοr AT&T hаѕ nοt referred to аnу οthеr nеw underline іn thе update. Though, ѕοmе аrе suspecting thаt ѕοmе ехсееnt things аrе packaged іntο thе Android 2.3.6 update. Sο, іf уου οwn a single οf thе Samsung Galaxy S2 Skyrocket, thеn уου mіɡht wish tο try out out уουr handset fοr thе update.
Hаνе уου implement thе refurbish οn уουr phone? Whаt οthеr elements іѕ enclosed οn thе update?
Posts
Well thank you guys. I hope I get it soon
Sent from my SAMSUNG-SGH-I727 using XDA App
My phone still saying up to date. Did I get a bad headset?
Sent from my SAMSUNG-SGH-I727 using XDA App
I am in the same boat. I have heard that carriers will often roll out updates to only a certain range of IMEIs over a period of time to reduce bandwidth/server constraint... usually one batch per week until all the IMEIs are white listed.
I do not know if this is the reason many of us (myself included) are unable to update, but I consider it possible.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Just got off the phone with at&t tech , they told me the update was pulled out then re-released but based on market to market basis, so all i can do is just sit & wait till my phone tells me its there or just keep checking every 24 hours , as of what the update changes they couldnt tell me because simply they have no idea what does it fix they just know that its live , thank you all for the help if anyone knows what does that update fixes please let me know , thank you all for all your help
They probebly pulled it because of all the white screens everyone was getting. All Stock, and rooted alike.
I wont touch it unless it has something in it worth the update.
pcrat said:
They probebly pulled it because of all the white screens everyone was getting. All Stock, and rooted alike.
I wont touch it unless it has something in it worth the update.
Click to expand...
Click to collapse
Exactly. With the exception of the removal of CIQ (which we can disable anyways), there's really nothing that the update has to offer
This old thread was in refrence to the other 2.3.6 update att started then pulled. It was kk1
Lol so the new ucla3 is there second time ...hmmmm

Update rolling out Soon

I spoke to a rep the other day regarding Jelly Bean. Long Story short he said it is rolling out to their systems now (computer support info) so we should have it very very VERY soon.
Sent from my SCH-I535 using Tapatalk 2
Your title gives the impression that it'll be JB
Edit : you edited your post.
Sent from my SCH-I535 using xda premium
blestsol said:
Your title gives the impression that it'll be JB
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
First mistake is assuming the reps have a clue about what they are talking about. They are lucky to dress themselves for work every morning. If I had a nickel for every time a rep told me an update is coming, I'd be a thousandaire.
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I think when he says a small update he is describing his post as a small update to here. No the actually Verizon update.
Of course the next Verizon update will be JB. They do not need to make our phone ready for JB, it is ready and the leak we have also says it is pretty ready to go.....
Yes to Jellybean. Sorry for the confusion.
Sent from my SCH-I535 using Tapatalk 2
ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I'm familiar with your posts in other threads. Carry on.
Sent from my SCH-I535 using xda premium
Never trust verizon reps....
I know a bunch of people who work for Verizon corporate.
I tell THEM when builds/phones are coming. I just updates their store model M to JB on Friday. They had no idea
Sent from my SCH-I535 using Tapatalk 2
Delete.
Sent from my Galaxy Nexus using xda app-developers app
The leak seems more stable than the ICS official to me...
I think these delays are more of a marketing strategy of sort rather than a real technical time to get it ready.... I might be wrong but...
Well VZW is going to have to do something either right before or same day the Note 2 comes out.
Sent from my SCH-I535 using Tapatalk 2
It seems more of a marketing strategy because t mobile released theirs after the note 2 was released.
Sent from my SCH-I535 using xda app-developers app
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Well that depends, what's their definition of "soon".
Terry_blair said:
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
I laughed to his face and told him I would never be doing business with his store again.
Sent from my SCH-I535 using xda app-developers app
josh995 said:
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
Click to expand...
Click to collapse
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
ooofest said:
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
Click to expand...
Click to collapse
Well I had been manually checking for like a week, however, I wasn't receiving an update that had been out for months. The phone was 2 updates behind!
The new phone with my same SIM updated instantly after it was set up. I didn't even have to manually check. And then it updated again. So I honestly believe there was something wrong with the phone. Very strange to not get an update that had been out for months, you know?
Sent from my SCH-I535 using xda app-developers app

Categories

Resources