[ROM][6.0.1]MODest Rom☆Multi-DPI☆Stock-Modded☆CQL1☆(1/26/18)

Is it important to you to have the most recent firmware?


  • Total voters
    192
Search This thread

FritzM

Senior Member
That's great news, so should it be possible to upgrade directly from the Magisk 21.4 version to the latest v23?
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:

 

dd350

Senior Member
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.
 

FritzM

Senior Member
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 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.
 

FritzM

Senior Member
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 should correct what I said above "patches and rebuilds the kernel".
It should say "patches, rebuilds, and flashes boot.img".
 

eliotargy

Senior Member
Oct 24, 2013
219
17
Hangzhou
Hello. The download link ifor the ROM n the OP is not working. Can someone update please?
1642852666156.png

And the link to the older version, Iget told I don't have permission to view or something.
 
Last edited:
  • Like
Reactions: commissionerg

Werve

Member
Aug 14, 2018
21
1
Samsung Galaxy Note 4
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?

Running 21.4 with the 22.1 app, I'd never installed the SafetyNet API code but when I did I got this:View attachment 5384037

I read that Magisk app previous than v.23 had SafetyNet API key invalidated so it will always display error.
 

FritzM

Senior Member
Hello. The download link ifor the ROM n the OP is not working. Can someone update please?
View attachment 5515389
And the link to the older version, Iget told I don't have permission to view or something.
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.
 

FritzM

Senior Member
I read that Magisk app previous than v.23 had SafetyNet API key invalidated so it will always display error.
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.
 

kevintm78

Senior Member
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.
 
  • Like
Reactions: xero4zero

kevintm78

Senior Member
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.
 

dd350

Senior Member
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.

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.
 
  • Like
Reactions: kevintm78

FritzM

Senior Member
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, 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:


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
 
Last edited:

FritzM

Senior Member
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.

 
  • Like
Reactions: kevintm78

FritzM

Senior Member
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.
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
 
Last edited:

kevintm78

Senior Member
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.
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.
 

dd350

Senior Member
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.
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?
 

kevintm78

