Hey guys big problem with cm12.1 stuck bootanimation. only I flashed render kernel r12 its boot successfuly but nfc, system ... crashed. Milestone and early some builds did not boot.
Twrp 2.8.7.1 data and cache f2fs
Clean install but same result. Where did I go wrong?
destroyer31 said:
Hey guys big problem with cm12.1 stuck bootanimation. only I flashed render kernel r12 its boot successfuly but nfc, system ... crashed. Milestone and early some builds did not boot.
Twrp 2.8.7.1 data and cache f2fs
Clean install but same result. Where did I go wrong?
Click to expand...
Click to collapse
Well you went wrong in that there's no official 12.1 for the g2, and any 12.1 roms are CAF, while render kernel is not.
Choristav said:
Well you went wrong in that there's no official 12.1 for the g2, and any 12.1 roms are CAF, while render kernel is not.
Click to expand...
Click to collapse
This link http://download.cyanogenmod.org/?device=d802
If I dont use render stuck bootanimation. Caf kernels dont work.
destroyer31 said:
This link http://download.cyanogenmod.org/?device=d802
If I dont use render stuck bootanimation. Caf kernels dont work.
Click to expand...
Click to collapse
Well that's because it's not a 12.1 rom, it's a 12 rom and render kernel works with non-caf roms such as cm12 for the g2.
What's your bootstack/modem?
Choristav said:
Well that's because it's not a 12.1 rom, it's a 12 rom and render kernel works with non-caf roms such as cm12 for the g2.
What's your bootstack/modem?
Click to expand...
Click to collapse
Already tried all bootstacks and modem but I can use r11 render because r12 for cm12.1
Which Should I use bootstack and modem for cm12
Related
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
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 ?? ==
Will the custom kernels made for CM13 work on Paranoid Android 6.0?If not then is there any way to disable BCL driver?
sanchitd5 said:
Will the custom kernels made for CM13 work on Paranoid Android 6.0?If not then is there any way to disable BCL driver?
Click to expand...
Click to collapse
I had the same doubt. I flashed paranoid android yesterday in my OPO2 and flashed benschholds kernel but it did not work. It got stuck on the oneplus logo. So, I guess there are no kernels which works on AOSPA as of yet as per my research. I even tried AK kernel but no luck.
Guys i am using moto g4 play single sim version (XT1607). Still can i root and flash these roms?
Sharath356 said:
Guys i am using moto g4 play single sim version (XT1607). Still can i root and flash these roms?
Click to expand...
Click to collapse
I'm using the US Cellular version which is the single SIM xt1607 and I've had no trouble unlocking boot loader and flashing twrp or any Rom, in stock Rom I was using xposed as well. Currently running axosp room with no issues.
jestyr8 said:
I'm using the US Cellular version which is the single SIM xt1607 and I've had no trouble unlocking boot loader and flashing twrp or any Rom, in stock Rom I was using xposed as well. Currently running axosp room with no issues.
Click to expand...
Click to collapse
Thank you bro. I previously used an MTK device and i know about flashing and rooting. But never used custom kernel. Can we use custom rom without any custom kernel? or is it necessary that i have to flash custom kernel for every custom rom?. Also give me links of bugless roms for our device?
Sharath356 said:
Thank you bro. I previously used an MTK device and i know about flashing and rooting. But never used custom kernel. Can we use custom rom without any custom kernel? or is it necessary that i have to flash custom kernel for every custom rom?. Also give me links of bugless roms for our device?
Click to expand...
Click to collapse
I've been using the ASOPEtended Rom and have had no issues. Download can be found in the main Android development thread. As for custom kernels. I've been using squids kernel, but you can use the kernel built into the Rom with no issues
jestyr8 said:
I've been using the ASOPEtended Rom and have had no issues. Download can be found in the main Android development thread. As for custom kernels. I've been using squids kernel, but you can use the kernel built into the Rom with no issues
Click to expand...
Click to collapse
Thanks for the info bro. I have to install kernel like flashing roms, right?. How is squid kernel any improvement?. How to flash super su on aosp exteneded rom?
Sharath356 said:
Thanks for the info bro. I have to install kernel like flashing roms, right?. How is squid kernel any improvement?. How to flash super su on aosp exteneded rom?
Click to expand...
Click to collapse
You flash the kernel just like the rom,I would flash the rom, then open gapps or bean gapps. Next I would flash supersu which you can find by doing a search of the forum, wipe dalvik cache, start finish setup then flash squid kernel. Also download kernel auditor from play store to get the most out of squid kernel. Helix kernel is another alternative based off squid kernel. Both squid and Helix allow you to change several options to improve battery life and performance.
jestyr8 said:
You flash the kernel just like the rom,I would flash the rom, then open gapps or bean gapps. Next I would flash supersu which you can find by doing a search of the forum, wipe dalvik cache, start finish setup then flash squid kernel. Also download kernel auditor from play store to get the most out of squid kernel. Helix kernel is another alternative based off squid kernel. Both squid and Helix allow you to change several options to improve battery life and performance.
Click to expand...
Click to collapse
Thank you bro. Installed Aospextended But there was a bug, camera and videos are stopping at a point. I flashed Helix kernel(Didn't tried squid kernel) then bug was gone, now everything is fine. I will try kernel auditor. Thanks for the guidance
Sharath356 said:
Thank you bro. Installed Aospextended But there was a bug, camera and videos are stopping at a point. I flashed Helix kernel(Didn't tried squid kernel) then bug was gone, now everything is fine. I will try kernel auditor. Thanks for the guidance
Click to expand...
Click to collapse
Yeah the bug seems to be in all the lineage based ROMs current builds
Could anyone provide me with the stock radio of xt1607 android 6.0.1?
i've been using DotOS for a long time at versiom 8.1.0 OPM2.171019.029 and MetaPhoenix V2 3.18.102
i thought of shifting from metaphoenix to another kernel but every kernel gives me a bootloop leaving me no choice but to flash metaphoenix again , Please help me install the new eXtreme Kernel OC on my device.
Kamran47 said:
i've been using DotOS for a long time at versiom 8.1.0 OPM2.171019.029 and MetaPhoenix V2 3.18.102
i thought of shifting from metaphoenix to another kernel but every kernel gives me a bootloop leaving me no choice but to flash metaphoenix again , Please help me install the new eXtreme Kernel OC on my device.
Click to expand...
Click to collapse
you need to dirty flash DotOS first before switching to other kernel. :good:
cheeze.keyk said:
you need to dirty flash DotOS first before switching to other kernel. :good:
Click to expand...
Click to collapse
ikr i thought of it but if i get a newer build of DotOS would my stuff be wiped
Kamran47 said:
ikr i thought of it but if i get a newer build of DotOS would my stuff be wiped
Click to expand...
Click to collapse
Dirty will not wipe your data. when your on TWRP just wipe cache/dalvik cache and then flash DotOS and after reboot your device and now the kernel will revert to stock DotOS's kernel.
Now that's the time you can switch to other kernel. :good: