So I had my phone previously overclocked to 1.9ghz back when it was new and hot stuff but then decided to install bacon bits to get my led notification working. Totally overlooked that the bacon bits would replace my OC with the 1.5ghz... I was ok with it since I just want 1Ghz. Shortly after I realized my wifi tether was not working with baconbits and reverted to my previous backup which is pretty much a stock root.
A bit later I attempted to do the kernel flash again and it just sent me to a boot loop. Reverted back again.
Tried OC Neon got a boot loop...
Reverted.
Tried the flippys new zip...boot loop...
Reverted....
Tried new OC neon...Boot loop...
what the sh!t!
Any suggestions I may have overlooked would be greatly appreciated!
Thanks
EDIT: Just noticed that restoring the boot & system only, brings the device to working order... If anyone requires any extra info about what I am running on, I'd be more than happy to share.
bump for some help?
Not sure what is going on here, but how were you overclocked previously? Had you already successfully flashed a custom kernel before or were you running a script. If you were using a script, perhaps it modified a system file that is incompatible with new kernels (causing the boot loop).
On my successful overclocking, I flashed flippys first 1.9ghz kernel using adb.
Well, I'm not sure what could help then. Did you try wiping the cache/dalvik-cache when flashing a new kernel (don't expect it to do anything, but you never know)? Maybe try restoring a backup from before you installed the 1.9GHz kernel just to see if flashing a new kernel works when everything is stock...
Oh, just thought of something that maybe should have been obvious (if it is the cause anyway). Are you using a script or app like SetCPU to overclock? The kernels you are trying do not support 1.9 GHz, so trying to set that at boot with them may cause your boot loop. Try setting your max frequency lower (maybe back to 806 MHz to be safe) before flashing a new kernel to see if that fixes thing...
yeah I'm not using a script or anything right now. I've tried a full wipe and nothing seems to be taking. I'm gonna try to flash the older kernels and see what happens later tonight. Hoping for the best :]
Related
Hey guys,
Just went to reboot my phone, and it is now stuck on the HTC Quietly Brilliant screen.
Any ideas what could be causing this? I am running ARHD 3.3. I had a few problems with it just freezing on the normal HTC screen.
Now it is stuck on the next screen, and it constantly refreshes itself. Really starting to get to me. First phone I have had such major reboot problems with.
Should I send it back for repair you think?
You have got yourself a bootloop. Go to clockworkmod recovery and flash a ROM that does not have OC/UV, it should fix the issue. For example Raidroid Stockify series ROMs should work. Some CPUs cannot handle the tightened CPU voltage values which custom ROMs have.
To get to the recovery, pull your battery out, put it back in and connect charger. Do not touch power button.
jkoljo said:
You have got yourself a bootloop. Go to clockworkmod recovery and flash a ROM that does not have OC/UV, it should fix the issue. For example Raidroid Stockify series ROMs should work. Some CPUs cannot handle the tightened CPU voltage values which custom ROMs have.
To get to the recovery, pull your battery out, put it back in and connect charger. Do not touch power button.
Click to expand...
Click to collapse
Ok thanks. Do you think I should simply ARHD 3.3 again, and then revert to a stock kernel?
Just to add, it doesn't always happen. This is the first time I have rebooted my phone for a day or two, but it does get very frustrating if every reboot you do crashes your entire phone and you need to reinstall the entire thing. Bit annoying! Also, it has only started happening in the past week or two. Before then, everything ran fine.
You can try arhd again for sure. Try to wipe cache and dalvik cache first, then flash the rom. Maybe this will fix your problem.
Otherwise try a fullwipe and flash the rom again.
I don't think that the cpu causes this problem. Should be only a bad flash or incompatibility with your old rom if you didn't wiped before flashing it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
Unfortunately you cannot use stock kernel with ARHD 3.3, you should ask mike to compile you a custom made EXT3 & stock kernel package. Your another choice is to ask Apache to build a kernel without UV.
Something else might cause this issue, too, so it might not be the voltages.. But usually too low voltages cause problems like this, especially as it hangs only sometimes. That tells us that something in the system is unstable. Try full wipe and reflash the ROM, see if that helps.
jkoljo said:
Unfortunately you cannot use stock kernel with ARHD 3.3, you should ask mike to compile you a custom made EXT3 & stock kernel package. Your another choice is to ask Apache to build a kernel without UV.
Something else might cause this issue, too, so it might not be the voltages.. But usually too low voltages cause problems like this, especially as it hangs only sometimes. That tells us that something in the system is unstable. Try full wipe and reflash the ROM, see if that helps.
Click to expand...
Click to collapse
Cool thanks. I had a problem with Busybox for a while, and managed to fix that (the latest stable version was messing the ROM on reboot).
It might be worth asking Apache to build a kernel without UV for sure, especially as people can have this problem as all CPUs are indeed different
I'm hoping that someone might be able to help me with a problem I'm having with the Franco Kernel. I have a rooted Galaxy Nexus, running on stock Android 4.0.2. I have a bit of experience running various custom ROMs and kernels with a OG Droid and HTC Thunderbolt. Until now, I've been content to run stock ICS on the GNex, along with the stock kernel.
I was impressed with the amount of praise I have recently read (I'm a habitual lurker on a number of Android forums) about the Franco kernel, however, and thought I would give it a go. If it can improve performance and battery life, that is fantastic. So, I bought the franco.Kernel updater from the Market, downloaded the zip file (#15), proceeded to recovery and installed it.
That seemed to all go smoothly. The problem is that when I rebooted, the phone got hung up on the black and white "Google" screen. I know sometimes, it can take a while for the phone to do what it needs to do under the hood before it boots up, but after ten minutes on the "Google" screen I did a battery pull, went straight to recovery and reverted to my latest backup.
I've done some searching for anyone who's had a similar issue, but I can't seem to find what the problem might be. Most likely, I'm simply missing something small but critical to the successful installation of this kernel. I'm hoping someone with more experience than me might recognize what it is I'm doing wrong.
Any patient assistance or advice would be heartily appreciated. Cheers!
I could be wrong, but Franco works for 4.0.3, not 4.0.2.
Which could be precisely the one small thing I am missing. I will check this out. Thanks for the suggestion.
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
P4p3r1n0 said:
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
Click to expand...
Click to collapse
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
bowsersoulstar said:
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
Click to expand...
Click to collapse
cool! thanks! good to know I read a bit everywhere.
I mean, I know how a kernel is, and thinking about it it's true that is not needed to wipe, but if he has some problems he could try this out :/ maybe a fresh installation of everything could be good
Hi guys, I urgently need your help! Yesterday my phone drastically slowed down, I don't know what may have been.
I was using cyanogenmod 10 with Franco kernel (I was testing 512 GPU version). So I tried restoring a backup, but no use, slooooow!
I did all the wipes and reflashed CM10 from scratch, with gapps. Problem still exists! Tried reflashkng Franco Kernel (380 GPU) and still the same. At first I thought I might have fried my GPU, but Franco kernel updater app shows gpu working.
So I think this may require a total wipe (including sdcard) and a stock good image reflash from the gn toolkit.
I'm attaching a log right after boot (which took AGES). It seems to me that something's not right.. by I need HELP!
Thank you guys...
http://db.tt/k3dz0aP9
I am not an expert of reading logs yet so probably another member will help you more regarding that.
It seems you have already done a full wipe and tried installing/flashing again but I am not sure which procedure you followed. So my suggestion is to put on your SD card a ROM and kernel, maybe Trinity just for a change, then do full wipe and install the ROM and the kernel so it will be all fresh with a new kernel as well.
If it is still slow, then download any app that would control the CPU and GPU speed to ensure of their speeds running now.
At worst case, returning to stock should help a lot in determining if it is a software or (hopefully not) hardware problem.
Good Luck
I found out that other people have this problem, so I'm asking in the already open threads. Close this please.
Sent from my Galaxy Nexus
I checked as much as I could handle but wasnt successful in finding my specific issue..
here goes..
im running wicked sensations v2.0 on Sprint sgs3. battery life was less than desirable so I flashed k747 kernel. now I noticed my boot animation is different and seems off from the audio. I noticed the visual will be half over before the sound plays. im not able to change the boot animation either and have only a blue flashing samsung logo. any ideas on a fix or is it not fixable? ive tried flashing from the kuban but nothing changes. ive tried flashing anis with no luck. im convinced the k747 kernel has to be the culprit but thats the only issue Ive so far seen. id like to know if theres an easy fix or not?
thanks in advance for any assistance.
Go back to stock that's what runs best with wicked sensations.. I'm running the modded ma4 kernel with no issue its smooth and solid! Here try it...
boot.img,init.d, custom bootanimation & adb..
http://db.tt/IpBAdPhn
Make sure you flash the kernel cleaner first.. here it is..
http://db.tt/TOXoIaqC
ImEVO said:
Go back to stock that's what runs best with wicked sensations.. I'm running the modded ma4 kernel with no issue its smooth and solid! Here try it...
boot.img,init.d, custom bootanimation & adb..
http://db.tt/IpBAdPhn
Make sure you flash the kernel cleaner first.. here it is..
http://db.tt/TOXoIaqC
Click to expand...
Click to collapse
Very good. Thanks for your time. So with this kernel, can I change boot animations with no issues from the kuban downloader? The main issue I had was after changing the kernel to K747, I wasn't able to flash new boot animations. I love the ROM - the look of it is fantastic but it ran like the stock Sprint ROM and battery didn't last much of the day. I'm a flash fiend and found a few ROMs I like and have them in recovery and switch almost daily but Wicked is my favorite. I'll try the links and give it a go. Thanks a bunch.
harry46222 said:
Very good. Thanks for your time. So with this kernel, can I change boot animations with no issues from the kuban downloader? The main issue I had was after changing the kernel to K747, I wasn't able to flash new boot animations. I love the ROM - the look of it is fantastic but it ran like the stock Sprint ROM and battery didn't last much of the day. I'm a flash fiend and found a few ROMs I like and have them in recovery and switch almost daily but Wicked is my favorite. I'll try the links and give it a go. Thanks a bunch.
Click to expand...
Click to collapse
Update...
Ok, so I downloaded the files. I went to move them to my PC for backup purposes and noticed every app that came with Wicked is loaded on my card! Holy crap! Slight panic attack there... I'm thinking if I remove them, I lose the apps in Wicked. Can these be moved or do they have to stay on my internal SD memory? I've had other ROMs flashed and can say I've never had any of those do this. Is there a reason it's like that or is the ROM set up to put all apps on the internal SD card by default (app to SD)? If it is, it makes sense and I'll put them back where they belong so my internal memory is clean and clutter free. Can I put these into a folder on the internal memory or at least in the system app folder and still be OK?
so I was able go flash the kernel and things seem to be going well so far but I noticed my wifi is disabled. I can only use data. wifi wont turn on at all. any ideas? I've reflashed the rom amd wifi works we expected but when I flas the kernel wifi is disabled.
No I don't set the rom up to copy apps to you're SD card. Not sure why that happened to you. I know WiFi works with the stock kernel, so If your having issues flashing another kernel, then you might want to re download the kernel again and follow their instructions for flashing. I usually flash the kernel, then wipe cache, dalvik cache then fix permissions.
On the K747 kernel, you can flash the bootanimations4u file and custom boot animations should work for you.
But I've been using an app to flash the boot animations and it works perfectly fine with RomToolBox
or ( ROOT ) Boot Animation from the Play Store.
The battery issue with KToonez kernel however on JB 4.1.x based roms is there was a specific issue regarding certain
governers that use up too much bat life.
I'm running the stock MA6 JB with KToonez, It's working flawlessly and even better when its over clocked ( Heat issue
when you're doing certain things over a long period of time. ) Adding on top of that a few scripts
that also force cpu cores off when your screen is off and my phone can last 2-3 days when doing nothing.
link to ktoonez kernel on the forum is here
http://forum.xda-developers.com/showthread.php?t=1800576
Link to the bootanimation4u.zip can be found here
http://forum.xda-developers.com/showthread.php?t=2063280
If the kernel supports custom boot animations flash this and use an app that installs custom boot animations
and it should work.
Hope this info helps.
Spark91 said:
On the K747 kernel, you can flash the bootanimations4u file and custom boot animations should work for you.
But I've been using an app to flash the boot animations and it works perfectly fine with RomToolBox
or ( ROOT ) Boot Animation from the Play Store.
The battery issue with KToonez kernel however on JB 4.1.x based roms is there was a specific issue regarding certain
governers that use up too much bat life.
I'm running the stock MA6 JB with KToonez, It's working flawlessly and even better when its over clocked ( Heat issue
when you're doing certain things over a long period of time. ) Adding on top of that a few scripts
that also force cpu cores off when your screen is off and my phone can last 2-3 days when doing nothing.
link to ktoonez kernel on the forum is here
http://forum.xda-developers.com/showthread.php?t=1800576
Link to the bootanimation4u.zip can be found here
http://forum.xda-developers.com/showthread.php?t=2063280
If the kernel supports custom boot animations flash this and use an app that installs custom boot animations
and it should work.
Hope this info helps.
Click to expand...
Click to collapse
Thanks, I'll try that. I've found a bunch of boot animations I want to take a look at. I couldn't get any other kernels to work right. Everything keep the phone in an awake condition and sucks my battery dead in less than 8 hours. I've even done a full and complete wipe of everything, even the memory (just for fun and after backing it all up) and nothing works well but the stock kernel. Good news is, I get fantastic battery life after nuking my memory. Perhaps some lingering file was the cause? Either way, I could never get K747 to work without keeping my phone awake and I'm pleasantly content with the stock kernel now. I can go about 36 hours between charges with minimal use and using just the media player, I can easily last 12 hours. I'll definitely check out that boot animation file.
Thanks all for your help...
Awesome to hear that. Glad it worked out for you and with the stock kernel make sure it has the boot animation support otherwise
flashing the bootanimation4u file would be pointless.
UPDATE... so I just flashed v2.1. The Kuban Updater mod files are what I mistook for apps. Durrr! Only found that out when I deleted them and nothing would show up in the Updater. .. needless to say I had to reflash. Mistakes lead to discoveries I guess. So I believe I solved that issue. I noticed Awesome Beats is new. Going to play with that. Battery life is super impressive. Nice job on this...
I've been trying to get this problem resolved in order to run the latest cm12 build or fml with the dirty_v kernel but haven't arrived to a solution. Basically for whatever reason my phone can't handle booting at 512mhz gpu (which is the default clock on the latest cm12) so I need to find a way to lower the gpu clock to 384 before boot. Is there a script that could do this for me? and yes i've tried both twrp and cwm along with doing several full wipes and trying different versions of gapps as to isolate the issue to the gpu.
xXrawrXx said:
I've been trying to get this problem resolved in order to run the latest cm12 build or fml with the dirty_v kernel but haven't arrived to a solution. Basically for whatever reason my phone can't handle booting at 512mhz gpu
Click to expand...
Click to collapse
Are you sure you're flashing the right kernel? Dirty V is the name of the Kitkat kernel, not the L version. Get Smitty L Beta 3.
My bad I forgot to clarify I've tried fml with all three betas and can't get past the boot logo. So is there anyway to lower the gpu frequency prior to boot?