Hello! Long time lurker, first time poster. I finally got around to making an account.
So, I'm having an issue when applying Da_G's overclocking kernels (Here).
The issue proliferates when I go into CWM and apply the AT&T .42 kernel and the 1.83ghz overclock script from the recovery menu. Basically, after cleaning the cache and the dalvik cache, I apply the .zips of the .42 kernel and the script, and reboot, and then I get a restart cycle that ends after the Samsung screen. I went ahead and did a full wipe of the phone, restored via ODIN to stock, and then tried flashing it again and this time I got to an "Android" logo followed by the same power cycling (this time with the camera LED flashing).
The strangest thing is that before I took my first Skyrocket back for dead pixels, I had gotten it running just fine before. But the last two I've had won't do it and get stuck in the aforementioned restart cycle.
I decided that it really wasn't worth the risk of bricking my phone (since I just got out of my 30 day warranty and had to take the phone back twice for dead pixels and the phone not turning on one day), and I guess in the end I'm just curious as to why I was having this issue. I guess if it's something stupid I'm doing, I'd go ahead and do it (especially since I have plans for that performance boost).
Anyways. Feedback appreciated.
The 1.83 isn't very stable that's what's causing the problems. Go one step down on the script
Alright, I'll try it right now. Maybe it was a fluke that it worked the first time.
EDIT: It booted up, but, then it shuts off when I open CPUTuner, but, they're talking about that in the official thread. Thanks!
1.83 is not stable and 1.78 and 1.72 are most stable with oc.
Sent from my SAMSUNG-SGH-I727 using xda premium
After running it for a few hours, now I'm getting Sleep of Deaths. I really want to speculate that it's the .42 version that I'm running, but, I haven't tinkering with it enough. I think I'll try downgrading to .3 to see if that fixes the issues, as that's what people seem to be saying is the most stable, and it's the one I ran before.
And if that doesn't work, eh, I'll flash back to stock kernel. Thanks guys.
Edit: Yeah, still getting SOD, flashing stock.
Did you try deleting your modules folder?
I had the same problem, 'cept I cranked it to 1.89ghz. I just flashed the stock att kernel and everything worked fine
Sent from my SAMSUNG-SGH-I727 using xda premium
Related
Just installed new rom on phone.
Keeps rebooting every couple of minutes. Now I am not sure if it happened before I installed rom or not as I just went straight ahead and installed it as I have just received a replacement handset from a broken screen.
Any help?
Sense rom? Aosp rom? Rom name? Root? No root? More info man...
*Swaypovano sa Desire S BRE*
Saga3D v3.0 (Desire S official Sense 3.0) - [2.3.5] OTA 2.10.401.5
That rom. Installed the new hboot and orig stock kernal
Assume you have rebooted into recovery and wiped data, cache and dalvik cache, then tried to reboot?
Yes, I have done that a couple of times. I left it on connected with cable overnight and it doesnt seem to have rebooted. Seems to point to a battery problem??
It does boot properly. But after a minute it just restarts.
Edit. A bit more testing and it doesnt reboot when using a game or app. As soon as it closes to main screen it seems to just reboot as the screen goes into standby.
Edit 2. I have changed setting to stop screen turning off and its not done a reboot for the whole 10 minutes.
Does anyone think its a warranty claim? Or any more things to try?
Warranty claim seems a bit drastic, I'd try installing the rom again, or try a different rom, Endymion is sense 3.5 and stable... I was toying with it today, or pre rooted stock or even cm7 which at least you know is also rock solid
Sent from my HTC Desire S using xda premium
Just tried cm7 and it does the exact same.
Edit.... tried 4 different roms now. Going to go to stock with s-on and test. Then back to the shop again
Edit 2. Just use RUU on it and it is the same. Looks like I need to return it yet again.
Any more tips before I take it back in?
I had the same problem after 2.3.5 update. Went back to old version and it's fine now.
Assuming that you are not OC or UV then continue, else adjust to stock settings and re-try.
I recall a couple of others having a similar problem that was caused by either
a) loose battery connection, resolved by placing a piece of folded paper on top of battery to ensure it sat solidly in the slot.
b) dodgy battery, suggest that you contact HTC support, explain that phone keeps rebooting you suspect battery and request that they post you a new battery - don't post old battery back until you are sure its the battery at fault.
Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...
charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...
Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.
If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.
getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
You're asking this at the wrong forum dude. You wont get any support here. Everyone's moved to Rootzwiki
http://rootzwiki.com/topic/15859-ics-b4-was-100-rebooted-and-bootloop-on-samsung-logo/
Yep but when fishing it helps to have multiple lines in the water...
Past experience
From what ive found out, once you have ICS flash on ur phone, ur not going to want to use the three finger salute. If you want to boot into recovery, only do it by rebooting into recovery through ics
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
galamdring said:
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm thinking that there must be something off in the bootloader. I'm hesitant to go playing with it since that is a quick road to bricking. I might dissect the boot.img that is included in the cm10 zip. I'm thinking there is a missing module, or something similar.
Any input would be appreciated.
New update. I was able to get back to CM10. I had forgotten to wipe data. Thats what I get for flashing when half asleep.
Still trying to understand what happened to stop my cardock from working. Charging in the dock works fine, but it doesn't start car dock mode, or push audio through the usb. I'd really like to get that working again.