yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 Guides, News, & Discussion] aa_chow:
Got this notification 10 mins ago.
[OnePlus 5 Guides, News, & Discussion] colindodds:
Doesn't say what the oxygen 5.0 hot fix is
[OnePlus 5 Guides, News, & Discussion] aa_chow:
Yeah unfortunately, that was the first thing I looked for.
[OnePlus 5 Guides, News, & Discussion] Tiago A:
Where u from?
[OnePlus 5 Guides, News, & Discussion] Poeta:
Try Canadá VPN ?
[OnePlus 5 Guides, News, & Discussion] burnski:
I got this update too but my bootloader is unlocked. Is there a full version I can flash instead of just the update?
[OnePlus 5 Guides, News, & Discussion] smartbuddy:
No Face unlock in this?

Anybody updated?
[OnePlus 5 Guides, News, & Discussion] Senaxo:
In Germany too
[OnePlus 5 Guides, News, & Discussion] vortex-5:
On TWRP bluespark 8.61 with the full zip file there's an error "unlocked bootloader"

Just in case people are wondering you won't be able to dirty flash or wipe /system and then flash.

Make sure you have a backup before you are going to go to 5.0.1
[OnePlus 5 Guides, News, & Discussion] tinuz97:
Works fine here with twrp-3.2.1-0-oreo-8.0-codeworkx twrp.

I dirty flashed from official 5.0 to 5.01, unlocked bootloader, encrypted, rooted with Magisk.

I booted bluespark 8.61 twrp, flashed codeworkx twrp with bluespark twrp.

Rebooted immediately to codeworkx twrp, wiped dalvik and cache, flashed 5.01, wiped dalvik and cache again, after that i flashed Magisk 15.2, wiped cache and dalvik again, reboot, done. Magisk works, still encrypted without any errors or losing data.
[OnePlus 5 Guides, News, & Discussion] tinuz97:
Credits to this guy, I followed these steps :
[OnePlus 5 Guides, News, & Discussion] vortex-5:
Yeah codeworkx seems to work I would recommend that one as well.

I'm unencrypted so the stock TWRP would've worked as well just not blue_spark
[OnePlus 5 Guides, News, & Discussion] Amos91:
Dirty flash worked fine here (encrypted) as per the above.
[OnePlus 5 Guides, News, & Discussion] Senaxo:
What am I doing wrong?

I have followed the instructions but I come back to the TWRP after the reboot.
[OnePlus 5 Guides, News, & Discussion] epr:
Can confirm that codeworx is doing the job.

Unlocked BL, encrypted, rooted with Magisk 15.2
[OnePlus 5 Guides, News, & Discussion] Lum_UK:
Apparently this is the full OTA, from the OnePlus forums: http://otafsg.h2os.com/patch/amazon...5Oxygen_23_OTA_028_all_1801031502_04d7cc5.zip

Not tested yet. Still backing up everything!
[OnePlus 5 Guides, News, & Discussion] Senaxo:
You still have to install the No Verity Mod!
[OnePlus 5 Guides, News, & Discussion] tinuz97:
No (I am encrypted) and did not flash no verity. Everything working fine.
[OnePlus 5 Guides, News, & Discussion] aa_chow:
Canada
[OnePlus 5 Guides, News, & Discussion] Yousvel:
Mega Mirror of OOS 5.0.1 full zip

Mega Mirror of OOS 5.0.1 full zip

https://mega.nz/#!xMdFWYBZ!HA_h5ffWS04kMezVjwJET12xsqg5r86io5NzWGKVDTA

Enjoy!
[OnePlus 5 Guides, News, & Discussion] romano19:
Does this update include Face Unlock? tks
[OnePlus 5 Guides, News, & Discussion] cirillo30:
i did this, installing also no verity mod and all works fine!

Thanks!
[OnePlus 5 Guides, News, & Discussion] emes2:
I confirmed. It's really works.

Wysłane z mojego ONEPLUS A5000 przy użyciu Tapatalka
[OnePlus 5 Guides, News, & Discussion] sleepwalking0593:
Over and out
[OnePlus 5 Guides, News, & Discussion] MadCow809:
I flashed twrp-3.2.1-0-oreo-8.0-codeworkx-cheeseburger, then when I tried to flash OOS 5.0.1 (full rom), I got the following error message:

E1001: Failed to update system image.

Updater process ended with ERROR: 7

Any idea why I'm getting this error message? :confused:

Edit: Nevermind, the rom worked after I cleared the system cache via TWRP.
[OnePlus 5 Guides, News, & Discussion] yupo72:
Hi, did you remove screen lock pattern/pin, fingerprints etc. before?
[OnePlus 5 Guides, News, & Discussion] cirillo30:
i did not and it works
[OnePlus 5 Guides, News, & Discussion] tinuz97:
Nope, I did not remove my pin/fingerprint. (and just working fine)
[OnePlus 5 Guides, News, & Discussion] yupo72:
I read in another discussion your same method but, before installing Magisk 15.2, they installed the no_verity_mod zip, and the update works fine......but, is it really needed if last version of Magisk is used (15.2)?
[OnePlus 5 Guides, News, & Discussion] tinuz97:
I am encrypted, and want to stay encrypted. No Verity is for decrypted? Correct me if I am wrong.
[OnePlus 5 Guides, News, & Discussion] Ashish.akc:
Yes it is. You don't need it
[OnePlus 5 Guides, News, & Discussion] yupo72:
Great....I'm Encrypted too and I don't even know what does it mean :laugh:
[OnePlus 5 Guides, News, & Discussion] tinuz97:
When you encrypt a device, you are wrapping the information on it in a layer of protective code that prevents unauthorized people from accessing it. As a step towards making sure your information is secured, your organization is requiring you to encrypt your Android device before you can access company files, email, or data.

Not my txt, I did Google it, because it was a little hard for me to explain in English :laugh:
[OnePlus 5 Guides, News, & Discussion] fanbogo:
They fixed double vibration issue?
[OnePlus 5 Guides, News, & Discussion] simo6:
Installed it (dirty flashed), i was on 5.0 crypted with no root, with stock kernel and stock recovery, but unlocked. No issues for now..
[OnePlus 5 Guides, News, & Discussion] Piplup702:
Clean flashed this coming from xxx 4.8 nougat. Bootloader unlocked, flashed codework twrp, wiped everything except internal storage, flashed ROM, magisk 15.2 and no verity zip for Oreo to remain decrypted. All is well, thanks to all ?
[OnePlus 5 Guides, News, & Discussion] Senaxo:
I have to decrypt the system with every flash with the No Verity Mod
[OnePlus 5 Guides, News, & Discussion] DvLAx3l:
Me too, damn, I want to stay encrypted...

I try to clean flash with no success, bootloop until I use no dm verity
[OnePlus 5 Guides, News, & Discussion] DorianX:
Thanks to OP (original poster) for this helpful thread! Now we have 3 for discuss the same thing, great! ???

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[OnePlus 5 Guides, News, & Discussion] lazostat:
And then why someone should go decrypted??
[OnePlus 5 Guides, News, & Discussion] Magnum_Enforcer:
Not needed. Go here: https://xdaforums.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003

Thread closed.
[Tasker Tips & Tricks] Froryrory:
In case you haven't heard, there is another Tasker Beta available (currently at 5.1b4) posted by the dev in the Tasker Google Groups page.

With that said, check out how to automate Tasker Beta Updates with my Tasker Beta Update Checker Project and never have to check for a new Beta!

Features:

