Related
At first I thought my issue was isolated to the 8.x snap kernels but now I am also having issues with KingX bfs 8 and netarchy's 4.1.9. I clear cache, and dalvik, flash the kernels and I either get a bootloop or the phone will load and just freeze after a minute or two. Flash an older kernel (kx bfs #6) and everything is fine again.
Is there something else I need to be doing aside from clearing cache and dalvik? What could be causing this?
hm i personally do not clear dalvik and cache when flashing kernels some roms i find i have problems when i do such as on Evio rom. you may try flashing the kernel with out wiping the data and see if it helps any.
also if you are using CM6 which i assume you are since you were using snap. not all kernels are compatible with CM since it is asop. this could also cause your boot loops. if it does not specifically say CM compatible i would assume it isnt.
lastly if you use setCPU make sure it is reconfigured to the new kernel. i normally get force close issues and not freezes but am trying to throw out anything can think of that might help.
The only kernels I tried with CM were the snap kernels. I gave up on CM and went back to Evio and tried the other kernels. I also delete SetCPU beforehand and reinstall it after the flash.
Gonna try flashing kx bfs 8 without clearing data....
EDIT: Still didn't work. It never gets past the "hTC EVO 4G" screen. Just hangs on it for a while and then reboots and repeats.
let us know i have the same problem flashing after clearing on evio. i believe it has to do with how the dalvik is moved to the cache partition so i never wipe when flashing kernel with it.
hopefully that works also the new evio 1.2 has king 8 presintalled
I noticed my phone acting a little funny with Kings #8, so I reverted back to #6 and my phone has been back to normal since doing so.
I'm going to flash VirusROM carbon as soon as he gets it up. It's packaged with #8 too so we will see what happens.
When I first flashed CM6 I repartitioned my SD card, maybe I need to do that again when going back to a sense rom/kernel? Going to clear everything in my phone and repartition SD card before I flash virusROM Carbon. Maybe that will clear it up.
Nope, that didn't work either.
Does anyone have any ideas why this is happening?
Could it be my recovery that's doing it? I'm using AmonRA.
Bump.
I just tried kingx bfs9 and once again- bootloops.
Does anyone have any ideas what could be causing this?? Please?
i tried different roms lately but everyone that i try my phone randomly reboots it self i was wondering could someone please HELP ME
Basic questions.
What ROM are you running now? What kernel?
How do you flash, in recovery or with ROM Manager?
What recovery do you have?
HipKat said:
Basic questions.
What ROM are you running now? What kernel?
How do you flash, in recovery or with ROM Manager?
What recovery do you have?
Click to expand...
Click to collapse
the rom i am currently using is mikG 2.55 and using Freedom0.9 aggressive for my kernel. and i flashed them both with Amon_RA v2.3
what was your method of flashing? did u flash rom, then reboot? Or did u flash both of them @ same time in recovery? give me a run down and i'll see what i can do to help
u prob know all this stuff but sometimes i forget something as simple as wiping diff stuff. Best option might be a fresh install and maybe flashing virus superwipe first.
I disagree with superwipes.
Just go to wipe in Amon RA and wipe every option there is, except SD Card: and Battery Stats, if you're not full ycharged. Wipe Cache and Dalvik-Cache twice, then flash the ROM, reboot, let it settle for a few minutes, reboot to recovery. Wipe Cache and Dalvik Cache again, flash the kernel.
Reboot, let it settle a few minutes and start doing your setup
I flashed CM7.1 and I'm stuck in a boot loop. I tried wipe cache partition, wipe date/factory reset, wiping dalvik cache and reflashing a different rom but still keep getting the boot loop. What else should I try doing to slove this ?
Could be kernel related, are you using an aosp and hopefully not a sense kernel? Need more info, what kernel, recovery are you using?
I'm using ClockworkMod recovery I'm not sure what kernel I using
Easy fix, recommend starting from new. wipe the entire phone in recovery at least 3 times, sd card also, backup sd card to computer if you need to via USb toggle, flash Cm 7.1, flash tiamat kernel, found in development section, reboot, good to go, nandroid once up and running, happy flashing
Thanks, okay I'm glad you said easy fix I'm not as worried now. I'm gonna follow your advice. Whats a roamer kernel ?
sorry swype acting weird, use tiamat kernel 4.1 something in development section
The FIRST Thing you should do is get rid of Clockwork Mod, and get Amon Ra, so you can wipe everything.
Just wiping Data/Cache/Dalvik when flashing a new ROM isn't enough.
Hey thanks again ! ! I followed your advice and got everything working again
I tried to flash HONO Full Throttle V2, cleared cache, dalvik cache.
Now my phone keeps rebotting loopping. I tried to access ROM manager but it reboots before it can do it. I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Do i have to unbrick?
Any help is appreciated, thank you
When that happened to me, with a different ROM, I went ahead and pressed power again at that screen and it continued to CWM, didn't wipe/reset my phone.
neuty said:
I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Click to expand...
Click to collapse
That is what you are supposed to see. Press power button twice to "accept" the factory reset. It won't actually reset anything -- instead it will boot directly to CWM.
Oh, okay thanks so much RealyPssd and Drumist! Got a bit scared for a second there. Was able to flash back
Edit: I might have found the problem:
I tried installing HONO's P930 CM9 Kernel V5 and it did the same thing but worse, it didnt even let me past the CM boot guy.
Went through the same thing
I tried flashing HO!NO!'s CM9 Full Throttle this morning and went through the same thing. Sometimes it would boot into the OS, other times it wouldn't get past the CM9 guy, and even sometimes it wouldn't get past the HO!NO! logo. I even had a hard time getting into CWM via the factory hard reset method (I kept getting just a blank screen, but the phone was still on. I pressed the volume down button and that seemed to get it into CWM, although it could have just been a coincidence).
I tried re-flashing the ROM but still no change. So I then flashed CM9 RC-1 and haven't had an problems since.
From what I've read in the Full Throttle thread, the HO!NO!'s ROM already comes with HO!NO!'s kernel. I've also read that the instability is due to the undervolting that's taking place in the ROM (and I'd have to agree based on my experiences with overclocking).
If you really want CM9 go with the RC-1 (or even the nightly). I find it to be incredibly fast so far. Maybe HO!NO! can make a ROM compiled with the linaro toolchain that has a slightly less aggressive undervolting settings
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Wiped everything but had a backup
HO!NO! said:
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Click to expand...
Click to collapse
I was coming from a stock ROM that I had rooted with SuperOneClick, and installed CWM using Rom Manager from the market. When I went to install your ROM I first made a backup of the current ROM (i wanted to having something to fall back to). I did a wipe data/factory reset, wipe cache, wipe dalvik, then flashed your ROM. I also flashed gapps as well (could that have caused a problem?)
Does it sound like anything is off? I would really like to be running your Full Throttle ROM (it's the only reason why I tried to flash my phone in the first place)
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.
once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.
dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution
Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.
sorry for being a newbie....but what do you mean by fix permissions? =/
ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back
droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did