yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Encryption

I know this was a topic here before, but I can't make enough sense of it, so I hope you'll excuse me for asking again:

Is decrypting an encrypted device with current TWRP 3.2.1-1 or the upcoming 3.2.2 supposed to work?

When I tried it a few weeks ago, it wasn't decrypting, but perhaps it got fixed in the meantime. I'm using LOS 15.1, but would like to only try again if there's a reasonable chance it's working.

There was a post here about "TWRP not supporting Samsung encryption", but I don't think that applies to LOS, and furthermore I have another Samsung running with LOS 15.1 (Galaxy Note 4) where the decryption with TWRP works, so shouldn't be Samsung-specific.

Anyone know more about this? Thx!
[Samsung Galaxy S9 & S9+ Cross Device Development] :
3.2.2-0 won't come for our device
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Just 3.2.2 or will TWRp not be updated for S9? Why?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
The dev is not at his Computer until october
[Samsung Galaxy S9 & S9+ Cross Device Development] j1gga84:
Where is the problem? so the update will come after october ;)

TWRP in this stage is running good. :good:

regards
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Did i say it is a problem? No!
[Samsung Galaxy S9 & S9+ Cross Device Development] AZWildcat:
Root or Custom Kernel First After TWRP?

#3 says to install a custom kernel before root:

However the the first sentence in step 3 of the ElementalX "How to install" tab says to root first before installing a custom kernel:

I did not see anything in the previous 48 pages of this thread saying definitively which should be done first to avoid problems. Can anyone offer a confirmation either way? Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
If you install a custom kernel after rooting the device, you effectively unroot it again, unless you happen to be installing a custom kernel boot image prepatched with root.

So, you typically need to reroot after every flash of a custom kernel.
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Ah OK.

But is decrypting a LineageOS system in TWRP working for somebody here?
[Samsung Galaxy S9 & S9+ Cross Device Development] SkyperGER:
Unfortunately no. I'm waiting for a TWRP release with encryption support too.

At the moment it isn't possible to update Lineage without formating the whole phone :(.
[Samsung Galaxy S9 & S9+ Cross Device Development] gusnz:
ADB sideload works in the meantime for upgrading encrypted phones. Connect USB cable, choose "Advanced" -> "ADB Sideload" in TWRP, then on your computer type:

adb sideload lineage-15.1-DATE-nightly-star2lte-signed.zip
[Samsung Galaxy S9 & S9+ Cross Device Development] SHOTOKANKATANA:
S9+ freezes after flashing twrp.

Hi... I've been running into a problem trying to get my s9+ rooted. Or actually I narrowed it down to twrp being the issue, cause I can get my phone rooted.

Let me try and explain...

I can install twrp perfectly fine. It works but after flashing twrp when I reboot into the os my phone freezes when the screen goes dark. If I keep my screen on it keeps working, but when I turn off the screen with the power button or it goes dark by itself it freezes.

When it does nothing works, not even responding to the charger. The only thing that works is holding the volume down and power button to make it restart.

Restarting works but again when the screen goes dark it freezes, sometimes instantly, other times after a minute or so.

I tried it with resurrection rom and official Samsung firmware. Both the same result. After flashing twrp it freezes when the screen goes dark.

I installed the latest official firmware through odin last night, I think it's BRF8 or BFR8, I would have to check to be sure, in any case there's no issue now. It works like a charm. No freezing what so ever.

So the problem has to come from twrp, no verity or RMM bypass. Since that's all I'm flashing.

Does anyone experience similar issues? I can't find anything online about this issue, only 1 person I found here on XDA had the same issue.

Any help would be much appreciated!
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
damn..this problem is freaking me out.. I'm not using dual account apps... I'm on magsik 16.6
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Is your current firmware the same (or comparable) with that of your backup? That could be the problem.
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
yes.. I'm still on BRE5
[Samsung Galaxy S9 & S9+ Cross Device Development] ExodusNZ:
Is no-verity (DM) included in this file or do I need to flash that separately?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Read the first posts
[Samsung Galaxy S9 & S9+ Cross Device Development] ratnapatka:
I'm experiencing this issue as well, I've been using the "SOD Killer" app from the Play Store to prevent my phone from sleeping while I'm looking for a solution.
[Samsung Galaxy S9 & S9+ Cross Device Development] Braunbär_1:
Hi slarti76,

