yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] NotATechnician:
Hallo Forum.

I have finally suceeded in installing TWRP (3.2.3-0), on my DS S9. I initially messed it up and ended up without an OS, and since I was having problems with using ODIN to flash the stock, I ended up installing Lineage OS. I install GApps, rooted it and got it more or less up and running. Then I found out what I doing wrong with the stock/ODIN and reflashed that, waited 7 days, installed TWRP and rooted it using https://highonandroid.com/android-smartphones/how-to-root-galaxy-s9-s9-on-android-9-0-pie/.

However, I am not able to restore any of the Lineage OS backups I made. (and there are several... the initial, the rooted and the fully functional, etc.) I've tried a number of different approaches, but I always end up in a bootloop (but I am able to successfully flash the rooted stock image, so there is that). In all of the backups I ticked EVERYTHING. I've since seen posts saying this is unnecessary, but I am not experienced and risk averse, so backing up everything seemed the way to go.

I have tried restoring the whole backup (i.e. everything).

I have tried wiping system, data and cache and restoring them.

I have tried wiping system, data and cache, then restoring data and cache, rebooting to recovery and restoring system separately (the advice came from someone struggling to restore lineage OS on a different phone).

In all cases, I obviously go to Mount and until "Mount system partition as read-only" and restore that after the restore and before the reboot.

In all cases, I wipe Dalvik and Cache after doing the restore and before rebooting to system.

It would be really nice to be able to swap between them. I could "install" Lineage OS again, but I do not really want to go through the clean-up and system hardening if it can be avoided (particularly if doing that would somehow prevent me from restoring my rooted stock backup). Does anyone have any advice?
[Samsung Galaxy S9 & S9+ Cross Device Development] b0uncyfr0:
So i want to root my S9 asap. It was purchased in India 6 months ago - and i'm currently using it in Estonia (In EU) as the second owner. Should i register it before rooting so Samsung cant give me too much hassle? I have the receipt and everything.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Wouldn't think there should be any problems as you have been using it.
[Samsung Galaxy S9 & S9+ Cross Device Development] b0uncyfr0:
I cant register it though in Estonia as the serial numbers are from India - if that makes a difference?
[Samsung Galaxy S9 & S9+ Cross Device Development] kost7:
AFAIK you should not restore a system backup partition onto another ROM (it makes no sense anyhow). Additionally, there is no reason to restore cache. The only thing that could work is restoring data.
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
Restoring system only should be ok if system is wiped first.
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
Already answered, it's not a big deal...

It will be fixed soon
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
It's already been fixed ;)

https://twrp.me/samsung/samsunggalaxys9plus.html
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
But not yet released [emoji854][emoji854]
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
It has been released, I have it installed 3.2.1-1

https://eu.dl.twrp.me/star2lte/
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
Sorry but you are wrong, i already have that version a couple of days...

If you look at dates you will see, 3.2.1-1 was released on 16/03 and the issue was fixed on 17/03...

So, not yet released :)
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
For some reason the dates had bypassed my brain, all i can say is that after installing 3.2.1-1 the cpefs error wasn't there, but that was installing straight over 3.2.1-0 so maybe that has a bearing?
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
Probably cause i flashed 3.2.1-1 straight up
[Samsung Galaxy S9 & S9+ Cross Device Development] mileder:
as you can see it was only for "star" also for Galaxy S9; star2lte will probably come later. And then will be released.

I installed 3.2.1-1 version and the same error is there!
[Samsung Galaxy S9 & S9+ Cross Device Development] ratsalad:
That's true, I firmly stand corrected, sorry everyone...
[Samsung Galaxy S9 & S9+ Cross Device Development] MMLP2:
It has been said multiple times that it doesn't affect the install process, some people just can't read
[Samsung Galaxy S9 & S9+ Cross Device Development] DevilStyle:
Thanks for good work man :)
[Samsung Galaxy S9 & S9+ Cross Device Development] jfm91:
Will this wipe my phone?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
I see you didn't read the first posts of jesec... There your question is answered
[Samsung Galaxy S9 & S9+ Cross Device Development] jfm91:
What happens if you don't wipe? Bootloop?

Can you log in to snapchat after installing TWRP?
[Samsung Galaxy S9 & S9+ Cross Device Development] n-j-f:
So is it necessary or advisable to install the N965F_root_OEM_issue_devices.zip from Dr Ketan's thread after installing TWRP? At the moment, my phone still has the OEM Unlock feature showing.
[Samsung Galaxy S9 & S9+ Cross Device Development] aussie1234:
SAMMOBILE download problem fixed

