My Alltel heroc randomly soft resets itself. It's done this while unrooted and on the stock 2.1 ROM, and most recently again after I rooted and flashed CM7 on it.
The only change I can think of causing this behavior is that I installed the CWM Tether app on it, but I find it difficult to blame the app for this behavior.
I've perused other threads, but none of them seem to offer any help or solutions. What should I do? Thanks in advance.
Update!
The phone was originally S-on, this did not seem to affect flashing CM7 or anything though. I got the phone S-off, then changed recoveries to CWM from darthstar recovery. I had seen that CM 7.2 had been updated to RC3 for the heroc, so I downloaded it, wiped everything, and flashed it. I also formatted the SD card before and after the flash. I hope this will take care of it for good.
hopefully your issues are gone for good, but if they come back and you figure out what the deal was please let us know
Related
alright so a while back i flashed a custom kernel im not sure which one it was but in settings under kernel it says "2.6.27GK-0.32 gbhilstovepipe )". now when i flashed it i didnt really know what it was or what it does but it said it would make it faster. i havent noticed any difference and ive been looking around and searching but i cant find much information on the hero kernel. i was just wondering if anyone knows how i can get my kernel back to stock and if you could either explain to me or link me to what a custom kernel does. I know this is probably a dumb question but i was just wondering if anyone can help?
and just one more quick question. i have been trying out several of the new 2.1 roms and love them but cant deal with some of the bugs on them so i went back to gumbo 1.5c. i wiped and did a nandroid restore and everything seemed to be back to perfect but ive noticed that now it keeps acting like how it did when i put 2.1 on by slowing down after a while to the point where its just about unusable and i have to restart it. has anyone experienced this or know why my hero is acting so dumb?
Youll probably just want to reflash your rom again without wiping, should work fine. If not youll have to wipe and reflash to get everything back to normal.
Anyone else having this problem? Any time I try to move an app to SD it just sits there for a little bit and then reboots. I can't update google skymap because I think it's trying to install on the SD too.
I tried searching but my search-fu is weak in this case. I did find someone in some other forum saying he had this problem but it seems to have gone unnoticed.
Anyone? Bueller? Not even a "apps2sd works for me wtf are you talking about?"?
Apps2sd works for me wtf are you talking about?
How about some details?
AT&T or T-Mobile Nexus One?
Bootloader locked or unlocked.
Rooted or unrooted
Stock FROYO? FRF50? FRF72?
What radio?
Using custom cooked rom?
This is me: AT&T Nexus One, unlocked, rooted, official FRF72, apps2sd works just fine, wtf are you talking about?
I'm having this problem too. I suspect it's related to having used cyanogenmod's a2sd for the apps in question - your thoughts on that?
I'm currently running frf50 on an unlocked t-mobile n1. I used someone's pre-rooted Rom. I was running cyanogen 5.0.7, used apps2sd once but decided to undo it and did a nandroid restore. I didn't do a wipe so I'm going to try that and see if it makes any difference.
This is exactly my situation, I suspect even the same pre-rooted froyo (Paul's). Let me know if the wipe helps, and if it does... how do you recover all your stuff?
paulvallee said:
This is exactly my situation, I suspect even the same pre-rooted froyo (Paul's). Let me know if the wipe helps, and if it does... how do you recover all your stuff?
Click to expand...
Click to collapse
So I wiped my phone last night, and everything seems to be working now. Started up my phone, logged in, and all my apps started reinstalling. I used SMS backup & restore to restore my SMSs, and everything is mostly back to normal.
How are you moving apps to sd?
I have the exact same problem as the op describes.
Running frf50 on a T-Mobile N1 that I updated the day that build leaked. Not the pre-rooted version I don't believe.
I'd like to figure out exactly how to fix it since from time to time my phone will tell me it's low on space and I end up having to delete several things.
I'm gonna be blunt and say anyone who doesn't want too root their phone really should not be running leak builds of an OS either.
You're just asking for trouble, and without recourse to fix it.
wrong topic
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
So sorry for having to ask ... I have managed to get my One (ATT) version stuck in a boot loop. I cannot seem to find anything to restore from in CWM and the only thing on the SD card currently is the custom ROM I was attempting to flash ... I really don't know how to fix this, if anyone could help me I'd really appreciate it. I did some searching around and haven't found a solution to my specific problem, even though others have soft bricked theirs, it seems their fix was much more simple than mine.
I'd love to help, can you explain what rom you were flashing and what went wrong? Did it get stuck in aroma installer?
You should always perform a nandroid backup before doing anything for future reference.
Sent from my Tricked out HTC One
Thanks for the quick reply. I was flashing Android Revolution HD. However, when it was complete I attempted to use Titanium Backup to restore my contacts etc. Apparently the ROM didn't like some of the things I attempted to restore as it conflicted. Like Blink Feed didn't work any longer, just a blank screen where it once was. I decided I would try and re-load the rom again via CWM and went through the wipe process. However, before I went through that I believe I accidentially unrooted the phone by selecting fastboot? Before I got into recovery. Now, if I try to re-load Android Revolution ROM .zip via CWM, it will become unresponsive halfway through the installation. I am pretty sure CWM re-rooted my phone for me as I saw a message asking if I would like to do so and I selected yes. So as of now, I'm just stuck and unaware of what I need to do to fix it =(