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

Reboot Issue = $30 credit to your account

C.C.W.

Member
Call VZW, patch through to tier 2 support and nicely moan, bellyache, whine and pitch a sweet fit with kindness towards the support rep and get a $29.99 credit to your account. :)

Yes, it works.

Note: I spoke with a Tier 2 rep for 35 minutes and she also has a rebooting Tbolt. She was very knowledgable as well as helpful in the fact that she said she personally spoke with HTC directly yesterday afternoon and gave me some very helpful info in regards to the reboot issue including the Gbread update. Not even going to post what she said because it's been said 1000 times, but per her conversation with HTC, the update started pushing yesterday. Not sure where it pushed to/from/etc, but she said that every VZW customer will have the update by "Mid July" per HTC/VZW.

I know, we've heard it all time and time again.

On the same note, she did say that replacement devices are futile as all of their replacement devices are now on the devilish, rebooting update so a replacement is a gamble. I don't think I have ever had a more pleasant conversation with a VZW rep in all my 10 years.
 
Call VZW, patch through to tier 2 support and nicely moan, bellyache, whine and pitch a sweet fit with kindness towards the support rep and get a $29.99 credit to your account. :)

Yes, it works.

Note: I spoke with a Tier 2 rep for 35 minutes and she also has a rebooting Tbolt. She was very knowledgable as well as helpful in the fact that she said she personally spoke with HTC directly yesterday afternoon and gave me some very helpful info in regards to the reboot issue including the Gbread update. Not even going to post what she said because it's been said 1000 times, but per her conversation with HTC, the update started pushing yesterday. Not sure where it pushed to/from/etc, but she said that every VZW customer will have the update by "Mid July" per HTC/VZW.

I know, we've heard it all time and time again.

On the same note, she did say that replacement devices are futile as all of their replacement devices are now on the devilish, rebooting update so a replacement is a gamble. I don't think I have ever had a more pleasant conversation with a VZW rep in all my 10 years.

I don't buy its a software problem that is causing the reboots. If it was software problem it would be happening to everyone not just some/most. I am on my 5th refurb and I have not had one reboot in the 2 weeks I have had it. And them telling you/us that software will fix the issue, I wouldn't drink that either. Rooted users have been running the software "fix" for weeks now and still getting reboots.

Thunderbolt, while a great phone IMO, has/had some serious quality control issues.

First phone was great but had dead pixels.

Second phone rebooted like crazy, once a day.

Third phone was okay, rebooted once in the week I had it. Got knew one because whoever refurbed it thought it was okay to leave dirt on camera.

Fourth phone reboot 3 times in 60 minutes sent it right back.

Fifth phone has not rebooted and seems to be perfect in the 2 weeks I have had it.

Its not a software problem, get a new phone until it stops rebooting. Just my opinion. Ask a tier 2 tech why some reboot and some don't, they won't be able to answer that one. If they had a software fix for it then they would be able to tell you the difference.
 
Call VZW, patch through to tier 2 support and nicely moan, bellyache, whine and pitch a sweet fit with kindness towards the support rep and get a $29.99 credit to your account. :)

Yes, it works.

Note: I spoke with a Tier 2 rep for 35 minutes and she also has a rebooting Tbolt. She was very knowledgable as well as helpful in the fact that she said she personally spoke with HTC directly yesterday afternoon and gave me some very helpful info in regards to the reboot issue including the Gbread update. Not even going to post what she said because it's been said 1000 times, but per her conversation with HTC, the update started pushing yesterday. Not sure where it pushed to/from/etc, but she said that every VZW customer will have the update by "Mid July" per HTC/VZW.

I know, we've heard it all time and time again.

On the same note, she did say that replacement devices are futile as all of their replacement devices are now on the devilish, rebooting update so a replacement is a gamble. I don't think I have ever had a more pleasant conversation with a VZW rep in all my 10 years.

If the update started yesterday it will be everywhere before the middle of july. probably within the next day or two.
 
I don't buy its a software problem that is causing the reboots. If it was software problem it would be happening to everyone not just some/most. I am on my 5th refurb and I have not had one reboot in the 2 weeks I have had it. And them telling you/us that software will fix the issue, I wouldn't drink that either. Rooted users have been running the software "fix" for weeks now and still getting reboots.

Thunderbolt, while a great phone IMO, has/had some serious quality control issues.

First phone was great but had dead pixels.

Second phone rebooted like crazy, once a day.

Third phone was okay, rebooted once in the week I had it. Got knew one because whoever refurbed it thought it was okay to leave dirt on camera.

Fourth phone reboot 3 times in 60 minutes sent it right back.

Fifth phone has not rebooted and seems to be perfect in the 2 weeks I have had it.

Its not a software problem, get a new phone until it stops rebooting. Just my opinion. Ask a tier 2 tech why some reboot and some don't, they won't be able to answer that one. If they had a software fix for it then they would be able to tell you the difference.
well guess what it is software. Because no ones phone rebooted before that ota. Then after the update it seemed the majority of the phones started the reboot issues. Why who knows could be a bad download or a glitch while installing. I have seen people have issues loading roms while others do not have a single issue.

M phone had the reboot issue. I installed the leaked MR2 update like many others has and our reboot issues has stopped. So how did the MR2 update fix it if you say it cant be software.

There are so many fixes out for this phone but I am begining to see some people just wants to complain.
 