Same here. I setup an account but the piece of crap Sammobile site just changes my logged in status to 'Login' every time I try to select the firmware page.

SOLUTION: right click about the blue download S and select 'Open link in new tab'.

Thanks

Aussie
[Samsung Galaxy S9 & S9+ Cross Device Development] MSH2000FF:
I checked my developer options but I did not find OEM unlock as usual.

What to do ?

finished 7 day's.. not active
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
Did you restarted your device during that time?

Have you tried this?
[Samsung Galaxy S9 & S9+ Cross Device Development] MSH2000FF:
Yes sir.. Restart my device
[Samsung Galaxy S9 & S9+ Cross Device Development] cebs:
You can't restart your device cause the 7 days time will restart...

Try the zip file above
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
You need the firmware pieces (modem, vendor, boot sector, etc.) to match the system that you're reinstalling. When you went back to factory, you changed these. You need to match them again -- check the requirements for the rom you're restoring -- usually listed on the 1st few posts for the rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] NotATechnician:
That is what I thought, hence....

and

That means:

System

System Image

Data

Boot

Recovery

Baseband

There were no other options. Cache was always 0 anyway, but could have been excluded. The restore of recovery is clearly working because after reflashing the recovery from backup I am still able to boot into TWRP.

---------- Post added at 09:53 AM ---------- Previous post was at 09:37 AM ----------

Maybe this is my problem...? The system *is* the ROM, is it not?

Maybe I have the wrong expectation, by my expectation here is that TWRP would allow me to restore the Samsung ROM (system?) and data (and baseband, etc.) and/or the LineageOS ROM (system) (and data and baseband, etc...).
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
Ok... Using a bad analogy... System is like Linux. It is backed up. The missing stuff is like your bios. It is not backed up - I think the assumption is, it doesn't change so it doesn't need to be - to save space. You need to get it from the appropriate Manu ROM images or from another source. The 1st few posts of the ROM should tell you what Manu ROM is needed and usually what pieces. Usually, vendor and sometimes boot. I believe they're part of user low ship (of you unzip the ROM package).

Ps., another good place to find missing pieces is the soldiernnn roms. He often has flashable images of the factory/manufacturer pieces needed that will work for other ROMs also.
[Samsung Galaxy S9 & S9+ Cross Device Development] ralfgm04:
Guys I'm having a new problem. Haven't encountered anything like this. Don't know what to do.

I can't seem to backup my rom, everytime I press backup TWRP it just restarts. :(

Help please, I want to backup my current rom.

Edit:

I added a video so you can see my problem better.

>> https://streamable.com/crxkq (30 second TWRP clip)

Quick story:

My first rom was ambasadii, but it was battery hungry rom couldn't even last a day on it. After that I tried the soldier rom, not on my likings,

went back to ambasadii with my backup rom, deleted my backup afterwards.

Now I wanna try the new LightRom, couldn't install it cause I keep crashing on backup. So frustrating. :(
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
Just guessing....

Are you sure you have enough space for the backup?

Have you tried to repair your partitions? Or pull your sd card and do a chkdsk in Windows?

Some of your experimenting may have corrupted twrp. Have you tried a reinstall? Or maybe a reset to defaults?
[Samsung Galaxy S9 & S9+ Cross Device Development] ralfgm04:
Yup. I still got about 80gb left on internal.

Repair the partition, not yet.

Tried SD Card, didn't work also.

Tried reinstalling it, even installing a lower version on it, still nope. Tried resetting to default also.

I wanna try a partition fix, but I'm afraid it will destroy my current rom. (I'm not sure if what you're saying is what I'm thinking... Going to change partition system to i.e. from ext4 to ext2 then ext4 again?)

Thanks for the suggestions though.
[Samsung Galaxy S9 & S9+ Cross Device Development] ralfgm04:
Managed to fix it. Turns out my (system) was broken.

Thanks I guess.
[Samsung Galaxy S9 & S9+ Cross Device Development] davidk21770:
A corrupt system (or data) partition has caused me problems on several devices. A repair of both has become automatic for me when things seem flakey and I can't put a finger on it.
[Samsung Galaxy S9 & S9+ Cross Device Development] Myskiis2fast4u:
i've got a really really really dumb question that I haven't found an answer to..... and please forgive me because I've been on note 4 the last 6years!!! S9+ new to me.... The no-verity-opt-encrypt-samsung-1.0.zip that removes the samsung crap of RMM.......does this get removed when you wipe and format in TWRP? I'm ok on this lineage rom here but lets say I change over, I'm used to wiping and formatting EVERYTHING and then starting with the new rom. Will this remove that super special patch? Again sorry for asking newb questions........

