Database Info

[Q] data and roaming issues

I hope this is in the right place if not I apologize. Anyways I was running AOSP v0.9 and this morning I turned off data to conserve battery life. After that my phone will only connect to 1x and it is always roaming. It seems to realize that it is supposed to be on USCC it even says USCC in the status bar. So I called customer service and they told me to do a *228 and from what I hear this is really bad for anyone running ASOP then I did it anyways and it connected me to verizon so I disconnected the call and am still stuck roaming and with no 3g. Then I decided to switch back to MIUI and I'm still having the same problems. Another weird note, if I set my network to automatic it kills my connection but if I put it on home only I am roaming. Any ideas guys.
Sent from my SCH-I500 using XDA Premium App

This is the same issue I posted earlier that I haven't resolved yet. I am getting the verizon thing when I dial *228 as well. It is really frustrating because the phone is virtually unusable for data now. Hopefully we get it figured out. I'll let you know if I come up with anything.
Sent from my SCH-I500 using XDA App

OK so after doing some research, it looks like this issue can happen if you disable your data (using a toggle, such as the ones in the notification bars of some roms), and then flash a new rom or kernel or something with the data off. It looks like it wipes the APN? Anyone know if this sounds like what may be the issue or how we might go about fixing it?

Well I just got off an hour long call with tech support they think it is an issue with the radio and want me to do an exchange since I bought it less than thirty days ago. So I don't know maybe I should just cancel this and get a new phone with a new carrier. Maybe something with 4g. But I love this phone so I don't know what I'm going to do. Keep me updated if you find a fix.
Swyped on my Mesmerize using XDA Premium App

Check the Showcase AOSP thread. I managed to find a little trick that fixed our phones suffering from the same issue. Its worth a shot on yours.

add144 said:
Check the Showcase AOSP thread. I managed to find a little trick that fixed our phones suffering from the same issue. Its worth a shot on yours.
Click to expand...
Click to collapse
Tried your method and nothing. Kind of running out of ideas here. Any radio/modem I should need would be in the ROM right? I have gone as far as to flash all the way back to DI14 and can't get this thing to work. Still can't figure out how it even happened in the first place.

Well I figured it out for me anyways. Call US cellular and they will give you a new phone under warranty. I'm on mine now. It is back to 2.1 and stock but it works!
Sent from my SCH-I500 using XDA App

bsbokc said:
Well I figured it out for me anyways. Call US cellular and they will give you a new phone under warranty. I'm on mine now. It is back to 2.1 and stock but it works!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Just got mine working about 10 minutes ago. Call USCC tech and they said that for some reason I was no longer "provisioned" for 3G service so they fixed it. I know our issues were a little different. Glad we're both up and running again. Now lets see if I can do something else to screw this up . . . . .

JayRHamlin said:
Just got mine working about 10 minutes ago....Now lets see if I can do something else to screw this up . . . . .
Click to expand...
Click to collapse
Amen to that I spent 4 hours on the phone with them yesterday and they couldn't fix it. So the actually brought me a new phone to my work. I couldn't believe they would do something like that.
Sent from my SCH-I500 using XDA App

Wow now that's service. I have to say US Cellular has hands down the best customer service I have ever had to deal with. Store, tech support, billing. Everything.
Sent from my SCH-I500 using XDA App

JayRHamlin said:
Now lets see if I can do something else to screw this up . . . . .
Click to expand...
Click to collapse
Well it only took me about three hours I tried flashing a new kernel with an app I downloaded from the market can't remember the name but of course everything went to hell. Since I don't have a computer it took me 2 days to find one and get it flaked to stock in odin now my speaker doesn't work oh well maybe in another couple of days I can flag it again. Maybe I should just quit screwing worth it but it's just to much fun lol.
Sent from my SCH-I500 using XDA App

[Q] Time to speak up

Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?

Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App

Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.

I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App

I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.

Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.

Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)

Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App

sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk

It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App

satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App

It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal

I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App

I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App

satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.

It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App

jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.

Official Gingerbread Update Soon???

So I've been looking for a way to try that GB sweetness on my Tbolt. The leak a few weeks ago was very tempting, but due to bricking issue and the fact that the leak is just a test build made me hesitant.
After googling GB update for TB, a few links came up that suggest that the TB and Evo should get official update to 2.3 in June.
Here is my question: I just saw an announcement for Evo update to 2.3 on June 6. When is it our turn??? I know it's a bit antsy but they can't just throw a wet cat in front of me and not expect me to beat that sh#$ up.
But seriously, anyone got news?
here's a poll for ya speculations

