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.
So I was looking to leave my Sprint contract (long story) and decided to sell my Evo 4g LTE to help pay off the massive contract-breaking bill. I'd had my phone rooted and running CM10 nightlies for quite a while without any sort of trouble.
So right before I put the phone on the market, I took out the SD card, and wiped everything using TWRP recovery. This included Cache/Dalvik/System/Factory reset and the only thing I did different, which was to wipe Internal and External storage.
After that, I flashed the latest CM10 nightly at the time (which was cm-10-20121008 at the time) and called it a day as I didn't want to put any of my info on the phone before I sold it.
Flash forward a couple of days, I sell the phone and almost immediately get a call back saying it has no sound at all.
The guy I sold it to tells me he even tried unrooting and flashing the stock ROM to no avail. I bought the phone back from him, and am trying to figure out what exactly is wrong with it.
Since then, I've discovered that not only is there no sound, although occasionally I will hear the buttons click, so I know the speaker hardware itself is fine, There is also no video playback at all, which makes me think this is some sort of software or firmware problem, though I can't tell where the problem lies.
I've tried installing different ROM's and the best I could get out of video was the Youtube app showing still images every couple of seconds, without any sound at all. I tried loading videos to the SD cards only to get a message saying "This video cannot be played" without any further reason.
I'm currently downloading the latest OTA stock ROM to see if I can restore it to Factory settings, but I'm lost as to what could possibly cause this strange behaviour.
Anybody ever encounter something similar? Any ideas what I could try next?
Alternatively, does anyone want a (mostly) working phone at a steep discount?
Have you ran an RUU yet?
How much do you want for it as is?
jayjam99 said:
Have you ran an RUU yet?
How much do you want for it as is?
Click to expand...
Click to collapse
I tried running the RUU, still won't work.
If you want it, an even $100 will do.
i have the exact same problem ive ran ruu and relocked and locked bootloader i have unrooted ive done everything and the problem still is there please someone help me
So here's what's going on...
I was working outside today, out of range of my router, and I noticed that my phone was..... rather warm. I have the OtterBox case without the holster, so if I can tell it's hot, I know something is wrong. I checked my connections, and my EVO was refusing to recognize any close networks (mine or my neighbors') and there was no data connection to boot. I've been running the CM 10.1 M2 for a week or so, but I hadn't made any changes to the ROM or kernel or anything in well over a week.
As a typical PC user, my first thought was "restart". I mean, it's barely functional as it is; how much worse can it get?
That was 8 hrs ago. I've re-installed all of my Nandroids (the one I made before flashing my first ROM, a MeanBean, and a CM backup) to no avail. Those don't even make it past the boot ani. The most recent CM nightly gets the furthest; if I can skip Wifi and Google account setup, I can get about 2 minutes out of it before the back (right above the kickstand) gets remarkably hot and the phone locks and reboots. I've downgraded TWRP to 2.3.3.0 and wiped that way. I'm just short of going the RUU route, but I'm S-Off so I don't know the effect that might have.
I'm looking for any answers you may have, forum. Could it be a faulty wifi radio causing the issue? If so, why can't I get any data connections either?
Headed to bed for tonight; here's hoping we can get it worked out soon. Back on the Opti S for tomorrow. Thanks in advance!
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Something is wrong with the software hes using if working on regular sense build and not cm,best aaking in the rom developers thread.
paradoxed said:
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Click to expand...
Click to collapse
Yes but after 4.1.2 RUU it still cuts data on and off. Is it possible it's a bad radio or should we try a differentRUU?U
first id say get to an area where the radio reception is better, get an att card and not straight talk and test.this could very well be a hardware issue as well, but it seems more of a simcard issue/software issue than a hardware issue
Hi all,
First, a bit of phone history. I rooted my phone before 4.4 and my sole purpose of rooting was to have the WIFI tether app working since I use my iPad at work and wanted to be able to connect to the internet there using my phone. I didn't care about custom ROMS, since I really don't have the customizing curiosity most of you have with totally overhauling my phone. (I'm getting old, I think, heh)
So it was working fine all summer and then about 2 months ago after I said to myself, "Hey, I wouldn't mind having fastboot turned on again", my phone got stuck in a horrid bootloop. It took about 5 hours of rebooting and swearing for it to finally give me any access to the bootloader.
When I was able to do anything to the phone, in a panic, I simply did a factory reset.
It actually went well. Though I had to do it twice for it to go smoothly. Now my phone runs much smoother. (Even though I don't do custom ROMS, I do install a ton of interface tweaks from the App Store. And yes, I pay for them) Also the battery lasts a LOT longer.
Now the bad news. My bootloaded shows I'm tampered and unlocked, but my superuser must be broken and nothing on the phone shows I'm rooted. Root required apps won't work and apps to check if I'm rooted say I'm not.
WIFI tether of course also doesn't work but that's not the problem I'm asking you all about.
The REAL problem is my 3G/4G radios seem to be broken. What I mean is if I set my phone to be LTE/CDMA the phone will switch back and forth every couple minutes between the two regardless of signal strength leaving the connection gone while it keeps switching back and forth. If I leave it on CDMA only, my connection is fine, except of course I'm on 3G which is slow. (duh) This problem occurs anywhere. The same at work or at home 20 miles away, which I assume uses a different tower.
Yesterday my boss at work got a new Galaxy 5 and asked my to help him set it up. We are both on Sprint and work in a factory which causes the 4G to be quite slow inside, but I promptly installed speedtest and ran it on both his phone and mine (I turned my 4G back on for the test) He scored a 22 Mbps while I scored a .5 Mbps.
Yikes! I guess my radio really is broken.
Can anyone help me to get this phone going in either direction? Either fully rooted with the radio and WIFI tether fixed or even backwards going unrooted stock with the radios fixed?
I'm heading out right now so can't reply right away, so forgive me if I can't answer any questions until later tonight.
Thanks in advance!
p.s. I'm fairly knowledgeable with computers and can follow most rooting guides without hand-holding, though I admit some of the Rooting process is beyond my grasp since I'm not really into the developing mindset.
Yikes, 24 views and no replies. I thought I might have been too long winded . ?
I should have just posted this; Help, I'm unlocked but my superuser isn't working
?
Hello, I am by all means no expert and i had seen this and figured one of those would come here and help you but it seems everyone may be busy for the holidays. Kidding aside, if it were mine and this happened what I would do is flash a custom recovery like TWRP and then it will tell you you are not rooted and then you can install supersu from there. There may be other ways or easier ways to accomplish what you need but this is the method that I personally would try. I know just enough to get myself in and out of basic situations but I do believe this will work for you. Maybe one of the more knowledgeable folks will chime in with some better advise. Good luck and let us know if you get it sorted.
Bryon
Thanks Byron, I'll give it a try after work, don't want to screw up my phone right before I need it.
I still haven't tried it yet, I want to wait until I'm off for the holidays to blow up my phone