Related
Good afternoon.
I am using 4.2.2 in my LG Nexus 4. It is rooted with SuperSU and I am using Franco kernel.
Every time I try to enter in Settings -> Security I receive an error. I already tried go back to the default kernel, installed the Clockworkmod recovery and wiped the Dalvik cache and the error continues.
I don't know if there is anyway to export this error report, so here goes the screenshots:
Thank you!
Assertion issues, what rom are you using?
It is not really recommended to flash a custom kernel on the stock rom.
Sent from my Nexus 4
andyabc said:
Assertion issues, what rom are you using?
It is not really recommended to flash a custom kernel on the stock rom.
Sent from my Nexus 4
Click to expand...
Click to collapse
Whats wrong with flashing custom kernels on stock rom?
Rizy7 said:
Whats wrong with flashing custom kernels on stock rom?
Click to expand...
Click to collapse
The stock rom only works well with the stock kernel for multiple reasons, I cannot get into detail why custom kernels can be bad for stock ROMS.
I maybe can get to detail if you want me to.
Sent from my Nexus 4
andyabc said:
The stock rom only works well with the stock kernel for multiple reasons, I cannot get into detail why custom kernels can be bad for stock ROMS.
I maybe can get to detail if you want me to.
Click to expand...
Click to collapse
What???
I am running stock ROM with a custom kernel (Franco), as are many others, and it's fine.
A custom kernel is usually just the stock kernel with some modifications (could be a tiny change or something bigger). What's wrong with that?
Sent from my Nexus 4
andyabc said:
The stock rom only works well with the stock kernel for multiple reasons, I cannot get into detail why custom kernels can be bad for stock ROMS.
I maybe can get to detail if you want me to.
Sent from my Nexus 4
Click to expand...
Click to collapse
Its the first time I've seen someone say custom kernels aren't recommended for stock rom. So just curious to find out why that is the case.
steviewevie said:
What???
I am running stock ROM with a custom kernel (Franco), as are many others, and it's fine.
A custom kernel is usually just the stock kernel with some modifications (could be a tiny change or something bigger). What's wrong with that?
Sent from my Nexus 4
Click to expand...
Click to collapse
It can go well but sometimes something can go wrong so I am saying that it really depends on anything on the device.
Sent from my Nexus 4
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
Rizy7 said:
Its the first time I've seen someone say custom kernels aren't recommended for stock rom. So just curious to find out why that is the case.
Click to expand...
Click to collapse
Some custom kernels can cause issue on the stock ROM while others has no issues.
Sent from my Nexus 4
andyabc said:
Some custom kernels can cause issue on the stock ROM while others has no issues.
Click to expand...
Click to collapse
Sorry but this doesn't make any sense. Any app, ROM, kernel or whatever could have "issues", it's the same with any software.
Earlier you said that custom kernels shouldn't be used on the stock ROM and that's just nonsense which you don't seem able to justify. What's so special about the stock ROM which makes it less suitable than a custom ROM?
If a custom kernel has been designed purely for a particular custom ROM then maybe that one shouldn't be used on a stock ROM, but you seem to be drastically over-generalising. Most custom kernels are designed for any ROM on the N4, particularly since most custom ROMs are built on exactly the same AOSP base.
Sent from my Nexus 4
steviewevie said:
Sorry but this doesn't make any sense. Any app, ROM, kernel or whatever could have "issues", it's the same with any software.
Earlier you said that custom kernels shouldn't be used on the stock ROM and that's just nonsense which you don't seem able to justify. What's so special about the stock ROM which makes it less suitable than a custom ROM?
If a custom kernel has been designed purely for a particular custom ROM then maybe that one shouldn't be used on a stock ROM, but you seem to be drastically over-generalising. Most custom kernels are designed for any ROM on the N4, particularly since most custom ROMs are built on exactly the same AOSP base.
Sent from my Nexus 4
Click to expand...
Click to collapse
I understand...
Sent from my Nexus 4
I'm currently using the i9505 GE ROM but it's causing lots of problems (random reboots, can't make phone calls) so since I am new to custom ROMs I don't know how to safely flash another rom if the one I am using now is using a different kernel. Help
poninaine said:
I'm currently using the i9505 GE ROM but it's causing lots of problems (random reboots, can't make phone calls) so since I am new to custom ROMs I don't know how to safely flash another rom if the one I am using now is using a different kernel. Help
Click to expand...
Click to collapse
For each rom has instructions on how to install
These are really basic question. You should already have know the awnser for it, before you started flashing.
Forget about kernels etc for a while. It's not important for you.
Just fully wipe and flash the rom you want with the custom recovery.
Lennyz1988 said:
These are really basic question. You should already have know the awnser for it, before you started flashing.
Forget about kernels etc for a while. It's not important for you.
Just fully wipe and flash the rom you want with the custom recovery.
Click to expand...
Click to collapse
I know it's basic but I don't know where to find the answers.
So is it safe to flash the stock rom while i'm on a GE faux123 kernel?
poninaine said:
I know it's basic but I don't know where to find the answers.
So is it safe to flash the stock rom while i'm on a GE faux123 kernel?
Click to expand...
Click to collapse
Yes you are mixing things up.
A kernel has nothing to do with flashing roms. It doesn't matter on what kernel you are in order to flash.
So forget about kernels, it's not important for you.
hey guys, i wanna ask, i have a custom KK rom now, if i flash stock lollipop, then root and flash custom KK or lollipop rom, will i get the IMEI issues??
THANKS
Normally no.
But why would you flash stock, root, and re-flash custom roms?
GDReaper said:
Normally no.
But why would you flash stock, root, and re-flash custom roms?
Click to expand...
Click to collapse
i wanna try the stock lollipop, i tried custom lollipop roms, and they all have bugs and lags, i wanna check if the stock is better, and if not, i will flash a custom rom again...
I heard the stock rom is not much better..
hajyihia said:
i wanna try the stock lollipop, i tried custom lollipop roms, and they all have bugs and lags, i wanna check if the stock is better, and if not, i will flash a custom rom again...
Click to expand...
Click to collapse
The stock is not better because the custom roms are based on the stock.....that is if they are tw based.
hajyihia said:
i wanna try the stock lollipop, i tried custom lollipop roms, and they all have bugs and lags, i wanna check if the stock is better, and if not, i will flash a custom rom again...
Click to expand...
Click to collapse
Have you tried the GPE roms? It has been the most stable and hassle free rom I used so far.
Or try CM12.1. I use it currently in combination with Ktoonsez 5.1 kernel and it works with no problems. Also it is a lot smoother than 5.0.1
GDReaper said:
Have you tried the GPE roms? It has been the most stable and hassle free rom I used so far.
Or try CM12.1. I use it currently in combination with Ktoonsez 5.1 kernel and it works with no problems. Also it is a lot smoother than 5.0.1
Click to expand...
Click to collapse
i have the i9500 variant, so GBE roms wont work, and CM12 or CM12.1 are good, but battery life is horrible, and the camera is s***....i tried cm12 couple weeks ago, its smooth enough but the camera i not good, AOSP roms have bad cameras....
Lennyz1988 said:
The stock is not better because the custom roms are based on the stock.....that is if they are tw based.
Click to expand...
Click to collapse
your right, but sometimes custom roms breaks some functionality, so maybe its a bit better, i dont know for sure...
If any developer has the time, please consider looking into making a cm rom, cause we've managed to get echoe rom working on the Sprint S7.
ItsYaminNoodlez said:
If any developer has the time, please consider looking into making a cm rom, cause we've managed to get echoe rom working on the Sprint S7.
Click to expand...
Click to collapse
Idk if it can be done on locked bootloaders that are tw launcher based because Cm is aosp based
vegoja said:
Idk if it can be done on locked bootloaders that are tw launcher based because Cm is aosp based
Click to expand...
Click to collapse
True didn't think of that. Hopefully we find a way to bypass that or unlock the bootloader.
The only thing that stops us from having a Cyanogen rom on our phones is our locked bootloaders. It doesn't matter that we have Twiz based OS on our phones cuz when you flash a rom from a custom recovery, it basically writes a whole new OS onto the phone. So whatever OS your running prior to the flash gets overwritten with the new OS.
So the only way we can flash a custom OS is if our bootloaders get unlocked, cuz once that happens we can flash a custom recovery, and from there we can flash whatever rom we want, as long as its made for our phones. First we got to have a working root method, then we have to have our bootloaders unlocked so we can flash a custom recovery, then we can flash away. We have a root method now, so it's only a matter of time until our bootloaders are unlocked. IMO
Sent from my SM-G930P using Tapatalk
sniperkill said:
The only thing that stops us from having a Cyanogen rom on our phones is our locked bootloaders. It doesn't matter that we have Twiz based OS on our phones cuz when you flash a rom from a custom recovery, it basically writes a whole new OS onto the phone. So whatever OS your running prior to the flash gets overwritten with the new OS.
So the only way we can flash a custom OS is if our bootloaders get unlocked, cuz once that happens we can flash a custom recovery, and from there we can flash whatever rom we want, as long as its made for our phones. First we got to have a working root method, then we have to have our bootloaders unlocked so we can flash a custom recovery, then we can flash away. We have a root method now, so it's only a matter of time until our bootloaders are unlocked. IMO
Click to expand...
Click to collapse
So wait, I've flashed a custom rom (echoe rom) on the galaxy s7 using flashfire and it works fine, so what would stop Cyanogenmod from working on the Galaxy s7?
ItsYaminNoodlez said:
So wait, I've flashed a custom rom (echoe rom) on the galaxy s7 using flashfire and it works fine, so what would stop Cyanogenmod from working on the Galaxy s7?
Click to expand...
Click to collapse
That rom is still touchwiz based. Kernel is the same, usually cm/aosp roms use a different kernel or greatly modified kernel.
Sent from my SM-G930P using XDA-Developers mobile app
lvpre said:
That rom is still touchwiz based. Kernel is the same, usually cm/aosp roms use a different kernel or greatly modified kernel.
Click to expand...
Click to collapse
Ah.
Hi,
I am running the Android N firmware on Athene: Custom Rom RR_5.8.0
I was playing around with dual boot, and successfully, but I only tried the 7.0/7.1.1 custom ROMs.
Could I flash MM custom ROM to dual boot, or simply put, can I downgrade to a MM ROM without messing with the N firmware, with and without dualboot on separate occasions or do I need to flash stock MM?
Does it sort of have a backwards compatibility?
What sort of risks will I be looking at?
Thanks in advance, this community is wonderful!
GuyGotMadNameGame said:
Could I flash MM custom ROM to dual boot, or simply put, can I downgrade to a MM ROM without messing with the N firmware, with and without dualboot on separate occasions or do I need to flash stock MM?
Click to expand...
Click to collapse
You don't need to flash stock MM.
Does it sort of have a backwards compatibility?
Click to expand...
Click to collapse
Theoretically, the ROMs should not have any issue.
What sort of risks will I be looking at?
Click to expand...
Click to collapse
From what I've seen, ONE person had some issue with fingerprint recognition on MM after flashing an N ROM. Otherwise, I've encountered nobody who has had issues.