Open mrslezak opened 4 years ago
Looks like because 865 devices use a super partition and system vendor odb etc are read only it fails.
I think it's because it relies on traditional BusyBox but the 865 with a read only super partition uses the systemless Magisk Module for BusyBox NDK since it can not install to /system/ or related partitions.
Worked fine in the past but now doesn't seem to have the proper rights to flash a kernel completely. FK kernel manager and EX both can still flash kernels. I don't know how many people use this feature I'm a kernel dev so I always tell people to use SmartPack over the others just this one issue I don't know what causes it.
I'm not sure, but the screenshot says the flashing process is completed (doesn't necessarily succeeded). It is very likely that the issue is related with some busybox binaries. I always found (of-course on older cpu's) that the flashing from our apps (this one and Smart Flasher) occasionally failed when using with BusyBox Magisk Module won't. Have you tried installing a standalone busybox (here is an app by our team). Also, updating AnyKernel to the latest will also help.
Worked fine in the past but now doesn't seem to have the proper rights to flash a kernel completely. FK kernel manager and EX both can still flash kernels. I don't know how many people use this feature I'm a kernel dev so I always tell people to use SmartPack over the others just this one issue I don't know what causes it.