yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] IngoPan:
Wasnt the tutorial a few days completely different? Just curious ...

Wasnt there a tutotial without flashfire? i rooted my a5 a few days ago but now it seems the tut is completely different.

Any easier way to go? adb sideload the non-integrity check for example? thanks.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tsarig:
Flashfire is only used for backing up your data because nandroid can't work on encrypted phone, and has nothing to do with adb-sideload.

Its the same tutorial as in the OP, just tried to make it more simple for some people. I've omitted the backup part assuming people already wiped their devices while trying to install root. anyway, it's all there in the OP.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] av1choudhary:
[MENTION=3660325]bassbounce[/MENTION] or anyone how can i get source code of kernel of my samsung having software as below
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] kevkev0320:
Klinkt misschien dom,

Maar heb je na het flashen je Cache/DALVIK ook geleegd?

Did you wipe cache/dalvik afterwards?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] luccajan:
Oeps, daar ging het mis, is idd best dom ja :p
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] djmaxis:
Hi,

Today I received A5 after failed SuperSU flash. Friend of my tried to flash SuperSU without formatting encrypted data partition and flashing no-verify-no-encrypt package. Now device stuck's at Integration verify error, he don't want to loose his data. Is there any posibility to make it work without wipe?

If I flash no-verify-no-encrypt on encrypted data partition it will work properly? Or reflash stock firmware via odin?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Just reflash the stock firmware. It should then boot normally.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] djmaxis:
Thanks for answer. Just to make sure: flash BL + AP + CP + CSC or only one of that?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] gerchev:
boot loop

Hello! I made an error installing tmrp. after I got into it I gave a swap modifing and the phone stands on a samsung logo after a restart. can you help me start the phone normally.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Just AP should do.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] hugstari:
stuck on downloading

After getting the two files and booting into download mode i can not progress any further. It is stuck on "downloading. Do not turn off target" I can not select A5-SM-A520F-TWRP-3.0.2.0.tar.

I must be missing something.

Edit: Yes i think i got it. It was a pretty stupid mistake :)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Furax31:
Hello, (I use google translation)

1) Is the tutorial up to date for the A5 2017 Android 7.0?

2) I have to download the mentioned files or take the latest ones?

3) Thank you :)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] catdoggy:
Hello, i have Samsung since S3, S4, S5, J5 and rooted every time. But at all models it was a "must-have" in Odin to tick "F. Reset Time"... and here its first time to untick it- is this really the right way??

Edit: sorry for my english and Thanks :)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] fromhungarytolnacounty:
how to root A520FXXS2BQIJ? This method works? thx
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ryRy:
a5 2017 nougat

will this work on a5 nougat?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Essentrix:
Yes working well on nougat.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] av1choudhary:
My lockscreen is lagging after rooting. Any help ?

If i enter PIN it takes 2-3 seconds to unlock but fingerprint works fine.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Use an earlier version of SuperSU.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] av1choudhary:
Curently using 2.82 i think.

Any suggestions which version to use?

And sure it will work just after flashing earlier version?

---------- Post added at 10:52 AM ---------- Previous post was at 09:56 AM ----------

I just falshed old version of superSu but now my bootanimation is changed earlier it was black screen white samsung now its white screen black samsung.

Any help with that ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
Hi all. I've encountered a really annoying problem. I've already enabled OEM unlock and USB debugging but when flashing TWRP via Odin it just tell me

"Only official release binaries are allowed to be flashed"..

has anyone encountered this problem too? I can't just get pass through it. Please help it's so heartbreaking when your knox is tripped with no root previliges :crying:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Roofprod:
you were updated to the last firmware? The problem is that the vendor disabled loading of the stranger of recovery. I have the same problem
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
I did manage to root it previously until I messed something up so I flashed it back to stock then fell asleep and woke up with my device updated. So yeah
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
I take it that means downgrades are blocked?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
Yeah. Downgrading gives me an error

SW REV Device something...

Is it possible to flash TWRP again someday for updated devices? I don't really know what causes it is it because of the bootloader?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] DeviceTester:
Guys, as you said, we can't install TWRP on the last update? A520FXXU2BQK1 can't be rooted and etc? And we can't downgrade, right? I'm very sad, cuz I updated 29.11.2017, and only today wanted to install custom ROM and saw this(
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Which is the firmware build that is bootloader locking devices?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] DeviceTester:
Yes, for me, SER(Russia) after updating to A520FXXU2BQK1(29.11.2017) we can't install TWRP and etc.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
So have you guys tried to go back to A520FXXU2BQIE?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
I have A520FXXU2BQH4 which I think is older still get the same error
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
So does anyone know what the last firmware was before the bootloader got locked?

