yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] mauricio.hs12:
You may change the usb port on your PC.
[Samsung Galaxy S9 & S9+ Cross Device Development] [Acme]:
Could I install TWRP in my S9 (Exynos SM-G960F) using the official app?

What would be the process? Install the app, download twrp and flash it?

Thanks in advance!
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
Yes you can but twrp requires root access to work properly.
[Samsung Galaxy S9 & S9+ Cross Device Development] [Acme]:
Thanks for your reply.

Then I can but I shouldn't.

I will do it using Heimdall.
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
I can't help with using Heimdall.

Not sure what your asking for?

Installing twrp is basically via OP.

Since there no official twrp for Android Q following the procedures leads me to getting stuck on second Samsung logo and not going any further. So, on Q, Formating Data is causing me issues booting to the system.

If you want root you will have to use the patch method.
[Samsung Galaxy S9 & S9+ Cross Device Development] [Acme]:
I was asking about install twrp using an alternative way.

OP??? What is it?

Do you have any tutorial about patch method?
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
OP is the person that started this thread ( or any thread ). ie: first page first thread.

Any alternative methods of installing twrp that I know of still need Odin at some point.

Installing Magisk patch method

https://topjohnwu.github.io/Magisk/install.html
[Samsung Galaxy S9 & S9+ Cross Device Development] j1gga84:
Hello everybody,

I cannot install the recent canary builds of EdXposed anymore in TWRP (error 123, zip file cannot be extracted).

I am using latest TWRP, could magisk be the problem?

Any ideas?

Edit:

A new update of magisk manager solved the issue.

Regards

Sent from my SM-G960F with Tapatalk
[Samsung Galaxy S9 & S9+ Cross Device Development] Srbija2012:
I must be living under a rock, TLDR:..

I have TWRP 3.3.1-0, but some roms request you downgrade to 3.2.3-0 before flashing their ZIP.. Can someone explain why?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
I read this comment in the Exynos 9810-group on Telegram: "TWRP 3.3.1 is broken and causes most bootloops because encryption is f****d. 3.2.3 always boots and fixed most bootloops for me."

I'm on LOS 17.1 and use a modified vendor that doesn't force encryption, and so far TWRP 3.3.1.0 hasn't failed me. Encryption on or off is apparently the key.
[Samsung Galaxy S9 & S9+ Cross Device Development] Srbija2012:
Thanks mate . Would downgrading be a simple as flashing 3.2.3 via Odin and then rebooting the phone?
[Samsung Galaxy S9 & S9+ Cross Device Development] :
Yes, it's that simple. Flashing the correct .img-file with TWRP itself should also work.
[Samsung Galaxy S9 & S9+ Cross Device Development] Srbija2012:
.IMG or .IMG tar?

Had no idea you could upgrade/downgrade TWRP within itself... And I've been flashing ROMs for years... LoL
[Samsung Galaxy S9 & S9+ Cross Device Development] :
I've downgraded from within TWRP in the past several times, no problem. Can't image the newest version would prevent downgrading, but hey, even programs get smarter by the day. ?

