Hi all! I am having an issue. I have just installed LineageOS, Magisk Root, and ElementalX kernel on my Pixel 3a (In that order). After installing ElementalX, my wifi does not work. I turn it on, it says Turning on... then it turns off. Any idea on how to fix this issue?
ElementalX is for stock. I am sure the Lineage team is using a different WiFi driver than stock which would make ElementalX not compatible.
Uzephi said:
ElementalX is for stock. I am sure the Lineage team is using a different WiFi driver than stock which would make ElementalX not compatible.
Click to expand...
Click to collapse
Thanks for the input. I ended up wiping my phone (I installed Magisk incorrectly) and I just used the stock kernel. Sorry for the late response, everything js working good now.
Related
I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!
boredomkillz said:
I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!
Click to expand...
Click to collapse
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.
simms22 said:
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.
Click to expand...
Click to collapse
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.
boredomkillz said:
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.
Click to expand...
Click to collapse
na.. i run either nightly or kang as a daily. should be much more stable than rc1 in any case
Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.
boredomkillz said:
Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.
Click to expand...
Click to collapse
does it work with any other rom/kernel?
simms22 said:
does it work with any other rom/kernel?
Click to expand...
Click to collapse
I've done a CM7/Netarchy(BFS) as well as reddev1's/Netarchy(BFS) combination which have both worked well without a hitch.
i've never tried a video until today (i've cataclysm rom, but i've never tried video on stock rom) and i've this audio problem
http://youtu.be/2PZrFiXB_-o
what do you think?
phantomEVO said:
i've never tried a video until today (i've cataclysm rom, but i've never tried video on stock rom) and i've this audio problem
http://youtu.be/2PZrFiXB_-o
what do you think?
Click to expand...
Click to collapse
Currently, Im running Cataclysm ROM as well with franco kernel and do not have the issue. Do you have any thing else installed (Xposed, root apps for sound, custom kernel, etc)? If not, try fresh WIPE, install of the ROM again.
i've last elementalx
phantomEVO said:
i've last elementalx
Click to expand...
Click to collapse
Try a different kernel and see if problem persists. If it does, then you need to do a clean flash of ROM and try again with elementalX. Franco works very well for me and may have something to do with that.
RevelationOmega said:
Try a different kernel and see if problem persists. If it does, then you need to do a clean flash of ROM and try again with elementalX. Franco works very well for me and may have something to do with that.
Click to expand...
Click to collapse
if i reflash the rom, will i lost the elemental kernel?
phantomEVO said:
if i reflash the rom, will i lost the elemental kernel?
Click to expand...
Click to collapse
Yes, reflashing the ROM will overwrite the kernel and replace the installed ROM stock kernel, you will need to reflash the elementalX kernel again or another kernel to have the custom one installed. I'd recommend another kernel to test if the problem was kernel related. Most kernels, with audio support, can throw off sound in areas/apps.
phantomEVO said:
i've never tried a video until today (i've cataclysm rom, but i've never tried video on stock rom) and i've this audio problem
http://youtu.be/2PZrFiXB_-o
what do you think?
Click to expand...
Click to collapse
That static noise while recording video's is a known bug of android 4.4.2, its even there on stock rom
I got my N5 yesterday
unlocked bootloader
running TWRP
can flash and setup any rom
CAN NOT GET ANY KERNEL TO BOOT (using CM types when available, latest try was running sylentprofet minimal}
not sure what is going on, probably something small that I am missing.
tried:
faux
franco
N3o
ElementalX
Sorry if it is a simple fix. Did try to search but no real results that helped
If you're running cm look for CAF kernels.
As stated above, the problem started when you flashed, faux, franco kernel. Elementalx has a version which is compatible to CM Roms but need to read well. I heard of some people having problems after flashing franco, where another kernel wouldn't boot after franco.
Do a clean Rom installation, boot the phone with the stock CM kernel, then try to flash Chaos kernel and see how it does
thanks
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
orvon.freeman said:
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
Click to expand...
Click to collapse
Glad you got it working
A quick search returned this from faux. more CAF info available around:
http://forum.xda-developers.com/showpost.php?p=46098546&postcount=15393
Well, title talks for itself. How do I wipe everything battery-related so my phone will calculate it normally again? TWRP shows charge correctly. Reboot, dalvik/cache wipe and baterystats.bin deleting did not help
You don't have to charge your phone at least 40 days
? ? ? ? ? ?
This happened to me if I was using a 6.0 kernel with 6.0.1, it fixed itself when I flashed an updated one. Today's ElementalX release worked for me.
murdi said:
This happened to me if I was using a 6.0 kernel with 6.0.1, it fixed itself when I flashed an updated one. Today's ElementalX release worked for me.
Click to expand...
Click to collapse
Yes, also figured this out. But about ElementalX -- does it work good for you? Tried to flash it on 6.0 the other day -- freezes were everywhere, couldn't live with it more than a day.
I've not really used it much, I prefer a fairly stock kernel tweaked for root. ElementalX just happened to be the first kernel I found updated for 6.0.1.
murdi said:
This happened to me if I was using a 6.0 kernel with 6.0.1, it fixed itself when I flashed an updated one. Today's ElementalX release worked for me.
Click to expand...
Click to collapse
Did you do anything special for the ElementalX kernel install? I've installed the N5-6.07 version but my battery percentage is still in the thousands.
Never mind. Turns out if you read carefully you can find the answer your looking for.
Do NOT flash this over other custom kernels!
You should only flash ElementalX over the kernel that came with your ROM!!!
Click to expand...
Click to collapse
I spaced that I was installing the modified 6.0.0 bootloader for root since I was using the nexus root toolkit and its not yet updated for 6.0.1; And since the kernel needs the stock boot image as it modifies the current kernel instead of replacing the kernel all together, I was still technically running a 6.0.0 kernel. After flashing the unmodified 6.0.1 kernel and installing the ElementalX kernel on top of that I am good to go. At 17% and charging.
This is Google's fault, flashed stock (6.0.1) and also got this
BrownEye02 said:
Did you do anything special for the ElementalX kernel install? I've installed the N5-6.07 version but my battery percentage is still in the thousands.
Never mind. Turns out if you read carefully you can find the answer your looking for.
I spaced that I was installing the modified 6.0.0 bootloader for root since I was using the nexus root toolkit and its not yet updated for 6.0.1; And since the kernel needs the stock boot image as it modifies the current kernel instead of replacing the kernel all together, I was still technically running a 6.0.0 kernel. After flashing the unmodified 6.0.1 kernel and installing the ElementalX kernel on top of that I am good to go. At 17% and charging.
Click to expand...
Click to collapse
I have the same problem, where can I find unmodified 6.0.1 kernel?
Sent from my Nexus 5 using Tapatalk
AFAIK it's a problem related to some kernels, i think franco and hells, i'm using Elemental and have no problem
shariat said:
I have the same problem, where can I find unmodified 6.0.1 kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WugFresh's Nexus Root Toolkit was recently updated for 6.0.1 and now has the stock kernel that has been modified for root only. Just switched to it from the ElementalX kernel and the battery % are correct.
I flashed 6.0.1 from 6.0 via wugfresh and am getting 3833% battery, any ideas ?
I flashed stock boot, system and cache images with fastboot. For root used supersu 2.63.3. Everything is fine now
Sent from my Nexus 5 using Tapatalk
Reflashed boot, all good here now
Having the same issue. I took mine back to stock though. So your saying flash stock boot.img to fix?
Edit: reflashed all stock, flashed recovery, installed su 2.62 and everything worked fine. Battery percentage back to normal and battery tab back
shariat said:
I flashed stock boot, system and cache images with fastboot. For root used supersu 2.63.3. Everything is fine now
Click to expand...
Click to collapse
I did the altered boot & superSU 2.63.2 and have the bug still, so I'll try this. Cheers.
Edit: you sure you don't mean 2.62.3?
As the title would imply, every time I install either a custom kernel, or root, it will remove the other. I have a google pixel (verizon model, unsure if this matters) that will work fine with either one by itself, but I cant have both. ElementalX is the only kernel that seems to work, but it won't really cohabit with either Magisk or SuperSU. Any help or ideas would be appreciated.
JadeTank said:
As the title would imply, every time I install either a custom kernel, or root, it will remove the other. I have a google pixel (verizon model, unsure if this matters) that will work fine with either one by itself, but I cant have both. ElementalX is the only kernel that seems to work, but it won't really cohabit with either Magisk or SuperSU. Any help or ideas would be appreciated.
Click to expand...
Click to collapse
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.
Arju said:
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.
Click to expand...
Click to collapse
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.
JadeTank said:
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.
Click to expand...
Click to collapse
I wouldn't recommend SuperSU anymore. Magisk hides root from apps so that apps that search for root would work. With SuperSU you won't find that. SuperSU is pretty much outdated.
JadeTank said:
I managed to get magisk running with a kernel, but it was only after having to factory reset. For some reason, when I was trying it before Magisk didnt work. But I did follow the steps you said and it worked, so thanks for the tip. If you know btw, is there a reason SuperSU wont work with a custom kernel? Im relatively new to this kind of stuff, and was wondering if it wont work that way.
Click to expand...
Click to collapse
To add to what @Arju said, no version of SuperSU works on with Android 8.1 on the 2016 Pixel.
Arju said:
How is your flashing process? You're supposed to flash kernel and then magisk straight after and then reboot into system. If you do it the other way around then the kernel overwrites magisk as magisk will patch the previous version first. So in short flash kernel and then magisk after that reboot into system.
Click to expand...
Click to collapse
If it's an AnyKernel2 kernel, it doesn't matter what order you flash them in since only ramdisk modifications are made. I prefer flashing Magisk first so it backs up the stock boot.img.