Are you able to flash this?

http://updato.com/firmware-archive-select-model?record=02D5E95B714911E7963AFA163EE8F90B

---------- Post added at 09:56 PM ---------- Previous post was at 09:40 PM ----------

What error do you get with that firmware?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
Error I get when flashing Android 6 stock is

*sw rev check fail device 2 binary 1*

Error I get when flashing twrp is

*only official release binary is allowed to be flashed(recovery)*

I believe QK1 is the firmware that locks the boot loader.

Before I was used to update my device before rooting it so I am convinced that it is QK1. Prior versions haven't gave me any errors.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] DeviceTester:
Yep, it doesn't work... I knew about that stupid update from one famous Russian forum(I won't say name, because i don't want to advertise). Everyone says, that booloader(or something like this) become locked after update, and we can't downgrade or install any modifications.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Have you actually tried to flash THIS firmware? It's a revision 2 firmware not revision 1, so shouldn't say it's 'binary 1'
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
Okay sorry not that specific Firmware actually.. sorry for not being clear enough i'll try flashing it when my internet comes better.. I'll just leave a reply btw thank you so much for the replies

---------- Post added at 11:20 AM ---------- Previous post was at 11:06 AM ----------

I hope that's not true. I really regret flashing Russian firmware.. should've sticked to my country firmware, such a bad move leaving my back ups useless my work my stuff my files all gone I'm so sick of it.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] waltermsalomon:
I got my device updated to latest nougat as well and I am not able to flash TWRP anymore. Is there any chance for a fix to make TWRP work again? Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] DeviceTester:
As I read on one site, it's not possible to downgrade by using Odin. Do you guys know, how to downgrade?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
See my post further up.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
thanks [MENTION=4899305]ashyx[/MENTION] did managed to downgrarde :good::svetius:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Good stuff, so you can confirm you managed to downgrade to MM and you are now able to install TWRP and root etc.?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
Yes running on rooted stock Nougat as of now. Thank you so much :svetius:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
OK are you able to confirm which Nougat build is safe to flash after downgrading to MM?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
QIE if I'm not mistaken.. Anyways I'm on QK1 now latest update.

I just flashed the stock BL file (bootloader) of the link you gave me after updating

Then reboot and flash TWRP and I'm good to go.

btw what does the error sw rev check fail mean?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Ah right, so nougat boots on the MM bootloader?

It means that part of the firmware, usually the bootloader was revised with some changes. Maybe related to security. On this occasion locking the bootloader.

Once a revised bootloader is flashed it cannot be downgraded to a lower revision.

However luckily there was a revision 2 MM bootloader so it didn't get rejected.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] joowdx:
As far as I can tell, yes it does.

Ohh okay I see it took me so long to understand this. Thanks for the info and everything man :)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] mikail21:
Hi there

Can u help me with rooting of a500G without pc? Ive tried all kinds of rooting apk but to no avail.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Nope, not possible. Find a PC.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] T-Rex:
guys can someone please upload MM boot loader so we don't have to download the ROM completely (approx 2.1 GO )

THANKS GUYS
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
A520FXXU2AQF7_6.0.1_sboot.tar
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] T-Rex:
can i use it with the Russian nougat firmware A520FXXU2BQK1 ?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
Probably.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] T-Rex:
Thank you so much i was stuck at the Samsung logo but after i followed these steps everything went very well

thank you again
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] morx:
Guys, i have a problem....

Tried to root my phone.

Downloaded Odin v3.12 as topic says.

Downloaded SuperSU 2.79 as topic says too.

Connected my phone on download mode @ Odin, set everything good and PASS.

Booted in TWRP and didnt swipe like guide said.

Went in to flash SuperSU and right after, said /data (and some other) were failed to be mount.

Phone restarted and when prompted me to ender my PIN, right after that i couldnt move on. Was asking me to erase all my data cause of encryption.

I ended up in boot loop cause of that. Thought i could flash again TWRP and take the steps again one by one, but when i tried to enter recovery now it says:

Recovery is not seandroid enfocring

custom binary blocked by FRP lock

What can i do ?

Phone is just out of its box! Just received it to root it. :(

Original CSC when i tried that, was A520FOXX2BQG7
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] morx:
Good news, i managed to run KIES3 and recover from there.

Started downloading the latest official firmware (which, too bad is November update).

Phone recovered fully, all went well.

Tried once again to reproduce the steps on this guide (1st post) BUT FAILED AGAIN.

USB Debugging: ON as usual.

When superSU tries to install, it says cannot mount data.

When i press reboot, phone asks me to erase all data and factory reset. I have no other option, so it's on a boot loop.

Am i missing something?

