No
Nojust there is no Samsung update for this device (newer than July security patches). Theoretically I could prepare N960FXXU9FVK1 update but it would rather be a psychological update
![]()
Thread has been updated, SAFWB3 (One UI v2.5) DevBase v7.4 (February 2023 security patches, changelist 24343300)
Download ROM:
SM-N960F/DS:
(BL update is not necessary if you are on any Q bootloader already)
NOTE: I don't have any rooted device for testing anymore, so there is still Magisk v23 inside (same as in my previous build for N960F) - old but well tested with my last rooted deviceI'm just not sure if a newer version works well as a task in my DevBase installer and if it works better with this device overall. This is the only set I can prepare "blindly"
Of course - you can install any version of Magisk as a separate installer, after flashing this ROM
Thank you yes i flash with twrp 3.6.1.xxxx et no problem this rom work very well, i intall Firefox kit and gravitybox, all is OK and thank you to Alexndr for this rom
Thank you yes i flash with twrp 3.6.1.xxxx et no problem this rom work very well, i intall Firefox kit and gravitybox, all is OK and thank you to Alexndr for this rom
Try install the last official firmware with home_csc in odin. Check your cable too. It may caused by data transfer... I've resolved a same problem once. Good luck.I have a weird issue. I had been using the DevBase 7.4 based on FVH1 for some time without any issues and then decided to upgrade to DevBase 7.4 based on SAFWB3. I did a dirty flash and had been experiencing random reboots for a few days and then decided to do a clean flash of the SAFWB3 base. When I did this, the phone started up without any mobile reception and had a popup about no IMEI number. I thought it might be the firmware so tried again using the FVH1 base and still had the same issue. I then tried to put "Rescue" in the filename for the SAFWB3 base and this gave me reception but I was still experiencing random reboots on a clean install. I then tried "Rescue" in the filename for the FVH1 base but ended up with no reception again.
I thought I would then try and AOSP based ROM to see if I had any issues and reception worked fine on these ROMs so I thought it might be something corrupted when flashing the DevBase ROMs. I thought I would do what I normally do when I break something and that is to do a clean install of the OS using Odin. When I did this I had the same issue and ended up with no IMEI number. This has normally worked for me in the past when I have broken something but I can't get it to work. I even tried restoring my EFS from a TWRP backup but ended up with a bootloop so had to wipe and do a fresh install to get the phone to startup again.
I have now had to settle with using an AOSP based ROM as this is my only phone and I need to be contactable. I really want to go back to stock but don't really know what to do now. Is anyone able to advise what I can do to get the phone running normally with this ROM?
Thanks in advance and sorry for the long post.
Because this is how it should be done, otherwise you'll get an error and Magisk won't install !!!
FVK1 is older than FWB3 !And what's base off DevBase 7.4? FVK1 (lastest) or older? @_alexndr Sir?
After odin to stock FVK1 From DevBase 7.4 my IMEI gone, i used efs backup from devbase create, or backed up from twrp but still cant get back IMEI. How can i get it back now?
zip -r -9 N960FXXUxxxxx_DevBase.zip META-INF options.prop ALEXNDR
cat /external_sd/.backup/efs/efs_backup.txt