Even if sombody has a date its always wrong. So let's get over the guessing game. The bamf gb rom is flawless you just need a little experience when it comes to wiping data and radio updates. But I have had no problems once the ROM is up and running.

And battery life is better in this ROM then froyo from my personal experiences.

Going to have to add another vote for BAMF GB. Loving me some "ROM of Death" ;}

The latest CM7 Alpha build from Slayher is almost problem free for me (no big issues, all data etc. working great) and I've had lots of problems with previous builds. It's worth a shot.

I'm guessing there will be some more leaked builds, but the final version and OTA won't happen until September... 4 to 5 months after the first leak seems to be the standard procedure with VZW and Android updates...

I got an email from HTC yesterday and was told that Gingerbread will be out this summer.
I Emailed HTC to complain about the constant rebooting issue and battery life after the OTA.....bla bla ect ect & asked when the Tbolt will get Gingerbread and this is what I received back.
Dear XXXXX XXXXX,
I understand your device is randomly rebooting after the latest OTA. I will advise how to back up your contacts and perform a factory data reset. If the device continues to reboot we are currently advising customers to swap the device out with Verizon, but I will provide another option as well.
I do not currently have any information that indicates the cause of the rebooting issue or whether it is possible for it to be resolved in a software update. I can advise you that the Thunderbolt will be receiving Gingerbread this Summer.
To back up your contacts launch the People application and press menu=>import/export=>export to SD card=>Phone. If you are not sure that your contacts are in Google you can repeat this step and select the Google category.
The Thunderbolt is usually configured to mass-reinstall your Market applications after a factory data reset if you log in with the same Gmail account. If you wish to avoid this for troubleshooting purposes you can open the Market and press Menu>My Apps and uninstall your applications. Alternatively, after the factory data reset, you can wait to enter your Gmail account until you have had a chance to test the phone functionality.
A factory reset will clear all of the settings and data from your phone's internal memory and restore your device to its default state. Media on your storage card, which includes your pictures and videos, however, will not be affected. To perform this reset, from the home screen, press menu=>settings=>SD & Phone Storage=>Factory Data Reset.
If device behavior continues we are asking customers to swap their devices out at a Verizon store. However, you can also use your warranty with HTC by calling our warranty provider PCD at 1-800-229-1235 (8:30 AM - 5 PM EDT M-F).
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 XXXXXXXXXX.
Sincerely,
Douglas
HTC

Braggo said:
The latest CM7 Alpha build from Slayher is almost problem free for me (no big issues, all data etc. working great) and I've had lots of problems with previous builds. It's worth a shot.
Click to expand...
Click to collapse
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.

We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.

ctinsley said:
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.
Click to expand...
Click to collapse
From what I understand, the 3G/4G/WiFi handoff is fixed in the version released early this morning/late last night.

We went threw the same thing with the incredible-froyo update. When we get updates, is anyone else like, wow that took a year?? Sure we get a couple new features and performance bumps and new extra awesome crapware, but this time I don't think I'll be marking off days on the calendar.
Sent from my ADR6400L using Tapatalk

miketoasty said:
We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.
Click to expand...
Click to collapse
Exactly. So if you're itching for some Gingerbread, you might as well flash one of the roms based on the GB leak. Otherwise you could be waiting much longer than expected
Sent from my ADR6400L using XDA App

ctinsley said:
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.
Click to expand...
Click to collapse
From work to my house to my girlfriends house, I have 4g everywhere. That was the sole reason I dumped CM7. After last nights update, I figured I would give it a try, and am glad I did! 4G Has been fixed and this is now the ROM to use! Everything is working great and have had 0 issues after using it for the last 12 hours or so.

@Miketoasty Do you have a link to your particular ROM and radio?
Sent from my ADR6400L using XDA App

rester555 said:
@Miketoasty Do you have a link to your particular ROM and radio?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Just the latest cm7 and dream kernel. Both on the first page of the dev section.
Sent from my ThunderBolt using XDA App

I hope it comes soon. I'm strongly considering going back to das bamf 2.0 but don't want to brick my phone
Sent from my ADR6400L using XDA App

I didn't know that the DAS BAMF 2.0 was causing some of the bricks. I guess that makes sense being that it is on the leaked version of GB

miketoasty said:
We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.
Click to expand...
Click to collapse
unless HTC/VZW observes Indian summer....
Sent from my ADR6400L using XDA Premium App

I'm running das bamf 2.0 and its GB 2.3.3 with sense 3.0. Runs flawless, quick, and battery is better than anything I've used before.
Sent from my DasBAMF 2.0 Thunderbolt using XDA App

