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.
Related
I recently traded my Sammy Moment for a HERO. I am rooted and flashed but found that some ROMS gave me trouble; Fresh being one of them. Looping boot screens and slow performance contrary to what I read about the roms I flash. Is there anything I may be missing? I rooted via ADB and did find an issue while the recovery was flashing it said: MD5 failure and no space; but recovery still flashed and works.
Last I was on XDA was with my G1 and Tilt. Anyone wanna hip me to what I have been missing? By the way I have succefully flashed the BUUF rom and and the Zen, darch booted with FC's and the others looped.
I wiped dalvik and system and reformated my SD.
Does your Hero have "With Google" branding?
Some of the older phones don't. And at that, some of the older chipset phones can't over clock as high, and OC'd roms will cause a boot loop.
That's the only thing I can think of that wil lbe causing the issue.
You should also try to Wipe everything under the wipe menu except maybe rotate and batt stats before you flash a rom. I always try to wipe clean before I flash.
What Kcarpenter said.
I got my Hero the first day out at BB. I can only clock to 710 otherwise phone starts blitzing.
Gorguts said:
...slow performance contrary to what I read about the roms I flash...
Click to expand...
Click to collapse
Yeah, this is just what most of us here have learned to deal with, as this phone model is nearly a year old and built with hardware that isn't quite powerful enough to smoothly handle the software stuff we try to put on it these days. We are still way ahead of regular HTC/Sprint stock though which is nice.
other than what the others have said...
other options to try...
have you tried the DamageControl ROMs? they are very stable.
if issues persist... maybe you have a bad memory card? there were a rash of them and can cause weird issues.
or you have a bad hero! was it new? warranty??
if so.. get warranty trade in. if you can show issues with phone that is not related to flashing and rooting!!!
Try froyo if you don't care about sense. I have yet to have a bootloop flashing nightlies. Flash a new bootloader, wipe dalvic, system and cache. I'd do each several times just to be sure. Use a new download and verify the checksum
Sent from my HERO200 using XDA App
Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!
Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android
Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking
Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android
The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.
I am in dier (sp?) need of a new rom. I'm currently running cyanogen ..dont know what version but its the purple glass one. Lately everything is coming up as errors, my camera doesnt even work 98% of the time, and it takes about 3 minutes just to dial someone.
So question of the day: I was told by someone I consider "superior in phreaker knowledge" that I shouldnt run 2.3 on my phone. Mainly because his is *so much better than mine* but whatever.
I just need a good rom, a FAST one. I am open to suggestions. And if running 2.3 on my hero is stable and fast then I am open to it. preferably something less glitchy.
Try aosp's new gb build
Sent from my HTC Hero CDMA using XDA App
I ran cyanogen 6 for a while, then Jaybobs extblue froyo build for about 6 months. I've had Aosp's gingerbread mod since Feb, and it is by far the best rom I've ever had.
Yep asop 2.3 best rom I have tryed
clutch_08 said:
Yep asop 2.3 best rom I have tryed
Click to expand...
Click to collapse
+800%. The AOSP Froyo build is awesome, but there is nothing like showing off our little Heroes running Gingerbread like a dream. AOSP 2.3 is damn good.
As of the 4/21 build of AOSP, I would highly recommend it as the go-to gingerbread rom. CM7 and Gingersense are all well and good, but nothing has felt quite as snappy as this build (ymmv). It's also a smaller download than the others by a good margin. Not to mention GB includes a built in CPU governor, so you'll no longer need SetCPU. Seriously, just try it out.
ahhhhhhhhhhh!!!!!!!!!! ive tried flashing 2.3 3 times now. ive tried re-downloading the file, tried downloading it to the phone and via sugarsync, tried wiping everything and it keeps showing "android" then goes to set up, then back to android, then back to set up. guess im going with 2.2
What all are you wiping before you flash?
followed a guide since it'd been over 6 mns since my last flash. did the factory reset, wiped cache, i think those were the only 2 options it gave me to wipe.
MyHerox25 said:
followed a guide since it'd been over 6 mns since my last flash. did the factory reset, wiped cache, i think those were the only 2 options it gave me to wipe.
Click to expand...
Click to collapse
First, if you have the sprint radio that ends in .27, you should upgrade it to .29. Second, if you don't have clockworkmod recovery, get it because it wipes all the correct stuff. Third, go to this site and follow the step by step: http://romrepo.info/wiki/index.php?title=Sprint_HTC_Hero
Definitely get ClockworkMod set as your recovery. I'm not even using the newest one and it works great. Every time I go to a new rom, I wipe the user data, cache, battery stats, and dalvik cache.
i already use rom manager and clockworkrecovery 2.3 just did NOT want to install correctly on my hero, so I went with asop (sp?) 2.2 and it worked perfectly. I love my hero once again- very fast.
Omg this Tom has been the answer to my battery nightmare. Since flashing, I can go all day without my phone dying (and I use it a LOT!)
Sent from my HERO200 using XDA App
I flashed with the stable build of CM7 on my N1. This the first time I have flashed it.
For awhile it was working ok. There were a few bugs here and there, but no showstoppers.
But now, the Launcher has decided to not work at all. It's completely unresponsive to any touch, and it's in an infinite FC loop. My phone is useless now. I've rebooted, powered off, cleaned the cache -- nothing is working.
My question is... can I flash it back to stock? This is beyond frustrating, and I'd rather just stick with a no frills stock OS without all the bells and whistles.
Yes, read the wiki's on how to flash to stock.
Did you do a full wipe before flashing cm7? This include welling the system partition
i followed each and every step of the CM7 instructions.
thanks! i will look into it.
If you flashed CM 7.1 Then i had the same problems as my N1 locked solid.
After a few minutes of flashing it used to become unresponsive and all.
I tried everything but sadly havent been able to find a solution.
I say you should try Cm 7.0.3 That is very stable. I am currently using that and am loving it!!
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