You need the .img-file if you want to use TWRP and the .tar-file if you want to use Odin.
[Samsung Galaxy S9 & S9+ Cross Device Development] Srbija2012:
Again, thanks legend....
[Samsung Galaxy S9 & S9+ Cross Device Development] Tarar:
I have tried each and every thing as described but every time i reboot to the system after sideloading the no vrrity file via adb (mtp isn't working for me due to some reason) phone keeps displaying the samsung logo and doesn't boot to the system. i am on one ui 2.0. any idea what's happening here? i am using the latest no verity file.
[Samsung Galaxy S9 & S9+ Cross Device Development] BigDawg443:
Having the exact same issue too. Downloaded the latest no-verity-opt-encrypt-6.1.zip and flashed it then after that flashed Magisk v20.4 and still the same issue. Tried just booting it up after only flashing the no-verity-opt-encrypt-6.1.zip but still no good
[Samsung Galaxy S9 & S9+ Cross Device Development] mindstorms54:
Is it possible to mod the recovery, to add the function of decrypting Android q encryption?
[Samsung Galaxy S9 & S9+ Cross Device Development] spawnlives:
While I do believe there is work going on with Android Q but I have not seen a version that can decrypt data yet.

While I do have Magisk and Exposed installed it still does get around the encryption issue.

So I guess it will be a waiting game for twrp with Q support unless you can revert back to pie.
[Samsung Galaxy S9 & S9+ Cross Device Development] Racoonator:
Android 10

Hi all,

I flash my S9 sm-960F with the latest rom on Android 10 from my mobil phone provider (https://www.sammobile.com/samsung/galaxy-s9/firmware/SM-G960F/FTM/download/G960FXXS7DTB5/328264)

After I flash TWRP 3.3.1 in the goal to install magisk.

First install of TWRP is ok, I reboot in recovery and install dm-verify as said in the procedure with success.

At this step I don't try to install magisk, just reboot phone, and I stay stuck on SAMSUNG logo with blue led flashing.

I wait around 20 minutes, but nothing happen. To unblock phone I've to flash the stock rom again.

What am I missing to make TWRP and rom working together ?

Regards
[Samsung Galaxy S9 & S9+ Cross Device Development] Misterjunky:
Your problem is that after you flash the rom and install twrp you need to install dm-verify.zip file and then the proper bootloader zip file BEFORE you the phone reboots.

(flash the bootloader LAST because it will auto reboot your phone automatically after flashing.)

Good luck, have a great day!
[Samsung Galaxy S9 & S9+ Cross Device Development] Racoonator:
I found this tutorial on youtube : https://youtu.be/eaiyarH2CoQ

I tested it and.. it works !

So after the first reboot of TWRP, instead of flash dm-verify I installed this : Multi_Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip

This file is provided by the man who make the tutorial, the link are in the video. With this file, everything work perfectly ! No problem to install Magisk 20.4 too

Regards
[Samsung Galaxy S9 & S9+ Cross Device Development] Overload87:
Bootloader Coding

I want to ask why TWRP can't made, some like an Android bootup an Phone with Costum or other Roms, Kernel a.s.o.

?

Would love to Boot Phone Roms by USB-micro Flash-Device,Stick, SD Card with Micro USB Adapter and so on..

IV GOT 1X Samsung S5(rooted) ,

HUAWEI P10(STOCK ROM)

AND SAMSUNG S9Plus!

If i could help with that Project, Iam Willing to Do whatever helps.

Just Wright me, Thanks for all your work!

If Dual Patcher would realy works fine that would be very ery nice
[Samsung Galaxy S9 & S9+ Cross Device Development] GalaxyS9User:
I am also stuck exactly there. How did you get out of the Samsung logo and what did you do next?

---------- Post added at 11:14 AM ---------- Previous post was at 11:08 AM ----------

I am also stuck exactly there. How did you get out of the Samsung logo and what did you do next? :crying:
[Samsung Galaxy S9 & S9+ Cross Device Development] stefano2626:
Read carefully the post you quoted. He flashed the official rom to unblock the phone
[Samsung Galaxy S9 & S9+ Cross Device Development] coolbat07:
rom stock vernee X2_euros

hello ,, I'm looking for the original stock rom of the X2 vernee _euros Android 9.0 pie or I can download it because I would like to root my phoneI would like to root this phone of the brand Vernee manufacturer model X2_euro (X2_eiro_EEA) chipset MT6739WWthank you: D
[Samsung Galaxy S9 & S9+ Cross Device Development] BackToAndroid:
I'm unable to take back up using twrp. I'm trying to take back up of system, system image, data, base band, carrier, boot and vendor image.

But no matter how many times I tried all I get error is backup failed. I tried on sd card s well as otg pen drive.

There is no other error, can some one help
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Try to do separate backups. So a nandroid backup (boot, system and data) and then others apart from that, if you need anything else.
[Samsung Galaxy S9 & S9+ Cross Device Development] apaxtc:
insert image

Multi_Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip is special for S9+ G965F ? I can also use it for G960F ? has anyone tried / works ? thx :)

I'm solved ,

pretty good video tutorial

but I didn't use it file bay user video produced I used no-verity-opt-encrypt-6.1 bay Corsicanu file for my fone G960F.
[Samsung Galaxy S9 & S9+ Cross Device Development] baderlyon:
Hello,

A few days ago I installed the latest TWRP version on my S9 + running Android 10 and then rooted it.

Everything worked fine until today when I tried to make a backup of my system, I discovered a big problem in the TWRP; the backup repeatedly fails!

I also note that it is impossible for me to mount my partition "/ data"!

I have lots of error messages like:

could not mount / data and unable to find crypto footer

failed to mount '/ data' (invalid argument) ...

I tried a solution which consists in repairing and changing the extension of the partition but without success.

Is there anyone who has encountered this problem or who can help me find a solution?

Thank you
[Samsung Galaxy S9 & S9+ Cross Device Development] apaxtc:
look here or try https://xdaforums.com/galaxy-s9/sam...covery-sky-hawk-recovery-project-2-2-t4097709
[Samsung Galaxy S9 & S9+ Cross Device Development] sexler:
Hello,

I got a question about TWRP for the S9. Maybe I get something wrong here.

So, I tried the latest version of TWRP and also version 3.2.3.0 which I have currently installed. I am also using LOS 17.1.

I installed TWRP exactly as described on the first page with the zip file (dm-verity and force encryption disabler). After that I installed LOS 17.1 and can reboot into system to complete the first time setup.

After I install a ROM the decryption in TWRP fails and I am unable to mount the storage partition. I read that this is a commonly known error (Samsung encryption). But I am able to use TWRP to install Magisk and enable root on my device. But it is not possible to install other files, for example NanoDroid. I got an error that the data partition cannot be mounted.

Is this because of the failing decryption?

So, I cannot use TWRP to install files that need the data or storage partition to be mounted. Is that correct (ADB sideload doesn't work, too)?

Thank you for your help!
[Samsung Galaxy S9 & S9+ Cross Device Development] mrjoy:
Hi. I need emergency help. I'm new on s9+ & flashed twrp as well formatted data partition then flashed no-verity-opt-encrypt-6.1 but whenever entered to system then returned to recovery mode then i lost internal storage again again & again. Please help me. I'm on latest android 10 firmware.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I don't know this problem but would try to start all over again. And I would double check if I have twrp and os for the right device.
[Samsung Galaxy S9 & S9+ Cross Device Development] sexler:
As far as I understand it this is normal because TWRP is not able to decrypt the storage or data partition on Samsung devices after a system is installed and has encrypted the partitions.

The data partition becomes available again when you format it with TWRP and install the no-verity-opt-encrypt zip-file again. But, of course you’ll lose your data.
[Samsung Galaxy S9 & S9+ Cross Device Development] slarti76:
TWRP 3.4.0

Any interesting news with 3.4.0?

https://twrp.me/site/update/2020/06/...-released.html

From the changelog, looks like Samsung encryption still not supported, right?
[Samsung Galaxy S9 & S9+ Cross Device Development] poker1234:
Hy 1 question ist this file no-verity-opt-encrypt-samsung-1.0.zip from post 3 up to date ? or where i find the newest version of that file for the s9+ with android 10 one ui 2.1 ? hope someone can assist me
[Samsung Galaxy S9 & S9+ Cross Device Development] strapy:
tray to look here

https://www.androidinfotech.com/no-verity-opt-encrypt-versions/

https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Samsung Galaxy S9 & S9+ Cross Device Development] Hung Kings:
My phone s9+ stuck boot after restore backup rom android 10 with twrp 3.3.1.1. How to fix ?.:crying:
[Samsung Galaxy S9 & S9+ Cross Device Development] lordsolrac2:
Make sure you have an updated vendor image. Though this also happens if part of data is missing, at least for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] mb0:
Check this from DevBase ROM. I hade some problems with restore because i backed all the partitions that i saw on TWRP and restored all
[Samsung Galaxy S9 & S9+ Cross Device Development] elenhil:
Guys, please help: installing no-verity-opt doesn't remove forced encryption on custom OS installation. Is there something I'm missing?

UPD: Apparently, it was an outdated fix. Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip did the trick.
[Samsung Galaxy S9 & S9+ Cross Device Development] sacharja:
>Enable software encryption support (general AOSP only, Samsung method remain unsupported)

Any plans on implementing this or anything one can support or test? Even limited support for a Magisk patched stock would be awesome, where the add. Samsung checks should be disabled.

(I can only use stock [cannot downgrade BL] and use TWRP just for full backup / restore, with disabled encryption I can not even use any form of screen lock)
[Samsung Galaxy S9 & S9+ Cross Device Development] kevin#34:
does this 7-day buffer period applies to all Samsung S9 960F/960F DS, or just to enteprisese devices?

thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] AudioMiner:
No, if your seriously trying to get your "S9 or S9+" to work with "RMM" in "checking State" and flash TWRP follow my procedure::

VERY FIRST THING THOUGH IS TO MAKE SURE OEM IS ALREADY UNLOCKED OR BOOTLOADER IS "UNLOCKED" very imporant

1. Re-Flash Samsung Stock Firmware to "JUST" on Stock through odin (Download from Samsung Website)

2. Let phone sit for 30 min on after entering OS state

3. Reboot Device, again let phone sit on for 20 more minutes afterwards

4. Check about phone and make sure Developers settings is not showing, but Hidden. "Make sure your Bootloader is Unlocked after checking this through odin mode" very imporant

5. Power back on to TouchWiz OS, Now you want to play with your phone a bit go watch youtube videos or download large files, the whole point is to get Samsungs servers to see your device serial number and push its so called big update to your phone. At this stage you should of seen a toast that says "Device Verified". It quickly dissapears so keep your eyes peeled. Once 500mb of data has passed through you should see sammys big updater wanting you to download.

6. Power off device and then boot into odin mode again

7. Rmm should now say Status "Checking"

You can now flash TWRP and then Format device - Type "YES"

MAKE SURE DEVELOPERS OPTIONS IS NOT SEEN DO NOT OPEN IT THROUGH BUILD NUMBER UNTIL YOUR DEVICE HAS SAT FOR 3 DAYS AFTER FLASHING A CUSTOM OS OR YOULL BUMP THE LINE AND IM NOT SURE IF REBOOTS START UP OR SLOW PROCESSING

Hope this helps
[Samsung Galaxy S9 & S9+ Cross Device Development] kevin#34:
thanks!

can be this, the reason why each time I try to reboot my S9 960F in TWRP recovery mode,the Samsung recovery overwrite the TWRP one?? :(
[Samsung Galaxy S9 & S9+ Cross Device Development] sacharja:
>Last Updated 2018-08-15

Seems this is dead here

---------- Post added at 11:58 PM ---------- Previous post was at 11:57 PM ----------

>Last Updated 2018-08-15

Seems this is dead here
[Samsung Galaxy S9 & S9+ Cross Device Development] duplicationcube:
I managed to get TWRP installed, then flashed no-verity-opt-encrypt-samsung-1.0.zip

But I can't get magisk to work... "Unable to repack boot image!"

What's up with that?
[Samsung Galaxy S9 & S9+ Cross Device Development] r0nr:
Galaxy S9+ exynos

- Original vodafone firmware (android 10)

- Latest TWRP: twrp-3.4.0-0-star2lte.img.tar

- Latest Magisk: Magisk-v21.1.zip

- Latest no-verity: no-verity-opt-encrypt-6.1.zip

1)

Question: What do I need to check below.

If I want to wipe to clean state, what can I check below in order wipe to clean state.

(Assuming I have a full backup ready so I can restore that backup)

[ ] Dalvik / ART Cache

[ ] Cache

