yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Android Development] kevintm78:
Here's the latest free version of 3minit settings. Just download the attached app and install it like normal as a user app. This is to change battery styles for 3minit battery mod. Sorry for the delay.

DISABLE AD BLOCKER IF USING ONE.
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
Hey that one worked.

Can you help me. I installed the Marshmallow SD Fix in xposed but its not working. The problem is, its not requesting root permissions. Do you know how i can manually force it to request the permission or to manually add it to the SU list.
[Verizon Galaxy Note 4 Android Development] Snake-Plissken:
I cant access multiwindow anymore (via long pressing the back key). Nothing happens.

also resizing the screen via the swipe motion from the corner to the center and back doesnt work.

Both are enabled in settings. Does anyone else have the same issue?

----------------

Re-enabling every option worked.

Is there a way to map resizing screen size (swiping from the left or right corner to the center and back out) to three times home button like on the Note 7.
[Verizon Galaxy Note 4 Android Development] FritzM:
Can you post a link to where I can get the USB cable that worked with your Note 4 on Modest? If you can't post a link, then just the brand and model number of the cable would be great. I have already tried 3 different cables.
[Verizon Galaxy Note 4 Android Development] FritzM:
I tried something similar to those steps, but transferred the adb_keys file to my Note 4 via cloud storage.

Regarding the steps:

chmod 0644 /data/misc/adb/adb_keys

chown -u shell /data/misc/adb/adb_keys

I might not have executed the chown command, but I am not sure.

If this fixes the authorization for the one Windows machine, will future authorizations work normally for subsequent Windows machines or does this manual method of adding new keys have to be used for EACH server you might connect to?

I am asking because as long as I stay on Flashpoint v3.1 or Flashpoint v5 my USB auth/revoke works normally. It is only when I flash the Anykernel v3 based Flashpoint v5r1 and Flashpoint v6 from Kevin that I have the auth/revoke problem. I really don't want to go through all the manual steps to authorize a new Windows machine every time unless it is the only way to move forward to the new Magisk v22, and I find that I really need to upgrade to Magisk v22.
[Verizon Galaxy Note 4 Android Development] dd350:
Just these I got on Amazon, ostensibly nothing special. $8.99 for a 3-pack. When I called Kenwood for help they told me 10 times out of 10 if you have problems with Android it's the cable.

10ft 3 Pack Extra Long Charging Cord Nylon Braided High Speed Durable Fast Charging USB Charger Android Cable for Samsung Galaxy
[Verizon Galaxy Note 4 Android Development] dd350:
Upgraded to the Flashpoint v6 kernel and got this new icon on my notification bar, anyone know what it is?

Found it, it's Rich Communication Services (RCS).
[Verizon Galaxy Note 4 Android Development] dd350:
I'm looking to do this upgrade - was this ever confirmed to be the correct way to upgrade Magisk to v22 using the canary version?
[Verizon Galaxy Note 4 Android Development] FritzM:
I was still waiting to hear from Kevin (Modest creator) to confirm that this was the way forward.
[Verizon Galaxy Note 4 Android Development] FritzM:
So does this mean you can enable Chat Features in Google Messages app?

I have had no luck using the Flashpoint v5 kernel.
[Verizon Galaxy Note 4 Android Development] FritzM:
I got the cables today. They are behaving the same as the other 3 cables I tried. I think we have to consider the likelihood that there is some difference between the 2021 Honda Accord entertainment/navigation stock headunit vs the Kenwoods you were using. Maybe I could try updating the kernel and see if that makes a difference. I really don't use the adb function anyway. I would be willing to give up adb if Android Auto would work, but I doubt it will help.
[Verizon Galaxy Note 4 Android Development] dd350:
I've sent him a DM but haven't heard back yet either.
[Verizon Galaxy Note 4 Android Development] dd350:
I don't use the Google Messages app, I use Google Voice, so I'm not sure whether that would work.
[Verizon Galaxy Note 4 Android Development] dd350:
Sorry to hear that those cables didn't work with the Android Auto on your Honda Pilot, but they are still good cables for this phone. I've used them for everything from data transfer to Odin flashing. Just don't bend the plug at the phone connection, like any other cable, as it's toast once it's bent.
[Verizon Galaxy Note 4 Android Development] FritzM:
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?
[Verizon Galaxy Note 4 Android Development] dd350:
Running 21.4 with the 22.1 app, I'd never installed the SafetyNet API code but when I did I got this:
[Verizon Galaxy Note 4 Android Development] FritzM:
I assume that if you install an app to check SafetyNet (separate app from the Magisk app) , the other app will pass SafetyNet?

