Hey guys,
I'm running the unofficial Cyanogenmod 11S on my Nexus 4 and just flashed Franco Kernel and am getting weird colours now. My screen also blinks at random times, anyway to fix this without factory resetting? Thanks
Flash your rom again without Franco kernel. It's the kernel that causes this behavior. Just re-flash your current rom/nightlie zip or whatever and it should be fine.
--
Wrong version of kernel used
I think most likely you have used the wrong kernel or not following installation instructions.
Whenever opt to install kernel, do look into the requirements:
a. for which version of android (4.4.4 ? 4.4.2? 5.0?)
b. what type of release of android (Cyanogenmod (CM/CAF)? AOSP? MIUI?)
c. installation method and steps (some kernels required to flash on top of stock kernel)
For now I would suggest that you find out the version and release of the android that you using currently and just flash the suitable kernel for it. The way i see it, you are using a cyanogenmod (CM), a CM compatible kernel will do.
I have build from source CM12 and when I flashed the ROM it is in an infinite loop in the GOOGLE logo. I have done everything correctly.
I installed a CM12.1 build and there is no problem.
Flashed factory images of 5.0, 5.02 an 5.1.1 and then flashed my build but still it is in loop. No problem when I flash a CM12.1 build.
Can you point out what I did wrong ?
Sounds like kernel mismatch or misbuild to me. Really difficult to say more without looking over your shoulder during the build.
I build it twice, but still same problem.
Flash a prebuilt kernel over your custom build and see if it boots the ROM, then you know something is wrong with the kernel build and not the ROM if it boots.
Otherwise personally I don't know why you can't just use the built ROM flashable and not a self compiled version, unless you're trying to get into learning how to build roms?
fwayfarer said:
Flash a prebuilt kernel over your custom build and see if it boots the ROM, then you know something is wrong with the kernel build and not the ROM if it boots.
Otherwise personally I don't know why you can't just use the built ROM flashable and not a self compiled version, unless you're trying to get into learning how to build roms?
Click to expand...
Click to collapse
Ya, I'm learning to build ROMs.
Hello,
I have previously installed AOKP and different versions of Cyanogenmod on this phone (i9300) but when I try to install the paranoid android 5.1 latest rom using TWRP it installs successfully but just before boot I get a message saying supersu doesn't appear to be installed and would I like to install it. The latest version of supersu is installed (along with the latest TWRP) and whether I click yes or no the phone reboots and gets stuck in a boot loop.
This doesn't happen when I install other roms so I am puzzled
It has nothing to do with SuperSU.
The rom doesn't ship with root, that's left up to you. The problem you are seeing is because there is an issue with i9300. There are many posts about this in the g+ community and a few here as well. You need boeffla kernel to flash just after flashing ROM
Pirateghost said:
It has nothing to do with SuperSU.
The rom doesn't ship with root, that's left up to you. The problem you are seeing is because there is an issue with i9300. There are many posts about this in the g+ community and a few here as well. You need boeffla kernel to flash just after flashing ROM
Click to expand...
Click to collapse
Yes you are right, thanks.
For people installing on i9300: only 4.0 alpha 3 worked for me, the latest version (6) failed. Saw on the g+ community another person failed to boot with alpha 6 too.
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
pissgoat said:
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
Click to expand...
Click to collapse
I have already replied same thing on older thread, [ https://forum.xda-developers.com/moto-g4-plus/help/quick-questions-kernel-installations-t3794980 ]
if you flash ROM, it will also install kernel which is considered stock for that installed ROM. You need to flash kernel only if you have modified it (by flashing custom kernel or SU zips).
If you want to flash different ROM, you can flash without doing anything else, just wipe and flash.
PS invictaOS is discontinued long ago, invictaOS-Nougat is stable, Oreo will be more bugfull than current available ROMs..
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
veikaas11880 said:
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
Click to expand...
Click to collapse
Though these forums are for the Moto G4 Plus, that does suggest an issue with the build of Lineage OS that you're using. Can you confirm with the developer that this build is successfully running on their device? Do you have a compatible Lineage 17 OS based kernel you could try to flash?
Was your device working with other stock or custom ROMs before flashing Lineage 17?