Develop Bugs

[Q] Cannot run any Kernel besides HTC Stock?!

Hey guys, I feel like I have ran out of options on this problem so I figured I would post and see what you guys think. I am currently running Myn's RLS 2 and ever since I flashed the first version I have not been able to get past running the HTC Stock Kernel. If I flash any other Kernel my phone runs for a bit and then will freeze up and randomly reboot. Even during reboots sometimes it will reboot again. Do I need to be running SetCpu at all to help with this, or is it another problem? Any suggestions would be greatly appreciated. Thank You.

Depends on which kernel you want to run ... some play better with certain roms. I notice that you mention Netarchy's kernel in your signature ... have you tried his universal 4.1.9? Anyway ... whenever I install a different kernel, here's the procedure I use ...
Boot into recovery (I use RA) ... wipe cache and dalvik cache twice each ... flash the kernel ... wipe cache and dalvik again ... reboot.

stuck at boot on all jellybean roms

any jellybean rom i use if i reboot or turn it off then back on it softbricks being stuck at the google logo. i can access fastboot and recovery and flash a stock image but someone inform me why it does this. i love jellybean but cant factory restore everytime i need to boot the phone up

I too am having this issue.

Wipe cache and dalvik cache. Then flash the ROM again. Boot it up.
Sent from my Galaxy Nexus using xda app-developers app

When installing a new ROM you have to do a full wipe, oh and stay away from the franco kernel a lot of people are having problems with it

Mars196 said:
When installing a new ROM you have to do a full wipe, oh and stay away from the franco kernel a lot of people are having problems with it
Click to expand...
Click to collapse
? I don't have any problems with it as many other people are using Franco Kernel on JB and ICS based ROMs... please don't make false comments without any proof.

[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] CM10 with trinity

Can anyone who is using trinity with cm10 tell me how to flash the kernel ?
Everytime I flash it I get the trinity logo and then nothing but a black screen.
Help will be appreciated.
Thank You.

viraj071 said:
Can anyone who is using trinity with cm10 tell me how to flash the kernel ?
Everytime I flash it I get the trinity logo and then nothing but a black screen.
Help will be appreciated.
Thank You.
Click to expand...
Click to collapse
I was just told by someone that more current versions of CM10 don't work. You'll have to install older versions and see what works. Can you post this when you find out?

viraj071 said:
Can anyone who is using trinity with cm10 tell me how to flash the kernel ?
Everytime I flash it I get the trinity logo and then nothing but a black screen.
Help will be appreciated.
Thank You.
Click to expand...
Click to collapse
you need to post more info than this.
what ROM did you flash?
what version of said ROM?
did you format all partitions before you flashed?
did you verify your download was good with an md5 checksum?
what recovery are you using?
since you cannot boot into your current ROM, because you have an outdated kernel flashed to your disk....but first pull your battery out.....
put battery back in
hold volume up, your home button, and the power button (in that order) until you see a small line of text flicker on the top of your screen, then release all buttons. you are now in recovery.
wipe cache 3 times
wipe dalvik cache 3 times
re-flash your current ROM
let it boot.
let it sit until the screen automatically turns off
after it boots...go to the original android dev section, download lean kernel 1.9 to your device, boot to recovery again, wipe cache, wipe dalvik cache, flash kernel. just a guess, but i bet that fixes it.
good luck

cobraboy85 said:
you need to post more info than this.
what ROM did you flash?
what version of said ROM?
did you format all partitions before you flashed?
did you verify your download was good with an md5 checksum?
what recovery are you using?
since you cannot boot into your current ROM, because you have an outdated kernel flashed to your disk....but first pull your battery out.....
put battery back in
hold volume up, your home button, and the power button (in that order) until you see a small line of text flicker on the top of your screen, then release all buttons. you are now in recovery.
wipe cache 3 times
wipe dalvik cache 3 times
re-flash your current ROM
let it boot.
let it sit until the screen automatically turns off
after it boots...go to the original android dev section, download lean kernel 1.9 to your device, boot to recovery again, wipe cache, wipe dalvik cache, flash kernel. just a guess, but i bet that fixes it.
good luck
Click to expand...
Click to collapse
You actually don't have to wipe the caches at all. Just flash the kernel and you're good. There is code built in to kernels that takes care of the old kernel for you. And leankernel is NOT trinity.
Anyways CM10 just released a stable release today so I'll wait for trinity to catch up.

sherfick said:
You actually don't have to wipe the caches at all. Just flash the kernel and you're good. There is code built in to kernels that takes care of the old kernel for you. And leankernel is NOT trinity.
Anyways CM10 just released a stable release today so I'll wait for trinity to catch up.
Click to expand...
Click to collapse
I understand lean kernel is not trinity. I told him to flash that one because it will actually boot.
And I instructed him to wipe caches because he needed to re-install his ROM... as it would not boot.
Sent from Galaxy S III

cobraboy85 said:
I understand lean kernel is not trinity. I told him to flash that one because it will actually boot.
And I instructed him to wipe caches because he needed to re-install his ROM... as it would not boot.
Sent from Galaxy S III
Click to expand...
Click to collapse
One wipe is always plenty. But 3 won't hurt I guess
Sent from my SGH-T999 using xda premium

My apologies cobraboy, I skimmed through your post. I've been frustrated trying to get trinity. Cm10's kernel is actually performing very well for me, I have half my battery after a full day of normal use! I recommend installing the new stable version of CM10 and just leave the kernel alone.
Sent from my SGH-T999

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?

nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.

zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.

nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.

zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.

nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.

Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12

What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)

I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!

No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.

xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse

fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.

xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.

I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)