I am using the same Magisk 21.4 that you have, but I am still using the old 8.0.7 Magisk app.

Does your 22.1 Magisk app actually show the 21.4 Magisk version?

When I tried your config, the Magisk app showed "N/A" for the Magisk version.
[Verizon Galaxy Note 4 Android Development] dd350:
It shows the correct version with the Flashpoint V6 Kernel update.

I haven't tried testing SafetyNet from another app.
[Verizon Galaxy Note 4 Android Development] FritzM:
I assume things like Google Pay, MagiskHide, etc, are working which would indicate that your are actually passing SafetyNet? I installed the "SafetyNet Device Check" and "SafetyNet Helper Sample" apps so I can verify I am passing SafetyNet given that Magisk checker is broken.

So you are ruinning Flashpoint V6 Kernel.

If you go into Settings->Developer options do you still have the "Revoke USB debugging authorizations" option?

I tried running the V6 kernel, but it broke the pop up authorizations to use ADB, so I am stuck on the older kernel.
[Verizon Galaxy Note 4 Android Development] dd350:
It's not there. I never use ADB once the rooting and installation process is complete, so that's a non-issue for me.
[Verizon Galaxy Note 4 Android Development] FritzM:
I guess it is worth trying the v6 kernel to see if it fixes my Android Auto connection. The truth is that I don't use ADB right now, but I like to avoid losing capabilities that I might need down the road, unless there is a worthwhile benefit.

So did you see any benefit with upgrading to the Magisk 22.1 app while still running 21.4 Magisk?
[Verizon Galaxy Note 4 Android Development] dd350:
It's the only way I've run it, so I don't have any basis for comparison.
[Verizon Galaxy Note 4 Android Development] FritzM:
I upgraded to the v6 kernel, then I went ahead and upgraded to the Magisk 22 canary version (Magisk and app) that Kevin suggested and it worked fine. After that I took the plunge and upgraded to the latest Magisk 23 (Magisk and app) and that is working ok as well. My Android Auto is still not working, but I found the following to try as a workaround:

https://xdaforums.com/t/android-4-1-proxy-gateway-for-android-auto.3813163/

The RCS was still not working right, but I don't really care about that anyway.

Maybe some day Kevin can create a 6.1 kernel that fixes ADB Revoke Authorizations issue, but I don't really need that either.
[Verizon Galaxy Note 4 Android Development] dd350:
That's great news, so should it be possible to upgrade directly from the Magisk 21.4 version to the latest v23?
[Verizon Galaxy Note 4 Android Development] FritzM:
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:

https://xdaforums.com/t/rom-6-0-1-m...-9734-cql1-9734-1-26-18.3458377/post-84935697
[Verizon Galaxy Note 4 Android Development] dd350:
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.
[Verizon Galaxy Note 4 Android Development] FritzM:
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.
[Verizon Galaxy Note 4 Android Development] FritzM:
I should correct what I said above "patches and rebuilds the kernel".

It should say "patches, rebuilds, and flashes boot.img".
[Verizon Galaxy Note 4 Android Development] eliotargy:
Hello. The download link ifor the ROM n the OP is not working. Can someone update please?

