Develop Bugs

[HELP] My GS3 hates customs kernels

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

[Q] How to get rid of having to do a battery pull

Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!

Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily

ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0

Wondering if someone could shed some light...

Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk

Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.

I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2

Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.

Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2

[Q] Flashing issue or not ?

Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?

Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.

Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium

Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.

kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.

mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?

It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium

4.3 issues

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