Senior Member
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:


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
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.


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
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 154
    MODEST ROM


    So, this is my rom. It's basically an all stock rom with some added features that, in my opinion, make for a much better overall experience than true stock. It comes with a custom kernel that is fully upstreamed for all the latest fixes and patches. If you like stock Note 4 look I don't think you'll find a better rom.

    Features :
    Flashpoint Kernel v3.1- Linux v.3.10.108 Thread Link
    Rooted with Magisk v15.3
    Busybox by osm0sis
    Deodexed
    Zip-aligned
    Multi-DPI (Currently set at 560)
    Private Mode Working
    Safe volume removed
    All apps multi-window
    Brought back "once and always" buttons
    Call record
    5way reboot
    6 in the Hotseat
    TouchWiz swipe left
    Toolbox enabled
    Flashlight in QuickSettings Panel
    Volume Up for flashlight- turn on in Settings/Display/Torch light
    Tethering check disabled
    1120 Fonts- Main Thread
    Viper4android

    There are a lot of thinks to give out, so here goes.
    @topjohnwu
    @carlosggb
    @jovy23
    @viper520
    @SuperR.
    @iBotPeaches
    @nathanchance
    @asc1977
    @tdunham
    @gharrington
    @mariozawa
    @Ticklefish
    @osm0sis
    @Kamy
    @Alexandr
    @BRoy_98
    @1Xfan
    @mhmdalsfaf
    @supergrobi94
    @dagrim1
    @BeckPC
    @Winb33
    And for bringing root to the 910V. The following:
    @beaups
    @ryanbg
    @Kingxteam

    I really could go on and on. Everything I've learned is from members of XDA. Thank you to anyone who has taken the time to share their knowledge and if I've forgotten you just pm me and it will be corrected immediately.

    ModestRom v11--- DOWNLOAD


    If you've already upgraded your bootloader to CPD1 (MM 6.0.1) the only thing you need to upgrade is your modem. Using Odin, just place the modem file in the AP slot and boot your phone into download mode and flash.

    CQL1 Modem Upgrade-- DOWNLOAD

    Instructions
    If you are on 5.1.1 you will need to upgrade your bootloader and reroot using this Guide.

    If you have already upgraded to 6.0, unlocked your bootloader, and have TWRP installed, all you need to do is the following:

    -Download the CQL1 modem upgrade to your pc
    -Download the Rom to your internal or external sdcard
    -Boot into recovery and factory reset your device
    -Do not boot straight from recovery to download mode - download mode does not properly boot without doing the following
    -Power off your device and pull your battery for 3-5 seconds (this will ensure that your device properly boots into download mode)
    -Insert your battery and boot to download mode by holding vol. down + home button + power button at the same time
    -Using Odin flash the CQL1 modem and once that completes, power off your device
    -Now boot to recovery by holding vol. up + home button + power button
    -Once you're in recovery go to advanced wipe and wipe everything but the internal and external sdcard (I always do this step twice)
    -Then just go to install and flash the MODestRom zip file
    -Boot time is about 7 to 10 minutes
    -Enjoy!!


    XDA:DevDB Information
    MODest Rom, ROM for the Samsung Galaxy Note 4

    Contributors
    kevintm78
    Source Code: https://github.com/kevintm78/Flashpoint_3

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: CQI2
    Based On: TouchWiz

    Version Information
    Status: Stable
    Current Stable Version: MODestRom v11
    Stable Release Date: 2018-01-26

    Created 2016-09-09
    Last Updated 2018-01-26
    49
    Advanced/WiFi Calling Fix
    This is how I got mine working; it's the same fix that @mharleston brought to light a while back.
    Using any root explorer do the following:
    -Go to /system/csc/ and find the sales_code.dat file
    -Open with a text editor and change the VZW to TMB
    -Save that file and reboot
    -After the reboot go back to the same file and change it back to VZW and reboot again

    Once it boots back up check in Settings and you should be able to access both the Advanced Calling and WiFi Calling

    Flashpoint Kernel-most recent kernel
    Link to kernel thread

    How to Update Bootloader from CPD1 to CQI2
    Link to post

    MAGISK
    Link to all things Magisk


    Xposed-system-less v87.3_Updated for Magisk v18+
    See this post

    TWRP 3.2.2
    TWRP 3.2.2 is now available! Here's the link The .tar file gets flashed in Odin (in the ap slot) and the image file can be flashed in recovery.

    Theme's by @supergrobi94
    Tons of different options.- and here's an example of my own personal favorite here.
    38
    ☆☆Edge Panel for ModestRom v11☆☆
    DOWNLOAD-This will change your Contacts app to the S6 version and the IncallUI app to the Note 7 version because the people stripe will not work with the N4 contacts.

    ☆☆3minit Battery Flashable for ModestRom v11☆☆
    DOWNLOAD

    ☆☆3minit Battery-3minit Clock for ModestRom v11☆☆
    DOWNLOAD

    ☆☆3minit Battery-3minit Clock-Gradient Statusbar for ModestRom v11☆☆
    Download

    ☆☆Signature Spoofing for ModestRom v11☆☆
    Link to info and Download


    ☆☆Older ModestRom Versions☆☆
    DOWNLOADS


    GRACE Apps
    Grace_Contacts
    GRACE_Email
    GRACE_VoiceNotes
    Grace_InCallUI

    Other Apps
    S7 S-Voice flashable zip - after you flash that you can update it with this app.
    Modded YouTube app- allows background playback and no ads
    Kernel Adiutor-mod- alternative app that has different options and may suit some people better
    Device Check- a must have app. Will tell you nearly everything you need to know about your device.
    Adaway app- another must have app. Imo this app greatly speeds up stock browser and Chrome
    arkTube app-an app for downloading YouTube videos.
    S7 Keyboard
    TerrariumTV app- a great app to watch all your favorite shows and movies
    25
    UPDATE!!!

    Update is posted! I think I may have to change the name of this rom soon. There's some great roms out there but if you like a stock Note 4 where everything works as it should there is no better option.
    CHANGELOG:
    -Firmware Upgrade to CQB2
    -Updated Viper4Android v2.5.0.5
    -Removed 3minit, Potato Clock, Gradient Statusbar
    -Removed Overclock from the kernel
    -Fixed many errors in kernel
    -A lot more Debloated

    I will provide options soon for anyone that might want the UI mods and I'll probably bring back the overclock if I can get it to behave. Also the Debloat zip removes 50 extra apps. I did it that way since some things need to be there on first boot or certain features will break and also if anyone wants to customize it you can unzip the file and anything you want to keep you can remove from the updater script.

    If you like this rom and want to see future releases please support my work by pressing the thanks button. I see a lot of downloads but not many thanks so it's hard to tell if people are trying and not liking or just forgetting the thanks button.
    18
    Update Posted

    Op is updated with the new version. I left more of the bloatware in this time and will be posting some debloat scripts very soon. Currently, I don't have phone service with my note 4 so I'm not able to test any of the service related features. Please let me know if there are issues of any kind on that front. I'm also going to try and get some requests going on this soon, but wanted to get the unaltered version up for those who want that.

    ModestRom X-- Download

    CQI2 Modem-- Download

    Oh, and I'm adding a link to YouTube download app in the 3rd post and probably some other handy apps I've been trying 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.
    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.