Related
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
The last link you put up is a theme, not a Rom. Which ROM are you currently using?
Be sure when changing roms to wipe data and cache. Not doing so will cause a boot loop, which you described above. Also, if you have to reactivate your phone and can't get a dial pad, long press the menu button to bring up the keyboard and use the keyboard numbers.
Sent from my ultra fast Liberated Droid 2
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
I don't know what all roms you have tried that won't boot but there was one person who's phones could not boot my cfsv6 through cfsv8 kernels. I fixed the issue in cfsv9 kernel so check to see if the roms you have tried are using those kernels. I know the one you said booted was an older rom and was not using my kernel. CELBFroyo is using the v9 kernel if you want to test that. If that is your issue you can just download the cfsv9 kernel and flash it after flashing the rom of your choice. It was something to do with the hardware in a small percentage of eris's that the kernel would not work with. Maybe you have the same hardware as that case...
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
WheelieBin said:
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
drock212 said:
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sorry, I should have specified... yes, I have pulled battery - issue persists. I hadn't gone as far as a factory reset, but it's definitely less dramatic than a reflashing, so trying that now...
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
WheelieBin said:
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
Click to expand...
Click to collapse
Congrats friend! Glad to hear you're out of that boot loop.
Sent from my MB860 using XDA Premium App
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
I have checked the forum and no thread had the fix I am looking for. I have K13 flashed on my phone and it was working great for over a week, but now all of a sudden today it stopped connecting to rogers. I have the correct internet and mms apns but my phone does not connect to rogers. I get no data and can send messages only some of the time, but I can receive them. I also can make phone calls, but cannot receive them.
Regardless, I have tried entering the apns again, resetting he network connection multiple times and resetting my phone multiple times. I have no idea why it is doing this. Could it be due to the firmware or is there a setting I need to change. Please help!
I had an issue with rogers today also, had no connection at work through out the day but once i left work it started working.
I really don't think this is a rogers issue. I am going to try flashing a different firmware on my phone... maybe that will fix it... I really don't know what to do. :-(
Another discovery is it works on occasion only and sometimes it shows 3g but does not connect to H+ when it sends out data.
Sounds pretty weird. Did you insert another 50cents when the operator asked??
Was working for a week then with no change at your end the weird crap started...
I'd flash back to stock Rom for your provider and see if all goes back to normal. I'd make a backup 1st to switch back if it's your provider and not the device.
Good luck.
Sent from my GT-I9100 using XDA App
aceofclubs said:
Sounds pretty weird. Did you insert another 50cents when the operator asked??
Was working for a week then with no change at your end the weird crap started...
I'd flash back to stock Rom for your provider and see if all goes back to normal. I'd make a backup 1st to switch back if it's your provider and not the device.
Good luck.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'm flashing back to an earlier version. KG5 was working fine for me... should I really flash back to original though? that would be KE2 for me.
SirRomie said:
I'm flashing back to an earlier version. KG5 was working fine for me... should I really flash back to original though? that would be KE2 for me.
Click to expand...
Click to collapse
Up to you really. If KG5 was working good try that 1st. That's what I would do if you are sure it's not your provider at fault.
Just a methodical process of elimination.
Sent from my GT-I9100 using XDA App
Fashing back did not solve the issue...
Doesn't point to your devices software to me from the little I know of your situation.
Could try a different sim...maybe from another network to see if there is something going on there.
Could try your sim in another device also. See if it works the.
Otherwise could flash back to stock. Reset flash counter if need be with jig and take back to shop and see if they can get it going.
Sorry I can't be more helpful without hands on.
Sent from my GT-I9100 using XDA App
I will try the sim card thing. It seems weird to me that it would just stop working like this, but after reading around some think that it is the modem? How could that have even changed in my phone? Does flashing cause it to change? It was working fine for two months solid and for one week on K13.
It is definitely not the sim card. Modem?
I did read somewhere that someones ime number changed when they flashed.
Might be worth a search as I dont have a link.
There is a way to check if ur ime is correct by using the dialer.
Sent from my GT-I9100 using XDA App
Well Rogers actually fixed the issue. I called them and they apparently had tower issues in my area. It is back up and running after me trying to figure all this out. Such a headache, but at least I will know for next time... a problem like this should not randomly arise and the modem should not change if stock firmware is used (given it is the right version). My IME is still there.
Glad to hear all is good. Had my doubts about it being your device
Sent from my GT-I9100 using XDA App
Thanks for all the help. I went through so many different processes, but I actually managed to get KIES to work with my phone now and all the settings I had are back on it too. So at least something good came out of it. Even if Rogers gave me a huge headache.
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.