[ ] System

[ ] Vendor

[ ] Data

[ ] Internal Storage

[ ] Preload

[ ] Micro SD card (I never wipe this)

[ ] USB OTG (I never wipe this)

In (some) other devices I could not wipe the "system" partition if I wanted to restore a backup which included the system partition.

It would end up in the device getting stuck in the boot animation. (samsung A5, 2016).

The only way to make it work is NOT to check the system partition and restore full backup (overwriting the existing system partition)

then the device would boot.

In other devices (moto g5) I could check all the items and restore a full backup.

2)

Question: What do I need to check below.

If want to restore a full backup are the items below checked correct?

(I backupped system image AND system, just in case. But I am restoring system image only, not system).

Take note of ODM image and ODM, do I need to check them both or is ODM image sufficient?

[v ] Boot (55 MB)

[ v] Recovery (64 MB)

[ v] Cache (0 MB)

[ ] System (4073 MB) <====== not checked, because "system image" is checked

[v ] Vendor (559 MB)

[ v] Data (excl. storage) (0 MB)

[ v] System Image (4400 MB)

[ v] Vendor Image (650 MB)

[ v] ODM Image (646 MB) <===== check this AND "ODM"?

[ v] Baseband (50 MB)

[ v] EFS (2 MB)

[ v] ODM (579 MB) <===== check this AND "ODM image"?

3)

Question: Did I take the correct path?

I have tested the following, which boots the backup

Step 1, Format Data first

(because of error: Failed to mount '/data' (Invalid argument) , when I try to wipe. Doing a Format Data first and then do a wipe seems to work)

Step 2, Wipe

Dalvik / ART Cache , Cache , System , Vendor , Data , Internal Storage , Preload

Step 3, Restore

Boot , Recovery , Cache , Vendor , Data , System Image , Vendor Image , ODM Image , Baseband , EFS

(Did NOT restore ODM only restored ODM Image).
[Samsung Galaxy S9 & S9+ Cross Device Development] Tarar:
Did anyone try rooting with the latest TWRP 3.5.0_9-1 and One UI 2.5? I have tried disabling encryption with multiple files and no one seems to work. Here's what i have tried

Installed new stock firmware

Flashed TWRP lastest version

Formatted Data and rebooted into the recovery

Installed no-verity-opt-encrypt 6.1 Failed

Installed Disable DM Verity Forced encrypt 11-4-2020 Installed but upon rebooting, phone stuck in loop.

Can anyone help please?
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
I have recently tried to flash "no-verity-opt-encrypt 6.1" with TWRP 3.5.0_9-1 under Android 10 and also failed. Afterwards, I flashed TWRP 3.4.0.0, repeated my attempt with "no-verity-opt-encrypt 6.1" and succeeded. My conclusion is that TWRP 3.5.0_9-* is only suitable for Android firmware

<

9, while TWRP 3.5.0_10-* (once available) will be suitable for Android firmware 10. In the meantime I stick to TWRP 3.4.0.0. "One UI 2.5" seems to be based on Android 10.

Please also have a look at the release notes of TWRP 3.5.0.
[Samsung Galaxy S9 & S9+ Cross Device Development] falciatrice10:
Hi guys

I tried to root my galaxy s9+ android 10

I downloaded a firmware from frija and made a clean installation

I installed twrp

I made a full data wipe, but it givee errors

I tried to install no-verity-opt-encrypt-6.1.zip but got error also

finally i installed magisk, with no errors

Root checker says that root is ok.

Now my phone reboot many times a day for no reason

Do i need to redo the entire operations ? And how to avoid these errors (i tried 3 times with same result)
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
The errors referring to the "data" partition are probably due to the fact, that TWRP cannot (yet) read an encrypted data partition under Android 10 firmware. What revision of TWRP did you install?

This is the error I was referring to in my previous post.

As the frequent booting is concerned, I can only speculate on the reason. Nevertheless, for more experienced members it might be interesting to know, if you are talking about a boot loop or "just" random boot events.
[Samsung Galaxy S9 & S9+ Cross Device Development] falciatrice10:
1. I flashed TWRP 3.5.0_9-1

