yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
well since the note 8 ive been using 256gb sd cards with extfat and no problems.

fat32 and cards over 128 gig dosent work well
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
With Beta4 you have now NTFS and FAT32 full support ;)
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Ahaha seriously?! I think you did not understand his question. Or you are the troll?:confused:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] zencooler:
It's really great TWRP!

My backup size now is reduced from 18GB to 12GB.

Well done job! Thanks!
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] karapoutsoglou:
yes i already installed. you are amazing
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] DEVILOPS 007:
Come on don't tell people to use anything other than ext4 or f2fs lol
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
So you don't reread or don't understand his question?:confused: ( Or troll again?:silly: )

We talked about a microSD dude!
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] DEVILOPS 007:
Sorry I'm just joking around. Thought that was obvious so my bad?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] tycoon78[stoner]:
Mate the beta 4 still has the start up bug. It get stuck at the twrp screen for 8 secs. Hoping u can fix the issue. Thanks for ur hard work n time ????
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] azZA_09:
I think it is related to mtp service. The twrp boots when you hear the sound of fiding your phone on pc. However, idk if it is a really problem to wait a little
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] LostElf:
No worries Arteush, you're always simply outstanding! Thank you very much once again! ^_^
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] AoiSeaghdha:
I don't see a response to the decryption bug later in the thread (fsync appears to have been reenabled in the latest commit to the tree, so I assume that'll be in the next r2.1); does the r2 build fix this? geiti94's build can't decrypt in recovery, so I was considering flashing this upgrade if it was fixed. Skimming the Internet I'm aware this is apparently a widespread TWRP issue, so I'm not sure how big a bug it is.

Also another post already seemed to confirm it, but does this work both for the N960F and the G960F? Thread title and TWRP file say Note9/crownlte but the title also specifies G960F, which is the Galaxy S9. Just a typo?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Abaddon:
hi will this work on N960N (korean variant)? thank you
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] AoiSeaghdha:
Assuming the G in the thread title is a typo, then yes. It should work for the N960F, the N960DS, and the N960N.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
New update

All our issues seems to be finally fixed :svetius:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] TurricanM3:
You are the best. Thanks a lot.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
nope.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Icetea:
Do you have more informations about existing issues for us? :confused:

Not everybody is fully involved.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
i posted all about this back in april or may.

read all about it if you want. parts of scripts fail silently. i use a csc flashing zip and after system cannot see which csc im on after flashing it on this twrp(regular twrp works fine). files are there but something is screwed up. either its an odm partition issue or a permissions issue but all that is know is that there are no errors in the logs. again I've reported it in the past so not going to reiterate over and over what was already said.

im just reporting that this is still not fixed.

regards,
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Icetea:
to write "the same mistakes as before" would have been enough. No one has requested a detailed description!;)

Thanks anyway! After your message, i have been returned to v r2.1
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
My crap, sorry. The one I uploaded has issue yep.

The fresh link is ok. Download again.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] AoiSeaghdha:
Does this mean that the r3 update has AOSP decryption, fsync enabled, and also fixes the MTP/ADB freezing issue mentioned two pages back?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] freeza:
R3 freezes at TWRP splash screen for me

EDIT: never mind. it just took a long time to boot.

EDIT2: adb works fine.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Yes for the last two but no data decryption, hard job with samsung. Actually I just don't have the knowledge :laugh:

:svetius: Curious to know how long? Are you using f2fs?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] freeza:
About a minute and yes f2fs with no encryption :)
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
yup all good now.

thank you!

edit:

on a n960n i dont have any lag b4 entering twrp

i did flash recovery with Odin and not img withing twrp. i also deleted TWRP folder from intl. storage to be sure to start fresh.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] azZA_09:
Everything works as it should.

You have the green light to flash any ROM !!!
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] AoiSeaghdha:
Damn, that's a letdown. Still, I was expecting as much, considering it's such a widespread issue. According to the FAQ on their website, it's definitely seems to be the type of issue where we'll have to wait for them to work out the kinks upstream.

[MENTION=7861769]Synt4x.93[/MENTION] looks like we're going to have to wait until mainline 3.3.2, however long that may take. Still, an upgrade is better than no upgrade, so I suppose there's no reason not to flash this through Odin.

