yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Panzotti:
Hi, I need some help from you guys. I flashed TWRP following the tutorial on the first post on my G930F running samsung stock ROM (Oreo) and got an error about not being able to mount /data. I rebooted and got the verification fail error. When I reboot to TWRP it appeared for a short while, threw a bunch of errors and reboots. I tried installing my previous stock rom back with Odin but it fails while flashing System. I also tried flashing a Nougat stock ROM but it will also fail, giving a SW REV error: Devie: 2, Binary: 1.

I don't know what else to do. I hope someone can point me in the right direction.

Cheers!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
You need to format data in TWRP

Note: You lose all data
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Panzotti:
Thanks for replying. The problem is I can't make TWRP work. When I access TWRP it shows a list of errors and reboots. I've tried reflashing TWRP, which it does without errors, but when I access it again I get the same result.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] wegiwegi:
Maybe this is a stupid question, but are you sure that you have the right twrp version for your model??? if I remember well, that base one for the S7 was 3.0.2.4 to start with
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Panzotti:
I'm using the image I downloaded from TWRP site for this phone: twrp-3.2.1-1-herolte.img.tar

I managed to make TWRP work again and tried formatting data, for which I got the following errors:

Could not mount /data and unable to find crypto footer.

Failed to mount '/data' (Invalid argument)

Unable to recreate /data/media folder.

Updating partition details...

Failed to mount '/system' (Invalid argument)

Failed to mount '/data' (Invalid argument)

...done

Unable to mount storage

Failed to mount '/data' (Invalid argument)

Full SELinux support is present.

Unable to mount /data/media/TWRP/.twrps

MTP enabled

Formatting Data using make_ext4fs...

You may need to reboot recovery to be able to use /data again.

Updating partition details...

Failed to mount '/system' (Invalid argument)

...done

Then I tried Changing File System to /data applying this method:

"Fix: In TWRP recovery, go to "Wipe", select "Data", press "Repair or Change File System", press "Change File System", press "EXT3", and do "Swipe to change". Then repeat the same steps, except this time "Change File System" back to "EXT4" instead of "EXT3"."

But also showed errors (as below):

Updating partition details...

Failed to mount '/system' (Invalid argument)

...done

Hope someone has gone through something similar and can help.:confused:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Panzotti:
Update: I ended up performing a deep-clean-flash (with PIT file) as described in another post and managed to go back to my Oreo stock ROM.

Thanks for all your help anyway. ;)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] jimbobmcginty:
I had the same problems with various partitions not being mounted inside TWRP, I followed your steps right up to changing /data back to EXT4 - I left it as EXT3.

I installed twrp-3.2.1-1, tried to wipe, but got the red "can't mount" errors in TWRP, then got the Samsung "You need to factory reset" message.

Ignored that and held power button and selected to restart.

While restarting held power+home+vol-up to get back into TWRP.

Then changed the /data partition to EXT3. Then I flashed Magisk 16.0, and then flashed no-verity-opt-encrypt-6.0.zip, and the wiped dalvik/cache.

Then reboot to system remembering not to opt to install TWRP manager etc....

Has just booted without problem. Note this is on Android 7 / Nougat. I'll update to 8 / Oreo and try again.

(update)

I've found this trick (to get it to boot) works for both Nougat and Oreo, however I can't get no-verity to work, on the first boot it re-encrypts /data, and system is not RW even using a root explorer.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Phantom Thief:
So in short there's no need to unlock bootloaders like xiaomi devices do, right? Also do you really need to wipe data like the video linked in the OP? My girlfriend's S7 is using nougat atm. I wanna install TWRP and Magisk.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Domino5:
[MENTION=5672995]jcadduono[/MENTION] we still have the same bugs since 3.1.1-0 some zips don't flash correctly and I see all the time "e: recv error on uevent" please do something about it :rolleyes:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] xanderovitch:
Hello there, is latest version working with Oreo stock?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
Version 3.2.2-0 has been released. It fixed the errors I was having with back-ups
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] jioleight:
international variants are unlocked by default. Just knox getting tripped.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Phantom Thief:
Thanks. But is it really a must to wipe data in order to just flash a recovery and then magisk?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Pat750:
If you want to modify the system partition (like deleting system apps) and also make backups with TWRP then you have to format data like you saw in the video.

No need to use dm-verity zip if you use Magisk though (only with SuperSU).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] rajputz:
Hi guys. I used ODIN to install twrp on my samsung s7. Everything worked fine, untill i tried to do a wipe. I too got the following errors.

Could not mount /data and unable to find crypto footer.

Failed to mount '/data' (Invalid argument)

Unable to recreate /data/media folder.

Updating partition details...

