[Recovery][Exynos] Official TWRP for Galaxy S7 edge (hero2lte)

[Sirseregas]

When Im installing TWRP on first roobt its said that I cannot start system and got just option restart on lower panel on screen?

 

[exnokiafan]

No matter how hard I try, it's not possible to get rid of encryption and I always get internal storage = 0 inside twrp

 

[Anarchy16]

No matter how hard I try, it's not possible to get rid of encryption and I always get internal storage = 0 inside twrp

have u try "format data" ?
if not, u had to do that, but remember to backup storage before proceed

 

[exnokiafan]

have u try "format data" ?
if not, u had to do that, but remember to backup storage before proceed

Of course mate. I've successfully completed the task multiple times on other devices. Last week on a Galaxy A5 on oreo and a couple of months ago on my S7. But yesterday I flashed the latest stock oreo and that's the result. I just wanted a stock rom with my personal debloat and that's where I'm at now

 

[zsizsef]

No matter how hard I try, it's not possible to get rid of encryption and I always get internal storage = 0 inside twrp

In file manager (Solid Explorer or other) check hidden folder. Twrp ok, presents internal storage.

 

[exnokiafan]

have u try "format data" ?
if not, u had to do that, but remember to backup storage before proceed

A user suggested not to swipe for modifications, in order not to trigger the dm-veriti thing. Then flash both dm-verity and remove_encription, then magisk.

I don't know if this might work.

 

[mauam]

Version 3.2.3-0 is out.
Changelog:
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files

 

[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)

 

[Anthonomy]

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)

Could you do the same modification for the hero2ltekor variants? Thanks!

 

[Tkkg1994]

Could you do the same modification for the hero2ltekor variants? Thanks!

I don't have a kernel nor an updated device tree for this variant. I'm afraid you won't get that update unless you can manage it yourself

 

[shah22]

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)

So this is was the reason on oreo that after flashing magisk in twrp and rebooting, twrp won't see /data ?

Sent from my S7 Edge using XDA Labs

 

[babyboy3265]

Just to clarify for a friend, will this TWRP installation method work with magisk root, and will it wipe the phone? Thank you so much.

 

[Andi46]

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)

THX a lot for sharing the files and info :good:
Now FULL BACKUPS are no problem anymore

 

[Ubimo]

Restoring a nougat rom is not booting with the new modified TWRP. How can I go back to a nougat rom? I tried an oreo rom but want to go back to nougat. Older TWRP does not mount data.

 

[Pat750]

Restoring a nougat rom is not booting with the new modified TWRP. How can I go back to a nougat rom? I tried an oreo rom but want to go back to nougat. Older TWRP does not mount data.

I'm not sure, but I would format data with new TWRP, then flash older TWRP and reboot recovery, then check if data can be mounted.
This is only a suggestion...

 

[Ubimo]

I'm not sure, but I would format data with new TWRP, then flash older TWRP and reboot recovery, then check if data can be mounted.
This is only a suggestion...

Thank you, thank you, thank you, that did the trick. :good::victory:
I did try several different combinations of BLs and other TWRPs but I would've never guessed that formatting data with modified TWRP and the flashing "old" TWRP would work.

 

[savvy1968]

Cheers bud

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)

Its been annoying when flashing getting data cant be mounted..Thanks:good:

 

[mrsmtt]

Hi everyone! Just to be sure, even with Tkkg1994's TWRP version recv error is still there right? Because I'm facing it right after flashing Superman v3

 

[luka(s7 edge)]

would it work with superkernel?

 

[adel alsayed]

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)

Question
In TWRP V2.X.X in old device like s4 note 3 thar is option when i do full wipe thin restart recovery the twrp asking install root access .. But in v 3.x.x no more this option
Q. can you make v3.x. have that option it's ( include ) it in helpful to get root without searching for root zip file