yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
Well, from the perspective of some custom kernels that refuse to boot occasionally, it could be because you had enabled adoptable storage. Apparently logs suggest that enabling adoptable storage does re-encrypts the data partition, but it's not the same type of encryption... anyways to undo it; all that is needed is a clean flash of any rom.

Even wiping all partitions in TWRP is not enough to undo adoptable storage changes it seems..., for some reason a re-flash of a rom with full wipe is required to undo adoptable storage.

Also another point, it seems it's very important for this phone/twrp ver. to keep a copy of your rom install zip's tucked away for safe keeping. Restore operations does not always work but they do always work if you re-flash the origional rom install zip ffirst, then restore.
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
Hmm, one part of that isn't quite clear to me.

You say you format /data to remove encryption after updating to the latest stock firmware and reflashing TWRP. Are you therefore also saying that the mere act of flashing new stock firmware re-encrypts a previously formatted (by TRWP) and therefore currently unencrypted /data partition?

If that's the case, can the re-encryption be avoided by not rebooting the phone between flashing the stock firmware update and flashing TWRP? In other words, if you boot straight into TWRP after flashing the new firmware and TWRP, can you move straight to installing dm-verity and the encryption disabler without having to reformat /data?

Thanks in advance.
[Samsung Galaxy S8 & S8+ Cross Device Development] kevje1406:
Highly unrecomended for private forums? You truly are pathetic dude

Verstuurd vanaf mijn SM-G955F met Tapatalk
[Samsung Galaxy S8 & S8+ Cross Device Development] jiggle1991:
:good::good::good::good::good:
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
hy,

im french excuse my english, when i install trwp and supersu its ok that work when i restart.

supersu need to update and the root has erased i dont know why.

if 1 want to help me thank you

and excuse me again formy english
[Samsung Galaxy S8 & S8+ Cross Device Development] carlitobahsoun:
try uninstall su and use magisk coz su latest 2.79 is ok...after they release v2.80 and 2.81 and it update it self and had a prob...my opinion use magisk better
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
hy,

ive red error message in twrp when i install magisk.

RE now i've install sucessfuly magisk but the rooot is erased again ...

help me pls
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
Did you install dm- verify first?
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
yes ive install no-verity-opt-encrypt-5.1.zip in 1st in trwp
[Samsung Galaxy S8 & S8+ Cross Device Development] carlitobahsoun:
magisk app in app drawer or not???
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
its impossible to install magisk in trwp

ive install magisk in playstore and ive load zip file update for install in trwp
[Samsung Galaxy S8 & S8+ Cross Device Development] carlitobahsoun:
u must flash magisk in twrp why imposible??? than must have the app in app drawer
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
when i want install magisk zip in trwp ive red error message
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
What is the message please
[Samsung Galaxy S8 & S8+ Cross Device Development] alibisse:
magisk sd ext card error(1) however ive insert magisk.zip in external sd
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
If you wipe data as part of the original twrp install?
[Samsung Galaxy S8 & S8+ Cross Device Development] vibrantliker:
I'm on T-mobile in the U.S.

Where can I buy an Exynos version of the S8+ that I know can be rooted? I'm afraid to pay almost $1000 and be suckerd.

Any help appreciated.
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
see the q&a thread, already discussed at lengths there.
[Samsung Galaxy S8 & S8+ Cross Device Development] shadowdudez2:
Does this mean i'm rooted and okay to go? I'm getting the red x for safetynet and i don't know if that something i need to be concerned about. Also keep getting this Security notification from SecurityLog agent, how should i disable that or is it related to the safetynet?
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
red x = no netflix, android pay, pokemon or super mario run
[Samsung Galaxy S8 & S8+ Cross Device Development] Café King:
Noob question maybe, but here we go. Can I flash twrp, then flash magisk and then backup via Titanium before I wipe from twrp?

Thank you in advance

/CK
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
No, but you can perform a nandroid backup and restore that from titanium.
[Samsung Galaxy S8 & S8+ Cross Device Development] Café King:
I can make a nand when I can't mount /data?

/CK
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
Good point, mine was from the previous phone so not an issue I even thought about.
[Samsung Galaxy S8 & S8+ Cross Device Development] silentvisitor:
Hi

Anything like

fastboot boot twrp.img

is possible on Samsung FW?

Want to keep Knox undisturbed while flashing Magisk and run few scripts ?

Thanks ?
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
My S8+ suffered a software calamity yesterday.

I've only had it a couple of weeks, but it was decrypted, running TWRP and rooted with SuperSU (2.79 SR3). The device was running perfectly until yesterday.

Then, I saw there was a firmware update, so I flashed it using Odin and rebooted the phone into Android, so that the OS could finishing any post-installation tasks it needed to do.

I then used Odin to reinstall TWRP and, without rebooting into Android, booted into recover. There, I installed the dm-verity and no encryption patch, but noticed there were errors concerning /data being unmountable. Uh-oh.

I flashed SuperSU and then rebooted back into Android. Unfortunately, dm-verity was triggered and the device refused to finish booting, instead offering only to reset it.

Not to worry, I thought. I have a back-up.

I went back into TWRP, wiped /data and then set about restoring my back-up.

Alas, 27% into the restore, I got the dreaded extractTarFork() process ended with ERROR=255. Uh-oh.

Examination of the back-up files showed that several of them were truncated. I pulled them to my laptop with adb and was able to salvage some stuff from them, but mostly the back-up is a write-off. What a huge disappointment. I set about reinstalling the device and configuring it from scratch.

I have no idea what went wrong with that back-up. When I made it, it completed normally and without any kind of error.

However, my main concern right now isn't the broken back-up. It's the fact that I don't really understand how, why or when /data became re-encrypted in my effort to upgrade the firmware.

Well, the when component must logically be when I booted the OS after upgrading the firmware. Does that forcibly encrypt /data if it is found to be unencrypted? It seems so.

If that's the case, I suppose the solution is to upgrade the firmware and then, without rebooting, reinstall TWRP and then boot into recovery. I thought it was safe to reboot into the OS after a firmware upgrade (including a new bootloader image), because TWRP has been replaced by the upgrade, so dm-verity won't be triggered. I didn't know that /data will apparently be re-encrypted if found to be exposed.

Can anyone please confirm that my reading of what happened and why is the correct one, and correct any false assumptions I have made?

Regarding the extractTarFork() error, is there a common cause for that? I googled around, of course, but found mostly old posts without a common cause.

Thanks in advance.
[Samsung Galaxy S8 & S8+ Cross Device Development] Clandaries:
They dont want us to root our expensive phones.

I still dont get i twhy i cant do anything i want with MY phone...

Sad.
[Samsung Galaxy S8 & S8+ Cross Device Development] iamnotkurtcobain:
[MENTION=6371894]jesec[/MENTION]

Please look at this error
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
My mistake
[Samsung Galaxy S8 & S8+ Cross Device Development] d.cortez:
did you format data after installing TWRP and before you flashed dm-verity zip? 2nd post instructions say "Format Data" and reboot to recovery before installing dm-verity zip and rooting the phone.

wasn't mentioned in your post, but did you format data before starting the nandroid restore process? anyway, i got the same extractTarFork error with a backup i made before updating to the latest stock ROM. in fact, i restored my backup to make sure it would work before i flashed the latest stock ROM. my solution was this issue was:

reboot to TWRP and format data one more time

reboot to system and walk-through the setup process (skipping all options)

reboot to TWRP, backup my boot image to internal storage to create a TWRP directory in internal storage

reboot to system and use Samsung's file explorer to copy my backup from the microSD (external storage) to internal storage

reboot to TWRP and restore my backup, it finished without issue

reboot to system and verify phone is working as it did before the ROM update.

now, my approach might not be the correct process to follow, but it at least worked for me. will defer to the more technically/Android knowledgeable members to address your other questions.

