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

Status
Not open for further replies.
Search This thread

Montero7o

Senior Member
May 11, 2017
79
13
65
Good evening @ghembuls

Thank you for your answer
Actually I did not understand that you indicated the twrp-3.3.1-r3.6-crownlte.tar.

Certainly Android 10 uses the new "SAR" structure, but not on older phones released with Android PIE or OREO.
In the Android 10 ROMs of Note 9 There are always the "Boot", "System" and "Recovery" files, which is not the case with the Android 10 "SAR" ROM as on my One + 7T pro with the system A/B partition.
It is the variable "BOARD_BUILD_SYSTEM_ROOT_IMAGE" (= True for Note9) which indicates which system is active "A B devices" or "No A B devices"

That's why I try to keep the "Recovery Custom" in order to keep the functionality of Backup and Restore.
I do not use Magisk to create the AP_magisk_patched file, because the "Recovery.img" disappears and is included in the "Boot.img".

On my One 9, I will therefore install with Odin the latest ROM "N960FXXS4DTA1", then with Odin I will install the twrp-3.3.1-r3.6-crownlte.tar, then from TWRP I will install "Disable_Dm- Verity_ForceEncrypt_02.02.2020" then "magisk-canary"

I would see if I can mount the partitions this way. with TWRP "twrp-3.2.3-0-crownlte" it did not work.
Thank you again for your response and I wish you a good evening.
 
Oct 21, 2015
21
3
so what i understand:
1. did you installed magisk on stock Android 10 with twrp 3.3.1 r 3.6 for PIE?

2. After installing Magisk , and check if Magisk is installed in Android, rebooting in TWRP - the data partition is mounted? or shows 0MB and cannot be accesed?

i need the solution for a TWRP to acces / mount Data partition after wiping and installing Magisk, anytime after using the phone - note 9
Edit: i see when installing Magisk - in log it says that note 9 is System-As-Root. Magisk sayis this

thank you
 
Last edited:

Montero7o

Senior Member
May 11, 2017
79
13
65
Good morning all,

The objective of this method is to have an Android 10, with Root with TWRP operational for backups and restoration of all partitions.
I spent many days (nights) researching XDA to develop this procedure and find out how Android Q blocked the mounting of partitions from the start after the installation of the ROM.
I tested on my 2 Galaxy Note 9 SM-N960F

REQUIREMENTS:
Have a Note 9 SM-N960F
Andoid Q stock ROM: N960FXXS4DTA1-XEF (or the next ROMs)
Odin3 v3.14.1
TWRP for Android 10: twrp-3.3.1-r3.7-Q-crownlte.tar
Magisk: magisk-canary - Copy to ExtSDCard
Dm-Verity & ForceEncrypt Disabler v02.02.2020 - Copy to ExtSDCard
Have a "BootLoader" already unlocked.

Very important the order of pressing the keys: If it is noted "Power" + "Bixby" + "High Volume", do not do "Bixby + Power + High Volume", respect the order of the keys.

STEP 1: On your Andoid PIE or Q, Activate the developer mode
-Activated = ON
-OEM unlocking = ON
-Auto system update = OFF
- USB debugging = ON
-Check apps via USB = OFF
-Verif bytecode debuggable apps = OFF (only available on Android 10)
- Default USB connection = File transfer / Android Auto (Android Auto is only present in Android 10)

Turn off Note 9, "Power" button

STEP 2: Flash the stock ROM
1-Restart in Download mode
-Hold the Note 9 in the palm of one hand and with the thumb press the "Bixby" button and keep it pressed,
-With the other hand, plug the USB cable into the phone,
-Then press the "Volume Down" button with your free hand.
-As soon as the first screen is displayed, release the buttons, then confirm with the "High Volume" button

Now open Odin on your PC in Admin mode,
-Important: check "Auto Reboot" and "F.Reset Time" in the Odin options and nothing else.
-Select your AP, BL, CP and CSC_xxxx firmware files (do not put HOME_CSC), then click on "Start"
You got the "PASS!" in Odin, the Note 9 will restart and you will see a blue screen indicating that your device is updating for 2 to 5 seconds, then the Note 9 will restart again.

Very important: As soon as the screen turns off for a second restart, you must press "Power" + "Bixby" + "Volume High" to force the boot on the Recovery stock.
This is very important because if it starts initializing, mounting partitions in TWRP will be impossible and you can start again from point 1.