[MENTION=4259991]Arteush[/MENTION] I'd recommend pointing it out in the "Known Bugs" section and putting (Upstream Issue) or some such alongside it. Bonus points if you explain somewhere that TWRP works fine until you encrypt your phone, so people can simply flash what they need/want to beforehand and then either encrypt their phone, or opt to not encrypt.

Or just link to this post.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Humm.. Too long.. I can't find how to fix this issue.

One thing I heard, letting cache on ext4 could bypass that.

Yep you are right I will had this :good:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
I didn't mention (this big stuff) that r3 was based on omni 8.1.

It's no longer the case with r3.1 which use omni 9 :)
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
FYI restoring a backup created under r3.1, causes ODM restore to fail:

extracttarfork() process ended with error 255

if i try to restore ODM from unofficial twrp 3.2.3.0 is also fails. so it is not an issue with the archive but the process that restores it.

edit:

uppon restoring a full backup, skipping ODM there is clearly something wrong with the restored images. no more pairing on galaxy watch, phone is slow and unresponsive something is really screwed up.(using stock settings in twrp, no f2fs)

going to restore same backup under regular 3.2.3.0 twrp and report back.

edit2:

so no go.seems the backup taken on r3.1 was no good on top of the different ODM issue. i restored it on 3.2.3.0 and still cant pair watch. seems like a weird issue and will try to replicate again. but i do not have the weird lags where i could barely type on the keyboard when restored in r.3.1

edit3

confirmed, fresh installed rom, paired watch. connected each time after reboot. made a full twrp backup on r3.1. and restored it(skiped ODM because of pending issue as described) and phone would no longer pair to watch after twrp restore.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Hum.. I haven't notice backup issue since a while, did you try a odm backup then restore with 3.2.3 twrp? Anyone else with same issue?

If you have a log it could help.

R3 and previous versions didn't apply the good selinux context to /odm/omc files(but it still worked idk why), so R3.1 is safer. I don't think so but it could be related.

About the watch, someone in the thread had same issue with old releases, again doesn't 3.2.3 twrp give same issue?

To finish, we didn't notice performance regression while doing a backup/restore, try a cache/dalvik wipe.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
as stated, for odm, r 3.1 cannot restore any odm backups. regardless of if it was created under 3.2.3 or current one.

also as stated before, for the watch, anything made under r 3.1 causes the issue. if i restore the backup made on r3.1 with 3.2.3, issue is still there.

these 2 issues of course were never there before. that's why i noticed them.

all tests were done by backing up amd then restoring right after. no reboots to home screen between or even hours or days. so wiping caches should not be needed if the backup were truly 1:1. ( again i can do these same tests and not have regression under 3.2.3)

but i didint think of grabbing logs because it can be so easily produced everytime. ive went back to full stock and re did each test 3 times. after the 3rd time i moved on. ambasadii released his v6 so since my old backups were trash now i put back good old twrp 3.2.3 and reinstalled everything.

maybe someone else can do the rest of the troubleshooting. i did my part for now.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
We just do some tests in two different devices, restore a 3.2.3 and a r3.1 backup with r3.1, the same with 3.2.3. No issues here.

Understand that your issue could be local.

A least not for Galaxy Watch which seems to be old.

If anyone else have these issues and accept to provide log, I will be able to investigate.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] karapoutsoglou:
enable usb debug first
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
New release :)

See changelog

Surely the last for twrp 3.3.1
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
so same old ODM restore issue. log attached.

flashed new twrp with odin, created a backuon on internal storage. rebooted back to recovery, tried to restore it, ODM failed. exact same scenario as last time.

Logs point to a file failing to extarct within ODM:

tar_extract_file(): failed to extract /odm//sipdb/es_us/general_nlm.bin !!!

file size is 4,946KB

if i use regular twrp it works fine.

next test will be to manually delete /odm//sipdb/es_us/general_nlm.bin file from device and retake a backup and try the restore again.. if an other file fails again then new twrp has a either a block size issue when restoring to ODM partition or some other problem.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
so as expected, ODM restored on the next file:

tar_extract_file(): failed to extract /odm//sipdb/es_us/general_nlm_voc_s.bin !!!
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
ok so i figured out the problem. for some unknown reason to me, your twrp resizes my odm partition. this is not something the standard twrp does.

in korean n960n phones, the odm partition is smaller than F. in it self this is not a problem. in fact as stated before, regular twrp backs up and restores this partition correctly without resizing it.

see 1st image of disk info tool, that picture was taken showing an ODM oartition restored under regular twrp. as you can see my odm total size is 143mb