Failed to mount '/system' (Invalid argument)

Failed to mount '/data' (Invalid argument)

Without knowledge I did a complete format. I then mounted the partition and installed lineage 15.1 Ivans rom.

After few minutes of testing and playing, I flashed with ODIN, my stock rom india version. Everything went fine untill i noticed: -

1. Samsung Pay, Samsung Health and Secure Folder are not working.

2. My current service provide, JIO cannot work on my phone. I can use data over volte and receive text, but cannot make or receive calls or cannot send a text. I went to service center and they told me that every sim except jio will work on my phone. Now i am using a new operator.

Is there a way I can use samsung pay, samsung health or samsung secure folder again. I tried flashing stock rom again but of no use.

When I reboot into Android Recovery it shows

Is there a way to install official recovery now?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kiss4luna:
E:recv error on uevent
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
When you slap on this error without some explanation, I gather you want a solution? If you'd bothered to read just a few posts back, you'd have found that the new version 3.2.2.0 works errorless. It worked for me.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kiss4luna:
Well, I think everybody is trying the 3.2.2.0 now.

Yes, it's 3.2.2.0 I'm using and the Galaxy S7 without a doubt in this section of the forum.

I don't think there IS a solution to this currently because many people have the similar error since 3.2.1.0 when 3.1.1.0 works fine.

Both internal and external storage formatted and reset, it still occurs when trying to backup system data.

Any solution I missed? I beg you to show me the exact post. Will be extremely appreciated.:o
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
I had the same error as you with 3.2.1.0, flashed the new version and gone was the error. So I can't help you there.

In general: if you'd written in the first place what you wrote in answer to my reaction, not only would that have been the polite way to post a bug but it would also have been directly clear with what version you were having issues. :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kiss4luna:
Well, I think that's just a misunderstanding for both of us.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Nevaran:
Ok after a painful 2 days of messing around, i figured out that internal storage 0mb bug/glitch/whatever happens if you install original rom and then root it(installed mine from sammobile).

Now using Dylan's S7 rom, and the internal storage in twrp is showing correctly, and able to do backups
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ripee:
TWRP 3.2.3-0

I don't mean to impose, but I went ahead and built 3.2.3-0 for herolte, hero2lte, heroltekor, and hero2qltechn, from the official device trees developed by jcadduono. These can be considered official because they're from the same sources as the builds that will be released on twrp.me:

twrp-3.2.3-0-herolte.img

twrp-3.2.3-0-herolte.tar

twrp-3.2.3-0-hero2lte.img

twrp-3.2.3-0-hero2lte.tar

twrp-3.2.3-0-heroltekor.img

twrp-3.2.3-0-heroltekor.tar

twrp-3.2.3-0-hero2qltechn.img

twrp-3.2.3-0-hero2qltechn.tar
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MalharB:
I am already rooted. If I install .img file in recovery , do I still need to flash dm-verity zip ?

And also if I flash .tar through odin, do I have to flash dm-verity

Thanks
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shaggyskunk:
What method did you use for Root?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MalharB:
Magisk
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shaggyskunk:
Well you had to use TWRP to Flash Magisk.. So I'm not sure what the issue with Flashing TWRP is? Are you just asking about updating the version of TWRP?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] super_nooby:
[MENTION=6005084]ripee[/MENTION]:

big thx for your work, but for me the error still exists. I've to reflash 3.1.1.0 through odin. this is the only version that works for me. :confused:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MalharB:
Yes I am asking about updating
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shaggyskunk:
If you're just updating the version of TWRP - Boot into Recovery & Flash the img - (Tab) Bottom right on the Install Screen in TWRP - Flash img & Select Recovery - Done ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MalharB:
Thanks
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] exnokiafan:
Same problem here. I was on ambasadii OREO + TWRP 3.1.1 and everything was fine. Yesterday I updated to 3.2.2 TWRP after flashing a fresh ERG2 stock Oreo.

So the steps were: flashing stock oreo, flashing TWRP, booting into TWRP, swipe to allow modification, FORMAT data, applied opt verity patch, flashed magisk and then rebooted.

This morning I woke up, I turned the phone on and went into twrp to reinstall some backups I made and voilà, SD=0.

DAMMIT!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Nktnet:
Edit: Woops wrong thread sorry.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Droiderat:
You state "format data"; I have found success by changing the data format from ext4 to ext2, and then back to ext4. That may/may not be the same as what you are doing. Since you are using Magisk, I don't believe you need to use the verity patch. Finally, I found that I need to use a custom kernel to solve the TWRP data=0 issue. I use the TRP kernel (current version is 6.6.0, and it is very stable); it includes Magisk.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] devilhunter47:
Any chance of a changelog. I'm on 3.2.2 now. Want to know if I should upgrade
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ripee:
Not until TeamWin posts some info about it.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] exnokiafan:
A custom kernel might be the solution but I find the latest stock one to be the best I've ever used :)