-Use the volume buttons to navigate the Recovery stock menu and the power button to select an option.
- Choose the "Power Off" option and remove your USB Type-C cable from the Note 9.

STEP 3: Flash TWRP

1-Restart in Download mode
-Hold the Note 9 in the palm of one hand and with the thumb press the "Bixby" button and keep it pressed,
-With the other hand, connect the usb cable to the Note 9,
-Press the "Volume Down" button with your free hand.
-As soon as the first screen is displayed, release the buttons, then confirm with the "High Volume" button

2-Now open Odin on your PC in Admin mode,
-Important: Uncheck "Auto Reboot" and leave checked "F.Reset Time" in the Odin options and nothing else.
-Select in TW the file TWRP (twrp-3.3.1-r3.7-Q-crownlte.tar) then click on "Start"
-You got the "PASS!" in Odin, remove the USB Type-C cable from the Note 9.

3-The next step is very important, you must force the Note 9 to stop, then restart in Recovery mode
Press "Power" + "Volume Down" for 7 seconds to exit the download mode.
As soon as the screen turns off, immediately press the "Power" + "Bixby" + "Volume Up" keys to start Recovery, as soon as the screen turns on release all the buttons.
After a first boot, if the screen turns off and then restarts, immediately press the "Power" + "Bixby" + "Volume High" keys,
You must have the TWRP screen, if this is not the case, initialization has started, you must repeat all the procedure in point 1 because the TWRP fash will not be operational for the rest.

STEP 4: Root of Note 9
-In TWRP, you must swipe to authorize the modification
-Now format your data, Press "Wipe", then "Format Data", then on the confirmation screen type "yes" to continue.

(Very important, If there are red lines during the format, there is a decryption error, then go back and reboot Recovery
Format your data again, Press "Wipe", then "Format Data", then on the confirmation screen type "yes" to continue.)

- Back button for the first screen, then press "reboot" then "Recovery"
-Now you need to Install Magisk Canary in TWRP,
-Click on "Install" and select "Magisk Canary.zip" located on the ExtSDCard then validate the flash.
-You must have the message "Done"
-Return back, then Install then "Dm-Verity & ForceEncrypt Disabler v02.02.2020" located also on the ExtSDCard.
-You must have a message "Done", then an error line "Failed to mont '/ odm" then done, ignore it.

Click "Reboot sytem" to start your system.

Configure all the settings, install your applications and test the full functionality

Important: If you are switching from Android PIE to Android Q, it is preferable not to authorize the restoration from Google or Samsung, but to redo the installation of the applications from the Google Store or from your APKs.

STEP 5: Backing up the partitions
-Turn off Note 9 with the "Power" beam
-Press the keys "Power" + "Bixby" + "Volume High" to start in TWRP
-You should no longer have the "swipe to authorize the modification" screen, if this is the case then authorize the modification again
-Select "Backup", then activate all partitions.
-Select ExtSDCard or OTG as destination
-Set "Today's date + INIT-Android 10" as the backup name, then zip to start the backup.

(Very important, there must be no error otherwise the partition (s) are locked by Android 10 and restoration will be impossible)

-If the backup is OK, click the restart button.

STEP 6: Test the Restoration of the partitions
-Turn off Note 9 with the "Power" beam
-Press the keys "Power" + "Bixby" + "Volume High" to start in TWRP
-Click on "Restoration"
-Select the previous backup then zip to start the Restoration.

(Very important, there must be no error otherwise the partition (s) are locked by Android 10 and recovery is impossible, TWRP is badly initialized and locked by Android)

-If the Restore is OK, click the restart button.

It's over.

Thanks to Zackptg5, topjohnwu and jcadduono for the "Dm-Verity & ForceEncrypt Disabler v02.02.2020"
Thanks to Geiti94 for the twrp-3.3.1-r3.7-Q-crownlte.

Good reading
 
  • Like
Reactions: nalakadll
Oct 21, 2015
21
3
Thank you for the procedure
I have 3 questions

1. The magisk canary is the same as the latest magisk 20.3?
2. After rooting and working in Android 10, and rebooting back to twrp, the data partition is mounted and accessiblle?
3. Where do we get the dm verty 02.02.2020 patch or canary?

Maybe it will be great to post them on the first page of this thread.

Thank you
 

Montero7o

Senior Member
May 11, 2017
79
13
65
Thank you for the procedure
I have 3 questions

1. The magisk canary is the same as the latest magisk 20.3?
2. After rooting and working in Android 10, and rebooting back to twrp, the data partition is mounted and accessiblle?
3. Where do we get the dm verty 02.02.2020 patch or canary?