now after restoring using your twrp my ODM partition has shrunk! it is now 129mb. see 2nd picture.

so the partition is backed up fully. but for some odd reason when it prepares the file system for the restore, its screws up either block size or partition size so now the partition is smaller. no wonder the backup dosent fit anymore even though it was just backed up successful using the original size!
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
I don't know your way to change of csc region but there is a problem. As your odm partition shouldn't be full.

So doubtless this cause your issue.

After talking with few note 9 owner no one else had this issue.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
I am not talking about the space used.( how i fill it up has no impact on the problem at hand, if i want i can use 1 % of the space or i can use 100% of it. i should be able to use all of it if i wish)

so i am talking about total capacity of the partition that changes once your version of twrp restores it. also, as demonstrated: old twrp does not have this issue. so clearly partition sizes changing is not a good thing.

apart from telling me I'm the problem, how can you explain your version reducing the size of the capacity of the partition?

i have a feeling this is going towards the same discussion we had months ago when i reported the other issues and i was not taken seriously.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
As there is no problem about that and this is surely related to twrp and omni updates, there is no reason to investigate.

And I just can't do more as your partition isn't standard, but I give you the direction to solve it.

Try with a stock odm, you will see that everything works as expected.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
i posted issue in 2 different gits, once in 3arthur6's git and the other in official twrp.

but i wont restore original odm since just using 3.2.3-0 works fine. ive also reduced the data size to 88/143MB and after 3.3.1r3.2 backup and restore i get 88/129MB.

just for fun, attached is a log of 3.2.3-0 that successfully restores odm with out data loss or any other fork extract issues. partition stays intact as well.

also upon comparing 3.2.3-0 logs with 3.3.1.r3.2, i notice weird illegal characters upon checking 3.3.1r3.2 log at the [RESTORE STARTED] log section. and also im wondering if its the make2fs that might be the issue as well. (module/function seems old 2016?)

could you make a 3.3.1r3.2 build without make2fs? that would really help determine where the issue is.( would be a shame that the issue wasint with original devicetree)

thanks
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
omg you r really the cancer

You see yourself that don't have a totally full partition, which sound normal, solve your issue.

But no, you never stop. And now you start to spamm my github with your bullshits.

You speak about things you don't understand. Toybox is part of the android pie platform, no reason to switch back. And understand that there are different ways to write files on a disk and to calculate sizes of them.

Make some comparisons if, as it seems, you have time to loose. 100% sure that files are identical before and after the restoration.

Now I will stop to waste my time for you.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Tchania:
Tried flashing devbase rom with 3-2 and it said it couldn't detect csc. Reverted to 3-1 and flashed fine.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
and it starts again. when i provide proof of an issue you ignore it.

but yeah you are right i really don't understand... you.

even if you have no idea why this is happening, it dosent mean its not happening and that it is user caused. even if your work is based on other's, and the issue that i am reporting is part of the other's work, dosent mean you can't acknowledge it and try to report it as well instead if compeltely trying to ignore it.

once again good riddance. was just reporting with more details in the spirit of having the issue seen and understood.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Thanks to point it out!

It seems the android unzip command is broken, and fails to decompress some zips (as DevBase and DrKetan roms). I will replace it by a precompiled one.

One more release needed :silly:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Tchania:
I may have no right to say this without logs, but I also couldn't restore a backup made with twrp 3.2.3-0.

I don't remember what I read (sorry maybe not that helpful here) but I think formating some partitions during the restore process failed.

I was in a rush I reverted to twrp 3.2.3-0 and successfully restored.

Oh and one more thing, I read in the changelog release 3.2, switch to stock samsung kernel source (latest CSI3).

Is this responsible for the lockscreen loop and samsung account issues?

I'm using tgp kernel but it patches the ramdisk to match firmware's version but after flashing the lastest trwp (release 3.2) I ran into lockscreen loop and Samsung account problems.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] sco00262:
Me too,after r3.2 i got samsung account problem again…
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Samsung account is related to your kernel. Your kernel security level have to match with your system security level. Not related to recovery.

Did you flash anything else after r3.2? It could be more related to the zip problem than something else.

About your restoration issue, you should be able to restore a 3.2.3 backup with this twrp and vice versa.

So without log, I can't help..