:)
[Samsung Galaxy S8 & S8+ Cross Device Development] Clandaries:
Offtopic:

Someone tried the CF-Auto-Root for the Galaxy S8?

There are many saying it is working and they could install TWRP with Flashfire....

Greetings
[Samsung Galaxy S8 & S8+ Cross Device Development] Life Companion:
I flashed it on s8...but oem is locked nd odin fails.....and there is no oem option in developers Menu...

How to get it off??
[Samsung Galaxy S8 & S8+ Cross Device Development] Clandaries:
I think it is just for Exynos models...
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
When I first installed the phone two weeks ago, I formatted /data to remove encryption before I flashed the dm-verity zip.

This time, however, I updated the firmware with Odin, booted to system, then went back to download mode and reflashed TWRP with Odin, booted into TWRP and flashed the dm-verity ZIP. I did not format /data at all this time, because I believed there to be no need. Encryption had already been removed from that partition two weeks earlier.

I didn't, but I could see from the messages that TWRP does a wipe of the partition anyway before it attempts the restore.

When that failed, I started to clutch at straws, so then I manually wiped /data and tried the restored again, but it failed, of course, in exactly the same spot.

You're saying that the same back-up files that TWRP was bombing on when they were on your external SD card performed flawlessly when you moved them to internal storage? Is that correct?

If so, that's a pretty major flaw somewhere in the system.

Regardless, I'll never have the confidence to rely on a TWRP back-up again. Back-ups (and restores) need to be absolutely flawless, and this little caper has taken me more than a full day of intensive labour to recover from.
[Samsung Galaxy S8 & S8+ Cross Device Development] d.cortez:
it's been my experience/observation that you have to format data every time a full-stock ROM is flashed to your device. i could be misinformed; i equate the fact that, after installing TWRP via ODIN, i cannot access internal storage from TWRP and therefore need to format data. i want access to internal storage from TWRP because TWRP backups to internal storage are much faster than using the microSD. you know that format data and wipe are very different, right? my understanding is that format data removes content and encryption and wipe data removes content but doesn't affect encryption. (just asking, i apologize if you're offended by me asking). :)

yes, that's what i'm saying. don't know why, but it worked.

maybe, but i can't rule out user error (where i am=user).:o

the

only time

any of my TWRP backups didn't work was when i tried to restore from a microSD after a full stock ROM flash via ODIN. all other TWRP restores from internal or external (microSD) storage have worked without issue.
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
Well, that observation concurs with what I saw yesterday, but it's not explicitly mentioned anywhere that I have read.

When does /data get re-encrypted? It can't be the act of flashing from Odin, so it must be when one boots into system for the first time.

Presumably, then, this problem can be avoided by not booting into system between flashing the firmware and flashing TWRP, instead booting straight into recovery to flash the dm-verity ZIP.

It would be great if someone could verify this.

Yes, I understand. I thought that once /data had been formatted, encryption was gone for good so long as the user didn't manually re-encrypt it from the phone's Settings, but this appears not to be the case.

This is when it let me down, too, but in my case this is the most common use scenario.
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
Ive pointed this out a couple of times before already in this thread, back up and restore will always work if you first flash the rom install zip from which the backup was made before restore!

My therory is, different roms/kernels establish slightly different partition sizes and twrp isnt resizing properly everytime when presented with these... and based on the research ive done in the past, your tar fork error supports this theory. Anyways, again, the work around, always have a backup of your rom zip! flash it again, then restore!

ive noticed too wipes do not work in some scenarios but re-installling the rom with fulll wipe setting in auroma will wipe corectly.
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
The use case being discussed here is stock firmware via odin - no zips available!
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
ahh, in that case find a custom rom with the same base as the backup, that works too, make sure to full wipe with auroma! renovate should do the trick.
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
I considered this possibility, so when all else failed, I used Odin to flash the phone back to its original firmware, then reflashed TWRP and attempted to restore my back-up of /data to the same firmware it had been created from. However, I got the same tar fork error during the restore; but this time slightly further into the operation, IIRC.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ker~Man:
Wasn't there supposed to be an update for TWRP a few days ago??
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
Yes, I've already reported this issue in the thread, here's what I discovered:

Using Odin to reflash the same firmware produces the /data restore error at different points each time the flash is performed. This also happens each time /data is formatted.

I then found that formatting /data to ext3 allowed a restore, but I could no longer update existing apps or add new, which I could live with pending a fix.

This came about as I was testing F2FS, so with /data formatted to ext3 and data restored, I then formatted cache to F2FS which booted successfully, however, diskinfo now reported both partitions as ext4 (restores performed without formatting to original format and cache not backed up or restored). Returning to TWRP showed both partitions now are ext4).​