Can you please describe in detail what you have done?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fracarol:
Deleted
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] gnogno1985:
Hi,

is it possible have root with this method without loosing my data?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tkkg1994:
Hey guys :) :highfive:

Some may know me, some probably not. It's not important who I am BUT I found that our device tree for TWRP builds is damn outdated (based on MM).

I don't know if you faced this issue already, but some people couldn't mount /data partition in TWRP even though they removed encryption. Why this happens?

Explanation:

Samsung added quota support in their oreo update for the /data partition. Means a TWRP update with proper quota support is needed to get this new feature to work. Till now, many developer simply disabled this feature again on their kernels (so they can mount /data without issues on the old TWRP).

What I did:

I updated the tree with the latest files, kernels and so on. Including the above mentioned quota support.

This TWRP version works on stock and supported oreo kernels. Older kernels (which removed quota to fix mounting problems) won't work here. Please advice your kernel developer to update his kernel with the changes :good:

Download:

Img file (flash via TWRP)

tar.md5 file (flash via odin)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] maumaus:
I really appreciate it. Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ALIGATOR26:
Thank you!!![emoji6]

Trimis de pe al meu SM-G930F folosind Tapatalk
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Droiderat:
So, my SM-G930F phone uses a stock Oreo ROM (CSC: BTU), TWRP, and the TGP custom kernel. I used Odin to upgrade from the ERG2 ROM, rebooted, and then used Odin to install TWRP. I restarted into TWRP, and went to back up my data, but even with your revised version of TWRP, the contents of the Data partition showed "0". I then installed the custom kernel, but that didn't help. I had to reformat "Data" (from Ext4 to Ext2, and then back to Ext4); after that, the Data could be seen (but the format wiped out all of the previous data; fortunately, I had a recent TWRP backup of the Data partition).

So my question is, why do I still have this issue after your patch? Is it the TGP kernel? The change/feature log for the kernel doesn't mention "quota." If I use "no-verity-opt-encrypt-6.0.zip", may I stay with the stock kernel (even though the TWRP/Herolte instructions indicate that I *must* use a custom kernel with TWRP)?

Update: I was able to update to ERGE (using Odin), install TWRP (your build); and install "no-verity-opt-encrypt-6.0.zip" and Magisk (using TWRP), and everything works, without the need for a custom kernel. BUT, in TWRP, the Data partition still appeared as 0 (immediately after install), and it was necessary to reformat it (Ext4 -> Ext2 -> Ext4), and reload the Data from a TWRP backup (as I have always done). So, I'm not quite sure what your build fixed.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Dggellman:
Hi all,

I'm a little bit of a noob, I hope someone here will have the patience to answer (I don't know if this has been answered before, 125 pages is too much to read through...).

My S7 exynos (g930f) is currently running stock oreo 8.0 (I updated via odin once the proper version for my region came out), I'd like to root my device (for purposes of removing bloatware, using xposed, etc. not flashing a custom rom).

I'm not worried about tripping knox (already tripped it a while back, during a failed root attempt on nougat).

My main concern is wiping data. I'd really prefer not to, if there's any way to avoid it. Is this possible?

I prefer to root with magisk and not supersu, but that's not as important as avoiding data wipe.

I'm happy to provide any other information needed about the device, to anyone with the patience to help me with the process.

Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] blazethelight:
You mean after flash the the new TWRP Version with stock Rom & without custom kernel, you can't read the data partition?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Prof_NoLife:
For me it was necessary to format data in TWRP and after reboot into recovery (immediately! means no boot into ROM between.) to see the data partition. This worked for me on two devices with Stock Kernel & ROM (Oreo builts from 05.2018). When I just formatted data and then rebooted into Stock ROM, the next time I booted into recovery data partition was again not mountable.

Of course this method only works to backup the stock configuration. With this upgraded recovery, I guess the data partition recognition remains even after a boot into ROM but that doesnt mean that a dirty flash without wiping data will work!

Btw, I installed on both LineageOS 14.1 after a wipe of data, cache and system but still with stock kernel. I rooted it with the Lineage SU-Addon and installed Magisk later with magisk Manager which works flawless. I didn't use "no-verity-opt-encrypt".

So for my point of view, the clue of TkkGs TWRP is to format the data partition once and after the data partition stays recognized in the recovery even after a boot into ROM.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] moshi lyxander:
I flashed IMG file using TWRP, and it caused me Bootloop with RedScreen flashing after splash screen. Why is that happens actually?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tkkg1994:
Mates, I just added quota support not encryption support... this is something different.