Checks for new beta everyday at noon (you'll have to update to your specific timezone in the profile)

Provides simple Notification to update Tasker and Tasker App Factory APKs

Uses visual feedback by way of a previous Tasker Project: Custom running Checklist Progress Dialogs

Tutorial and Project download are here:

Tasker Beta Update Checker Project

Go get the new Beta!
[Galaxy S6 Edge Q&A, Help & Troubleshooting] BleachDark:
Hello everyone, forgive the trouble, but I would like to bring back what seems to be a defect of the new Samsung (And not only)

I state that I have 5 mobile phones and I have tested the following problem with everyone.

S3 - PROBLEM

S4 - RARELY

S6 Edge - PROBLEM (mobile phone I currently use)

S6 Edge plus - PROBLEM

S6 Edge plus (2) - PROBLEM

To perform the test I used Yet another touch screen test, app that serves to test the touchscreen.

If you hold down on the touch screen with two fingers and leave one of them (Keep your first finger firmly on the screen) the system reports that we still have both fingers on the screen (when it is not so!)

The problem can be seen in games where you use a lot of two fingers, especially in musical games, where you may need precision and punctually you can not do anything about it.

My S4 is dead, but I've got to have another one lately and indeed with neither of the two I find this problem, when it happens, it's very rarely.

While on the other hand, with all the others, the problem is frequent and I do not understand why. I do not think it is a software problem, also because on the S3 I have another operating system and it is completely modified, the S6 EDge, the one I currently use, is rooted, but with very few background applications and without any particular problem.

I state that I have already tried to upgrade the TSP with the secret command via dialer, but the problem persists.

Do you know any solutions? I do not know what to do and although it is not a "heavy" problem, it affects me a lot ...

I hope I can find a solution! Thanks in advance for any answers.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
how to? hahaha

same problem it was before "only official release binaries are allowed to be flashed"

only now I have no BL "A520FXXU3" to power flash with the December att patch
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
Follow the same procedure as below:

https://xdaforums.com/samsung-a-series-2017/how-to/tutorial-root-november-security-update-t3715661
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] thangluong:
Cannot bro. Until now, only the December security update use "level 3" block bootloader. So cannot use BL of other lower firmware. November security update use the same "level" bootloader with lastest MM update ("level" 2).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
Worked for me. I have rooted mine using the same process by flashing below combination:

BL: A520FXXU2AQFA

AP+CP+CSC: All from Dec. 18 nougat build (QLA)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Can you upload BL that you used? It's work even you're in the latest security patch version december?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
I have attached the BL file. Yes, working on latest security patch (december).
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] sawas.t01:
Hey man it didn't work for me any other methods to root?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
It did not work for me either. sw rev. check fail. device 3. binary 2

What country is your rom?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
It is Philippines (XTC) and phone origin is Vietnam, we are in the same CSC group and it should work. Please try exactly what I did.

Flash nougat BL with nov security patch along with the dec nougat build for AP+CP+CSC. After complete installation, I tried flashing TWRP (ofcourse enabling OEM unlock and USB debugging) and it failed. So went again to download mode then flashed BL (the file I attached) along with the dec nougat build. Again completed installation, then successfully flashed TWRP via odin. Afterwards, proceed to rooting my device.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
I can not flash BL nougat from the September patch because it has level 2, and my BL is level 3 ....
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Are you also Filipino?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
Strange, maybe it is country specific issue. Mine has level 2 BL and rest Level 3 per dec build and I was successful flashing it. If you have a way to revert back from previous nougat build, say nov security patch, and can re-root your device, try flashing the latest nougat via flash fire. Use "flash firmware" action button and follow the instructions. Untick the "recovery" checkbox so you maintain twrp. From there, reroot your device through twrp. I also did this process and I was successful doing the whole thing.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
I am.

---------- Post added at 09:00 PM ---------- Previous post was at 08:25 PM ----------