TY
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Update available

* Fix selinux issues during formatting - dianlujitao

* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff

* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy

* Add option to uninstall TWRP app from /system - Dees_Troy

* Create digest for subpartitions - bigbiff
[Samsung Galaxy S9 & S9+ Cross Device Development] DeadPicsel:
Does anyone know if encryption and decrypting is working?
[Samsung Galaxy S9 & S9+ Cross Device Development] k2828:
i dont think so. no dev seems to need his s9 decrypted via twrp. really sad. i had to reflash everything multiple times because i was not able to flash bqck a twrp backup....
[Samsung Galaxy S9 & S9+ Cross Device Development] TheAKAlias:
how did you decrypt your internal storage? I have an encrypted sd card now as well, and TWRP does not wipe it.

Thanks a lot!
[Samsung Galaxy S9 & S9+ Cross Device Development] amakuramio:
where is latest twrp cant find on site.

edit: found it
[Samsung Galaxy S9 & S9+ Cross Device Development] amakuramio:
3.3.1 0 gives me some ecf??? partition error
[Samsung Galaxy S9 & S9+ Cross Device Development] D_Vovan_238:
Hi ?

Me too, but everything works :)
[Samsung Galaxy S9 & S9+ Cross Device Development] guacianiero:
sorry I performed the flash twrp procedure to install magisk on stock firmware only that I have problems in the configuration of the terminal probably due to the security measures implemented in the kernel. Can anyone please tell me a modified kernel for my stock firmware Android 9 Pie (G960FXXU6CSG8_G960FOXM6CSG5_ITV)?
[Samsung Galaxy S9 & S9+ Cross Device Development] dandreye:
Hi all, I'm trying to bring back to operation an ex-employee's SM-G965F, who upon surrendering it said the phone had no security enabled but apparently it's asking a PIN code, so I suppose it's no different than a lost/stolen phone as a result. Part 1 of the procedure instructs in particular to enable OEM Unlock, which I cannot do now. I tried booting into the Bootloader mode (Vol-/Bixby/Power) and can see FRP=ON and OEM=ON there. Do I get it right that if I go ahead and flash TWRP from this thread using the rest of the steps in Part 1 (and the n whole Part 2) thereby omitting the OEM Unlock enabling step I'll run into that 7-day freeze period or perhaps some other lock? A prompt reply would really help... Many thanks in anticipation.

Update

: all sorted using combination (factory binary) image flashed with Odin. Got FRP=OFF and OEM=OFF now, flashed stock ROM afterwards.
[Samsung Galaxy S9 & S9+ Cross Device Development] patuxco:
Hey guys,

Noob question here.

I've used this method in my SM-G960F using the following firmware:

Version	Android 9

Changelist	15367606

Build date	Wed, 20 Feb 2019 12:46:24 +0000

Security Patch Level	2019-02-01

PDA	G960FXXU2CSB9

CSC	G960FOXM2CSB3

Now I'm thinking about doing a clean install, and install the latest firmware available:

Version	Android 9

Changelist	16553818

Build date	Thu, 29 Aug 2019 01:49:24 +0000

Security Patch Level	2019-09-01

PDA	G960FXXS6CSH5

CSC	G960FOXM6CSH1

Will this method for TWRP still work with the latest firmware of the S9?

Thank you very much :)
[Samsung Galaxy S9 & S9+ Cross Device Development] philberto:
Worked fine for me on the + ?
[Samsung Galaxy S9 & S9+ Cross Device Development] patuxco:
Thanks, it worked :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Stucko:
Can the S9+ TWRP 3.3.1-0 image be used for the Note 9 as well? Has anybody tried, yet?
[Samsung Galaxy S9 & S9+ Cross Device Development] EagleSoldier:
Yes, should work
[Samsung Galaxy S9 & S9+ Cross Device Development] Stucko:
That would be awesome! Did you try yourself? I don't want to brick my N9, so I am extra careful. I wonder why they don't list the N9 next to the S9+ as a compatible device on the TWRP website if it can be used for both, that is why I asked if anybody tried so far.
[Samsung Galaxy S9 & S9+ Cross Device Development] EagleSoldier:
Ive read it somewhere in the telegram group.

Some guys use S9 recovery for there n9.