MsSassypants said:
unless HTC/VZW observes Indian summer....
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Please don't jinx it I could so see a developer like Motorola or Samsung pulling something like that.
"Oh yea by summer we actually meant Indian summer so yea just buy a new phone if you want gingerbread now."

Going back to Gingerbread.

I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.

Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.

Dnakaman said:
Ya, I'm starting to think this may have had alot to do with just user error. I remember back in the early days of rooting when people used to brick phones because they didn't know what they were doing.
I think I'll wait another week and if I don't hear of anymore "bricks" I may switch back to GB.
Click to expand...
Click to collapse
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?

bp328i said:
I'm one of the ones who's Thunderbolt's bricked. I can tell you that mine had zero to do with user error. I have been rooting since the G1 days (not my phone but I rooted it for a friend) and this is the first phone I have never been able to fix.
My Thunderbolt was running the best it had ever run (not even overclocked) when it bricked.
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Man, that sucks. I know I've seen you post about the issue, but you seem to be the only one that actually has this issue that has actually posted anything concrete here.
Others that have posted about "bricks" sounded like they just didn't know what they were doing and were actually recoverable.
But like Mike said, enough for me to wait until more evidence is uncovered.
Thanks for the info.

miketoasty said:
Interesting, thats actual enough for me to hold off till a future release. I had a friend who got bricked but had little Android/Rooting knowledge so I kind of blew it off as it must have been user error. Thanks for the heads up, and will now continue waiting for a new release. Damn.
Edit: Did you have any luck getting a replacement from Verizon?
Click to expand...
Click to collapse
And to add to the above I do all my rooting via adb, I have never used a one click root. I'm also an Official Themer on another forum, so I know my way around Android a little.
I had insurance that made me send it off to try to have it repaired first. I just got a new one yesterday.
I'm waiting on a new Gingerbread radio to come out before going back to Gingerbread even though how much I miss it.

Well right before the news was posted, I noticed some connection issues, it was kind of a weird issue. So I reverted back right after seeing the brick thread....
SCARY!

I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!

bp328i said:
I was running BAMF 2.0.4-1 put my phone on the charger when outside to mow the lawn and when I came back in, BAM it's booting to the splash screen then rebooting over and over.
Click to expand...
Click to collapse
Question for you. Did you have a third-party or extended battery in it?

want a droid said:
I was just about to make a thread similar to this. Seems as though the bricking phenomenon has blown over. I just flashed gingeritis beta IX and I'm loving it!
Click to expand...
Click to collapse
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Nope, stock battery and charger.
Sent from my ADR6400L using XDA App

SirVilhelm said:
It's blown over because most everyone went back to froyo. Nothing has actually been resolved.
Click to expand...
Click to collapse
This is what I figured.

A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX

want a droid said:
A lot of people stayed on gingerbread though with no more reports of bricks...
Sent from my ADR6400L running Gingeritis v1.0 Beta IX
Click to expand...
Click to collapse
I think that is where the real problem is.
The issue is so random, there is no set explaination at this time to explain why/how it happened.
Since the one person that I know of sounds like a very creditable person based on feedback on these forums, I myself am going to error on the side of caution.
I was running GB with no issues as well, but I would hate to kill my phone, just because I "thought" it was safe to reload GB.

I have been on BAMF since they came onto the TB scene. Less than a week from phone release I rooted and started rom'ing. I loaded the new ginger radio about a day before the first report of the brick came out. I havent had any problems. But I have been keeping my eyes open to see when or what will cause a brick so every two seconds I cheack my phone BUT i can't post in the development forum yet So i gotta wait till ten UGH

i'll wait for our developers to give the thumbs up on going over to GB roms, whats the rush vs the risk? Not a big deal to wait another week or two considering what u could be going thru. BAMF remix 1.7 is running flawlessly for me after I dropped back from GB.

I was using Gingeritis from Beta 3 to Gingeritis IX. Honestly, I haven't had a single random reboot or any problem at all.
However, I did have a data issue. If my phone would change to a 3g signal, it wouldn't bring back 4G. But, once I rebooted the phone one time, the problem was fixed from there on.
I still have Gingeritis IX on my phone, and its great. I'm running Imo's test6 kernel as well.

miketoasty said:
I was about to make the jump back to Gingerbread "I.e. The ROM/Radio of death" and just wanted to know how many people have gotten over the bricking debacle.
I have yet to hear of anyone who has had a bricked device since a day or two after the incident was brought up.
Click to expand...
Click to collapse
Honestly the bricking thing threw me off first, then I noticed it takes forever to charge, drains quicker and camera and camcorder sucks on gingerbread. So I'm sticking on froyo Bamf for awhile.

