I cannot confirm that. To be safe, I followed Kevin's directions upgrading from Magisk 21 using 22 canary, THEN I did upgrade to 23 version as usual from inside the Magisk 22 canary app. See the following URL to use canary:
I should have verified that link, sorry.The link from Kevin's old post to the Canary version has actually been updated to 23. I downloaded it and tried installing it as a normal APK and it said it installed successfully, but the installed version was still 21.4 in the app. I renamed it to .zip and installed it from recovery, and it worked.
I should correct what I said above "patches and rebuilds the kernel".I should have verified that link, sorry.
With the version 22 and later format, you would normally install it as a normal APK as you did.
After that install, when back in to the updated v23 app, you should now see two versions listed one for app and one for Magisk.
You should have seen the app version as 23 and Magisk would still show 21.4.
In the upgraded version 23 Magisk app UI there should have been an "upgrade" button next to the Magisk version 21.4.
You could have pushed that button and be able to do a direct upgrade of Magisk to 23. This is the step that patches and rebuilds the kernel, and it is the step where I thought the beta version was the way to go because Kevin used it.
If it is working ok for you AND you now see version 23 for Both Magisk app and Magisk, then you should be fine.
I don't know if there will be many more upgrades anyway with Topjohnwu working for Google now.
I am still running Magisk 21.4 with the 8.0.7 Magisk app. I noticed that the "Check SafetyNet" is now failing from within the Magisk 8.0.7 app, but I have other SafetyNet checking apps that show SafetyNet passing without a problem. Also, I am experiencing no other symptoms to suggest that my SafetyNet is failing, so I am assuming it is nothing to worry about.
I was wondering if anyone else using Magisk 21.4/8.0.7 is seeing this?
I am not sure if the developer is still supporting this ROM. I did some looking around and you might be able to get some of the files from this link https://androidfilehost.com/?w=profile&uid=24651430732238045 (just click on "Galaxy Note 4" under Supported Devices) I cannot be sure of the file content from this link, so use at your own risk.
That makes sense. I have now been running on Magisk v23 for some time and it has been working great. The only problem is that more and more apps are dropping support for Android 6.0.1, so I guess the day is approaching where I might have to upgrade my phone hardware. I really like the Note 4 and want to keep using it.
Kevin, glad to see you back!The latest canary build for Magisk v24 just installed successfully with flashpoint kernel v5. It will probably work with stock kernel and any others that were failing previously.
Magisk v24 aka (24103) canary update
If you're using v21.4 install the apk over your current version with a file manager and then update through the app. The manager tends to install v22.1 first before going to the latest version and that's the one failing install correctly.
You may want to read Magisk update notes as well. Topjonwu is now employed by Google and I can't imagine any employer being ok with developing software that circumvents their own security checks. The safetynet check has been removed, root detection bypassing will need help through a module(s), and there's no longer a module repo which is kind of a bummer. However, modules can still be installed from storage. There's also a feature called zygisk that I don't really understand but according to the notes should help module devs stay on top of root detection.
Kevin,I'm really late to the party with these CTI1 files so I'm guessing they may have been posted already. If not, then they'll be here.
CTI1 modem - flash using Odin if Windows computer or if flashing with Linux I used JOdin, or any Heimdall spinoff.
CTI1 Files - stock recovery, boot, pit, and an Odin flash able "safe" full upgrade. "Safe" meaning it includes everything except the aboot and recovery so TWRP doesn't get removed and bootloader doesn't lock (nor upgrade). The safe file is still uploading but shouldn't be much longer.
I haven't tried unlocking a bootloader in awhile. If you're up for being a test I used magisk to patch a full firmware of CTI1.Hey Kevin, glad you're back - my Note 4 on MODest recently started the "random reboots of death", so I've been planning a motherboard replacement... When I attempted it today with a new board I could no longer get a cloud connection with KingRoot. Not sure what has happened, though with world events such as they are today who knows. Has anyone else tried rooting lately? I just get "Network error, couldn't get a cloud strategy".
Not good news for the community with TJW being hired by Google. Hopefully there was a padawan who can continue the fight.
Sure, I'll try it... I've got several test devices. Just want to be 100% sure, this is only for devices with a LOCKED bootloader?
That's correct. If it flashes at all, it should update and relock the bootloader. But I'm hoping the root will survive long enough to complete the unlock process.
Damn, this xda app is something else. It keeps force closing and erasing my responses.Kevin, glad to see you back!
I am still running Magisk v23 and I am wondering if it is better to wait to upgrade to Magisk v24 until there is a reliable/tested replacement for the MagiskHide capability removed in v24.
The Zygisk capability might have an issue with our older 3.10 vintage kernel, and it seems to still be up in the air:
[Wontfix] Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) · Issue #5395 · topjohnwu/MagiskDevice: Samsung Android version: N/A Magisk version name: N/A Magisk version code: 24102 For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the pro...github.com
To refresh where I am now:
I used your Flashpoint v3.1, then Flashpoint v5r1, then Flashpoint v6 and successfully upgraded from Magisk v21.4 to Magisk v22 using your instructions. When Magisk v23 became available, I successfully upgraded to that from inside the app.
Is there any way you could create a new Flashpoint v7 that would combine all the fixes from v5, v5r1 and v6, but also fix the breaking of ADB? Also, maybe the Flashpoint v3.1 could be updated to include Magisk v23 and rename it to Flashpoint v3.2?
Below are the last details I could find about ADB in earlier threads:
There's a value set in the default.prop in the kernel ramdisk that is set wrong. Since v5 is packaged with anykernel the wrong value doesn't get overwritten like it does with v3.1 which is replacing the entire boot.img (ramdisk + zImage + dtb). The best part of anykernel is that it only touches what you specify in the anykernel script but that's also what's working against us. Until recently I didn't know there was an issue with adb so the changes weren't added to the script.
In a nutshell :
Flashing v5 only= adb still broke
Flashing 3.1 only= adb works
Flashing v3.1 and then v5= adb works
Flashing stock CQL1 kernel= adb works
CQL1 + v5= adb works
If you don't have the time for updating this old stuff, I can just stick with my current config and live without ADB.
Thanks again for all your work over the years,
There's something weird happening with Android Flie Host so for the time being here's a mega link for the safe upgrade.Kevin,
I was running with baseband N910VVRU2CQL1, and after I did the ODIN upgrade with modem file, my baseband is now N910VVRU2CTI1. Do you know if there were any fixes/improvements by upgrading to CTI1? I could not find any sort of changelog or release notes.
Is there any reason I would want to use the "safe" full upgrade, or to use Magisk app to patch the boot.img file you included with the "CTI1 Files"?
By the way, I don't see the "safe" full upgrade file at the link you provided, so maybe the upload timed out?
I'm still getting an error trying to link PayPal with the fingerprint login. It could be the permissive kernel. I'll try a few more possibilities and see if we can get that worked out.Hi brother, I want to tell you that I love this rom, it moves very well, something I would like to comment on if it is possible, it is the part of being able to use the fingerprint in PayPal since in the previous roms it does not work in this app, thanks in advance.