Glad to hear. Yeah,the 1.6 version doesn't work for everyone. The reason is still rather unclear to me,but either way,glad the 1.5 version is working for you!
Actually, that could be it @spookcity138 as I'm using F2FS on data and cache. On the stock RR boot images it works fine and also at least until v4.0 in your kernel. Did you mess with F2FS/fstab in v4.0+/v5.0?
No i didn't mess with F2FS. Just thinking if it works. If you use it maybe i could try too.Actually, that could be it @spookcity138 as I'm using F2FS on data and cache. On the stock RR boot images it works fine and also at least until v4.0 in your kernel. Did you mess with F2FS/fstab in v4.0+/v5.0?
I've not directly messed with F2FS,but perhaps another commit I made has created some problem. It's possible and it has to be something along these lines as not too many are experiencing issues with the kernel. I've had no time lately to look into it,sorry. I have made changes and added some features to the kernel a few weeks ago. I plan to release a test build hopefully this week. Perhaps by some great chance that will solve it. If not that's the next thing I'll do when I have time... Try to figure out the cause.Actually, that could be it @spookcity138 as I'm using F2FS on data and cache. On the stock RR boot images it works fine and also at least until v4.0 in your kernel. Did you mess with F2FS/fstab in v4.0+/v5.0?
No you have to clear the data from kernel aduitor
Try to flash the original boot.img from the zip, then flash kernel and root method again. Had the same when using an older kernel and updated to 5.0.
Interesting. I'm not sure why this would be. I've been meaning to release a new test build for my kernel. I've just been really busy. I will look into this then. In the meantime,if you open (don't extract) the kernel zip and open the anykernel.sh file in a text editor..Then change the line ”do.devicecheck=1" to "do.devicecheck=0" That should hopefully allow you to successfully flash the kernel.Running AICP latest build
Gesendet von meinem SM-G800F mit Tapatalk
No later than this weekend. I promise [emoji4]Is there any new kernel to test
It's in the zip file of the ROM you use (AICP). Open the zip and extract it to your storage. Then flash with TWRP, press install and then the button on the bottom right to flash an img file.
Sorry for the bad picture quality and my noobness [emoji6]
Select boot.Sorry for the bad picture quality and my noobness [emoji6]
Gesendet von meinem SM-G800F mit Tapatalk
This method also leads to the same error message in TWRP as before
Hmm,perhaps something has changed. I will try to look into it by the weekend. You may need to edit the anykernel.sh file as I posted earlier. I'm really not sure what the problem is.
That really is strange, never happened here. I would now do a dirty flash with the ROM (only wipe the caches) to get the original kernel back. But to be honest I don't have any ideas left when that doesn't work.