Running stock rom and kernel means your device is encrypted and twrp can't access data partition. To remove encryption you can either do that "changing file system" thing or just click format, wipe data (you need to type "yes" with the keyboard) and data partition is visible as well.

In case you aren't removing force encryption, data partition will be encrypted on next boot and again it's not visible to you

Sent with my Flash powered SM-G965F
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mooms:
Link in the first page is dead, here is the correct one: https://twrp.me/samsung/samsunggalaxys7.html
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] LaCruz:
Error-Log

Maybe helpful:

SD=0-LOG:

recover.log:

I:Setting up '/data' as data/media emulated storage.
I:Created '/sdcard' folder.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
get_crypt_ftr_info crypto key location: 'footer'
Bad magic for real block device /dev/block/sda18
Could not mount /data and unable to find crypto footer.
I:Setting up '/data' as data/media emulated storage.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
Failed to mount '/data' (Invalid argument)
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
Unable to recreate /data/media folder.
I:Backup folder set to '/data/media/TWRP/BACKUPS/9885e6384f4b424f39'
I:Settings storage is '/data/media'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
Updating partition details...
Failed to mount '/data' (Invalid argument)
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/sda18', current file system: 'ext4'
Unable to mount storage
I:Unmounting main partitions...

/data | /dev/block/sda18 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/sda18
Length: -20480
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537

dmesg:

...
<3>[ 4.750870] [5: recovery: 2895] EXT4-fs (sda18): Filesystem with quota feature cannot be mounted RDWR without CONFIG_QUOTA
...

I am using latest TGP Kernel and Oreo Galaxy Project ROM.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Prof_NoLife:
Thanks for pointing out. So I understood it correctly at all and tried to explain that what you wrote in 3 sentences. :o

Now what does that mean for force encryption if I use stock kernel with official TWRP and LineageOS (14.1) with Magisk? Since I never flashed "no-verity-opt-encrypt disabler" nor something like this, does the ROM or Magisk the something like this or is it just because I dont use Stock ROM?

I ask because the instructions on page 1 are made for Nougat kernels and not for Oreo.

[MENTION=1255089]LaCruz[/MENTION] yes, that looks like the error messages you get when force encryption is enabled. In my opinion you need to wipe again to remove encryption once for all, but you better wait for TkkG or somebody more experienced :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Droiderat:
I need a bit more clarification, please.

My phone is running the stock Oreo ROM (EREG/BTU) with the stock kernel, TWRP and Magisk. It is *not* encrypted. And before I upgrade the ROM, I always do a backup of the Data partition, using TWRP. I then upgrade using Odin, and Home_CSC, so all of my data is preserved after the upgrade. However, as soon as I install TWRP after any upgrade, TWRP can no longer see the data (even though it could see it before the upgrade, and the data is fully accessible after the upgrade *before* TWRP is installed). And to make the data visible again, I use the "changing file system thing" (as you call it), and then reinstall the TWRP backup of my Data partition. I then use TWRP to install "no-verity-opt-encrypt-6.0.zip", followed by Magisk (I've read that the no-verity patch isn't necessary if you use Magisk, but I haven't tested it).

I can't tell that TWRP (or my required installation procedure) is any different after using your patched version. What am I missing? To me, the annoyance is the inability of TWRP to see data unless I do the "changing file system thing" .
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mooms:
Use a ROM that can be flashed from TWRP, this way the encryption will not be a problem. I recommend ALEXNDR, pretty close to stock, updated regularly.

You can dirty flash from stock.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] satanxda:
Works great, thanks! Now the next step is to integrate this fix to the official TWRP image :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kiss4luna:
follow the methods in step 10, install supersu or force encryption disabler will both trigger a "Failed to mout '/data' (Invalid argument)" error. Am I missing something?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] AlienCraB:
Hello!

I have been given an S7 for offline development purposes and I want to make sure I have a flash backup of the device just in case. The device came with TWRP 3.0.2-0 installed. Can the backup I take on this version be restored in, say, 3.0.2-4? Or do I need to update TWRP first, then take a backup?

I did some research online on the matter but it seems to vary depending on what were the updates between TWRP versions. I guess to be on the safe side I should first update TWRP, then take a backup or obtain a copy of 3.0.2-0, but the device I have is very sensitively used and I don't want to do anything unnecessary on it.

Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shaggyskunk:
Latest version of TWRP is 3.2.3-0 available here for herolte:

https://dl.twrp.me/herolte/

The latest version can restore Nandroid backups made by previous versions of TWRP 3.x.x-x ?

Sent from my SM-G965W ??