Join both Telegram groups and ask for it.

EDIT:

https://t.me/exynos9810

https://t.me/exynos9810roms
[Samsung Galaxy S9 & S9+ Cross Device Development] RICOS90:
Help me

help me i am facing an error on my S9+ G965N the message when i boot into twrp and if i want to backup a rom this message came.

'' FAILED TO MOUNT PRELOAD INVALID ARGUMENT ''

pliz can someone help me?
[Samsung Galaxy S9 & S9+ Cross Device Development] EsauMarduk:
Wonderful
[Samsung Galaxy S9 & S9+ Cross Device Development] Srbija2012:
What file did you flash prior to getting this error?

Try and flash stock OS via ODIN and see if it fixes it.
[Samsung Galaxy S9 & S9+ Cross Device Development] RICOS90:
Thankx.I ve returned to stock by flashing official firmware from sammobile.com. when I try to install twrp 3.3.1 I face the same error.and it made me not back up system at all. Try many twrp but nothing change.
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
A few things to try ( on twrp 3.3.1.1 )

In Mount menu try selecting preload partition.

Try in wipe menu - advance wipe - select preload - then swipe to wipe.

Should fix the failed to mount preload partition.

Or an earlier version than 3.3.1.1
[Samsung Galaxy S9 & S9+ Cross Device Development] RICOS90:
hello boss i ve try all twrp on thier web and i cannot select the preload in mount menu even in swipe menu i cannot select preload.thankx
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
According to twrp website, opening page, the latest release is 3.3.1.0. Some devices have version 3.3.1.1. The S9/S9+ Exynos version is 3.3.1.0 while the snapdragon version is 3.3.1.1.

I have seen a few issues about the preload mount error but nothing to really help you with in regards to twrp. Maybe someone else with a bit more knowledge can help or wait for a new twrp release.

Edit:

For me the Preload partition is somewhat of a grey area in regards to it's usage.

Quote:

OTHER PARTITIONS also CUSTOM or PRELOAD on some devices, it's used by stock ROM's, holding some preloaded system apps and regional settings which are installed on first use.

Taken from this thread:

https://xdaforums.com/android/general/info-android-device-partitions-basic-t3586565/post71782262
[Samsung Galaxy S9 & S9+ Cross Device Development] king200:
My S9 is coming tomorrow! I've read most of this thread.

Using WiFi, I will setup the S9 and have the Samsung and Google accounts set.

Do I need a SIM card to get TWRP procedure and install a ROM? Is the SIM necessary to do the Unlock in developers settings?

What I'd like to do is get the S9 completely configured before I use an active SIM
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
In general things you don't need to do for installing twrp, custom ROMs, root etc ( installation only ) :

Sim card

Setup of accounts

Basic setup as unlocking bootloader may factory reset phone

Internet access

The only thing needed is a fully unlocked bootloader.
[Samsung Galaxy S9 & S9+ Cross Device Development] king200:
Phone came to me. In Developer Options "OEM unlocking" has "Bootloader already unlocked". BUT, when I go into download mode, the state is "prenormal". Again, no SIM.

What should I do?
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
The rmm state being in prenormal will prevent you from flashing any unsigned Samsung firmware ie: twrp etc. Flashing will get the ' only official binary ' error crap to happen.

Generally you will have to wait 168hr for the rmm state to show normal or disappeared from download mode. It will also need to be connected to the internet using sim card or wi-fi.

To be able to flash ( twrp etc.) download mode will have to say:

RMM state : normal or dissappeared

KG state : checking

OEM lock : off

Maybe worth while after flashing twrp is to flash rmm bypass zip as well.

For more information about rmm state see this thread:

https://xdaforums.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535
[Samsung Galaxy S9 & S9+ Cross Device Development] gaww:
I suggest flashing a rom right after TWRP - one that has all the rmm and other crap handled.
[Samsung Galaxy S9 & S9+ Cross Device Development] king200:
I expected the 168 hours wait and was surprised when I saw the unlock off in developer options. I planned from the beginning to flash the Alexndr Dev base ROM https://xdaforums.com/galaxy-s9/sam...-development/rom-u1arc5-devbase-v5-2-t3764822 before I even bought the S9. I'll flash the 'no-verity-opt-encrypt-6.0-star.zip' before the rom even though I'm not sure that's necessary.

---------- Post added at 08:38 AM ---------- Previous post was at 08:26 AM ----------

