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

Status
Not open for further replies.
Search This thread

omnimj

Senior Member
Nov 30, 2014
95
15
Hello @omnimj
You will never be able to install the TWRP, once you have started Android 10, it will permanently lock the mounting of partitions by TWRP from the start of initialization.

I advise you to read and understand my tutorial which was duplicated at post # 341
If you don't understand what you need to do, you will never get there.
I can not help if you do not follow this tutorial and respect the "IMPORTANT" phases mentioned.
cordially

Hello @montero70, thank you for your quick reply.
I've already passed through the procedure that you described in the post # 324 from 06 February 2020.
Unfortunately I didn't manage to get TWRP that works well. I got boot-loop, missing partitions, I couldn't restore, my phone stocked several times etc.
I have also tried other suggested procedures, but no positive result.
I realized that in this stage is not possible to get TWRP properly working with the available tools and decided to root my N9 following the tread [Guide] Root Note 9 (Exynos) Android 10 (Q) With/Out Custom Recovery posted by Zer0De8th, Junior Member on 24th January 2020.
So I got into the current situation of having a rooted N9 on Q, which works fine. But, I'm still missing TWRP and I wouldn't give up.
I will listen to your suggestion and try again instructions that you gave at # 341 post. I saw the twrp-3.3.1-r3.8-Q-crownlte has been published in a mean time. Shall I try it instead the twrp-3.3.1-r3.7-Q-crownlte that you suggested in #341?

---------- Post added at 01:46 PM ---------- Previous post was at 01:40 PM ----------