If you have flashed level 3 BL initially then you have a slim chance of downgrading your device from previous builds. Maybe I was just lucky enough because I used flashfire at first to upgrade to dec nougat build. I just didn't like settings menu as it was quite different from previous nougat, so I reflashed everything via odin but using level 2 BL and the rest level 3 (dec build). Try to follow the furom from the thread I initially gave you as they have also issues same as yours.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
then ... for me it will not be possible because my bl is level 3 ... no way I can flash a bl level 2
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Flashfire doesn't flash bootloaders which is why you were able to root.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
I hope there's a other way to install twrp or cwm even the boot loader can't downgrade.?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Unlikely. Once it's locked that's usually it, no modifications possible.

It'll probably be locked down forever now unless Samsung release an unlocked firmware.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
How sad to hear that!?

But I know a lot of great devs. here so it's possible to fix that :good:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
Oh, I was lucky didn't flash v3 BL even when I reflashed via odin. Thanks for that info.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Anyupdate about this problem?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Quite simply if you've updated to a Rev. 3 bootloader you're out of luck.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] monsieur goonie:
can't go back with a full odin reinstall to old version??

ODIN would overwrite the BL, right?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Unfortunately not.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
As I said here https://xdaforums.com/showpost.php?p=75021065&postcount=336

And for those of you that havn't got update yet. Don't update through OTA. Either make a flashable zip of the downloaded tar using assayyed kitchen, or try odin without the BL part.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Probably easier to just flash updates with Flashfire. No worries of flashing locked bootloaders then.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Yeah, you're right :) I'm not a big fan of "flash apps" so it kind of slipped my mind.

---------- Post added at 09:39 PM ---------- Previous post was at 09:13 PM ----------

btw [MENTION=4899305]ashyx[/MENTION] Do you know if U3 sboot from combination fw have the same downgrade restriction, or could it be possible to downgrade?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Well it would be interesting to know if the U3 Sboot from the MM firmware would actually flash as Samsung are now even blocking engineering binaries.

If it does flash there's a chance it won't be locked and thus may allow root on Nougat.

Willing to test it out? ;)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Yeah, that's what I was wondering about too. Can't try myself though as I don't own any A520 but I do have this:

COMBINATION_FAC_FA60_A520FXXU3AQL1_FAC3AQL1_CL12642482_QB15985823_REV00_user_mid_noship.tar.md5

Should I make a tar.md5 of the sboot from it and see if someone's intrested to try? :p
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Well if someone would like to try, the U3 bootloader from MM combination firmware is below.

https://www.androidfilehost.com/?fid=889964283620777311
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
Ah great, you had it too. Will be intresting to see....
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
flash via odin in AP or BL?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Either.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
I can test here, just do not know how to flash the file
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] willingtolearn:
Waiting for the result mate..goodluck?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] caiquess95:
I tried flashing the file but the process on odin we can say it freezes.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Need more info and screen shot of odin.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] monowilliam:
Hello I would like to try the U4 bootloader from MM combination firmware because I updated looking for hasty solutions to the A520FXXU4BRA8 version and tried your U3 and it does not work thank you very much.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
.

No image?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
http://i1262.photobucket.com/albums/ii604/kobejor/received_1732335416788840_zpsigocs5ty.jpeg
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Any message on the device itself?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
Nothing

When you click start still on download mode nothing happened...
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Has someone tried with heimdall instead of odin?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] monowilliam:
If I already tried it with Heimdall in linux console and in windows heimdall-frontend and it did not work either ... I resigned myself to no root
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
You attempted to flash sboot.bin from the combination firmware?

What was the error?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] monowilliam:
when I try with Rodin and heimdall the sboot.bin does not start the flash, the application freezes, and in the telefeno no message does not appear, when I try with another BL it continues leaving SV REV. CHECK FAIL. DEVICE:.... BINARY:... , it will be possible if the new firmware of Sammobile A520FXXU4BRA8 is installed will work?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
I tried to flash MM AP,CP and CSC with latest N. BL... android security path level was change... but the security software version still ASKS v1.4_161228 ...

