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
Related
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)
Just like the title suggests, which KT747 kernal is compatible with CM10? Every time I flash the kernel my phone wont boot and I have to restore from a backup. I am currently on CM10-10/22 build 10827 and the KT747 kernel I am trying is the AOSP-JB-ATT-10-22-2012. I do have a ATT Galaxy S3 so I would assume that this should work?
Thanks for everyone's time!
Zehel
There is a version for pre 10-14 CM10 and one for after.
After you flash your ROM be sure to fully boot your device into android then go back into recovery again and then flash kt747 , then wipe cache+dalvik +fix permission . Reboot
Sent from my SGH-I747
Ah! Fix permissions could be a huge part of the problem. Let me try that and see if that fixes my problem. Also, maybe I am blind but I can't seem to find the one for CM. Is there a separate thread for the CM Kernel or is it in the thread by Ktoonsez?
Thanks again,
ZS
ZehelSitchel said:
Ah! Fix permissions could be a huge part of the problem. Let me try that and see if that fixes my problem. Also, maybe I am blind but I can't seem to find the one for CM. Is there a separate thread for the CM Kernel or is it in the thread by Ktoonsez?
Thanks again,
ZS
Click to expand...
Click to collapse
CM10 is an AOSP rom.
That makes crash822's post make sense. Thank you all for your help. I now have it working! Let the amazingness commence!
ZS
You checked "yes this is a question"
Guess where it belongs?
Moved to Q&A
FNM
ZehelSitchel said:
That makes crash822's post make sense. Thank you all for your help. I now have it working! Let the amazingness commence!
ZS
Click to expand...
Click to collapse
Hey man, do you mind sharing what you did to make the kernel work?
I have almost the same issue as you did before, and tried everything I know (including reflectingod's method), still doesn't work at all.
dingrn said:
Hey man, do you mind sharing what you did to make the kernel work?
I have almost the same issue as you did before, and tried everything I know (including reflectingod's method), still doesn't work at all.
Click to expand...
Click to collapse
Did you use the ktweaker app that installs automaticaly and turn on options from there.
Sent from my SGH-I747M using xda premium
ragzdincs said:
Did you use the ktweaker app that installs automaticaly and turn on options from there.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Well, to be more specific, KT747 kernel doesn't work at all on my GS3. I am using ATT variant i747, with task's AOKP ROM. I followed the full wipe -> ROM -> gapp -> kernel steps strictly, and was sure using the post-1014-JB kernel to pair with 1022 AOKP release, But still, my phone is suffering random hot reboot, black screen, system process are terminated randomly, and any opened apps will be closed within mins. Yes, I have cache/dalvik wiped after flashing the kernel, and permissions are fixed. I also tried to flash ROM first, then log on to system, then flash kernel, makes no difference. I really don't have a clue why KT747 kernel doesn't work on my phone, any suggestion is welcome.
I would suggest you to do a complete clean installation:
1. Wipe data
2. Wipe Cache
3. Wipe dalvik
4. Format /system
5. Format / data
6. Format / cache
7. Reboot recovery
8. Wipe data
9. Wipe Cache
10. Wipe dalvik
11. Mount /System
12. Install Rom
13. Install Gapp
14. Fix permission
15. Reboot & Setup your phone
16. Install Kernel
17. Wipe Cache
18. Wipe dalvik
19. Fix permission
It should be fine then.
noahattic said:
I would suggest you to do a complete clean installation:
1. Wipe data
2. Wipe Cache
3. Wipe dalvik
4. Format /system
5. Format / data
6. Format / cache
7. Reboot recovery
8. Wipe data
9. Wipe Cache
10. Wipe dalvik
11. Mount /System
12. Install Rom
13. Install Gapp
14. Fix permission
15. Reboot & Setup your phone
16. Install Kernel
17. Wipe Cache
18. Wipe dalvik
19. Fix permission
It should be fine then.
Click to expand...
Click to collapse
Thanks man, I will give this "full steps" a try. Hope it would work.
dingrn said:
Well, to be more specific, KT747 kernel doesn't work at all on my GS3. I am using ATT variant i747, with task's AOKP ROM. I followed the full wipe -> ROM -> gapp -> kernel steps strictly, and was sure using the post-1014-JB kernel to pair with 1022 AOKP release, But still, my phone is suffering random hot reboot, black screen, system process are terminated randomly, and any opened apps will be closed within mins. Yes, I have cache/dalvik wiped after flashing the kernel, and permissions are fixed. I also tried to flash ROM first, then log on to system, then flash kernel, makes no difference. I really don't have a clue why KT747 kernel doesn't work on my phone, any suggestion is welcome.
Click to expand...
Click to collapse
Rom is supposed to be flashed first. If you don't it overwrites the kernel with the one pre-loaded on with the Rom.Otherwise follow everyone else's instructions >Cache/Dalvik/FixPerms after flash. Go into settings and see that the kernel is there. Good luck
So I've been flashing a couple of different roms this week like Carbon (based on AOSP), PACMAN (Don't know what it's based on), Rootbox (based on AOKP) and Slimbean (AOSP) the method I've been using to flash is wiping data/factory reset, wiping cache/dalvic cache, flashing ROM & gapps, flashing NexusLouder mod, flashing custom kernel, advance restoring data only then rebooting. I think this could be the cause of the boot loops. Or... it could be the function implemented in Carbon which doesn't require you to constantly flash gapps anymore since it backs everything in /system/apps. Anyone know what the cause of the boot loops are for sure?
Extra details - I started using this method ever since I was on AOKP which was my first custom rom. Then a few months ago, I moved to Rootbox, then Carbon, then I tried out PACMAN for a while then reverted back and just today I went back to Rootbox for a while, then I tried out SlimBean and ever since today, I've been getting random bootloops when I restart my phone. It doesn't happen every time I reboot my phone but when it does, clearing the cache solves the problem temporarly and I also had to do a full restore of my nandroid a couple of times today.
Also, I use this method because I have over 75 songs on my playlist which I spent hours creating and I don't want to start all over again. I also don't want to set all my rom settings again either.
Reduce any OC
Undo any Voltage mods
Disable any apps that alter how the system behaves
Disable all apps and enable one by one until you have an issue
You get the idea.
Definitely want to avoid restoring data from another rom and flashing audio mod. If after flashing a new rom you still get the random reboot then you can narrow down the problem.
Sent from my Galaxy Nexus
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
I always do that :thumbup:
Sent from my Galaxy Nexus using xda premium
samersh72 said:
an easy hint may help: always wipe cache and dalvik AFTER flashing rom, mods... to prevent conflicts :good:
Click to expand...
Click to collapse
Thanks for the tip
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm