yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] astrovale:
Been using twrp for ages now, but this never happened to me: I cannot restore a backup because the process gets stopped right away and a red message appears saying that the backup cannot be restored because the drive is mounted read-only.

What can I do? What am I missing?

Thanks for any help guys

PS I'm on 3.2.1-2 and one more problem: the autogenerate name function doesn't seem to work anymore and the files are just named with a date and time, no more rom name..I've seen someone else reporting this problem

PPS: problema 1 solved. I went to the recovery menu and found that the system partition was mounted as read only. Now the backup restores OK.

Don't know yet about problema no. 2. at the end of the backup I'll be able to see the filename and report back here
[Samsung Galaxy S9 & S9+ Cross Device Development] W@llie:
[MENTION=6371894]jesec[/MENTION], Thanks! Followed you OP and everthing seems to work.

Also flashed the Magisk of [MENTION=7187684]ianmacd[/MENTION] and also works.

Kept the stock kernel and rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Wish more people would read this thread - lots of problems elsewhere. Good work here.
[Samsung Galaxy S9 & S9+ Cross Device Development] norbao:
I am stuck in a bootloop on my S9 SM-G960F/DS.

I have tried multiple versions of twrp. I get no errors installing LineageOS on the current one twrp-3.2.3-0-starlte.img (latest version), but I am stuck at boot when booting to system. I have flashed no-verity-opt-encrypt-samsung-1.0.zip, unlocked OEM and followed the official guide for installing LineageOS every step. I've tried the procedure multiple times in case I did something wrong, but I always end up being stuck at boot seeing the text "Samsung Galaxy S9. Secured by Knox. Powered by android".

Can anyone please help me out?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
If you can continue to flash, the problem must be the ROM. Wipe and try a clean install of one of the stable Oreo ROMs. It it works, it is your Lineage.
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
There is not any problem with Lineage Rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] norbao:
I solved the bootloop problem on my S9 now by flashing the BRE5 zip (Flashable_G96XF_Vendor_BRE5_r1.zip) in twrp. It boots nicely and Lineage OS works. Thank you xda!
[Samsung Galaxy S9 & S9+ Cross Device Development] Mihhail.ivanov1:
can you please upload link where u downloaded the file?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
That is what I suggested someone else try....
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
Hi everyone, I recently decided, well actually 7, 14, can't remember how many 7 days ago, to root my Galaxy S9+. I can get into twrp and root and it boots back into stock ROM rooted but then the OEM unlock is not visible. So when I reboot, it says I'm not allowed to flash things, you know the red words and then I have to Odin stock firmware again.

Anyway. I just want to know if it is possible to flash a custom ROM straight after I gone through all the rooting steps and I flash magisk?

Or do I need to boot into stock firmware rooted and wait for the OEM unlock to appear before I can start flashing custom ROMs.

I'm afraid that if I directly flash a custom ROM without booting into the stock ROM and waiting for the oem unlock option, that it'll give the red words again.

If anybody has experience please advise.

I appreciate the time and effort the community has put into this device.
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
Not had this happen. I don't think has anything to do with root. Root will not affect flashing capabilities. I wonder if your boot loader has become locked again?
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
Yes it is locked now, but tomorrow it'll be off the prenormal state again. And allow me to flash. I don't know why but my OEM unlock doesn't show after going through the steps in the OP. Guess I'll just play it safe and wait 7 days after I get it rooted again.
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
I think you should ignore OEM unlock disappearance in Samsung Experience rom. I think it disappeared for me too but bootloader was unlocked. I use Lineage rom now.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Prenormal can block you from flashing. What do you see in download mode ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
So this evening my pre normal went away after the 168 hours, and I flashed twrp and went through the steps. So I flashed the no verity and the OEM patch and all that jazz then I flashed soldier's ROM. The OEM unlock option disappeared again. So I guess I have to wait 7 days between flashing roms. Better than nothing I guess.
[Samsung Galaxy S9 & S9+ Cross Device Development] Docmjldds:
OEM unlock not seen is NORMAL. If you could flash a ROM, you still can flash a ROM!!!
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
On soldiers ROM he's removed the OEM Unlock by default. If You've got TWRP installed you won't need OEM Unlock
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
You guys are sure?

I'm really paranoid about this. This will be the third time I'm trying this and I'm really scared that if I reboot, it'll say the red official binaries message again.
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
Yep, see my dev options
[Samsung Galaxy S9 & S9+ Cross Device Development] BokkieAndijk:
Thanks to a lot of poeple here, i rooted my device and it works like acharm now.
[Samsung Galaxy S9 & S9+ Cross Device Development] illuzi0n:
Mines a australian G965F model and got the red failed sign stating failed only official binaries can be flashed aswel
[Samsung Galaxy S9 & S9+ Cross Device Development] mcn1970:
have you tried xposed?
[Samsung Galaxy S9 & S9+ Cross Device Development] pswin09:
This is well known problem in Note 8 xda thread. Wherever you flash custom recovery your Oem Unlock options in developers settling will disappear and will appear again after 7 days. If you reboot wothout oem unlock options showing in developers settling your phone will brick. Only way to comeback is flashing offical firmware from your region. After flashing offical firmware oem unlock options will still be missing. Oem unlock options will comeback after 7 days. [emoji16]
[Samsung Galaxy S9 & S9+ Cross Device Development] :
And how did you do?
[Samsung Galaxy S9 & S9+ Cross Device Development] BokkieAndijk:
That's a question that's hard to answer cause I made it work after lots of attempts. In TWRP I think it's important you never reboot system if some changing gave a red error. Install the no-verity 5.1 zip first and than the SuperSU v2.82 img. Than wipe dalvik and cache. If you didn't got any red line after doing one of this things, than it's worth to try a system reboot. Good luck guys. (And girls?)
[Samsung Galaxy S9 & S9+ Cross Device Development] Alieniii:
Software update

[MENTION=6371894]jesec[/MENTION] Hi guys just wondering is the latest software update for the S9+ supported ?? This is the new software number G960FXXU1ARC5
[Samsung Galaxy S9 & S9+ Cross Device Development] FRoZeN ACiD:
Thanks for the heads up... i used the stock firmware and flashed it back through odin. Now im stuck in the 7day jail. I thought after all this time (since note 8 release at least) that someone would have found a way around this. i basically will now wait the 7days while i use my S8+ and hopefully by then new custom ROMS would have been released to sort this issue out.
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
I'm always getting red message related to fpecs not mounted or something like that...

It's normal?
[Samsung Galaxy S9 & S9+ Cross Device Development] jesec:
Yes, usually TWRP can support a large range of firmware. I will give you special notice if a new firmware is non-compatible.

That won't affect functions of TWRP. This problem will be solved in next release.
[Samsung Galaxy S9 & S9+ Cross Device Development] Poulpyflu:
Hi guys

I'm in trouble.

I have success the step one but fail the step 2 (can't import the .zip file)

Now the phone is loop booting.

I can access to recevrery and download mod.

Do you have an idea for restet to factory the phone.

Thx for your help
[Samsung Galaxy S9 & S9+ Cross Device Development] jesec:
Make sure that you rebooted the recovery after you formatted the /data. (Note you must format the /data and reboot the TWRP before you can use the USB connection function)

Make sure that you installed drivers on your PC and your cable is functional.

Make sure that "Enable MTP" in Mount tab of TWRP is toggled.

If it still does not work, you can go to updato.com to download stock firmware and use Odin to restore the phone to stock firmware. Or you can use "Emergency firmware restoration" function of Samsung's Smart Switch.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Hi everybody. Today i flashed TWRP official to my device and rooted it with SuperSU, but this loads very long and i can't answer supersu requests. So it seems useless to me.

Any idea guys?
[Samsung Galaxy S9 & S9+ Cross Device Development] Poulpyflu:
restoration

Thx for your help.

I had to work with odin but the 3.12 version wasn't able to perform with the official ROM. That always stuck with file in .l4z

I tried to make a new file like it's explain for the S8/S8+ for Oreo rom, but that failed too.

Finally i have found a version of odin 3.13.1 and it work. So my S9+ is ok.

I wil try to root later.
[Samsung Galaxy S9 & S9+ Cross Device Development] rodhal:
CPEFS error

I seem to get an error. failed to mount /cpefs read-only file system. in TWRP when I try to root my CM-G965F.:(

Can anyone help
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
It will be fixed soon
[Samsung Galaxy S9 & S9+ Cross Device Development] Normusmaxamus:
Install supersu free app from Google play store.
[Samsung Galaxy S9 & S9+ Cross Device Development] illuzi0n:
do you flash dm-verity before OEM fix ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Serpentinefire76:
To grant SU access to an app/apps after missing the query, you can open the SuperSU app. On the Apps tab, long press/tap on the specific app and grant it SU access from there.

If SU is freezing all the time, boot in TWRP -> Advanced Wipe-> Wipe Dalvik and Cache. Reboot to system
[Samsung Galaxy S9 & S9+ Cross Device Development] mileder:
same by me! please fix it!
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
That image doesn't load. Anyway here goes nothing.
[Samsung Galaxy S9 & S9+ Cross Device Development] lndiana:
I did like you did,then flashed Nemesis, TGP, and finally soldier rom. OEM unlock never appeared again...
[Samsung Galaxy S9 & S9+ Cross Device Development] Lil-Tunechi:
Thanks guys! Been flashing ROMs all night ? No more OEM problems.
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
Nice one ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Emre67511:
If I don't have the rmm problem can I still do part 2 of the guide with the freezes for rmm or not ?

Or better question: does something happen if I still do it even if I don't have the problems ?
[Samsung Galaxy S9 & S9+ Cross Device Development] manulix:
Hi guys,

If I flash TWRP through Odin, I will break KNOX and guarantee?

Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] johnnyblaze1977:
Its mentioned in the OP, point 2.
[Samsung Galaxy S9 & S9+ Cross Device Development] MathewST1:
Yes, it will void your warranty and trip Knox.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Guarantee in US - not elsewhere for the most part.

---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------

You may have problems later if you don't.
[Samsung Galaxy S9 & S9+ Cross Device Development] manulix:
Are you referring to this:

Custom binaries could be also recovery?

I the main page of TWRP Galaxy S9 it's written a procedure for NO ROOT:

Odin Install Method (No Root Required)

-----------

I've Exynos device, so is Europe version...
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
The moment the device detects TWRP Knox will trip, TWRP is a custom binary aka custom recovery.

As you're in Italy (Europe) your hardware warranty shouldn't be affected unless it can be proven that software/firmware changes caused the hardware to fail, highly unlikely but it is a possibility.
[Samsung Galaxy S9 & S9+ Cross Device Development] manulix:
Ok, thank you ;)

What do you tell me about "TWRP Odin Install Method"? KNOX it will trip also if I follow this procedure?
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
Yes, Knox will still trip, TWRP doesn't root your device you achieve that by using other methods after installing twrp, the common method these days is to use magisk

As I say as soon as you install TWRP Knox will trip
[Samsung Galaxy S9 & S9+ Cross Device Development] donia1022006:
if i install twrp samsung pay and secure folder ? will dissapear even without rooting my device
[Samsung Galaxy S9 & S9+ Cross Device Development] Chrispearson172512:
Yes
[Samsung Galaxy S9 & S9+ Cross Device Development] AMDPOWERFIST:
I have an OEM Unlock issue....

Waited a full week for the OEM Unlock.

Ticked it last night.

Rebooted to download mode > Flashed TWRP > Passed.

Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF

Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.

Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???

I used the Patched ODIN here: https://xdaforums.com/and...-13-1-t3762572

Combined with TWRP 3.2.3-0 recovery....
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Make double sure your TWRP was the right one for your device.
[Samsung Galaxy S9 & S9+ Cross Device Development] jujubeans:
With S9+ Exynos, you're essentially saying if I TWRP, then flash with (example) AOSP GSI 9.0, does this mean that I won't get the 7 day lock anymore as long as I stay on the GSI custom ROM and not samsung stock ?

Or do i still need to do additional measures like 'oem fix' by dr. ketan.... or the dm verity stuff...or any of the other stuff to bypass the OEM etc.. ? so that I can restart and not get the 'not an official binary' error that breaks my phone and needs to go back to stock samsung firmware..
[Samsung Galaxy S9 & S9+ Cross Device Development] greenwhale6:
Trying to get the oem unlock option back...

But my s9+ is an optus(australia) version, and I'm in china now. Can't get the oem unlock option back with the Chinese sim card inside even after 7days.

It seems that the firmware country should be the same as the sim card.

I Can't flash an Chinese fw because the Chinese version s9+ is snapdragon version...

So is it possible that I can get the option back if I plug an optus sim card in my phone?(optus version fw)
[Samsung Galaxy S9 & S9+ Cross Device Development] jujubeans:
FRP lock

Can someone please clarify the FRP lock - Removing Google account/signing out.

Is this what unlocks FRP ?

Question: After 168 hours and OEM unlock is displayed, can you restart WITHOUT touching OEM unlock and you will still have OEM Unlock and no prenormal ?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
If you mean unlock is displayed in Developer Options, then yes. You would select OEM unlock and it will ask to do factory reset. Accept it, but then immediately go to Download Mode. Locks should be off and prenormal should be gone.

If you want TWRP to flash - Odin it now following OP instructions. If you let it reset, besides wiping everything - you will have to wait another 7 days to get rid of prenormal.
[Samsung Galaxy S9 & S9+ Cross Device Development] annie764:
On part 1, point 3 of the guide, when it says "BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS." does that mean do not allow the phone to reboot after the odin finishes flashing twrp? Is that why we should hold VOLUME DOWN + BIXBY + POWER before pressing start and until it reboots into twrp?

After this process and flashing the dm-verity software, will I encounter the 7 day wait if I make an accident?
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
The reset process is after selecting unlock and before Odining TWRP. You do the vol down stuff and the go straight to ODINing TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] annie764:
So I should select unlock oem and then directly reboot to download mode to flash using odin?
[Samsung Galaxy S9 & S9+ Cross Device Development] innocence07:
exactly what happened to me, original post should update the steps that first boot on twrp it will prompt an error but you should ignore this and before the text fades you should be holding up+bixby+power button if you dont you will need to wait 7days again sigh

[MENTION=6371894]jesec[/MENTION] can you please update the instruction in booting TWRP the first time? that it will prompt an error and reboot your device but before it does you should be holding up+bixby+power
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Yes after you select AND it asks to factory reset and you select that also - then go immediately to download mode.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Today i activated encryption in LOS and rebooted to recovery (latest TWRP).

TWRP recognizes the encrypted data but refuses to accept my correct password.

Booting back to LOS works so the password is the right one.

I'm glad for any help.
[Samsung Galaxy S9 & S9+ Cross Device Development] stewa2jm:
I'll be watching replies here... Same issue. I find it interesting that updates can still be applied without decryption. That tells me the system is still available to an update file. Makes me think that there would be an exploit here someone could use to decrypt the data. Seems like an update should fail if the system is encrypted and there isn't a password input to decrypt. Different partitions? If so, then why can't I access the /data file where the downloaded updates are saved and need to be read from to update the system? ...
[Samsung Galaxy S9 & S9+ Cross Device Development] Nickjaiani:
I was waiting for oem unlock button for 7 days, I flashed twrp, when I tried to reboot to twrp I saw twrp logo then some kind of red text and phone rebooted automatically to system and now im stuck again. I guess im gonna sell this sh*t and buy a normal phone
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You should not give up. It all works - just need to figure out what you are doing wrong.
[Samsung Galaxy S9 & S9+ Cross Device Development] Nickjaiani:
im pretty sure i did everything right, like I was doing it before and everything was fine. Since i bought this phone Im waiting for oem unlock button almost all the time
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
You should google search unlocking OEM S9+. I thought I saw a while back a method where you can unlock OEM now without waiting. It was article in XDA.
[Samsung Galaxy S9 & S9+ Cross Device Development] Nickjaiani:
yeah but it was before september security patch
[Samsung Galaxy S9 & S9+ Cross Device Development] DeHAWK:
Hey guys

Just wondering, did any of you have the OEM unlock available right after you got your S9+...I mean out of the box?

I had and I still had after making an OTA to XXU2BRJ3.

Now a new OTA is knocking on my door, but I haven't installed it yet. I purchased the phone 2 weeks ago and it's still 100% stock. Gonna try use this TWRP when I'm ready to root it. Keep up the good work.

Regards

DeHAWK
[Samsung Galaxy S9 & S9+ Cross Device Development] rsktkr1:
I think if you get it unlocked you will be glad you did. This is a very nice phone and Lineage will have PIE soon. I love this phone.
[Samsung Galaxy S9 & S9+ Cross Device Development] stewa2jm:
I encourage you to stick it out too. PM me and I can share my struggle and how I got through it. Or you can search for my posts... But that's ugly.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Mine had Unlock right out of the box. Was having fun flashing different rooms and kernals for a few weeks until a flash of a kernel blew it up. TWRP was gone, and it wouldn't boot, so ODIN'd a stock rom and then it was locked and OEM unlock option was gone.

So I became a member of the x 7 day club. Haven't had any problems since with unlocks or prenormal.
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
The trick for me was to turn off wifi and not allow it to connect to Google until after I had it unlocked and twrp and the updated boot installed.

But YMMV - the security patch may have changed that.
[Samsung Galaxy S9 & S9+ Cross Device Development] marquelito:
[MENTION=6371894]jesec[/MENTION] can we use with beta pie?

---------- Post added at 04:52 PM ---------- Previous post was at 04:52 PM ----------

[/COLOR [MENTION=6371894]jesec[/MENTION] can we use with beta pie?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Silly question...
[Samsung Galaxy S9 & S9+ Cross Device Development] bilbonotry:
Hello

I think [MENTION=4485380]innocence07[/MENTION] answered to that already here https://xdaforums.com/galaxy-s9/sam...development/twrp-exynos-t3763464/post78116490
[Samsung Galaxy S9 & S9+ Cross Device Development] Retenor:
This looks awesome, would really like to try that, I just got an S9 myself.

Just some questions (I'm actually really sort of scared modding my S9 even though i already did mod my S2 and S5 in the past):

- Will this work on the SM-G960F/DS (Bought in Germany, Dual Sim, and from what I know it can only have an Exynos)?

- If the "unlock OEM" button is enabled for me, do I still have to wait these 7 days?

- Do Magisk and Xposed go well with this? In the main post it was mentioned that some custom roots/roms might drain the battery and cause issues?

And as far as i'm informed I don't need SuperSU anymore if I have magisk?

If those questions are dumb and maybe already answered in this thread I apologize, I just went through a majority of it and got lost numerous times.

I also haven't done any modding for over 4 years now so I haven't really tracked any developements, also regarding new Android Versions (My S5 is still running on KitKat).

Any help highly appreciated!
[Samsung Galaxy S9 & S9+ Cross Device Development] marquelito:
Not so silly since when changed between nouugat and oreo there was issues with twrp from nougat versions
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
1 yes

2 no - you can unlock, and if it says it has to reset, accept it but IMMEDIATELY go into download mode and ODIN TWRP.

3 Magisk only works. Can't answer on Xposed - I had nothing but trouble but others didn't.

4 No SU - not supported anymore.
[Samsung Galaxy S9 & S9+ Cross Device Development] :
There never was nougat for S9 so it is silly
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
any fix?
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
I have Magisk & XPosed running with no problems on F-Variant (Dual SIM). Mind you, you need to install the XPosed module in Magisk, not a ZIP in TWRP!
[Samsung Galaxy S9 & S9+ Cross Device Development] gsser:
ok i got a question, i have managed to get oem unlock enabled, when im in download mode i can see frp and oem is off, but rmm state is prenormal. also in dev settings oem unlock button is toggled so what should i do? also guide is quite difficult to understand. especially the part to unlock bootloader...

this is much better than guide steps

Edit: i did what gaww said but still rmm state is prenormal with frp oem being off.

btw dont flame or trigger. anyone who is foreign can mess this up because of thread being too complicated. it could be easier for us to just see reboot to download/odin mode when you press factory reset button rather than dont let the reset process complete...