5 refurbs? Come on guys. Its things like that that are the reason Verizon has changed the return policy. I understand we paid alot for these phones. I have had a phone for 11 years. Some of those have been phones with known issues. I have never had that much trouble with a phone. I know this is off topic, but Its getting ridiculous the amount of people calling in getting replacement phones for issues they could track down and probably fix themselves. I've had two Thunderbolts, both brand new. Left the first one on the roof of my car and it was perfect in every way. No battery issues, no reboots. At first I thought I was just lucky. I was worried after I lost it that purchasing the new one I would get one of those problems. But guess what, this one is just as good as the first one. Completely different batch of phones. That only leads me to believe that most of the issues people complaining about have got to be something that can be fixed WITHOUT calling in to customer service for a replacement(minus of course the reboot issue caused by the OTA)
 
I also don't believe the rebooting problem is a device or software issue but rather a network issue. The day it launched I ordered the phone and activated it the following Monday. Since then I've used the phone all up and down the east coast and in Chicago and Las Vegas. There is only one area where I experience constant reboots and that is in Fogelsville, PA. I've been there multiple times and it's always a problem.
 
I also don't believe the rebooting problem is a device or software issue but rather a network issue. The day it launched I ordered the phone and activated it the following Monday. Since then I've used the phone all up and down the east coast and in Chicago and Las Vegas. There is only one area where I experience constant reboots and that is in Fogelsville, PA. I've been there multiple times and it's always a problem.
Which would make it a software issue.:rolleyes:
 
well guess what it is software. Because no ones phone rebooted before that ota. Then after the update it seemed the majority of the phones started the reboot issues. Why who knows could be a bad download or a glitch while installing. I have seen people have issues loading roms while others do not have a single issue.

M phone had the reboot issue. I installed the leaked MR2 update like many others has and our reboot issues has stopped. So how did the MR2 update fix it if you say it cant be software.

There are so many fixes out for this phone but I am begining to see some people just wants to complain.

Glad you proved my point. Phone that are not rebooting on MR2 or MR2.5 must not have hardware problems like I was having but am no longer. Hence the reason I sent mine back to get a good one.


Should anyone spend money to get a defective product? You think I could fix dead pixels? Yes I could at the cost of a new screen and a hour or so of my time.

Could I have fixed the dirt on the camera? Absolutely but why should I take it apart when someone else screwed it up?

I was not fradulent in any way whatsoever. I would not stand for a rebooting Thunderbolt under no means and you shouldn't either. I rely on my phone.

Also all my reboots occured on MR 2.5. Kind of funny how I am not having any reboots on MR 2.5 with this phone. Same software? Yes. Even well respected (well really good dev) was getting reboots on MR 2 before he exchanged his.

Another dev's phone just bricked. Must be software related right? I wouldn't think so.

I can certainly be talked into possibly being tower related at times.

But then again what do I know except that I have a Thunderbolt that doesn't reboot anymore:)
 
If it were a software issue with the phone I would experience reboots everywhere, not just in Fogelsville, PA. :rolleyes:
Because the software in the tower may not be compatible with the software in the phone. Why I said it was a software issue. :rolleyes:
 
OK... before everyone spirals down into a hardware-software-network issue black hole, until someone publishes the engineering analysis of the cause of sporadic rebooting which varies from unit to unit, along with a description of how HTC chose to fix it, this is a futile exercise.

This could be:

1. poor software that does not account for predictable variability in the hardware,
2. hardware that is outside the specified range in terms of some key parameter that the software cannot run on as designed
3. just plain poor software, where the reboot is triggered by an obscure accumulation of user or network interractions that just happen to overflow a buffer for which the action-on-overflow is deliberately or otherwise a reboot
4. a network-management issue that is overloading otherwise satisfactory HTC device software

Without register dumps for the reset events and detailed knowledge of the overall total phone hardware / software / network implementation, speculation is futile.

You can eliminate 4 unless the network management issue has to be left as-is to support all devices as Verizon seem to have said the fix is a software push

Designers have a choice when they implement fixes to such issues and the natural choice is to do it in the way that has the lowest implementation cost.

They can often fix hardware problems by software changes that circumvent the hardware issue and will always choose the fix with the lowest implementation cost, so that is network first, then device software, then hardware a long way last.

Once the fix is pushed, you'll not be able to figure out what the problem was then, unless HTC chose to publicize their engineering details, which they won't.

Of course it would be interesting if someone compared pre and post fix ROMs and identified what was changed, but the guys that dive into the code are usually engaged in more creative pursuits than that.
 
Yup, that's a network issue.
I like many others have fixed our bolts by doing the MR2 leaked update from HTC. I have not had a single reboot in a long time. That right there makes it software. As everyones phone was fine until that OTA update. :rolleyes:
 
I like many others have fixed our bolts by doing the MR2 leaked update from HTC. I have not had a single reboot in a long time. That right there makes it software. As everyones phone was fine until that OTA update. :rolleyes:

While some people have been lucky with the MR2 update it hasn't fixed it for everybody. I still maintain that in my case it's a network issue. ;)
 
I like many others have fixed our bolts by doing the MR2 leaked update from HTC. I have not had a single reboot in a long time. That right there makes it software. As everyones phone was fine until that OTA update. :rolleyes:

On the face of it, that's sound logic. Software got changed, issue started, software changes again and issue went away.

However you may find that the "bad" OTA push was bad in that it added something they wanted to but in doing so exposed a hardware issue / function that wasn't previously used by the function.

In that case the folk at HTC will be working on how to retain the wanted function and at the same time prevent the reboot.

Having spent more that a few years working stuff of this nature I know how easy it is to draw a sensible conclusion from the evidence in front of you. Sadly that can get very expensive if you don't have all the evidence (that will include very low level fault logs or running devices with patches to trap the state of the system immediately before a reboot).
 
Back
Top Bottom