I've no idea what's going on here (but I can confirm the F2FS /data will NOT boot, no ADB access available :( ).
[Samsung Galaxy S8 & S8+ Cross Device Development] Clandaries:
They really dont want us to root and use the phone as we will....

I love the S8 but i think it was my last Samsung device. I had all Phones since S2.

But maybe someone find a way, that works 100%...
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
It makes no sense to me that the restore operation would fail at a different point after each Odin reflash of the firmware, but if you've observed that behaviour, fair enough. When I repeatedly formatted /data, however, the restore continued to fail at the same spot every time: 27%.

TWRP back-up files seem to be tar files or some slight variation thereof, so partition boundaries changing between minor firmware releases shouldn't actually matter,

I commend you on your valiant attempt to get your device to the point that TWRP could restore your back-up, but it's clear to me that TWRP back-ups are not the straightforward, reliable proposition that I thought they were. And, given your and my observations, it seems that TWRP is at its most unreliable in precisely those circumstances where I need it most.

Conclusion: I need to look elsewhere for my back-up tool.
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
I've got the recovery logs to demonstrate the point to myself as I found/find it hard to comprehend.

I believe in trying to provide as much PD info as possible and have the time to perform testing.
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
Aside from my crib notes with respect to how to perform a backup and restore on this device with TWRP; the restore function has actually never failed me! I have done now at least 10+ restores with different roms including my very own stock backup. So....:rolleyes:
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
I understand, but this is my first attempt at restoring from a TWRP back-up, so I have a 100% failure rate. That's not a good start in anyone's book.
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
lol, did you try flashing another rom yet with the same base as your odin fw backup? If you haven't, you should and then try your restore again because it will likely work!!!!! if you do decide to give this advice a whirle be sure to select full wipe in auroma or it wont work! look for a compatible renovate rom or nemesis rom. if that doesnt work then try batstock, they seem to be working with different partition tables (or something!?) but one should match your odin backup.

and try reading what i posted above. your backup is very likely to be a good working backup. i have observered what seems to be a strange partition layout issue going on with this phone, twrp and different roms and kernels.
[Samsung Galaxy S8 & S8+ Cross Device Development] force70:
Who says you cant? We have root,twrp, roms etc...

Sent from my S8+, note 7, S7 Edge or S6

---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------

Yes exactly of course it is. Why anyone with a snapdragon would try it is beyond me lol

Sent from my S8+, note 7, S7 Edge or S6
[Samsung Galaxy S8 & S8+ Cross Device Development] tiho5:
That makes me think that the Wipe helps most... May be the Wipe option in recovery isn't doing a correct job?

I once played with doing several times a Wipe one after another. Every 3 or 4 times it would show an error.
[Samsung Galaxy S8 & S8+ Cross Device Development] force70:
Ive always just used odin to install twrp...flashfire i think i used once on my LG G2 but if you can use odin its the tried snd true method

Sent from my S8+, note 7, S7 Edge or S6
[Samsung Galaxy S8 & S8+ Cross Device Development] cantenna:
yes, thats what i have been trying to advise:)