Yeah I'm back on froyo. And to those who are "watching my phone and no signs of bricking", there will be no signs. You'll pull your phone from your pocket and have a bootlooping phone, unfortunately. I'm running CM7 gb, 95% of things work like they should, and since it's a froyo radio, I'm immune to the brick of death.
Sent from my ThunderBolt using XDA Premium App

Jaxidian said:
Question for you. Did you have a third-party or extended battery in it?
Click to expand...
Click to collapse
Hmmm... I was wondering this myself. I'm on GB BAMF 2.05 and only have random reboots when I have my 3rd party battery in. The stock battery doesn't seem to have any issues.

Sim frying, over heating, connection loosing, SAMSUNG SERVICE!!!

ok so i was running EP1f and had no major complaints (buttons didnt back light) so when i EP1W came out i ended up running it and absolutely loved it! everything worked and i actually liked my phone with the exception of loosing the stock basic android keyboard that was in EP1F (not the samsung added crap or the one in the market) but after about 2-3 weeks on EP1W i started having huge overheating issues and then i couldn't connect to any data (LTE, CDMA,WIFI) and then guess what!?! my phone decided that it wouldn't recognize the sim card so i truck down to verizon and get a new sim and no sooner than i walk out of the store does my phone decide that that sim isnt good enough either! so i get another new sim card and head home reflash back to stock 2.2 and still no data ability and the sim card malfunctions... verizon was clueless and refereed me to samsung who promptly wanted the phone back!
anyone else have anything like this ?

Eh. It happens. Just back up all your stuff, restock it, and get Sammy to send you a replacement.
Sent from my Droid Charge running GummyCharged 2.0

Yep, already did.. samsung is much easier to deal with than moto!

I've been getting alot of overheating here lately and don't know why. Do I just call the Samsung customer service people?
Sent from my Glitched MIUI Fascinate

Eris _2.1_2010 said:
I've been getting alot of overheating here lately and don't know why. Do I just call the Samsung customer service people?
Sent from my Glitched MIUI Fascinate
Click to expand...
Click to collapse
Iv been having it too i just went to VZW and they ordered me a replacement
Sent from my SCH-I510 using xda premium

I'd like to stay away from Verizon. I'm on my third replacement now.
Sent from my Glitched MIUI Fascinate

Eris _2.1_2010 said:
I'd like to stay away from Verizon. I'm on my third replacement now.
Sent from my Glitched MIUI Fascinate
Click to expand...
Click to collapse
Why would you want to stay away? It's not your fault the phone is having problems.
Sent from my SCH-I510 using xda premium

Well i'm coming from the Fascinate and got a replacement DC and that one had USB problems, then #2 upon first boot had lockups and reboots. Tried to rom it and that didn't help at all. And the DC I have now overheats and becomes unresponsive to touch when charging. So in short I'm tired of replacements and would like a brand new DC, but that won't happen.
Sent from my Droid Charge 4G running Gummy Charged 2.0

I'd stay away from verizon too and go thru the manufacturer. Verizon does in house "refurbishing" sometimes. Someone gets their phone replaced>defective phone goes back to warehouse>warehouse does in house testing - doesn't find an issue, though truly defective>warehouse deems defective device "no trouble found">defective device goes back into stock and eventually out to another consumer as a replacement>consumer has issue with that device. And this cycle can repeat countless times.
posted via tapatalk from my samsung stealth

ticholas said:
I'd stay away from verizon too and go thru the manufacturer. Verizon does in house "refurbishing" sometimes. Someone gets their phone replaced>defective phone goes back to warehouse>warehouse does in house testing - doesn't find an issue, though truly defective>warehouse deems defective device "no trouble found">defective device goes back into stock and eventually out to another consumer as a replacement>consumer has issue with that device. And this cycle can repeat countless times.
posted via tapatalk from my samsung stealth
Click to expand...
Click to collapse
i had that issue with my OG droid... i had 8 or 9 in less than a year... finally went to MOTO and they gave me a whole lot of hell but finally after 6 months of fighting they gave me a D2G which i keep as a back up... as for samsung i called and within 5 min they had emailed me shipping labels and set up my repair ticket...

Now with Samsung is it like VZW where they send out a replacement first and then I return the defective one? And you think they would send a new one instead of a owned one?. I swear we need a Carfax of sorts for these phones lol.
Sent from my Glitched MIUI Fascinate