[RECOVERY][SM-N960F/N] TWRP for Galaxy Note9 [3.3.1][F2FS][LZMA][UNOFFICIAL]

Status
Not open for further replies.
Search This thread

tamim.aleter

New member
Mar 2, 2020
1
0
Note 9 sm-N960N android 10

Hello , please can someone help with Note 9 SM-N960N have official android 10 to install twrp and root it , i spend 2 days and unsuccessful , please steps with file links
and how i can install different ver like n960F for dualsim ....

Thanks
 

omnimj

Senior Member
Nov 30, 2014
95
15
Install aroma rom work for 3.3.1 r3.9 ?
(Ketan rom super stable devbase )

I'm on Note 9 exynos , firmware ROM: N960FXXS4DTA5.
I flashed twrp 3.3.1-r3.9, rooted with Magisk 20.3 and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip and for me everything is working fine.

The only thing that I noticed is when I uninstall the unnecessary system apks (I don't use Linkedin, Dictionary, Facebook App installer, Facebook services) the phone boot in download mode. Is that usual for Android 10?
 

Fishballs

Member
Apr 27, 2017
13
4
Samsung Galaxy S21 Ultra
Delay??

Sorry if it has already been replied to before
I used this TWRP Recovery to change my Phone's Filesystem to F2FS, and noticed that it isn't Booting up within a Certain amount of time (roughly 5 mins)
There is a Known Bug with Boot Delay? Boot Delay for the Recovery? or the System? How long is this Delay? Does F2FS even work for Note 9?
Am using the Beta build of Zeus Kernel for Android Q and the S5DTB6 Devbase
Am way too new to this
 
Last edited:

Synt4x.93

Senior Member
Nov 15, 2016
176
520
Sorry if it has already been replied to before
I used this TWRP Recovery to change my Phone's Filesystem to F2FS, and noticed that it isn't Booting up within a Certain amount of time (roughly 5 mins)
There is a Known Bug with Boot Delay? Boot Delay for the Recovery? or the System? How long is this Delay? Does F2FS even work for Note 9?
Am using the Beta build of Zeus Kernel for Android Q and the S5DTB6 Devbase
Am way too new to this

I assumed you modified the stock vendor fstab for f2fs?
 

Synt4x.93

Senior Member
Nov 15, 2016
176
520
No clue what that is but i think i figured it out after a little bit of reading the kernel
Ty for the input

if you didnt, obviously it wont boot.
stock fstab mounts data as ext4 only, before Q the fstab was in ramdisk (in the kernel) now it is in vendor/etc
very simple you just need to add 1 line for each partition you want f2fs instead of ext4.

edit-
saw you update your post, just go to vendor/etc with rootexplorer and edit fstab and add the needed f2fs lines.
 

Fishballs

Member
Apr 27, 2017
13
4
Samsung Galaxy S21 Ultra
if you didnt, obviously it wont boot.
stock fstab mounts data as ext4 only, before Q the fstab was in ramdisk (in the kernel) now it is in vendor/etc
very simple you just need to add 1 line for each partition you want f2fs instead of ext4.

edit-
saw you update your post, just go to vendor/etc with rootexplorer and edit fstab and add the needed f2fs lines.

:confused: What are f2fs lines? I can do this using any Rom after adding the lines?
 

Detonatte

Senior Member
Jul 5, 2011
591
156
România
Use twrp-3.3.1-r3.9_q-crownlte.tar but why no mark System in Mount???
Try this:
wipe-advanced wipe select system - Repair or Change Files System - Change File System - Select F2FS - Swipe to Change
wipe-advanced wipe select system - Repair or Change Files System - Change File System - Select EXT4 - Swipe to Change
After restart my phone enter in bootlop :(
 
Last edited:

3arthur6

Senior Member
Sep 15, 2011
545
989
Samsung Galaxy S20
Use twrp-3.3.1-r3.9_q-crownlte.tar but why no mark System in Mount???
Try this:
wipe-advanced wipe select system - Repair or Change Files System - Change File System - Select F2FS - Swipe to Change
wipe-advanced wipe select system - Repair or Change Files System - Change File System - Select EXT4 - Swipe to Change
After restart my phone enter in bootlop :(

Not sure to understand..
Changing file system will format the partition, so if you just restart after that yes you can not boot.

Follow f2fs conversion guide.
No need to go to f2fs for system partition, benefits of f2fs come from better write operations and system partition is read only. Data and cache is enough.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    TWRP
    aka Team Win Recovery Project

    gsmarena_001.jpg



    First of all :
    • FOR EXYNOS ONLY
    • By flashing custom binaries, such as twrp, you will trip knox, loose your warranty and all Samsung Knox features FOREVER.
    • Firmware-Over-The-Air will no long works with custom binaries.
    • You have to enable "OEM Unlock" from developers settings.
    • Don't flash it if you don't understand the previous points.


    • Download links :

    • Changelogs : Post 2

    • Guide : @geiti94's guide

    • Device tree : android_device_samsung_crownlte

    • Kernel source : android_kernel_samsung_crownlte

    • Known bugs :
    • No data decryption
    • Boot delay with f2fs

    • Credits :

    Informations
    Status : Stable
    Created : 2019-05-13
    Last edited : 2019-05-08
    20
    Changelogs :

    • Betas

    Beta1 :
    • Removed unused and space hungry System Image backup option
    • Vendor is no more backed up as disk image, save more space in back up
    • Tried to get better read/write external sdcard speeds
    • Improved MTP compatibility (USB connection), closer to aosp

    Beta2 :
    • Backups from previous TWRP versions are now fully supported
    • F2FS support
    • Reduced image size
    • Possibly better i/o speeds
    • Others minors improvements

    Beta3 :
    • Fixed backups restoration issue (reverted back from 9 to 8.1 build platform for now)
    • Switched to LZMA compression (about 33% smaller)
    • Disabled twrp app install prompt (sorry for their authors but this is very annoying)
    • Other minors improvements

    Beta4 :
    • Fixed FAT32 support
    • Add NTFS support
    • Add lot of partitions to backup/restore/wipe
    • Experimental : Started to introduce an option to full backup data, including internal storage. The best way to switch between ext4 and f2fs. The checkbox is in the setting but it doesn't work for now.

    Beta5 :
    • Updated to TWRP 3.3.1-0
    • Builded on Pie platform (since backups restoration works perfectly now) which brings lot of improvements
    • Removed all modifications related to experimental full data backup
    • Possibly fixed F2FS boot lag

    • Old releases

    Release 1.1 :
    • Switched to ELS kernel, more up to date, this is the most significant part of this update
    • Synced with latest omni and twrp commits
    • Cleanedup device tree ( see sources above )
    • Implemented the LineageOS DTB image builder for more kernel compatibility (builder will understand)
    • Switched to gcc-9.1.1 toolchain for kernel compilation part
    • Deeply improved r/w speeds, at least in internal memory, globally +25% in average. It can reach 90MB/s during a backup saved in internal storage. ( Tests showed pics at 190MB/s in optimal condition :good: )
    • Fixed F2FS twrp boot delay -> Seems to be related to cache partition with F2FS
    • Doubtless more things I forgot and will add later
    • r1.1 : Prevention for some graphical issues

    Release 2 :
    • Less or not at all glitches
    • 95% of zip issues solved ( you can now flash devbase or all the others roms :highfive: )

    Release 2.1 :
    • TWRP source and ELS kernel source updated
    • Gcc kernel cross-compiler updated
    • Minors kernel improvements
    • Others minors improvements

    Release 3 :
    • Finally fixed all zip issue (Thanks to yarpiin for the help)
    • TWRP source updated
    • Switched to jesec kernel
    • Switched to cfq i/o scheduler
    • Minors improvements
    • Edit: Big omission to mention, based on omni 8.1

    Release 3.1 :
    • Finally fully working omni 9 twrp

    Release 3.2 :
    • Switch to stock samsung kernel source (latest CSI3)
    • Deeply reduced size by removing sound, ethernet, tcpip and lot of other useless drivers and stuff for twrp (Around 7MB less)
    • Update to gcc 10 cross-compiler for kernel part
    • Fixed toybox which now replaces and updates busybox
    • Changed MTP device name (Windows users will have to uninstall the phone from device manager then unplug/plug to see effects)
    • Other minor improvements

    Release 3.3 :
    • Fixed unzip fail with some zips by replacing it with precompiled UnZip/InfoZip 6.0
    • Fixed flashing .img on odm partition

    Release 3.4 :
    • Definitively fixed flashing .img on odm partition
    • Removed unusable encrypted backup option
    • Add an option to prevent samsung account and lockscreen loop issue in the zip install page - I strongly advise to check the box when flashing a kernel

    Release 3.5 :
    • Add a workaround for the (too) common busybox calls
    • Add the secured kernel flash checkbox for image flash

    Release 3.6 :
    • Synced to last sources
    • Switch to busybox which should fix most of zip flash issues
    • Fix screenshots color
    • Move secured kernel flash checkbox in settings

    Release 3.7_q :
    • Add support for system as root introduced in One UI 2 beta - Don't use it with android Pie
    • For devs : in line with twrp, system partition mount point as moved to /system_root and android system folder is symlinked at /system, some changes are needed to keep compatibility

    Release 3.8_q :
    • Synced to last source
    • Updated kernel to DTA1 source
    • Finally support almost all roms & zips
    • Fixed dmesg

    Release 3.9_q :
    • Synced to DTA5 kernel source with latest linux stable upstream (4.9.214)
    • Clang compiled kernel
    • Reworked system mounting, it should be more rom compliant

    Release 4.0_q :
    • Synced to DTCA and 4.9.218 kernel source
    • Fixed lockscreen/samsung account issue patch

    [/LIST]
    Release 4.0.1_q :
    • Fixed not clang compiled kernel in r4.0

    • Last release

    Release 4.1 :
    • Removed my hardcoded force system as root mount stuff (All AOSP 10 based and some OneUI roms (as DevBase) have now merged proper SAR support)
    • Merged some SAR related commits which unified Q and Pie support
    • Synced to last kernel and recovery sources
    • Fixed unencryptable data partition after format


    10
    @bober10113 @Arteush
    You guys, chill out. We are a community to work together for our phone. Just get over it and lets have a working recovery
    We are not a lot of guys working on this phone, we dont need to lose anyone. So lets work together for a better note 9.
    Shake your hands and lets move on
    6
    New release for One UI 2 beta support :)
    5
    glad you came clean about this issue. would have saved us alot of head aches if you'd had simply reported it from the get go....

    anyways, good riddance. I'm not going to use or test this anymore. especially when i report issues and put efforts to shine light on problems that apparently are "known" but kept away from the users. what good does that do?

    do you know the term: transparency?

    Stop making a fool of yourself. It becomes embarrassing.