Its possible but I cant say for sure.
[Samsung Galaxy S8 & S8+ Cross Device Development] ianmacd:
I tried two different versions of the stock firmware: the one I was trying to update to, and when that didn't work, the version I was trying to move from. Both gave a tar fork error.

I don't know whether the back-up itself is bad, or whether it's just something during the restore preventing its successful completion. What I do know, however, is that the tar files produced by TWRP are not normal tar files. Examining them and extracting files yields tar: Malformed extended header: missing equal sign amongst other problems. If those are supposed to be 100% compatible tar files, then the back-up is bad.

The partition lay-out shouldn't even really matter, since it's not a block-level back-up. Perhaps other partitions are restored at the block level, but for /data that's neither necessary nor desirable.
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
I'm sure the backup's fine - despite all of my issues I was eventually able to restore
[Samsung Galaxy S8 & S8+ Cross Device Development] HorstiG:
Is there any Changelog for v3.1.1.1?

Thank you
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
Tested v3.1.1.1

Backup and Restore of boot, recovery, system, data, cache, baseband, efs

All works fine

previous version i had fork err sometimes but this one no issue

With v3.1.1.1, i took backup of " boot, recovery, system, data, cache, baseband, efs " to internal and copied to sd and restored and it booted

Then took backup to sd directly and hit restore and it booted

Both way it works well this time:D
[Samsung Galaxy S8 & S8+ Cross Device Development] rafalubo:
Hello good night with the new recovery only with odin it works or plays put the file no-verity-encrypt thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
Flash twrp with odin

Nothing else
[Samsung Galaxy S8 & S8+ Cross Device Development] dilgit:
I have twrp 3.1.0-1 installed on my Galaxy S8 Plus....

Can I just flash the new version 3.1.1-1 with odin over the current version WITHOUT data format?
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
Yes mate
[Samsung Galaxy S8 & S8+ Cross Device Development] stevenazari:
I need some advice...

I followed instructions but when I get to TWRP, The screen is unresponsive, I know the phone isn't frozen because after a while it shows the lock screen and I can lock/unlock (turn off/on the screen), I just can't interact with it... any advice where I'm going wrong?

Edit - I had dream2lte (s8+) version... the instructions point to the s8+ version which I assumed was compatible for both... maybe change the link to the search section of site so we can find ourselves?
[Samsung Galaxy S8 & S8+ Cross Device Development] goRt:
Still not working here - I can do a full backup and then attempting to restore /data when partitioned as ext4 ALWAYS fails - I can restore straight away without issue to ext3 (well I can't update apps) or F2FS (but that's not bootable). The fix I reported previously seem to have been just some lucky coincidence.

This is on the stock rooted ROM AQDJ/H3G.

I've also tried flashing (via ODIN) the same stock firmware, booting, etc. but again that still fails when ext4 restore is attempted.

Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] sameer3006:
TWRP Error 255

CAN YOU PLEASE HELP ME ON THIS ( using g955FD )

whenever i go to make backup on internal storage of phone it displays error in red.

when it says " backing up system " right after 1 second it shows following error message in red color as

createTarFork( ) process ended with error :255

Backup failed. Cleaning back up folder

And if i try once more to make a backup, it says in red

Can not create /data/media/0/twrp/backups/ce031713fa773fc750c/2017-06-01 -- 16-25-39' folder

( read only file system)

Failed to make backup folder.

what should i do ? reinstall recovery ? would i be able to restore from backups made in previous recovery if i reinstall recovery on my device.
[Samsung Galaxy S8 & S8+ Cross Device Development] yash92duster:
:eek::eek:

i have flashed all roms and took backup of them

And restored then and all boots fine

my main backup rom is stock debloated rom " AQEB - INS "( Own Rom ):cool:

" boot, recovery, system, data, cache, baseband, efs "

At last restored my backup and that also booted fine

no fork issues or any other issues:D

Flash stock in odin and format with stock recovery

Then flash twrp

Use different sd card and try