New r3.3 update fixes issues when flashing some zips.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] sco00262:
Ya,but with 3.2.3 and 3.3.1 r3.1,flashed between Zenus and Tgp kernel with no problem. Didn't flash anything but kernel and magisk.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Ok it makes sense. Since r3.2 had issue, just flashing kernel and magisk could have fail at some points (e.g. executing the script to fix the account issue).
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] karapoutsoglou:
Flash it with the option in Odin :not reboot enabled. when flashed successfully then reboot and enter immediately the recovery. reboot from download mode is bixby and power i think.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] karapoutsoglou:
Dear [MENTION=4259991]Arteush[/MENTION] i had a problem flashing Zeus latest kernel with your latest recovery. Didn't flash the script and had a problem with samsung account, pin etc. With the stable recovery 3.2,i had no problem. All that happened with latest TGP rom.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] TurricanM3:
Same for me. :(
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Icetea:
Alexndr rom and twrp r3.3

I have restored my full backup yesterday. Including vendor, system, data, oem, cache, efs partition. No problems after restarting my phone! So in my case, twrp work as expected so far. My backup was created with version r3.3.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Yep I talked about it to tgp and zeus kernel devs.

It will be solved with their next releases.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
While waiting updates, last ones which work with this twrp (and any others) :

PieZeusKernel-2.3.96.zip

TGPKernel.N96xx.v1.6.2.20191008.zip

Thanks to their devs for agreement
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Need more informations..

Where does it fail, which tools used to flash

Search in post #1 for the guide to install twrp
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
So yep you didn't read guides and skip important steps

Check this guide
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Make some searches in xda, your problem is a common one. You will find explanations.

You have to enable OEM unlock first.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] karapoutsoglou:
is your usb debug on? did you unchecked the automatic Reboot in odin?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
What about the KG State in download mode screen?

If prenormal look that

Edit : Or search for the corsicanu's KG/RMM bypass v3 zip
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
So your KG state is prenormal?

If so you will find lot of guides to bypass this, you don't really need my help.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Not sure to understand what about you talk..

There is no reason you can't get twrp.

Flash a full stock rom with odin and follow guides to enable oem unlock and bypass rmm/kg.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
TWRP doesn't have to support any secure software dude...

You didn't answer about your kg state?

Which you can see in download mode.

Prenormal or checking?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Reboot in download mode, the mode to flash with odin, check for kg state in the lines. Report the value

Edit : Looks like this
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
So as expected your kg state is prenormal.

As I told you, make searches about kg state bypass guides, follow them. When you fixed this you will be able to install twrp and roms.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] namfat:
He told you please do searching...[emoji846][emoji846]
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
The new release include a patch to prevent samsung account and lockscreen loop issues, strongly recommended to check the box when flashing a kernel.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Da-BOSS:
Pretty darn nice! ;) :good:
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Tops1:
Hi I have older twrp already can I just extract the .img and flash that instead of going through oden.

Thanks
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Yep! As you want
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] Tops1:
OK cool thanks so much
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
The new release add a compatibility workaround for lot of "dirty" zip script. By that this a major one which you should install.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] bober10113:
my scripts must be extra "dirty" as the exact same problems are still there.

would you care to elaborate on the "too or 2? common commands" that were worked around? ( like write what these are)

that being said, the ODM issue that I reported a while back was indeed really resolved 2 versions ago.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Maybe yep. Could take a look if you need. Or just stop using my work we will both be happy.

The source links are in the first post.

Your odm stuff wasn't related to my build so idk.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] TurricanM3:
I switched to F2FS and i now have a quite long waiting time to enter the recovery. I see the initial screen for about 20s. Is this normal?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] TurricanM3:
Went back to ext4 and everything is fine again. F2fs still seem to have some bugs or strane behavior and i see no real world benefits.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Yep sorry I will add this in known bugs section.

Twrp checks partitions space at boot and in some other situations. But f2fs is very slow for this check. Dependent how much your f2fs partitions are full it could make long time.

Sadly I can't do much for that.
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
New release for One UI 2 beta support :)
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] AbdullahT3rx:
I'm getting stuck at samsung logo when I install it.

r3.6 doesn't go into bootloop but can't mount data due to new system location.

Any suggestions?
[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] 3arthur6:
Hmm.. You can't boot system right? Maybe some kernel security stuff

Try this Universal DM-Verity, ForceEncrypt, Disk Quota Disablers

And if it can't mount data it may more is because the partition is encrypted.