Hallo,
i just tried to flash Franco Kernel v191 to enable USB-OTG on my Nexus 4.
But now i can only boot into CWM Recovery.
When i boot normally, the Screen of my Phone stays black after i see the Google-Logo.
I'm not sure if i flashed the right Version (Do i need JWR or JSS?).
I also flashed only the *.img-File, not the .zip, which was obviously wrong.
How can i flash the right Kernel (or maybe the stock one first) ?
Im using the Nexus Toolkit.
Help me please.
suxx0r said:
Hallo,
i just tried to flash Franco Kernel v191 to enable USB-OTG on my Nexus 4.
But now i can only boot into CWM Recovery.
When i boot normally, the Screen of my Phone stays black after i see the Google-Logo.
I'm not sure if i flashed the right Version (Do i need JWR or JSS?).
I also flashed only the *.img-File, not the .zip, which was obviously wrong.
How can i flash the right Kernel (or maybe the stock one first) ?
Im using the Nexus Toolkit.
Help me please.
Click to expand...
Click to collapse
stop using the nexus toolkits. flash via recovery if a zip, or via fastboot if an img file.
I did flash the Kernel directly via Clockwork Recovery.
Which Version do i have to flash?
I manged to reinstall Cyanogenmod now.
But the ADB-Bridge to the PC doesnt seem to work anymore :/
I enabled USB-Debugging and PTP, but the pc doesnt recognize my phone.
Any Ideas how i can fix that?
suxx0r said:
I did flash the Kernel directly via Clockwork Recovery.
Which Version do i have to flash?
I manged to reinstall Cyanogenmod now.
But the ADB-Bridge to the PC doesnt seem to work anymore :/
I enabled USB-Debugging and PTP, but the pc doesnt recognize my phone.
Any Ideas how i can fix that?
Click to expand...
Click to collapse
oh, youre running cm, thats why. cm changed its source from aosp to qualcomm, so custom kernels are now a no go since the custom kernels are aosp based. the kernels that do boot up on cm, mess up the colors, and franco kernel has issues booting cm. its actually not franco kernels fault, its cm that messed it up for our community(unless you are using cm based kernels).
simms22 said:
oh, youre running cm, thats why. cm changed its source from aosp to qualcomm, so custom kernels are now a no go since the custom kernels are aosp based. the kernels that do boot up on cm, mess up the colors, and franco kernel has issues booting cm. its actually not franco kernels fault, its cm that messed it up for our community(unless you are using cm based kernels).
Click to expand...
Click to collapse
You can get your colors working properly again just copy and paste system/lib/liboverlay.so from non CAF ROM to CM
== Sent from my CarbonMako ?? ==
MaxFTW said:
You can get your colors working properly again just copy and paste system/lib/liboverlay.so from non CAF ROM to CM
== Sent from my CarbonMako ?? ==
Click to expand...
Click to collapse
yes, for now. but that doesn't help the issue here of franco not booting on the newer cm.
simms22 said:
yes, for now. but that doesn't help the issue here of franco not booting on the newer cm.
Click to expand...
Click to collapse
Ok, havent used CM for long since they decided to go full retard and use bloat CAF stuff
== Sent from my CarbonMako ?? ==
MaxFTW said:
Ok, havent used CM for long since they decided to go full retard and use bloat CAF stuff
== Sent from my CarbonMako ?? ==
Click to expand...
Click to collapse
i used to be the biggest cm fanboy back in the day(cm3.1-cm7). many even thoughti was part of cm for a bit(including people who were part of cm). but they had an incident with supercurio(creator of voodoo) that began cm's decline to now, so its been 2+ years since i last ran cm.
simms22 said:
i used to be the biggest cm fanboy back in the day(cm3.1-cm7). many even thoughti was part of cm for a bit(including people who were part of cm). but they had an incident with supercurio(creator of voodoo) that began cm's decline to now, so its been 2+ years since i last ran cm.
Click to expand...
Click to collapse
Same here, I remember this moment when booted CM7 on my Galaxy Mini first time ever Than Desire Z and so on It's been a realy good rom for long long time and I am still using CM10.2 on my Galaxy Tab 2 as it is the only reasonable choice for that device
== Sent from my CarbonMako ?? ==
Related
I was wondering about the overclocking kernal for cm7. just how do i put it in. Do I have to do that when I first install or can I add it later. also does it really help. I mean is the difference really noticeable or not at all. I am still deciding if I should do it or not.
Kernels are flashed through ClockworkMod and can be flash anytime after you flash a rom. If you use the search bar you can easily find what particular kernel works for your setup.
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
chad11 said:
OK, I think I found the right one but I was also wondering if I could install it when I first installed cm7. When I installed it I saw that it was searching for the kernel and for gapps but didn't find the n and skipped it. Could I install it then
Click to expand...
Click to collapse
CM7 has the ability to be overclocked as it sets.
settings > CM settings > performance > CPU settings.
just be extremely careful when Overclocking devices. it can takes it's toll in the long run.
and the g/apps are not kernel dependent they are ROM dependent.
OK but what do you mean by gapps are not kernal dependant
chad11 said:
OK but what do you mean by gapps are not kernal dependant
Click to expand...
Click to collapse
On *UNIX based devices. They have a section of the firmware called the "kernel". The kernel accepts the coding, binary and scripts from the RAM/ROM and tells the hardware how to act, what to do, and when to do it.
The g/apps have nothing to do with the kernel.
The g/apps are Google's property and cannot be included in AOSP based ROMs. Those ROMs are developed from Google's code. And developers do not have the ability to add those at will. So we must flash them after/prior (depending on he ROM) to get the Google Apps.
YES! DO IT!
for me its like day and night, it so much smoother with dals OC kernel. and yes you can flash the OC kernel any time. you can flash cm7 rc1 then OC kernel in the same boot. or you can first install cm7 to check it out for a while and then later flash the new kernel. if you planning to flash dal's 6/18 kernel, make sure to get his app NC Tweaks.
NC Tweaks here:
http://forum.xda-developers.com/showthread.php?t=1104039
Dal's Kernel here:
http://forum.xda-developers.com/showthread.php?t=925451
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
chad11 said:
thanks. What I want to know is how to flash it. do I do it the same way as gapps( have wifi and reboot in recovery mode) or is there a different way?
Click to expand...
Click to collapse
You place the over clock zip file in the root of your sd card and flash it through cwm like you would a rom or gapps. So for example you would flash cm7 then gapps then the overclock kernel.
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
JeramyEggs said:
Not to Jack this thread, but I want to update from cm7 old kernel to New nightly build. Does the new kernel flash with the nightly?
Sent from my Optimized Shift using XDA App
Click to expand...
Click to collapse
When you move from stable cm7 to cm7 nightly the new kernel is included. However the included kernel is overclockable only to 975mhz. If you want a higher clock speed you'll have to use dals 6182011 kernel, up to 1200mhz.
whats is cmw?
chad11 said:
whats is cmw?
Click to expand...
Click to collapse
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernel work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
I'm not following you cannot use just a Cyanogen(mod) kernel. They are built into their ROMs.
chad11 said:
OK. but this may be a stupid question but will the cm7 kernal work with the stable version7.0.3 because that is what I have.
Click to expand...
Click to collapse
sorry, but no. dal's 6/18 OC kernel will not work with 7.0.3....
...just flash n118 and you'll be fine
Ok thanks anyway. do you know when the kernal will work with a stable version
chad11 said:
Ok thanks anyway. do you know when the kernal will work with a stable version
Click to expand...
Click to collapse
The latest nightly should be considered stable. It is in release candidate stable for the next stable build. The next stable build should be released in the next couple of days.
neidlinger said:
it's actually CWM.
ClockWork Manager
basically boot into recovery then flash.
Click to expand...
Click to collapse
No--It's- Clock Work Mod Recovery
CWMR ;^}
Jimbo67 said:
No--It's- Clock Work Mod Recovery
CWMR ;^}
Click to expand...
Click to collapse
There is a Clockwork ROM Manager and a ClockworkMod Recovery image.
Together they are known as "CWM" Since one is a recovery and the other is a ROM manager.
Hi guys,
I use Cyanogenmod 10.1 shortly after I bought my Nexus 10 and had these reboots the whole time.
Usually I update once or twice a week to the current nightlys (depending on the changelog).
A problem I have from the beginning (with CM): When I stream music with Google Music to a Logitech Bluetooth receiver it works. But every 20-30 seconds I have a litte break in the playback. On my Galaxy S2 also with CM 10.1 I never had this problem.
What I did to solve the problem. Today I installed the stock Nexus 10 4.2.2 from Google and tried to reproduce the error. It worked fine. No problem at all.
Then I completely wiped the Nexus 10 again and installed the current nightly - from the scratch. Just installed Google Music and did a test. The same bluetooth problem again.
Ah and when I use a bluetooth keyboard the keyboard also loses connection time and again. Here the problem is even worse. When I´m are in web form the page gets reloaded and all I entered so far is gone...
Has anybody an idea?
I´m willing to give you all the information you need to help me (logcats etc.)
Thanks in advance
Marrtin
Have you tried using the stock kernel with CM10?
stiggy2012 said:
Have you tried using the stock kernel with CM10?
Click to expand...
Click to collapse
Hi and thanks for you answer.
Good idea. But I have no clue how to do that? And isnt´t the kernel always overwritten when I install a nightly of CM10.1?
Wishes
Martin
Martin7404 said:
Hi and thanks for you answer.
Good idea. But I have no clue how to do that? And isnt´t the kernel always overwritten when I install a nightly of CM10.1?
Wishes
Martin
Click to expand...
Click to collapse
I actually don't know off-hand, but it probably is, if its like other ROM's.
dibblebill said:
I actually don't know off-hand, but it probably is, if its like other ROM's.
Click to expand...
Click to collapse
Hmm - and where can I get the stock kernel from? Off course I found the whole stock firmware. But just the kernel out of it? And does this work together with CM?
Please make a bug report @ jira.CyanogenMod.org
Sent from my Nexus 10 using Tapatalk HD
Martin7404 said:
Hmm - and where can I get the stock kernel from? Off course I found the whole stock firmware. But just the kernel out of it? And does this work together with CM?
Click to expand...
Click to collapse
I don't think you can pull just the kernel out of it... I use KTManta myself.
dalingrin said:
Please make a bug report @ jira.CyanogenMod.org
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thanks - I just did so.
Martin7404 said:
Thanks - I just did so.
Click to expand...
Click to collapse
Thanks!
dibblebill said:
I don't think you can pull just the kernel out of it... I use KTManta myself.
Click to expand...
Click to collapse
You can. :good:
If you download and unzip the official rom package from google, you will find another zip inside. Extract that, and you will see a different rom for each partition of your nexus 10. boot.img is the kernel, and it can be flashed from fastboot using command "fastboot flash boot boot.img".
Thanks,
EDIT: If the KTManta kernel doesn't suffer bluetooth streaming issues for anyone else, flashing it instead of stock should serve as an equally good test. The original reason I mentioned flashing the stock kernel is because I too have seen bluetooth streaming issues, both with CM10 and when using the stock rom with franko r12 kernel. I'm now running completely stock rom and kernel, and have no issues.
stiggy2012 said:
You can. :good:
If you download and unzip the official rom package from google, you will find another zip inside. Extract that, and you will see a different rom for each partition of your nexus 10. boot.img is the kernel, and it can be flashed from fastboot using command "fastboot flash boot boot.img".
Thanks,
EDIT: If the KTManta kernel doesn't suffer bluetooth streaming issues for anyone else, flashing it instead of stock should serve as an equally good test. The original reason I mentioned flashing the stock kernel is because I too have seen bluetooth streaming issues, both with CM10 and when using the stock rom with franko r12 kernel. I'm now running completely stock rom and kernel, and have no issues.
Click to expand...
Click to collapse
If I switch back to CM, I'l be sure to test it. I'm currently in the process of deciding just how much I love "CRT Off", which I don't know if CM has added yet
Is there a solution for this stuttering problem? I have tried many roms and kernels, but bluetooth stutters when wifi is on.
Hey people, i recently bought a new nexus 4 and im LOVING it.
I seem to have a problem with custom kernels, i cant seem to boot up once i install one. Ive tried 3 different kernels ( Purity, Matr1x and Franco ) with the same results. here's what i do and what happens:
1) install a new rom after wiping everything in CWM recovery
2) Install Gapps
3) Install the kernel
4) Reboot
Everything installs successfully but when i boot up, after the 'Google' image when the boot animation is supposed to play out, i get a black screen with nothing on it. And the phone doesnt boot.
If i dont install the rom without the kernel, it boots up. ive also tried installing the rom, gapps and booting it and setting it up ( google account, etc ) and then go to recovery and installing the kernel, still the same results. And ive also tried using different roms and i still get the black screen
Hope ive explained everything
I have an idea that maybe i can change the default kernel that comes with the rom by copying the stuff from a kernel zip and pasting it somewhere in the rom zip. Can it be done? If yes, what exactly do i copy?
THANKS!
adil1508 said:
Hey people, i recently bought a new nexus 4 and im LOVING it.
I seem to have a problem with custom kernels, i cant seem to boot up once i install one. Ive tried 3 different kernels ( Purity, Matr1x and Franco ) with the same results. here's what i do and what happens:
1) install a new rom after wiping everything in CWM recovery
2) Install Gapps
3) Install the kernel
4) Reboot
Everything installs successfully but when i boot up, after the 'Google' image when the boot animation is supposed to play out, i get a black screen with nothing on it. And the phone doesnt boot.
If i dont install the rom without the kernel, it boots up. ive also tried installing the rom, gapps and booting it and setting it up ( google account, etc ) and then go to recovery and installing the kernel, still the same results. And ive also tried using different roms and i still get the black screen
Hope ive explained everything
I have an idea that maybe i can change the default kernel that comes with the rom by copying the stuff from a kernel zip and pasting it somewhere in the rom zip. Can it be done? If yes, what exactly do i copy?
THANKS!
Click to expand...
Click to collapse
very importantly, what rom are you using? not all roms are the same. and no, you cant update a kernel that way.
simms22 said:
very importantly, what rom are you using? not all roms are the same. and no, you cant update a kernel that way.
Click to expand...
Click to collapse
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
adil1508 said:
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
Click to expand...
Click to collapse
are you on android 4.2.2 or android 4.3?
simms22 said:
are you on android 4.2.2 or android 4.3?
Click to expand...
Click to collapse
4.2.2
adil1508 said:
4.2.2
Click to expand...
Click to collapse
ok reflash your rom and other stuff(without a custom kernel), boot up/set up, then go back and flash this trinity kernel, tf152 http://goo.gl/CDAGV7
did it boot?
simms22 said:
no, you cant update a kernel that way.
Click to expand...
Click to collapse
Yes you can, but it depends on how the kernel is structured inside the flashable zip. If it's just a boot.img file inside, you can definitely just drag & drop it into the flashable rom zip and replace the original one. Some kernels will work, others will not. If you're going from a rom that uses franco to one that uses an original ramdisk, for example, you may run into issues, but in most cases this won't be an issue.
simms22 said:
ok reflash your rom and other stuff(without a custom kernel), boot up/set up, then go back and flash this trinity kernel, tf152 http://goo.gl/CDAGV7
did it boot?
Click to expand...
Click to collapse
OK, ill make a backup and let you know how it goes
adil1508 said:
OK, ill make a backup and let you know how it goes
Click to expand...
Click to collapse
please..
---------- Post added at 03:05 PM ---------- Previous post was at 02:57 PM ----------
adil1508 said:
cant beleive i forgot to mention that. Im using the LiquidSmooth rom but i tried ALOT of roms when i wanted to install the kernel. Carbon, Purity, XenonHD, Xylon and the official CM10.1
Click to expand...
Click to collapse
whats the default kernel in that liquidsmooth that youre running?
simms22 said:
please..
---------- Post added at 03:05 PM ---------- Previous post was at 02:57 PM ----------
whats the default kernel in that liquidsmooth that youre running?
Click to expand...
Click to collapse
It did boot up with the trinity kernel although the app drawer didnt seem as smooth and fast and there was a problem with the widgets
And its the Liquid kernel, do u want me to type whatever is under the "kernel version"?
adil1508 said:
It did boot up with the trinity kernel although the app drawer didnt seem as smooth and fast and there was a problem with the widgets
And its the Liquid kernel, do u want me to type whatever is under the "kernel version"?
Click to expand...
Click to collapse
yes please.
earlier for the franco kernel, other kernels flashed over it wouldnt boot, only flashing the other kernels with the rom would let them boot. franco kernel has modified ramdisk, framcisco had to adjust it so other kernels would boot up after. i have a feeling that something similar is whats going on with their kernel. especially since you say trinity booted but the app drawer is laggy. i bet they also have modified ramdisk(or something messed up by accident).
Kernel Version: 3.4.0-perf-g3ac0f9c [email protected] #1
adil1508 said:
Kernel Version: 3.4.0-perf-g3ac0f9c [email protected] #1
Click to expand...
Click to collapse
its probably a modified stock kernel. did you ask in their thread if this is the normal behavior with custom kernels?
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
maybe its important but i coudnt get into the stock recovery before i rooted my phone. When i got into fastboot and selected recovery, i would get an android with a red triangle saying ' no command' and i had to press Volume up and power buttons to see the menu
adil1508 said:
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
maybe its important but i coudnt get into the stock recovery before i rooted my phone. When i got into fastboot and selected recovery, i would get an android with a red triangle saying ' no command' and i had to press Volume up and power buttons to see the menu
Click to expand...
Click to collapse
that android with a red triangle is the stock recovery
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
adil1508 said:
No actually, i didnt. I see your point but what happens with the other roms. XenonHD or Xylon, they have the same problem.
Click to expand...
Click to collapse
lots of roms here are related to one another, some very related, so more distant. liquidsmooth doesnt do much of their own coding, they pick up stuff from other roms/sources. these roms might be very similar.
but honestly, i dont know. it is a weird issue though.
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
youre mistaken, its not franco kernel that messes up your screen color, its your cm10.2 nightly.
cm xhanged its sourse from aosp to qualcomm, so running any asop kernel in cm will give you that effect. only cm based custom kernels will be fine. theres a temporary flashable fix for this floating around, if it still works that is.
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
Yes lately cm is causing some color problems.
Here is the colorfix zip file flash this in recovery and also use a JSS kernel AFAIK cm needs a JSS kernel'
COLORFIX zip : DOWNLOAD
Press thanks if I helped you.
how about CM11.. is there any colorfix available yet?
i flashed CM10 colorfix for the 4.4.X based CM11 variant but seems it'll restart the session after the boot animation
Hi guys, happy new year!
So, i'm testing the rom "Nexus 5 Experience (Kitkat 4.4.2)" and everything seems ok, i'm testing the version CAF Kernel. now i'm tryin install new kernels on this rom, but at every kernel I install i get the same error, after instal any kernel, I turn on my N4 and the screen seems very strange, colors flashing, sometimes when i start a game (or anything that forces the gpu) the screen is filled by one or two colors, but the touch is still working, is just a screen or gpu (i dont know) error.
I tryed to take some printscreens, but when i will check this on my pc, everything is ok, like if theres no error.
When i flash the rom again, everything works normally.
what i'm doing wrong ? I thought to change kernel is only flash him, is it wrong ?
i'm newbie, got my n4 yesterday but i have some experience in my old xperia..
sorry the bad english, im br
Thanks guys!!
Are you installing CM compatible kernels?
Try the AK kernel CM version
http://ak.hiddenbytes.org/old/cm//AK.309.CM11P.zip
goofball2k said:
Are you installing CM compatible kernels?
Try the AK kernel CM version
Click to expand...
Click to collapse
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
mendes1995 said:
heyy, this worked!
but i don't understand, i tryed this and a lot of kernels before (all compatible with CM) and doesnt work
so.. thanks! i will check this, recommend me another kernel ?
thanks again! cheers
Click to expand...
Click to collapse
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
goofball2k said:
I can't say what you did wrong, maybe you got the wrong version since many make 2 versions of their kernel, one for AOSP and one for CM.
I don't run CM ROM's so I don't know which kernels are out there. HellsCore is also another kernel to consider, I believe there are CM versions of it as well.
Click to expand...
Click to collapse
yes, i'll try HellsCore.
thanks for the help, i appreciate it!