see here: https://xdaforums.com/showpost.php?p=76706838&postcount=373 - it's not working, and it is unclear if upcoming TWRP versions will support it.
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Yeah, thx, that's the entry I saw - but the answer is only about "samsung encryption", and I have LineageOS installed, not stock Samsung, so I hoped TWRP would be able to handle that, as it manages it on another Samsung phone of mine. Alas, seems to be different, though...
[Samsung Galaxy S9 & S9+ Cross Device Development] Braunbär_1:
Hi slarti76,

Just read on: the answer was about "samsung encryption", but I was talking about LineageOS encryption, thus I insisted: https://xdaforums.com/showpost.php?p=76715884&postcount=377
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Bummer, I didn't see that... Thx a lot!

In the end, encryption could be part of the vendor image, so it would be Samsung specific, at least partly. Does anyone here know that?
[Samsung Galaxy S9 & S9+ Cross Device Development] yhvo2gt9:
comments and questions

Hi all, I have a series of comments and questions about TWRP on the S9. I got a new (unlocked) S9 this week and as usual I want to have the latest LineageOS on there.

comment 1: The OP guide focuses on Windows, but I was able to flash the TWRP image (not the zip) to the S9 from Linux using Heimdall. I wrote the command, held down power+Bixby+volume up, then hit the command below and it flashed and rebooted into TWRP:

heimdall flash --RECOVERY twrp-x.x.x-x-starlte.img

comment 2: At no point during or after the process has it been possible for me to mount the internal storage /sdcard/ when the device is in TWRP recovery - either in the TWRP application itself or over USB from a computer. The only way I was able to flash zips (including the dm-verity zip that's part of the TWRP process) was to put them on a microSD card, which TWRP was able to access. Any attempt to mount /sdcard/ in TWRP fails. This seems problematic.

comment 3: After installing LineageOS I re-encrypted the device. However TWRP can read the system files and does not ask for a decryption passphrase.

So my questions are:

Question 1: How can I get TWRP to mount the internal storage /sdcard/ ?

Question 2: What has subsequently been encrypted by the OS? How is it that TWRP can read the system files without a passphrase?

thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
GPS battery drain

[deleted, wrong thread]
[Samsung Galaxy S9 & S9+ Cross Device Development] force70:
I dont have that issue on my device

but what exactly does this have to do with twrp exactly?

sent from my Exynos S9 plus, Pixel 2 XL or Note FE
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Posted in wrong thread, so sorry!
[Samsung Galaxy S9 & S9+ Cross Device Development] Lord Spectre:
Guys, I've read all the 50 pages but is not clear which file I have to flash to avoid OEM 7 days lock.

After flashing: no-verity-opt-encrypt-samsung-1.0.zip

Which is the next file to flash?

N965F_Root_for_OEM_issue_devices_V3.zip

RMM-State_Bypass_Mesa_v2.zip

Thank you
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
Most of the roms now include those files so you dont have to flash any of those.
[Samsung Galaxy S9 & S9+ Cross Device Development] Lord Spectre:
Yep, but I don't want to flash a custom rom, I prefer the stock one. Maybe I'll give it a try with Iron Man Rom :)

So for now which file I have to flash with stock?
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
Iron man rom for s9 ? Really?
[Samsung Galaxy S9 & S9+ Cross Device Development] Lord Spectre:
I don't know if the name will be Iron Man, but I've read that Tkkg1994 will release a rom for s9/s9+
[Samsung Galaxy S9 & S9+ Cross Device Development] bobandar:
Then it all depends on the rom.