Why are you messing up by doing all steps that even doesn't requires for N9 which is not true SAR like s10/N10
Here very simple steps to get twrp and root on Note9 with Android 10
- Flash stock Q
- oem bootloader unlock
- flash twrp - reboot to twrp - flash latest stable magisk
- reboot twrp
- flash dm - verity disable force encrypt (link below)
- reboot twrp - format data (that you need to confirm by typing 'yes'
Reboot to system and done!

Here already I have explained on how to root thread
https://forum.xda-developers.com/showpost.php?p=81754803&postcount=588

Hello dr.ketan. Thank you for the reply.
As I have already described to Montero70 how I came into this situation and I wouldn't repeat myself.
I'll try yours and his procedure and I guess one will manage to get TWRP that works fine.
All the best.
 

dr.ketan

Recognized Developer / Recognized Contributor
Hello dr.ketan. Thank you for the reply.
As I have already described to Montero70 how I came into this situation and I wouldn't repeat myself.
I'll try yours and his procedure and I guess one will manage to get TWRP that works fine.
All the best.
I have read it, but you need to understand. With Android Q N9 is converter to SAR but yet it is far different from SAR with those devices, which born as SAR
So situation is zip (may be it ROM, some modes or scripts) you are flashing should be compatible with twtp you are using.
There are two twrp there one based on Q base and another older one (by gieti which made on Pie based)
All recoveries are stable but you needs to use which developer of zip recommends. For example my rom script based on old recovery (when I have released my first Q rom which was based on Q beta, that time there was no Q based twrp was available) so I recommended it. But if any rom have script based on sar, you needs to use newer twrp
Now regarding, backup and restore, you should know that since SAR, if you restore any backup that you made in form of non image like system, vendor etc, will break rootfs and device will bootloop. Don't blame rom or twtp for this, it's Google, who made this.
So, if you make backup with img format like system.img vendor.img on Android Q and restore it, it should work as it should, weather you use old or new twrp, it doesn't matter..
Another thing, what should you backup?
Normally we does modify, system, vendor, data, csc and boot and these are the components mostly any custom rom contains. If you backup those files, hardly you get any trouble.
Hope this helps
 
  • Like
Reactions: Techvir

omnimj

Senior Member
Nov 30, 2014
95
15
I have read it, but you need to understand. With Android Q N9 is converter to SAR but yet it is far different from SAR with those devices, which born as SAR
So situation is zip (may be it ROM, some modes or scripts) you are flashing should be compatible with twtp you are using.
There are two twrp there one based on Q base and another older one (by gieti which made on Pie based)
All recoveries are stable but you needs to use which developer of zip recommends. For example my rom script based on old recovery (when I have released my first Q rom which was based on Q beta, that time there was no Q based twrp was available) so I recommended it. But if any rom have script based on sar, you needs to use newer twrp
Now regarding, backup and restore, you should know that since SAR, if you restore any backup that you made in form of non image like system, vendor etc, will break rootfs and device will bootloop. Don't blame rom or twtp for this, it's Google, who made this.
So, if you make backup with img format like system.img vendor.img on Android Q and restore it, it should work as it should, weather you use old or new twrp, it doesn't matter..
Another thing, what should you backup?
Normally we does modify, system, vendor, data, csc and boot and these are the components mostly any custom rom contains. If you backup those files, hardly you get any trouble.
Hope this helps
Thank you for the additional explanation.
Since I'm not the expert in those things, I would like to ask you for some clarifications. Maybe it will sound stupid from your point of view and sorry for that.
First of all, what is SAR?
Second - the older twrp based on Pie you are mentioning is twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5 or similar?
- the two based on Q beta are twrp-3.3.1-r3.7-q-crownlte and twrp-3.3.1-r3.8-q-crownlte?
- for the custom Q rom N960FXXU4DSLA (21 January 2020) I should use the last twrp that I mentioned above?
Third, the magisk that I should use is magisk canary or magisk stable 20.3?
And the fourth, the explanation regarding the format of system, vendor etc. is the most important for me, since the previous questions are more/less clear and I just need the confirmation - are the components like system, vendor, data, csc and boot regularly in the .img format and not in any other format that may break root and cause bootloop and other unwanted behavior of the phone?
 

dr.ketan

Recognized Developer / Recognized Contributor
Thank you for the additional explanation.
Since I'm not the expert in those things, I would like to ask you for some clarifications. Maybe it will sound stupid from your point of view and sorry for that.
First of all, what is SAR?
Second - the older twrp based on Pie you are mentioning is twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5 or similar?
- the two based on Q beta are twrp-3.3.1-r3.7-q-crownlte and twrp-3.3.1-r3.8-q-crownlte?
- for the custom Q rom N960FXXU4DSLA (21 January 2020) I should use the last twrp that I mentioned above?
Third, the magisk that I should use is magisk canary or magisk stable 20.3?
And the fourth, the explanation regarding the format of system, vendor etc. is the most important for me, since the previous questions are more/less clear and I just need the confirmation - are the components like system, vendor, data, csc and boot regularly in the .img format and not in any other format that may break root and cause bootloop and other unwanted behavior of the phone?
1.System as root, implemented on N9 since Q
2.yes, any of three should work but myself yet not get chance to use newer and only tested 3.2.3 Pie based
3. I Always using latest stable 20.3
4.if you have made backup as system/vendor instead of system.img or vendor.img and you restore such non img backup, it will cause bootloop. Device doesn't boot so no question of additional behaviour
 

omnimj

Senior Member
Nov 30, 2014
95
15
1.System as root, implemented on N9 since Q
2.yes, any of three should work but myself yet not get chance to use newer and only tested 3.2.3 Pie based
3. I Always using latest stable 20.3
4.if you have made backup as system/vendor instead of system.img or vendor.img and you restore such non img backup, it will cause bootloop. Device doesn't boot so no question of additional behaviour
Thanks for the clarifications.
Regarding 4. how can i be sure i will make a backup as system.img or as vendor.img and not as non-img backup? What components such are system, vendor, data, csc, boot etc. should i check when i do backup or restore?
 

3arthur6

Senior Member
Sep 15, 2011
545
989
Samsung Galaxy S20
4.if you have made backup as system/vendor instead of system.img or vendor.img and you restore such non img backup, it will cause bootloop. Device doesn't boot so no question of additional behaviour

Using this twrp, don't care about .img or not, restore doesn't cause bootloop.
Not sure but I think it's related to twrp not builded with sar config flag, as geiti94 one.

Thanks for the clarifications.
Regarding 4. how can i be sure i will make a backup as system.img or as vendor.img and not as non-img backup? What components such are system, vendor, data, csc, boot etc. should i check when i do backup or restore?

So don't care about .img backup, check all partitions when you do a backup if unsure.
Regarding your trouble to flash twrp, you probably missed a step somewhere.
After odin twrp flash and before rebooting to system, format data partition, flash magisk, DM-verity and forceencrypt disabler and you should be good.
 
  • Like
Reactions: dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Using this twrp, don't care about .img or not, restore doesn't cause bootloop.
Not sure but I think it's related to twrp not builded with sar config flag, as geiti94 one.
.
Sorry I haven't yet tried this one so might missed that. This happens to all available N10 twrp because it breaks rootfs.
 

omnimj

Senior Member
Nov 30, 2014
95
15
Using this twrp, don't care about .img or not, restore doesn't cause bootloop.
Not sure but I think it's related to twrp not builded with sar config flag, as geiti94 one.



So don't care about .img backup, check all partitions when you do a backup if unsure.
Regarding your trouble to flash twrp, you probably missed a step somewhere.
After odin twrp flash and before rebooting to system, format data partition, flash magisk, DM-verity and forceencrypt disabler and you should be good.
Than you for the very useful explanations.
What would happen in my situation when I have rooted N9 Q and I use Flashify.apk to flash Recovery image? Maybe is this a shorter way to get TWRP rather to go again from the beginning with Odin?
 

3arthur6

Senior Member
Sep 15, 2011
545
989
Samsung Galaxy S20
Than you for the very useful explanations.
What would happen in my situation when I have rooted N9 Q and I use Flashify.apk to flash Recovery image? Maybe is this a shorter way to get TWRP rather to go again from the beginning with Odin?

Not to go to the beginning, just flash twrp thought odin.
Make some search dude, there is a lot of guide about how to install twrp.
 

omnimj

Senior Member
Nov 30, 2014
95
15
Not to go to the beginning, just flash twrp thought odin.
Make some search dude, there is a lot of guide about how to install twrp.
Maybe you missed my first post, but I already have rooted my N9Q using magisk patching method. Is it safe and possible now just to flash the twrp throught Odin?
 

omnimj

Senior Member
Nov 30, 2014
95
15
Yes it's safe.
But follow step by step a dedicated guide, and be sure to understand a bit what you are doing and what you have to do.
Ok if it is safe to flash twrp, bu what about Disable_Dm-Verity_ForceEncrypt_01.19.2020.zip? Should I flash it through the twrp once I flash the twrp via Odin?
 

zadox

Senior Member
Oct 1, 2010
105
31
Starting from @dr.ketan 's beta Q version it was never easy for me to upgrade to Q/Q04 (I was with @3arthur6 's TWRP). Took me days, followed guides and advice and I am now back at zero, which is a progress considering that I was at minus (being with a bootlooping system/non-system-mounting TWRP smartphone). I don't even remember now how on earth I managed to return to the previous, working state (Dr.Ketan's Q03) - downloading stock ROMs at 15KB/s from greedy sites didn't help things anyway. I think I am going to stay here (Q03) for a while, I don't have too much free time right now.
 

omnimj

Senior Member
Nov 30, 2014
95
15
Hello @3arthur6
Thank for the new version of Twrp (v9) for Android 10
Good job
Hello Montero70, related to my posts #361- 365 do you have any idea what to do with Disable_Dm-Verity_ForceEncrypt_01.19.2020.zip in my case? Should I flash it through the twrp once I flash the twrp via Odin? What to do with Magisk since the phone has been already rooted before flashing twrp?
 

Detonatte

Senior Member
Jul 5, 2011
591
156
România
3arthur6 with version r7 twrp backup and restore work perfect in Android 10. With r8 fail. With r9 work? Tested?

Trimis de pe al meu SM-N960F folosind Tapatalk
 
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.