Related
I dropped it but it still turns on. It gets to the Welcome to t-Moble screen or what ever splash screen from the rom I have loaded and stay there forever. I have tried a few SD card rom changes but no success. I asume since this happend after a fall it is a hardware issue. Is there anything that can be done?
Mike :shock:
Don't everyone respond at once? :?:
I cannot see that dropping it would wipe the flash memory however you could try hooking it up to usb and attempting a rom flash via that method, if there is no obvious sign of damage it should be returned to supplier for repair.
Thanks for the response
It won't even let me sync. Won't even connect. I dont think it is getting far enough to start those programs. The boot loader works fine and the diagnostic checks from the boot loader all say they are ok. It has indeed been through a lot and has quit a few obvious marks on it. Like I said before, it takes a boot load ROM up grade from an SD card but when I reset the device it just stops at the "splash" screen that says welcome to Tmobile. Cant get it to go any further
I'm havin a similar problem. I dropped my xda, and it 's stuck now in the bootloader. I can't even boot normal. I tried flashing it with another rom through an SD card, but he's still stuck in the bootloader menu.
Doing a hardware replacement will kost met 400 euro, so i'm not going to do that. If anyone has risky solutions, just pm me ... it's wasted anywayz
grtz
PLEASE HELP SOMEONE
Where can I send thid to get it fixed???
If there is a solution please post
amd2be said:
I dropped it but it still turns on. It gets to the Welcome to t-Moble screen or what ever splash screen from the rom I have loaded and stay there forever. I have tried a few SD card rom changes but no success. I asume since this happend after a fall it is a hardware issue. Is there anything that can be done?
Mike :shock:
Click to expand...
Click to collapse
Why did you drop it? try un dropping it.
Solution
Pick it back up.
Oh and... quit dropping that ****.
Either that or pay the $3 a month for insurance and just get a new one.
** I've fallen! And I can't get up! **
Sometimes the power button gets jammed down after a drop, worth checking the buttons for this. When you go to bootloader does gsm say ok? If the xda has intact bootloader and gsm I think there is still hope.
Android froze so i hard reset...upon doing so it shows the splash screen then vibrates seven times and does nothing
already tried pulling battery and waiting like i found in another thread.any one else have this problem?other thread didnt come up with any working solutions.
tehcor said:
Android froze so i hard reset...upon doing so it shows the splash screen then vibrates seven times and does nothing
already tried pulling battery and waiting like i found in another thread.any one else have this problem?other thread didnt come up with any working solutions.
Click to expand...
Click to collapse
I have this same issue.
I hadn't turned my phone on for about 2 weeks. I turned it on, it booted windows, I restarted and it just hung at the main booting screen. The numbers that show radio version and all of that never come up.
I've hard reset, I've gone into the boot loader without issue, I've soft reset a couple times -- no dice.
Any ideas?
i have same problem
but when i put it in cool place like freezer for 3-4 min it works but when it become hot again hung and restart then vibrates for 7 times again
i don`t know what should i do...
tehcor said:
Android froze so i hard reset...upon doing so it shows the splash screen then vibrates seven times and does nothing
already tried pulling battery and waiting like i found in another thread.any one else have this problem?other thread didnt come up with any working solutions.
Click to expand...
Click to collapse
you hard reset, because it froze in androiddd????but why???...android runs from sd card and hard reset restores your internal device storage...........you guys need to first read
well thanks for all the help instead of just telling them theyre stupid
i ve got the same issue.. android froze so took battery out..
after that it hangs on htc screen or vibrates then nothing..
i then put the stock rom back on via boot loader method (volume down and power)
managed to getting working once to setup the phone then it told me to reset so the settings took.. upon reboot same ****!!!!!!!!!!!!!!
GOt the same issue. I called HTC and they think it is a motherboard issue. So currently returning it back as it was and will sent it to them. Maybe Android fried something...with overclocking
I have the same ******* problem ! But 2 mi in freezer working fine
I experience this on my nexus one, any fix for this? thanks!
pakure said:
you hard reset, because it froze in androiddd????but why???...android runs from sd card and hard reset restores your internal device storage...........you guys need to first read
Click to expand...
Click to collapse
why do you think he runs android from SD?
android can be installed via magldr, too...
Been there done that, solution RMA it.
http://forum.xda-developers.com/showthread.php?t=982454
#6
3. problems get worse. At this stage it is possible to notice the 7 short vibrates at boot time if the phone is warm or kept in a warm environment. You don't have to push it very hard, it only needs to be warm. The vibration pattern is an error code made by the actual qualcomm chipset
can any help me i have the same issue HTC HD2 Vibrate 7times. I have HTC HD2 Tmobile
HTC HD2 Vibrate 7times. I have HTC HD2 Tmobile orange Poland locked
hello, do you have your stock rom somewhere?
I'm having a problem with my touchscreen that started happening yesterday after I flashed a new ROM. I flashed Android Revolution HD 1.1.1, and on the lockscreen after the first boot is when it first started acting up. This youtube video shows exactly what my phone is doing: http://www.youtube.com/watch?v=iIrmLOTiUZk
I've nand back to other roms that I've used in the past, and still the same issue. Superwiped and flashed different roms, and it would solve the problem for several hours, but the issue comes back. When the problem happens, a restart will solve the issue for maybe 15 minutes. It seems as if it's a hardware issue, but I don't get why rebooting/wiping and reflashing would solve the issue for a period of time. If anyone has any advice or the same issue with a fix, it would be much appreciated. Thanks in advance.
*Idk if it matters, but I'm hboot 1.4, zagg invisishield screen protector on.
Also, the touchscreen issue only happens at the bottom center of the screen - where the lock ring is located.
Update: I nand backed to stock rom, no issues for about 24 hours, started happening again. Any thoughts anyone??
Might be a hardware issue. If it keeps occurring I'd suggest taking it in to be looked at. Or you could try reflashing your recovery and doing a full data wipe and flash a stock rooted rom and see if that helps. Hope it does. Good luck.
Locked & Loaded
""shooter on Deck""
Thanks, I'll try reflashing my recovery tonight. It seems to be hardware related, but the temporary fix (data wipe and flash Rom) is what confuses me. I just hope I don't have to send it in and get a refurb with hboot 1.5.
Also, when I do super wipe, should it automatically boot into recovery? It just hangs on the white HTC screen, and I have to.pull the battery to get into recovery. And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Well if your doing a super wipe and it still keeps some of your old settings of a prior rom then I'd suggest trying a different wipe method or redownloading the the super wipe zip, you might have gotton a bad download. As far as if it's supposed to boot right into recovery that I don't know because I don't use any wipe method but the recovery. It hs always worked for me. Try reflashing your recovery and wiping with just the recovery options. Wipe data "complete factory" ,cache and davlik-cache. Then try flashing a stock rooted rom. Or if that doesn't work try the official ruu.
Locked & Loaded
""shooter on Deck""
b1gsby_02 said:
And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Click to expand...
Click to collapse
Well it keeps your wallpaper because Google syncs it with your Google account. That's normal. But as for everything else, it sounds like a hardware issue.
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Sent from my PG86100 using Tapatalk
I flashed twrp 1.1.1 over 1.0.3 and did a data wipe, cache and dalvik. Flashed a rom and so far so good. I'll see if I can go more than 24 hrs without an issue. If it's a hardware issue, I don't understand why flashing a new rom temporarily fixes the issue, and since the issue started right after I flashed a new rom. I'll continue to update on here and hopefully the reflashing of recovery helps - thanks laie.
Didn't know wallpaper was synced with google account - thanks gumby
Gumby63 said:
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Click to expand...
Click to collapse
Did you do anything else to try fix the problem?
b1gsby_02 said:
Did you do anything else to try fix the problem?
Click to expand...
Click to collapse
I'm not sure what else to do. I suppose I'm stuck with contacting HTC about a repair. I've done a little bit of research and some people having similar problems have said that it could be a problem with the digitizer. But most explanations were very vague so I'm still not sure what I'm going to do.
Sent from my PG86100 using Tapatalk
Well you should be good to go. Post back in 24hrs with what's going on. Glad your running ok for now.
Locked & Loaded
""shooter on Deck""
Phone was fine all last night and this morning. Early afternoon it started acting up a little bit. Nothing like it used to, but I notice when I set it down or shake the phone a little, it will trigger the issue. So it's more than likely hardware related. Does anyone know Sprint's policy on fixing a phone that is rooted? I am jw if I should revert back to s-on before I go to a Sprint store to have them look at it. I don't know if they check that or not. Usually the first thing they always do is make sure everything is up to date too. Any insight is appreciated, thanks.
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Rob the plumber said:
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Click to expand...
Click to collapse
Please update us after you talk to Sprint. I am curious to what they say about you being rooted and what the problem may be. My phone has been running fine for awhile now. After I reflashed recovery, data wipe, flashed rom, it acted up for a short while about 12 hours later. It's been almost 24 hours since it last acted up and has been fine so far.
Rob, just wondering if you talked to Sprint yet?
Also, does anyone know if I should go back to 100% stock and S-on before bringing my phone into Sprint? They always seem to update everything, and if there is an update, they usually tell you that's the reason why your phone isn't working the way it should.
UPDATE:
I went back to 100% stock and S-ON following this guide: http://forum.xda-developers.com/showthread.php?t=1194053 Then I went into my Sprint store, told them about the issue, and the first thing they did was asked if I had reset the phone and they checked to see if there's any updates available. The phone started to act up again while they were looking it, luckily, because they have to replicate the issue before they can fix the problem. They said it was probably the screen and they were going to replace it. They had me come back an hour and half later, told me they tried replacing the screen and that wasn't it. They didn't know what was wrong, but concluded it was a bad phone. They replaced my phone with one that someone returned within their 30 days. It's not a refurb, but not a brand new one either. I had to pay $35 for the service charge for fixing my phone. I hope this helps anyone who's having the same issue.
Of course my replacement phone has hboot 1.5.
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Rob the plumber said:
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Click to expand...
Click to collapse
I have tried a few different batteries, and it didn't seem to matter. Maybe your situation is different. Hopefully that fixes your issue!
My issues have returned. Off to the sprint store!
Rob the plumber said:
My issues have returned. Off to the sprint store!
Click to expand...
Click to collapse
Good luck! Did you revert back to stock and s-on? Or are you going to tell them you're rooted?
I think I'm going to just put a stock ROM on it and ask them first before I hand over the phone.
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App
first i wanna thank you guys for this awesome forum
i have an AT&T aria phone that randomly reboots
LIBERTY PVT SHIP S-OFF
HBOOT-1.02.0000
MICROP-831b
TOUCH panel-stn21_03
radio-7.16.35.11
Nov 4 2010
the phone is rooted with CWM v2.5.0.1 istalled.
i flashed the original ATT rom 2.2 from HTC website and it didnt fix it
i flashed shipped att rom and it didnt fix.. also flashed rooted rom yet no luck
1-i tried to unlock the bootloader with HTCDEV.COM but it gives me error message
fastboot oem get_identifier_token
...INFO[err] command error
2-i tried to use the revolutianary website and no luck either
3-i tried to put the original img on the sd card LIBEIMG.zip and booted into bootloader but the phone didnt recognize the file at all.
i am a newbie in the android word but i can swear i did every thing by the book in these last 3 steps** at least as i could understand**
p.s: i dont know wut or who did this to this phone
This is sort of a long shot, but did you happen to install a 32GB SD card around the time the problem started happening?
If not, did you change ANYTHING else? new SIM card? new charger? etc.
nope i did not install 32 GB card..
i dont know exactly what happened to this phone.. i took it AS IS..
when i first got the phone it had the original at&t 2.2 stock S-off ... i was lucky to flash CWM using fastboot..
i think if i can install HBOOT again and turn S on this might solve the problem... or may be i need to do something to the partitions but as i told u im a newbie in here
i am sure it is a software problem due to the error message i get when i try to unlock the bootloader...
I tried everything: stock AT&T Froyo rom, returned to S-on, new sd card, new sim card. Also returned to HTC for "repair," but it still rebooted so I returned to HTC for another try.
BTW, I used the Unrevoked method to root/S-off the phone, and the S-on method listed in the development forum to take the phone back to stock. Both with no problem (several times). The S-on was a little trickie, had to load stock AT&T rom, then follow the S-on instructions, which includes loading the stock AT&T Froyo rom again.
I'll report the results of my 2nd HTC repair on the 2 Arias reboot problem thread.
Sent from my MB860 using XDA
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
gdjy said:
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
Click to expand...
Click to collapse
Don't try to do that. HBOOT 1.03 will not fix your problem, it'll only make it worse (not being able to easily S-OFF). You should avoid HTC's official bootloader unlocking method -- it's worse than Revolutionary.
thank u drumist...
i tried already but no luck.. it says device ID error..
i am so desperate in here.. is there anyway i can fix this aria??
To my surprise I had called HTC and found out that my phone was still under warranty. As I said above, the phone is now back at HTC for a 2nd try. I will let you know what they found as soon as I get the phone back -- it took about a week last time.
Drumist was very supportive in my effort to find the problem, and against his advice and out of desperation, I did restore the HBOOT, and, as he said above, it did not solve the problem. The phone was back to being completely stock -- ATT Froyo 2.2 and S-ON -- and it sill had random reboots --taking anywhere from 1 minute to almost an hour before rebooting. Which is really annoying when trying to troubleshoot. I even re-rooted and S-Off'd the phone using Revolutionary, and still had the problem. I then returned the phone to stock again prior to sending it to HTC for repair. Checked one more time... still random rebooting. As I am now using another phone -- Atrix 4G -- solving this has become more of a challenge.
The other thing that's amazing is that I have 2 ATT Arias with exactly the same problem!
I wonder if it is a location thing. You don't happen to reside in SE Pennsylvania do you?
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
charbo187 said:
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
Click to expand...
Click to collapse
I have to agree with you, it is really annoying. Luckily I dont use my phone very often. I dont think it is location based, as I'm in eastern Iowa.
Ok. Just got my Aria back from HTC after their 2nd attempt at at fixing the random reboot problem. It rebooted within 5 minutes of turning it on! And twice after that.
The only thing I did was put in the battery. No SD or SIM card, and I did not plug in a battery charger. I didn't even have a chance to connect to my wifi.
I will call HTC tomorrow and anticipate sending it back to HTC for a 3rd try.
I really thought they would send me a new phone after the 2nd attempt at fixing it. Although now I'm really curious about what could be causing this.
It's interesting that that there are more reports about this problem. I had rooted and installed multiple roms before restoring it to stock AT&T Froyo prior to returning it to HTC for repair. Has anyone had this random reboot problem on a phone that was never rooted?
Oh well. I will probably be sending it back to HTC tomorrow, and will keep you posted about the results.
Sent from my MB860 using XDA
I am having the same issues...luckily I now have the HTC One X, however I do still use the Aria as a dedicated GPS, which is frustrating having CONSTANT reboots.
This also only happened recently...I wonder what the issue could be...
Reboot saga
Just spoke to HTC about their failed 2nd attempt to repair my phone. They told me the repair records state that they replaced the "main board," which I assume is like the mother board.
If that is true, I would assume that would be like getting a new phone. If that doesn't fix it, I am truly baffled. The ONLY thing I did was put the old fully charged battery in the phone to test it -- without a SIM or SD card . Could the problem be related to the battery? Since I have another Aria (with its own battery) with the same problem, I doubt it.
Regardless, HTC is having me send it back for a 3rd try to fix it, and they sent me a prepaid shipping label this time.
They said if the 3rd repair attempt doesn't fix it, they would send it to a higher level repair facility for a 4th try! I can't complain about HTC's commitment to trying to repair my phone.
From the responses on this thread, this has become a recent problem. Mine started about a month ago. Any theories out there?
Thanks for sharing your experiences yar, however I'll be dealing with the reboots cause I cant go that long without my phone.
Another thought I had while driving yesterday, Do your guy's that reboots, happen usually after you press the lock button? I've noticed after I send a text message and I hit the lock button is mostly when it will restart. Anyone think it would be that button causing the problem or maybe the HTC Sense Lockscreen?
While I'm waiting for HTC to return my phone after their 3rd attempt to fix this problem I have been experimenting with my other Aria.
I booted into CWM and left it there for over an hour and the phone did not reboot. Does this helps isolate the problem?
Also, has anyone managed to stop a random reboot problem?
Sent from my MB860 using XDA
Just got my Aria back from HTC after their 3rd attempt, and it rebooted within 10 minutes. I even used a new battery, thinking that somehow that was causing the problem. No sim or sd card, and I did not even log onto wifi. They claim they replaced the "main board." Its hard to believe they actually tested it.
Probably beating a dead horse, but I will take HTC up on their offer to send it to the next level of service for a 4th try at fixing the problem. Can't believe it wouldn't be more cost effective to just send me a new phone at this point... but then there might not be any new Arias available.
Sent from my MB860 using XDA
try setting the Aria data comm to Edge only
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
RWB Jr said:
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
Click to expand...
Click to collapse
I will have to give this a try, as for HTC and ATT knowing, they probably don't care and I dont really blame them this is a 2 year old phone.