ALL CUSTOM OR STOCK roms have those files included.
[Samsung Galaxy S9 & S9+ Cross Device Development] force70:
No worries i just thought maybe you figured it was something to do with twrp so i asked!
[Samsung Galaxy S9 & S9+ Cross Device Development] mohamad5758:
i cant put the file in odin cuz its an image file i am downloading the link that its supposed to be a tar file but its recovery.img with no tar or md5 signature can anyone tell me what to do?
[Samsung Galaxy S9 & S9+ Cross Device Development] cıyanogen:
good work
[Samsung Galaxy S9 & S9+ Cross Device Development] anin kontra:
I read about that oem problem-well its seams all s9 have that and that 7 days start from the moment you buy your phone/turn it on,but didnt read why sammy did that so gona wait for now
[Samsung Galaxy S9 & S9+ Cross Device Development] el7145:
No, that is false...everyone does not have that "oem problem" I was one of the lucky ones that did not suffer from that issue.
[Samsung Galaxy S9 & S9+ Cross Device Development] davitox87:
I do not suffer from the OEM problem on my note 8 and s9+.
[Samsung Galaxy S9 & S9+ Cross Device Development] blackberet:
I'm getting this error when trying to flush no-verify-opt-encrypt zip:

Filed to extract zip to /tmp/no-verify-opt-encrypt

Aborting...

Failed to patch boot image

...

Updater process ended with ERROR: 1

I copied the zip over TWRP MTP

On Windows the zip seems fine. MD5 passes ok.

Maybe TWRP MTP zip transfer issue?

TWRP 3.2.1-2

S9+

---------- Post added at 11:08 AM ---------- Previous post was at 10:22 AM ----------

Was indeed TWRP MTP issue. Copying the file via adb works OK.
[Samsung Galaxy S9 & S9+ Cross Device Development] Legasx:
What should I do if I got the oem unlock option after 7 days, toggled it, then let it reboot after the factory reset (I know this was wrong), then I had the oem unlock switch gone, but in download mode OEM lock and FRP lock are OFF, but RMM state is prenormal again, BUT I have waited for 7 days again and the RMM state still prenormal and the oem unlock switch won't appear anymore in dev options?
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
There is a another way on web somewhere to avoid 7 day wait search for it. New way.
[Samsung Galaxy S9 & S9+ Cross Device Development] Legasx:
What method do you mean?
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
I read somewhere there is new method where you do various steps and OEM unlock appear immediately. I was reading a week or two ago can't remember where it was search on web.
[Samsung Galaxy S9 & S9+ Cross Device Development] Legasx:
I don't undestand what method do you mean, can't read your mind.
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
Quick Google search and you find this: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
[Samsung Galaxy S9 & S9+ Cross Device Development] Legasx:
I already tried that, not working for me. That method is not that new, I thought you mean something newer.
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
Maybe your device is not "clean" on Sansung server.
[Samsung Galaxy S9 & S9+ Cross Device Development] giojj89:
Hello, sorry for my english! I need one info, i see in first post this: Real-time Kernel Protection (RKP) , this protection its present in all device? I have rooting many device: s6,s7,s8 but i never change kernel for rooting. For rooting S9 its necessary change kernel or its necessary because have Oreo? Also with Samsung s8 its necessary change kernel? Its possibile have more information? Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You do not have to change kernel to root. Privacy Guard built in you can activate root within developer options if you use Lineage or flash super-su to root touchwiz.
[Samsung Galaxy S9 & S9+ Cross Device Development] giojj89:
Hello, thanks for answer but i dont understand..i dont use lineage or other custom rom, i need root with stock rom. In first page i see: "Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion."Why jesec suggest to change kernel? It's the first time I've read about changing the kernel to avoid crash the system after root. Thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You should probably flash a custom kernel after you root but it is not required. Things get messy on rooted device with stock kernel.
[Samsung Galaxy S9 & S9+ Cross Device Development] DirkStorck:
Hi, maybe stupid question! I coming from an S7. In TWRP for the S9+ is an option "system image". Do I have to backup this one and what is the difference to "system"?

Do I have to backup "vendor image" and "carrier info" too ?

Thank you!
[Samsung Galaxy S9 & S9+ Cross Device Development] DirkStorck:
Ok thank you! :)
[Samsung Galaxy S9 & S9+ Cross Device Development] PlutoMonkey:
Does this work for SM-G960W?
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
No your boot loader locked.
[Samsung Galaxy S9 & S9+ Cross Device Development] force70:
If he wasnt so lazy he could have read that in the first paragraph in red in the OP.