I planned to flashing the Alexndr Dev Base ROM right away. I'm not sure I In need to flash 'no-verity-opt-encrypt-6.0-star.zip'. first. I've been using Alexndr rom in S7 for a couple years. Longest I've kept a phone from before 2012 when I participated in XDA.
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
The no-verity-opt-encypt zip ( new version out now 6.1 ) is to prevent your phone from being re-encryted after formatting your data partition. TWRP can still not handle encryption very well.

Personally I would flash the no verity and rmm bypass zips first even if the ROM has these features incorporated in them.
[Samsung Galaxy S9 & S9+ Cross Device Development] Haxomen:
Yeah crazy how twrp handles encryption. The whole storage dissapears and unmounts lol :D
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
Hopefully twrp can work with encrypted data in future versions.
[Samsung Galaxy S9 & S9+ Cross Device Development] lijianjunyonghu:
Want to join system_root
[Samsung Galaxy S9 & S9+ Cross Device Development] king200:
I followed your suggestion regarding "no-verify-opt-encrypt". I didn't want encryption anyway.

I flashed TWRP with Odin and booted directly to TWRP. Flashed the n-verify, Formatted data and then the ROM. I was amazed that it took almost exactly 168 hours before I could flash TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] sirucato:
no-verity-opt-encrypt

hello, where can I find the last no-verity-opt-encrypt to flash TWRP in my GS9+.

The link we have in the Part 2 - HOW-TO INITIALIZE TWRP is no-verity-opt-encrypt-samsung-1.0.zip

This 1.0 version is the last and right one?

Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] mb0:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

For anyone looking for updated no-verity-opt-encrypt file.

The file in the OP post wasn't worked for me but version 6 from the link did the job.
[Samsung Galaxy S9 & S9+ Cross Device Development] sirucato:
Thanks buddy
[Samsung Galaxy S9 & S9+ Cross Device Development] alejobog:
Does it support android10?
[Samsung Galaxy S9 & S9+ Cross Device Development] coolbat07:
Rooter__Vernee_ smartphone x2_euro

Good evening,

I would like to root this phone of the brand Vernee manufacturer model X2_euro (X2_eiro_EEA) chipset MT6739WW

I CANNOT ROTATE it with the classic apk how to proceed because then I would like to flash it and choose a rom having all the cards in hand for

get to my end find the original firmware in case of glitches, and find the right rom to flash it take the right recovery also TWRP seems to me the most appropriate ..

Thank you to the forum and helpers because very novice in this area and especially not to make missteps?.?. (Lol)

Changed by coolbat

writing error
[Samsung Galaxy S9 & S9+ Cross Device Development] dayonbochnia:
Hello.

I really need help.

I got Android 10, and did everything as oriented. But I'm stuck in Settup Connection on Odin.

<ID:0/006> Added!!

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

<ID:0/006> File analysis..

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

<ID:0/006> SetupConnection..

And that's the only thing that happens in my Odin whenever I start the process. Sometimes it shows the message "Odin can't open the serial(com) port".

I've tried disconnecting. I tried changing USB ports, chaging USB cable. I even tried in another computer with USB 2.0.

I've tried installing, uninstalling Kies, Smart Watch, Samsung Drivers and everything...

I've downloaded several versions of Odin. Tried with compatibility mode (Win 7, Win XP), but no success...

I've tried flashing different archives too. And always the same message: SetupConnection..

What should I do?
[Samsung Galaxy S9 & S9+ Cross Device Development] Misterjunky:
re: Odin

You need to install or re-install the Samsung usb drivers for mobile phones in Windows

and reboot the phone. For best results use the usb cable which came with the phone.

Here is the official download link:

https://developer.samsung.com/mobile/android-usb-driver.html

Good luck, have a great day!

---------- Post added at 07:57 AM ---------- Previous post was at 07:48 AM ----------

This forum and this thread are only for SAMSUNG Android phones.

Your phone is a Motorola so nothing here will be of any use to you.

Have a great day.
[Samsung Galaxy S9 & S9+ Cross Device Development] dayonbochnia:
But I've already downloaded and installed every possible version of the drivers. And also, I'm using both of my original cables and have already rebooted my phone...

Still stuck in SetupConnection or Can't open the serial(COM)port.

:confused::crying:
[Samsung Galaxy S9 & S9+ Cross Device Development] Deadman26:
Hello guys.... I unlocked the bootloader but have any waiting period and I factory reset my phone and booted back before flashing twrp... should I factory reset and flash twrp ?or lock and unlock OEM again and flash twrp.. I'm just being cautious cause I've not done this on exynos chipsets