Maybe it will be great to post them on the first page of this thread.

Thank you

Hello
The files are here:
TWRP : https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note-9-t3929901
Dm-Verity & ForceEncrypt Disabler v02.02.2020 : https://forum.xda-developers.com/galaxy-note-9/how-to/guide-root-note-9-magisk-android-10-q-t4039783
Magisk Canary : https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
 
Oct 21, 2015
21
3

Hello,
i rooted Android 10, it worked with TWRP 3.3.1 for Android 10, Magisk Canary and Verity Disabler.
Confirming the steps in the procedure.
Twrp has access to the data partition, is decrypted and monted. Confirming
 
Last edited:

Montero7o

Senior Member
May 11, 2017
79
13
65
Hello,
i rooted Android 10, it worked with TWRP 3.3.1 for Android 10, Magisk Canary and Verity Disabler.
Confirming the steps in the procedure.
Twrp has access to the data partition, is decrypted and monted. Confirming

Hello @ staicueduard @ gmail.com

Thank you for the feedback
The procedure may seem long, because it is very detailed so as not to miss certain operations.
I hope the French / English translation is good because I am very bad at English.
cordially
 
Oct 21, 2015
21
3
Hello @ staicueduard @ gmail.com

Thank you for the feedback
The procedure may seem long, because it is very detailed so as not to miss certain operations.
I hope the French / English translation is good because I am very bad at English.
cordially

After the first time it i easy.
Now we need to figure it out how to make smart view work again
In oreo and pie there was a code line to add in build.prop but now this line does not seem to work as the smart view cannot connect to any tv.

Do we have some new info?

EDIT: I was wrong. Smart view works with the old line code.
Everything is ok
 
Last edited:

Montero7o

Senior Member
May 11, 2017
79
13
65
After the first time it i easy.
Now we need to figure it out how to make smart view work again
In oreo and pie there was a code line to add in build.prop but now this line does not seem to work as the smart view cannot connect to any tv.

Do we have some new info?

Smart View works perfectly on the Note 9, Android 10, Root + TWRP without any modification, no need to put in build.prop "wlan.wfd.hdcp = disable"

https://dl.xda-cdn.com/4/9/4/5/5/4/9/IMG_1.jpg?key=A2UfzgefBsDDAKhOv0aIkw&ts=1581153242
IMG_1.jpg
 

Detonatte

Senior Member
  • Jul 5, 2011
    526
    138
    România
    TWRP-3.3.1-r3.7-q-crownlte.tar for Q contain:
    - System
    - Data (excl. storage)
    - Cache
    - DQMDBG Image
    - Boot
    - Recovery
    - CPDEB (MODEM_DEBUG)
    - Baseband (MODEM)
    - EFS
    - Vendor
    - ODM

    For restore complete (no bugs), what do i need to choose from the list??? I need to choose everything from the list or only some things from the list? Did anyone test it???

    Trimis de pe al meu SM-N960F folosind Tapatalk
     
    Last edited:
    Oct 21, 2015
    21
    3
    Hello again everyone.

    i am just presenting why I need root for a phone:
    1. first of all is the backup - partition backup

    2. access to all files and not read only - so with TWRP 3.3.1 for Android 10 and Magisk Canary, here on Note 9, the system partition is accessilbe and is writable. is NOT read only - hurrraaaayyy.
    So you can edit for example build.prop. etc etc etc, remove system apps that you don't need etc. without brick-ing the phone.

    3. I need root for modifying audio driver - so now i manage to install Viper4Android on Android 10 with no problems and now the audio is way better that that Dolby stock thing.

    4. and the final think to have root is to have the camera app/driver modified. On Android Pie there was the Zero Mod Camera mod, which you can modify the jpg compression, and the bitrates for all video resolutions, both for h264 and hevc codecs. BUT for the moment for Android 10 this mod is not available - YET I HOPE.

    so in conclusion - for Note 9, the last official Android will be 10 . And i think on this platform wich is NOT SYSTEM-AS-ROOT as the latest Samsung Phones , Note 9 will remain the best accessible phone to root and to have access to everything in it.
    so in this moment Note 9 is the best solution in terms of root and stuff , better then Note 10 and others
    @Detonatte P.S: I am from Romania to :)
     
    Last edited:
    Status
    Not open for further replies.

    Top Liked Posts

    • There are no posts matching your filters.
    • 31
      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.