2. it's just a random restart .
[Samsung Galaxy S9 & S9+ Cross Device Development] Tom1369:
Have you read the second and fourth paragraph of the TWRP 3.5.0 release notes?

I think you should better use TWRP 3.4.0.0 with your Android 10 phone rather than TWRP 3.5.0_9-1 which is targeting Android

<

9. I am not an expert, but maybe afterwards your random restarts are gone. Crossing my fingers.
[Samsung Galaxy S9 & S9+ Cross Device Development] falciatrice10:
Thanks man

I'll try it and inform you about result
[Samsung Galaxy S9 & S9+ Cross Device Development] Philipp_:
I installed TWRP over LOS recovery but TWRP now can't decrypt the phone. I put in the right pattern, but it still says "Unable to mount storage".

What can I do? Thanks
[Samsung Galaxy S9 & S9+ Cross Device Development] mazur38:
привет

Translation: Hello
[Samsung Galaxy S9 & S9+ Cross Device Development] Emanuele77:
Hello
[Samsung Galaxy S9 & S9+ Cross Device Development] nightmare1942:
Hi guys,

I have a problem flashing TWRP.

I installed newest stock FW G965FXXUFFUE1 with ODIN 3.14.4.

Bootloader was already disabled (from before) and show it is in disabled state.

I downloaded TWRP 3.4.0-0 (because the 3.5.x are not working for A10 as mentioned above) and I tried to install it via ODIN in AP mode.

After pressing Start it fails with message "Only official released binaries are allowed to be flashed(RECOVERY)"

Why is this happening?

Edit:

Nevermind....It seems that the KG State was Prenormal even though the "OEM unlock" was showing in dev options.
[Samsung Galaxy S9 & S9+ Cross Device Development] Rustdroid:
Just letting people know that if you have RMM prenormal on Android 10 it will be like that for good. I'm stuck on RMM prenormal on 10 and have waited over 168hours about 5 times before restarting device to check and would never change. 10 uses Knox guard instead of RMM, my KG state changes fine and gives me option to unlock bootloader but RMM always prenormal so can't flash anything.

hopefully Samsung fixes it one day for now I'm stuck on stock.
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Hi all

Hiya

need some help please with my S9 starlte

I flashed TWRP with Odin, apparently successfully and I can boot into recovery easily.

Booting to download mode shows FRP and OEM locks are OFF, Secure boot = enabled

I did not flash dm-verity or anything as i wanted to put Lineage OS on it

However if I then try to flash the Lineage ROM it throws the error

Failed to map file 'external_sd/lineage-18.1 (etc)

Error installing zip file 'external_sd/lineage-18.1 (etc)

plus..

failed to mount 'cpefs (RO file system) but I dont know whether this is significant

This looked like a TWRP error, but I have tried it with every version I can find for the S9 .

The stock meanwhile is stuck in a bootloop (and it still shows 'secured by knox' and cannot even turn it off, so im waiting for the battery to die!

Any ideas to fix? in theory I could reflash stock through Odin, but I sort of think the same issue will recur....(Iive posted this i=on the cross-dev thread, but actually i think it may be a TWRP exrts - but apologies for posting in two different placesl..)

UPDATE - using 3.4.0.0 I can successfully flash the ROM, that is TWRP does not error.

Previously I had cleared cache and dalvik and repaired the system parturition using the EXT2/EXT4 flip.

Buti still stuck in boot loop!

Any ideas appreciated
[Samsung Galaxy S9 & S9+ Cross Device Development] Rustdroid:
Did you format data ?
[Samsung Galaxy S9 & S9+ Cross Device Development] waynea:
Hi - yes, did wipe > format data, then reflashed the ROM followed by Gapps11 pico.

Still stuck I'm bootloop. Incidentally I see that the system partition is not mounted. But putting a tick on this box and reflashing makes no difference.. Still stuck in bootloop