I just reflashed stock firmware again and im just trying to figure out how the hell im gonna root this damn phone.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
As previously posted, consult original twrp thread.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] morx:
Could you guide me on that?

Where's a good step by step thread?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] ashyx:
All the info you need is in the twrp thread in the development section.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] leakcim56:
Hello,
[MENTION=4899305]ashyx[/MENTION] : there is a thread for the A5 2017 but why don't you create a good one as you do for the A3 2017? :confused:

I think your tutorials are much more better presented. :good:
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] morx:
Ashyx, thanks for your suggestion.

I searched about the topic you mentioned and all went pretty well.

I have my November update firmware (latest) rooted.

I agree with [MENTION=6298945]leakcim56[/MENTION] ... we lack good topics.

I went ahead step by step and in the process i found out that i'm missing a lot of info!
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] AtmaDarkwolf:
Idk whats changed recently, but just today my phone tried to update magisk (unsure if the manager or magisk itself, i blindly accepted it without thinking) and it got stuck in a bootloop (was able to get into recovery, but unable to do ANYTHING via recovery anymore, sideload, push, etc, nothing worked)

So I redid it all as i normally have to do*(IE complete reset phone with fresh stock boot, exact same ones I used before) but now, the phone instantly (even before I was able to get past any of the setup process to enable dev mode) downloaded some update and from then on I'm unable to install TWRP (Flashes fine via odin but will not actually work, phone has no working recovery anymore) and am unable to install magisk, unable to disable or remove bloat, etc.

I don't know whats changed but sadly I feel the phone is garbage now.

(A520W version, this process worked 3 months ago when I did it, but it will not now)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] MatRybnO:
http://www.teamandroid.com/2017/02/27/install-galaxy-a5-2017-twrp-3-0-2-recovery-complete-guide/2/

tu macie poprawny root
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
I wish I had heard about this before I tried to use Chainfire auto root and soft bricked my phone. After reinstalling stock firmware, I came here to seek information on rooting via TWRP and only now have I found out about this. I must say, it is very disappointing to hear that Samsung has decided to lock the bootloader on the a5, seemingly arbitrarily. After going through all the warning screens about the risks of using a custom OS and rooting when you go to enable OEM unlock, Samsung should see fit to let you make your own decision. It doesn't feel fair to have the the bootloader quietly locked like this, especially when I bought my A5 with the assurance that it would be easily rootable. It's such a shame to see Samsung go down this path.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] musv:
Hi there,

today my (wife's) A5 has been arrived. In the past we owned an Galaxy S4 and S3. I've read about the problems when rooting this thing. Therefore I'm not really sure, if I should do this torture. The device is already updated to 7.0 Nougat stock. I've activated the developer options, USB-debugging and OEM-unlock. I tried to access the Fastboot-Mode, which worked without any problems.

Some questions:

Odin Replacement: I know, this forum is quite a strong windows bastion. Nevertheless I don't have any Windows here. Can I use Heimdall instead of Odin? What about the plain command line tools like adb and fastboot? Or are the any known issues?

Russian Rom: In this Video Tutorial they insist of using the Russian Nougat Rom. Is that really necessary? I really would like to avoid flashing a whole rom only to get root access.

Magisk: This Howto uses SuperSU. AFAIK Magisk is to prefer to disable temporary root in order to get the official updates. Does anyone got the device rooted with Magisk instead of SuperSU?

Offical Updates: How about the official Samsung Updates? On the S4 and S3, the system update notifications stopped completely after rooting the device. How is this done with the A5? I don't want to stay with an unpatched system.

Build number is: NRD90M.A520FXXU2BQJ6
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] Charles Miller:
I'm something of novice myself, but I can partly answer some of your questions from knowledge that I gained while reseaching the topic. So far as I know, Odin is the only flashing tool for Samsung devices. It's actually what Samsung itself uses. With regards to adb and fastboot commands, I've heard that you can use them to unlock bootloaders, but I could never get it work properly with my a5. Fastboot tools in particular seem to be especially incompatible. I couldn't even get it to recognize my device. If you get it to work, that's great.

You don't need a russian rom. People can root without it, but recent events seem to dictate that you are going to need to do some creative flashing to get root access, anyway. Specifically, the current method seems to involve flashing the current firmware in every category of Odin except for the bootloader. You use the bootloader from Marshmallow 6.0.1 in place of the nougat bootloader, then follow the guide here normally. You can use Magisk as your root manager. I know people who rooted their a5 with it in the past and I agree that it's a preferable root manager to use, thanks to its root hiding functions. I don't know if the process for installing it is any different, although it may be.

