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

[3arthur6]

;79530801]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 ????

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

With F2FS data?

Could you provide a last_kmsg from /proc ?

 

[osk4rin]

Does this TWRP is for the Exynos SM N960F?
Thanks!

 

[bober10113]

Does this TWRP is for the Exynos SM N960F?
Thanks!

please read OP and thread title.

thanks

 

[karapoutsoglou]

holy shhhh, my phone is N960F!!! and i have installed this recovery

Sent from my [device_name] using XDA-Developers Legacy app

 

[azZA_09]

Does this TWRP is for the Exynos SM N960F?
Thanks!

Beside all trolls, yes. It is. But read op everytime.

 

[osk4rin]

Beside all trolls, yes. It is. But read op everytime.

My bad*
Thanks for clarify!

 

[bober10113]

id like to report weirdness

 

[bober10113]

id like to report weirdness

also wiping cache or formatting cache never actually deletes anything...

 

[karapoutsoglou]

also i formatted to f2fs using endurance kernel for pie with dr ketan latest rom and nothing changed. still ext4

Sent from my [device_name] using XDA-Developers Legacy app

 

[bober10113]

also i formatted to f2fs using endurance kernel for pie with dr ketan latest rom and nothing changed. still ext4

well im on f2fs( frankly not seeing any advantages, disk access actualy dropped compared to ext4) but my main issue is that cache dosen't get wiped. not sure for dalvik.

what leads me to belive this is:
when wiping and refreshing it always shows 14 mb instead of 0 when it was on ext4.
and when i reboot phone i dont get the " optimizing x of y apps" upon reboot where when i was on ext4 it would do that like every other android phone ive had in the past 5 years.

what am i missing? is this by design?

 

[3arthur6]

id like to report weirdness

also wiping cache or formatting cache never actually deletes anything...

also i formatted to f2fs using endurance kernel for pie with dr ketan latest rom and nothing changed. still ext4

Sent from my [device_name] using XDA-Developers Legacy app

well im on f2fs( frankly not seeing any advantages, disk access actualy dropped compared to ext4) but my main issue is that cache dosen't get wiped. not sure for dalvik.

what leads me to belive this is:
when wiping and refreshing it always shows 14 mb instead of 0 when it was on ext4.
and when i reboot phone i dont get the " optimizing x of y apps" upon reboot where when i was on ext4 it would do that like every other android phone ive had in the past 5 years.

what am i missing? is this by design?

Sorry for that... It is doubtless because of the changes I started for allowing internal backup, but I totally changed the way to do this. So next update will fix it. But I'm not sure that the internal backup will be possible with it.

 

[karapoutsoglou]

thank you for your hard work. i dont understand. why is internal backup so crucial? if you want f2fs you do a clean install after you formatted data and cache.

Sent from my [device_name] using XDA-Developers Legacy app

 

[3arthur6]

thank you for your hard work. i dont understand. why is internal backup so crucial? if you want f2fs you do a clean install after you formatted data and cache.

Sent from my [device_name] using XDA-Developers Legacy app

Absolutly not crucial. But I would like to have that

I will upload a clean release in few hours. With or without that

 

[3arthur6]

Sorry I postpone the update because twrp 3.3.1 just get out and the latest commits seem to fix the previous backup restoration issue with pie platform.
I have to rebase my build platform. One day more needed.

 

[bober10113]

Sorry I postpone the update because twrp 3.3.1 just get out and the latest commits seem to fix the previous backup restoration issue with pie platform.
I have to rebase my build platform. One day more needed.

take your time.
looking forward to test out new rebase.

 

[3arthur6]

take your time.
looking forward to test out new rebase.

A simple system backup/restore just confirmed it :good:

 

[bober10113]

A simple system backup/restore just confirmed it :good:

i took a backup but didn't have time to restore.

is it possible that the mounting point for preload dosent match the right path? or name?

attached pictures show mounting error and in the partition list the name seems to be dqmdbg

 

[3arthur6]

i took a backup but didn't have time to restore.

is it possible that the mounting point for preload dosent match the right path? or name?

attached pictures show mounting error and in the partition list the name seems to be dqmdbg

I removed preload (or hidden) "partition" as it's a part of system. So totaly useless.

Dqmdbg is probably a part of boot, or at least related to boot. It his needed when upgrade (and downgrade?) system.

 

[bober10113]

I removed preload (or hidden) "partition" as it's a part of system. So totaly useless.

Dqmdbg is probably a part of boot, or at least related to boot. It his needed when upgrade (and downgrade?) system.

ok but its strange how doing a cache wipe will throw that preload not found message.


also i just restaured a full backup and i had a bootloop. uppon 2nd reboot i got to home screen and all by magisk modules are not working. and also my sd card if now popping up as if it was a new one that i just inserted. its seems to be intact though so not much of an issue.

 

[Kingvtt]

Thank you ! Great work