Related
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.
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.
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
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
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5. I have rooted my phone with Odin3 v 1.85, but it's been running slow even before the root. (In fact, I rooted the phone so I could install a lagfix, but I can't find one for Captivate I897 running on 2.3.5).
Anyway, I don't see the reason for games and apps to be running slow because I've heard that the Captivate has a pretty good GPU. Also, it's not like I've overstocked my phone's storage; I only have a few apps.
I've also made a short video explaining my problem further. Just search "slow captivate" on youtube. I should be the first video: "Really Slow Samsung Galaxy S Captivate - Fix?"
I've searched everywhere for a fix, but I can't find anything, so I came here. Does anyone have an idea on how to fix this, or at least reduce the lag?
Thanks in advance,
-xxTDGPainxx
I was seeing my phone work slower and slower on 2.3.6, I suspected that the developers of the apps I used were starting to develop for ICS and that maybe it was different enough that the updates were causing the apps to misbehave on older versions. I flashed to ICS just to see... and it was a great move, ICS on the captivate flies!!! I used SlimICS, I think it is the right way to go for Galaxy S phones...
xxTDGPainxx said:
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5.
Click to expand...
Click to collapse
Have you run any tools to see what is sucking up your phone's resources?
[email protected] said:
Have you run any tools to see what is sucking up your phone's resources?
Click to expand...
Click to collapse
No, I don't think I've checked that. What app do you recommend on checking that?
xxTDGPainxx said:
No, I don't think I've checked that. What app do you recommend on checking that?
Click to expand...
Click to collapse
I would say cpu spy
Sent from my SGH-I897 using xda premium
First of all, lagfix isn't really used anymore. Also, I would say to get rid of those task killing apps. They don't help and only add to your problems. A lot of the symptoms you encountered are pretty common, and I was expecting something much worse. You seem to be running a different kernel that allows overclock; which is it?
If all else fails, try ICS
Sent from my ICS Samsung Captivate
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
xxTDGPainxx said:
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
Click to expand...
Click to collapse
You flashed it twice, correct? Try wiping your data.
korockinout13 said:
You flashed it twice, correct? Try wiping your data.
Click to expand...
Click to collapse
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
xxTDGPainxx said:
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
Click to expand...
Click to collapse
This is the stable ics in my opinion, but i use aokp by sixstrings.... http://forum.xda-developers.com/showthread.php?t=1362092
Sent from my SGH-I897 using xda premium
Maybe don't wipe dalvik cache. That can sometimes result in that happening
Sent from my ICS Samsung Captivate
I gave up on ICS... I could not get it to work for the life of me and it was getting me extremely frustrated. I almost bricked my phone (I think).
Maybe I'll try it again if someone could link me to a detailed step-by-step tutorial to upgrading to ICS. I'm very new to the way android works and a lot of the tutorials are just plain confusing to me...
I ended up reverting back to GB 2.3.4.
Thanks for helping me out though.
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
korockinout13 said:
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
Click to expand...
Click to collapse
The one in your sig is about the best I've seen. Great job!
GUIDE TO INSTALL ICS, my way at least
Hey if you're looking for a good guide to putting ICS on your captivate I can help, The first time i tried ICS i messed things up and angrily decided that i wouldn't try it again and reverted back to 2.3.5, after carefully trying ICS again i love it so much. I won't ever go back to android 2.whatever.
I used CM9 ICS and have no issues or bugs. It's possible there are other better ICS roms but i prefer this one since i know for a fact that it works great.
http://forum.xda-developers.com/showthread.php?t=1363760
You'll need to download CM9 v17 and a gapps package on your SD card.
trust me, ICS is worth it, it's much better than 2.3
if you have titanium backup backup your user apps (NOT SYSTEM APPS/SYSTEM DATA)
Rom installation:
First things first always do a nandroid backup so you can go back easier, if necessary.
once thats done go to CWM recovery and do a wipe data/factory reset, wipe cache partition. once that's done install the CM9 .zip package for the rom.
IT WILL STOP HALFWAY THROUGH AND REBOOT ITSELF, as this is the new kernel being installed. while it's still rebooting pull the battery and let it turn off, reboot straight into CWM recovery.
once this happens go back to install you CM9 .zip file again. it will finish all the installation after that. once it finishes the install you should definitely install the Gapps.zip. it will load up your google apps (market,gmail,youtube,etc and your google account sync) if you don't load the Gapps you will not have very much functionality to your captivate.
once you have your google apps installed you should be ready to fly with a fast responsive captivate. Hope this helps, it took a few trial and error runs before i figured it out.
If you used titanium backup to backup your apps you can restore APPS ONLY!!! don't restore any system data/system apps!!!! it's very important that you don't do that.
that should be it. enjoy your ICS, it's much better than android 2.blah
Fastness: CM7
Sexyness: CM9
That's the answer to everything.
I have run aokp (my current) and doc's master. Both have been great!
I'm far from an Android guru but if you follow the directions, you will be ok. Both also have relatively supportive forums if you get in a jam.
Sent from my SGH-I897 using Tapatalk