And the link to the older version, Iget told I don't have permission to view or something.
[Verizon Galaxy Note 4 Android Development] Werve:
I read that Magisk app previous than v.23 had SafetyNet API key invalidated so it will always display error.
[Verizon Galaxy Note 4 Android Development] FritzM:
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.
[Verizon Galaxy Note 4 Android Development] FritzM:
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.
[Verizon Galaxy Note 4 Android Development] kevintm78:
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.
[Verizon Galaxy Note 4 Android Development] kevintm78:
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.
[Verizon Galaxy Note 4 Android Development] dd350:
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.
[Verizon Galaxy Note 4 Android Development] FritzM:
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:

Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) · Issue #5395 · topjohnwu/Magisk

For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it...

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:

Start->

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

<- End

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,

-Fritz
[Verizon Galaxy Note 4 Android Development] FritzM:
Here is an interesting article on managing Magisk modules and towards the end they talk about "Fox's Magisk module manager" which I have installed to check out. I disabled the Androidacy repo for now so I am just using the old "official" repo and the newer "alt" repo.

How to install Magisk modules on a rooted Android phone

Finding new modules might look a little different from now on

www.androidpolice.com
[Verizon Galaxy Note 4 Android Development] FritzM:
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?

Thanks,

Fritz
[Verizon Galaxy Note 4 Android Development] kevintm78:
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.

***Obligatory Warning. This is a test.***

Magisk patched firmware - only try if you're bootloader is already locked.
[Verizon Galaxy Note 4 Android Development] dd350:
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?
[Verizon Galaxy Note 4 Android Development] kevintm78:
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.
[Verizon Galaxy Note 4 Android Development] dd350:
Odin flash failed.
[Verizon Galaxy Note 4 Android Development] kevintm78:
Damn, this xda app is something else. It keeps force closing and erasing my responses.

Thanks for the links you posted. That helps clear up a few things that I've been wondering about. For the moment I've rolled back to v21.4, it's been the most stable for me. I'm in agreement with you about Magisk compatibility. I'm not sure if I'm passing safetynet but Netflix, hbomax, etc seem to working. However, I did already have them installed.

I'll get another kernel posted soon. I've been experimenting quite a bit to fix as many problems from the past and, hopefully, make it compatible with the direction that Magisk is going. My hope is to have a good final release for both the rom and kernel.

As far as the CTI1 update, I wasn't able to find any real changelog either. I saw a generic one from Verizon that basically said yada, yada, bug fixes, but that's about it. I will say that my reception seems to be better. I had been seeing my roaming indicator a lot but since I flashed the modem file there hasn't been a sighting of it yet. That being said, I still want to update the rom just in case there's some system updates.

There's something weird happening with Android Flie Host so for the time being here's a mega link for the safe upgrade.

Safe upgrade CTI1
[Verizon Galaxy Note 4 Android Development] dd350:
From what I could find there are additional security patches applied in CTI1, bringing the Android Security Patch Level five months forward to Jan 2018. Better than nothing I guess!
[Verizon Galaxy Note 4 Android Development] dd350:
When I attempt to flash CTI1_Modem.tar.md5 I get "MD5 hash value is invalid." Renaming the file to CTI1_Modem.tar allowed it to flash.
[Verizon Galaxy Note 4 Android Development] FritzM:
I noticed that same behavior when I flashed that modem file via ODIN v3.10.6. I am wondering if we need to use a newer version of ODIN?
[Verizon Galaxy Note 4 Android Development] kevintm78:
Thanks for the feedback. I flashed it on Linux using Jodin3. I was hoping it worked for windows. Did you ever get KingRoot working? I was thinking about updating my bootloaders but it's more of a neurotic impulse than a necessity.

I hope you're right about the security update. The build.prop still has the security patch 2017-08-01 but I wouldn't be surprised if Samsung (or Verizon) just didn't update it. The last three kernel sources that I've gotten from Samsung have all been the same. I guess the just update the link with the new firmware. Now they've removed the downloads for all versions except F & G. I was shocked that there was an update at all so I guess I'll count my blessings.
[Verizon Galaxy Note 4 Android Development] dd350:
KingRoot native is still broken. I got ahold of a copy of the PC version that started to root last week, seemed like it was making progress but at about 55% it said the device was somehow uncooperative, I forget the specifics. Several attempts, all ended the same. Now this week it is saying "no strategy" and stopping right there at the beginning like the native version. If anyone knows of any other root alternatives for this pass it on.
[Verizon Galaxy Note 4 Android Development] FritzM:
Kevin,