sent from my Exynos S9 plus, Pixel 2 XL or Note FE
[Samsung Galaxy S9 & S9+ Cross Device Development] Yozak:
Has anyone tested encryption on 3.2.3-0?
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
Does that mean accessing an encrypted S9 with TWRP does now work? It didn't work for me at all (no need to think about automatic installing), and some people here confirmed to me it never worked so far. Was that fixed or is that just a copy&paste from a generic TWRP changelog?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
No, definitely not.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
pls delete. i f*cked up. another 168 hours.. yay.
[Samsung Galaxy S9 & S9+ Cross Device Development] DirkStorck:
Delete
[Samsung Galaxy S9 & S9+ Cross Device Development] superman1979:
1. Guys. Can you kindly teach me how to update twrp to the newest version using twrp. Thank you.

Mine is 3.2.1. I wana update to the newest twrp 3.2.3 . My phone is s9 exynos.

2. If I reflash an updated twrp from odin. Do i need to do everything again....like install no verify opt. Rmm bypass. Magic disk. Etc. Thank you.

Waiting for all your reply. Thank u.
[Samsung Galaxy S9 & S9+ Cross Device Development] PG101:
Nope.. simple flash via odin (AP)
[Samsung Galaxy S9 & S9+ Cross Device Development] force70:
Or....just flash using twrp lol.

Why would you bother with odin?

sent from my Exynos S9 plus, Pixel 2 XL or Note FE
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Encryption is broken, TWRP 3.2.3-0 is NOT able to decrypt your device. Please update, encryption is very important for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
hey all, once you have finished TWRP install and put on a custom rom you can make the system R/W in TWRP or do you have to keep R/O?
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
If you search this thread, you'll find that this is well-known and, according to some, will not get fixed anytime soon - seems to be something specific to this phone. So don't get your hopes up - but you're definitely not the only one disappointed about this...
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
so had my phone all setup nice... took a full backup of everything.. tried a kernel that i didnt like and attempted a restore and got "failed to mount system" cant even flash the rom that i flashed earlier! same error.. i have no phone now. i guess its back to odin... wtf

---------- Post added at 10:51 AM ---------- Previous post was at 10:48 AM ----------

hmmm fixed it with a manual format of system in twrp... bizarre. so restore cant mount system... flashing rom cant mount system.. though Wipe menu can.... now all is working again.. bug or what?
[Samsung Galaxy S9 & S9+ Cross Device Development] Docmjldds:
Finally...someone else this has happened to. For me, I Odin install the latest stock Firmware, then Odin TWRP, then I get rid of that fail to mount system issue. Sometimes its fails to mount Data. And in case someone runs into yet another strange bug......after doing this and thinking I have a working phone again, When I look at storage, it shows that the Phone only has 16GB instead of the 128Gb model it is. The fix is to Boot recovery, then have TWRP repair size of file system ONLY checking the Data Partition using TWRP. Then Voila, Phone now shows the true total storage.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
Thanks for the response. I assume you on the latest version of TWRP 3.2.3-0? If so maybe i will drop back to an earlier version.
[Samsung Galaxy S9 & S9+ Cross Device Development] Docmjldds:
YuK....Just happened to me again trying to restore a backup. Happens with current 3.2.3-0 as well as prior 3.2.1 or 3.2.2 flashable version vs Odin installed TWRP. Wish I knew the issue causing the failed to mount system :(
[Samsung Galaxy S9 & S9+ Cross Device Development] sielhadi:
Hi flash soldier rom but i decided to come back to renovate ice by restoring my backup. But now i can't install any even if i want renovate ice or enother custom rom it begin but before flashing phone reboots to recovery any help guy

---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------

Now i can't install anything with twrp. Please any help
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
What error? Is it failed mount system? Look at the replies directly above yours. Fix is to manually format system. Then restore or flash ROM. This TWRP needs work.
[Samsung Galaxy S9 & S9+ Cross Device Development] sielhadi:
The phone reboot just in beginning of flash without any error. I don't know what is problem. What i should do?
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
Raised the issue of not being able to mount system on the Github.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1299
[Samsung Galaxy S9 & S9+ Cross Device Development] mikael1022:
Hy first thanks for everything is very nice forum .

I want install twrp on my s9 with stock rom .

But i allready enable the oem bootloader and reboot the phone with reinitialisation of the rom .

So should i wait 7 day before install twrp ?

Or should reinstall the stock rom and enable the oem bootloader and restart installing twrp ?

I notice also that after enable the oem bootloader option some application in play store can t be installed is that because of the 7 day ?

Thank s a lot .
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You should not let factory reset occur boot directly in download mode after factory reset using power, volume down and bixby button then flash twrp with Odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] basicreece:
Flashed no issues. Using for past few days. Just a little confused about the RPK. Any suggestions on what kernel to flash?
[Samsung Galaxy S9 & S9+ Cross Device Development] gabwkk:
yellow "Set Warranty Bit: recovery" and loop restarting