I think need to change to v1.3_161228
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
I've repacked and uploaded it again in case there was an issue with the upload:

https://androidfilehost.com/?fid=889964283620777692

.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Just did it and it flashed sucessfully! So.. now, will try to go with twrp and see what happens

---------- Post added at 08:42 PM ---------- Previous post was at 08:22 PM ----------

Ok, so I flashed twrp, and I got into bootloop getting a little message that says, recovery image signature verification failed, reboot to avoid warranty bit set.. any suggestions?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Did you enable OEM unlock in developer settings?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Yes I did. However I did it prior flashing the file you provided, could it be that it needed to be done after that also? Maybe it returned to original state after it
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
It seems the device is failing the dm-verity check.

Might be worth trying to downgrade the bootloader to the MM rev 2 bootloader posted here.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Thanks!, will do now

---------- Post added at 09:15 PM ---------- Previous post was at 09:07 PM ----------

Ok, so did not work.. it is like if we had never flashed the sboot that you uploaded, even thought I am still getting the little green message of that sboot.. :(

---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------

It seems to stop in param.bin :

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> sboot.bin

<ID:0/004> param.bin

<ID:0/004> FAIL!

That is what we get.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
As long as it flashes sboot.bin that's all that matters.

Do you get any messages on the device?

If sboot has indeed flashed as above then the bootloader should have down graded.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
On the device it shows the progress bar until the middle and then I get error of rev 3 bin 2 and odin shows fail. I am about to give up. I am on latest Colombia firmware QLA. As soon as I get home will try with a November sec patch ind firmware that I have and redo the process again
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
The fact that you managed to actually even flash twrp is a partial success as a locked bootloader would have simply rejected it.

The hurdle is this apparent signature check.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Right, I agree on that. Will keep trying.. have a couple ideas in mind, if I am successfull will for sure share qith results or keep asking hahah.

Thank you for all the support!!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Well guys... it seems that we need a miracle... I tried unticking several things on the developer options that seems to be related but nothing... tried even the sboot that was on the root post that [MENTION=4899305]ashyx[/MENTION] commented for the 6.0.1 version.. nothing.. I even downloaded firmware from other countries with same BL to see if there was one with something.. and then redo the process.. nothing... I guess.. as a user, have not found anything... if someone else has another idea.. please share
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] willingtolearn:
I just found this method from charcool have you try this? Flash latest firmware then wait for the blue android screen that says installing updates etc etc...

After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp

Just dont let phone boot into android

With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone

I found this one from this thread https://xdaforums.com/samsung-a-series-2017/help/root-firmware-update-t3711395/page2
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Jemec26:
Well .. I have not.. so I will sure do tomorrow.. thanks for the advice! Tomorrow I will report back
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
OK first of all the dm-verity/encryption patch does NOT cause lag.

Out of 1000,s and 1000,s of people that have used it on many different devices literally 2 people have incorrectly attributed this so called lag to the patch.

It is not related to the patch nor is it possible for it to be so.

It is actually related to root.

Also the procedure you just posted will not help this case. We are attempting to circumvent a locked bootloader as well as bypass dm-verity.

For other devices the procedure you posted, while unnecessary, may initially work to allow the data partition to be mounted and the device rooted, but it will not work permanently.

Upon first boot the device will re-encrypt. If dm-verity is not disabled the device will also fail to boot.

Both Magisk and SuperSU can patch dm-verity and if required disable encryption.

However BOTH use exactly the same method as the patch.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
failed for me :crying:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
In what way?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
same as jemec

i will try it later after my work
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
But he flashed successfully?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kobejor:
My fist attempt failed. So I download sboot.bin again,and it's work,;) i flashed wtrp and it's successful. But when my phone reboot their is a message that need to reset the phone all date will be erase blaa blaa blaa.... then my phone bootloop like jerec said.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Are you booting from odin directly to twrp immediately after flashing?