For OTA (over the air) updates and root, they do tend to stop once you root. You can still manually update, with Odin, but updates to a rooted device have a tendency to undo root access, thanks to the way they install. For this reason, it's somewhat preferable for your phone to not auto update all the time.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] musv:
Thanks for your information. It's difficult to get reliable information. After a lot of researching and weighing up the pros and cons I rejected the plan to root the device.

My phone is an Oneplus 3. Rooting is quite easy. And the OTA update process works without any problems on a rooted phone. But here we are talking about Samsung and not Oneplus.

For Rooting and Flashing the Galaxy S4 and S3 I've used Heimdall successfully. As long as I don't know if it doesn't work with the A5 too, it's better not to flash. On the other side I was able to download the PIT. Nevertheless it's not worth to install Windows and the driver package when it works normally out of the box in Linux. The poor Linux support is a big downside in this forum.

The Cons:

No OTA updates anymore.

High chance to brick the device.

Risk that Odin does anything different or additional than Heimdall, which ends up in bricked device.

As Adblocker I've used Adguard. Most of the Samsung Bloatware I was able to deactivate.

But really annoying to me is that Samsung has deactivated the option to join a sdcard to the internal memory. Even in adb shell the commands didn't produce the preferable result. Will invest today some more hours to figure out, how I can change the standard folders for Download, DCIM and Documents to the external card. Already yesterday I've moved the download folder to the external card, which ended up to have 2 download folders (internal and external) after the next download.

My conclusion is I wouldn't have bought and I wouldn't buy a Samsung device. But the Oneplus and other comparable smartphones looked to "male" to my wife. Maybe Samsung produces reliable hardware. But the whole software part is a no-go for me.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] metallslug:
Thank you so much!

Just did this yesterday night, works flawlessly. You should create a new topic with this tutorial or pin this post somewhere, it could be useful to many people.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] takkob:
Hi there.. well, I read some pages but did not find the solution between the problem and the last "thx.. it worked".. maybe I'm blind, but can anybody describe how to root the BQK (7.0).. downgrade BL to BQJ or BQE (7.0) or to the 6.0.1 version? Will that work? I don't know if tsarig's solution is the right one to my problem ;)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] moozer:
Read the OP? Search XDA? Have you done this first?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] takkob:
for hours.. the point is, that it seems to be mixed 6.0.1 and 7.0 and when somebody writes.. "it works" or something like that I don't know which stock he is running.. also not the guy that found a solution. I'd prefer a prerooted debloated stockbased 7.0 rom ;)

^^'ve seen, you're on LineageOS, have seen the only issue that cam crashes when you want to film and read lte won't work properly, any other problems?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] moozer:
The result is only the bootloader being from MM, the rest is N.

On LOS, LTE randomly works then doesn't. I have no issue with it and just use 3G. Camera can be annoying as sometimes if doesn't focus in video. Sometimes.

No other issues.

Probably best ROM is Stockmini - it's stock based but debloated and a few extra bits on top.

I'm returning to version 5 of it now as version 3 was a bit hit and miss....the reason why I went with LOS
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] takkob:
I'll give stockmini a try.. I have to flash MM BL first? stockmini seems to be prerooted, great. I think I read yesterday about this rom but now I didn'Ät find the information - I think the Samsung Story got deleted. Right? If so, can it be reinstalled to change the theme or is it possible in another way? ..on my S7 i need that store..
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] moozer:
Should be a straightforward flash. As for Samsung store.....I don't know bro.

Just make sure you backup your current ROM. If you use titanium, you can backup an app to restore into the new ROM
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] takkob:
no need to backup, just bought it and flashed the newest stock.

"straightforward flash" aka "just-flash-twrp-put-the-rom-on-sd-and-flash-in-twrp"? ;)
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tavli:
new firmware A520FXXU3BQL1

twrp it will be possible to deliver?
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
It's upgraded to U3 which is the binary version.

If the last U2 was locked already, this will definitely lock it, with no chance to ever downgrade to U2 again.

---------- Post added at 03:39 AM ---------- Previous post was at 03:36 AM ----------

This can ofc be a preparation for Oreo update.
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] takkob:
Stockmini worked, but was not rooted.. installed magisk manager, tried to flash magisk in twrp.. didn't boot again.

^^stock with mm bl did also not work. it boots but as soon as twrp was flashed, it writes an error while booting that it has to do a factory reset.. tries and writes that again :/
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] moozer:
I flashed it myself. Rooted. No problem
[Samsung Galaxy A3, A5, A7 (2017) Guides, News, & D] tys0n:
If you're referring to the " kernel is not seandroid enforcing"" message is actually not an error. It's just info that you're running a modified kernel. It can be quite easily removed tho.