yellow "Set Warranty Bit: recovery" and loop restarting

========================================

my phone is s9+ hongkong version

i followed the steps

and all passed in odin3v3.13

but get yellow "Set Warranty Bit: recovery" and loop restarting

i test all vesions in the link : twrp.me/samsung/samsunggalaxys9plus.html

the logs are

<ID:0/006> Odin engine v(ID:3.1301)..

<ID:0/006> File analysis..

<ID:0/006> Total Binary size: 42 M

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> NAND Write Start!!

<ID:0/006> SingleDownload.

<ID:0/006> recovery.img

<ID:0/006> RQT_CLOSE !!

<ID:0/006> RES OK !!

<ID:0/006> Removed!!

<ID:0/006> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

by the way:

i unlock the ome locks

and the two key locker are all "off" when in bootloader ui
[Samsung Galaxy S9 & S9+ Cross Device Development] force70:
So you flashed exynos twrp on a snapdragon device and your wondering why its not working lol?

Dude, cmon lol

Sent from my Note 9 exynos, S9 plus exynos, Pixel 2 XL or Note FE
[Samsung Galaxy S9 & S9+ Cross Device Development] TheMadScientist:
This thread has been cleaned

Lets keep it on topic and please please read.

As well This is a site for people of all ages lets keep the language down as well
[Samsung Galaxy S9 & S9+ Cross Device Development] immu23:
Problem

I have almost tried everything, everytime I backup system image, it says that the backup has failed, i have sufficent storage, even tried to backup system kmage separetelt, to no avail. Cant attach log file here too since its too large.
[Samsung Galaxy S9 & S9+ Cross Device Development] droidsometimes:
I just checked, and I have successfully backed up the system partition as image twice during the last month.

ROM is LineageOS, and I used the internal storage as backup target.

What storage are you trying to back it up to?
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You probably need to go into wipe, advanced wipe, check system, repair or change file system, change file system, ext. 4, then wipe the system and retry backup. Problem is you cannot mount system I think. I think this is a bug in TWRP for S9. I think maybe be fixed when jessec get back.
[Samsung Galaxy S9 & S9+ Cross Device Development] LysolPionex:
I toggled the OEM unlock and flashed TWRP etc. then got locked and had to re-flash stock to get past red custom binaries text.

As of nearly 9 days ago my recovery screen said OEM was unlocked and RMM was prenormal.

Currently, OEM option is not in my dev options (uptime is 213 hours).

Can I boot to recovery to check my RMM status? I'm worried about resetting the uptime (I've seen some posts saying I have to have the phone on with a sim card in it for 168 hours straight). Or does uptime not matter?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
You boot to download mode and check locks and prenormal . If licks off - don't touch them. Hopefully prenormal will disappear in 7 days. Uptime doesn't matter - resetting does.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mohd Masab:
Dear Kindly Upload TWRP Recovery For Oppo F9 (Model CPH1823).
[Samsung Galaxy S9 & S9+ Cross Device Development] :
This is galaxy s9 / s9+ section
[Samsung Galaxy S9 & S9+ Cross Device Development] Teracotta:
I'm getting an error attempting to flash odm.img to the Carrier Configurations partition:

E: Cannot write images to system partitions
[Samsung Galaxy S9 & S9+ Cross Device Development] lospuegos:
what to do, if lineage os doesn't boot?
[Samsung Galaxy S9 & S9+ Cross Device Development] pixelmatt:
My Twrp doesn't auto-generate backup name with Rom name. Anyone else got this?

I tried to reflash twrp without success...

I used autoflasher before this behavior occurs.

Maybe it's something with open recovery script?