Could I use the boot.img file from the newer "N910VVRU2CTI1" set of files as a starting point to flash with Magisk, then reboot, and finally flash with Flashpoint v5?

This would mean I would not have the Flashpoint v3.1 from the MODest v11 ROM or the standalone Flashpoint v3.1 zip that I normally install. Would I get everything I need from only flashing Flashpoint v5? I am wondering if the RAMDISK would be missing anything?

Since I am currently running Magisk v23, I am thinking I would first try an experiment using Magisk v23 to patch the N910VVRU2CTI1 boot.img file. If that works, then I would flash with Flashpoint v5 and stay with Magisk v23 for now.

If the above does not work, then I would flash the N910VVRU2CTI1 boot.img, then flash Magisk 21.4, and then Flashpoint v5.

I successfully downloaded "CTI1_safe_update.zip" from your mega link.

I assume it needs to be unzipped to "CTI1_safe_full_update.tar.md5", and then installed under the "AP" section in ODIN?

I have been using ODIN v3.10.6. Should I be using a newer version?

I did have to drop the .md5 when installing the modem file, so it was a plain tar file.

Lastly, if I did install this file, would it not wipe out the MODest v11 ROM customizations?

I am trying to understand the scenarios where this file should be used. Maybe when you want to go back completely stock, but keep your boot loader unlocked?

Sorry for all the questions. I still have so much to learn. I read through a lot of history in this thread just to refresh my memory!
[Verizon Galaxy Note 4 Android Development] FritzM:
Kevin,

I tried using Magisk v23 to patch the boot.img file from the newer "N910VVRU2CTI1" set of files you posted. Magisk saved the patched boot.img file to my Downloads folder. I flashed that patched boot image file to the boot partition via TWRP.

At this point it did not matter if I flashed the Flashpoint v5 before or after booting up. Either way the Magisk app was missing its main ribbon menu and it had N/A for the Magisk version. This indicates that if we want ADB working, we must either stay on Magisk v21.4 or go to Magisk v24 where we lose MagiskHide. In order to use Magisk v22/v23, we have to use your Flashpoint v6, and that will stop ADB from working.

I decided to flash back to Magisk v21.4 with Magisk Manager v8.0.7.

From TWRP, I flashed the boot.img file from the newer "N910VVRU2CTI1" set of files to the boot partition, then flashed Magisk v21.4, then Flashpoint v5, and then booted up.

I noticed some errors when checking SafetyNet with the app "SafetyNet Check", so I went back to TWRP and wiped Cache and Dalvik Cache, then booted up. SafetyNet looks good now, and ADB is working with the "Revoke" option present under the Developer menu.

I am staying with this config unless/until you come out with further updates.

Thanks again for this ROM. I like it even after all these years!

Fritz
[Verizon Galaxy Note 4 Android Development] xero4zero:
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z | by jrkruse for Galaxy Note 4

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

might be helpful
[Verizon Galaxy Note 4 Android Development] FritzM:
Compared to Kevin's latest safe upgrade file, I see the files in this "force wipe" have .lz4 compression, and the following additional files:

carrier.img.ext4.lz4

recovery.img.lz4

TRLTE_USA_VZW.pit

Do we know if that recovery image includes TWRP?
[Verizon Galaxy Note 4 Android Development] xero4zero:
Not sure but here is the original thread by @jrkruse

https://xdaforums.com/t/2021_vzw_no...ck_u-p-dwngrade_bootloaders_kk-ll-mm.4018001/
[Verizon Galaxy Note 4 Android Development] FritzM:
Thanks for the info. I just hope the kingroot/kingoroot part is still working.

dd350 posted earlier it was not working.