Database Users

[HOW-TO] [GUIDE] [MM] Encrypt device with custom rom, knox 1, twrp installed, rooted

This Guide will work on S7 and S7 Edge Variants, probably also on other Samsung Phones. It doesn't matter if you have xposed and/or supersu installed
I did lately try to encrypt my device after installing my rom. So I tried to search on xda but I couldn't find anything useful until now.
After quit some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Attention, TWRP can't read /data partition after this guide, that's because twrp doesn't support samsungs encryption at all
Pre requests:
- A working pc with adb installed
- Enough battery (at least 80%)
- Charger in your near field
- Working internet connection
Steps:
1. Go to SuperSU application on your device
2. Head over to the settings Tab
3. Scroll down and hit Full unroot
4. Click continue, when it asks you to install stock boot.img say NO, also NO on restoring stock recovery
5. SuperSU app should disappear
6. Make one full reboot
7. Head over to settings, lock screen and security, set a password
8. Plug in your charger and start encryption
9. Wait until your phone has fully encrypted (this can take quit some time)
10. After your device has successfully encrypted, we want to gain root access again
11. Boot into TWRP recovery
12. You now need a pc with working adb connection
13. Click adb sideload on twrp
14. Download latest super su to your PC, you can get that from here: Beta Thread
15. Open a terminal on your PC
16. Put the supersu.zip in the same direction as your terminal is opened (example: user/home)
17. Type into terminal: adb sideload *supersu_name*.zip
18. Reboot your phone and you have a working, encrypted phone with root installed!
If this guide helped you, please share it and hit thanks as well! :good:

Tkkg1994 said:
After quite some time I finally managed it to get a working encryption, even with custom rom installed (which contains root and xposed). I will present the following steps here to help you folks to get an encrypted device.
Root will work as always after encryption :highfive:
Click to expand...
Click to collapse
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?

lost_ said:
:highfive:
Reverting/decrypting data would require a data wipe from TWRP, correct?
Click to expand...
Click to collapse
Exactly, with twrp or stock recovery

With TWRP not being abled to access /data partition, would it still be possible to make a complete nandroid? Second, what about updates of the custom ROM? Isn't the complete phone encrypted after the process, like /system and external sd as well?
Swyped via Tapatalk

what about systemless posed. would it work with the encryption, or it must be uninstalled.
I would like to try and encrypt my phone but I have systemless xposed installed and I would like to keep it. any information on that regards ?

Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...

@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?

bruzzy said:
@Tkkg1994 : Hi, I tried this method while using your Superman ROM, but unfortunatly it didn't work for me. After un-root the encryption application behaved as before: It started, saying "Encrypting...", but after some minutes it just rebooted with doing anything. So the device is still not encrypted. I read somewhere else, that in order to get the encryption working, the stock boot.img needs to be flashed. But that instruction have been for a different device, I guess dealing with a standard android encryption (as far as I now, Samsung uses a different one).
I'm just wondering, what would happen when I choose 'Yes' for replacing boot.img in step 4?
Click to expand...
Click to collapse
That step 4 actually means you should restore your boot.img.
I did it exactly this way and it worked back then when I tested it. Many things have changed since then. So it may needs some adaptions
Sent from my Hydra powered SM-N930F

OK, I tried the other option as well (i. e. saying 'yes' on the question about testoring the boot.img). What about the kernel, do you know which one you used at that time? I'm currently on the Superstock Kernel. So curious, whether this might have any effect as well...
Sent from my SM-G930F using XDA-Developers mobile app

@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!

bruzzy said:
@Tkkg1994: Sorry for pushing, but do you remember, which kernel you've used? And can you also tell me, what exactly is the difference between the Stock and the Superstock kernel in your Superman ROM? Thanks!
Click to expand...
Click to collapse
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone

tefole said:
Unfortunately it didnt worked for me. After i starting the encryption the phone does make a usual restart and i dont see any encryption process.
It just reboots. I am running cfw "S7 extreme debloated".
Any ideas?
btw: how safe is a rooted and encrypted phone, if you can replace any time the custom recovery?
are the encrypted partitions /data and /sdcard really safe?
Thanks...
Click to expand...
Click to collapse
I managed to encrypt by choosing full unroot in supersu app (say no to image restore questions).
Sadly, with a bootloader open, encryption will be as good as a password used. It's only entered once upon boot if you use fingerprints.
After encrypting root can be installed by flashing the zip again from sdcard or adb sideload.

Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.

hav0c said:
Does not work for me. After I sideload SuperSU the phone does boot but my password is not recognised anymore.
Click to expand...
Click to collapse
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.

Hi,
Does anyone have experience encrypting s7 nougat superstock rom? Wondering if it is the same. Because nougat has file-based encryption.

gnowak84 said:
Hi hav0c, Which version did you upload? I used this: CF-Auto-Root-herolte-heroltexx-smg930f.zip.
Click to expand...
Click to collapse
I have used https://download.chainfire.eu/supersu

So this doesn't work if we are using a non-stock kernel?

Tkkg1994 said:
Back then it was stock.
Stock is signed properly by samsung and can be used with trusted UI on while custom kernels have to disable real time kernel protection to even boot the phone
Click to expand...
Click to collapse
Hi Tkkg1994,
Wanted to know if you have any tip on the encrypt? Your work is really great and thanks for that but due to work i need to get the phone encrypt.
So wanted to know if you can help out as i dont want to go on stock firmware
Thank you

I tried following the guide using SuperStock 2.6, but after encryption finishes I get "Verification failed"

I have the same fault, any idea´s to fix same.

Return to Stock? (B20_Boot)

Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204

rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:

Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?

DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!

tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?

Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread

tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader

It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet

peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic

DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?

Working root for honor 8 pro

This is only for Honor 8 Pro (DUK-L09)​
DISCLAIMER​YOUR WARRANTY IS NOW VOID. IN NO WAY AM I RESPONSIBLE FOR THE EFFECTS YOU INFLICT ON YOUR MOBILE DEVICE BY FOLLOWING THE BELOW PROCEDURE. IMPROPER USAGE OF THE METHOD MIGHT END UP BRICKING YOUR DEVICE AND RENDERING IT UNUSABLE.
PLEASE BACKUP ALL YOUR DATA BEFORE PROCEEDING.​
Purpose of this thread is to provide a working rooting method for the Honor 8 Pro. Flashing Phhsuperuser doesn't grant SYSTEM WIDE root permission.
Functions like granting -rw permissions to apps demanding them for accessing /system partition was disabled, TWRP backup wouldn't work.
With this method, you will be able to operate the phone will proper root privileges.
INSTALLATION INSTRUCTIONS
1. UNLOCK BOOTLOADER​
Assuming you have a Huawei ID, use THIS PAGE to get your Unlock code.
Once you have that, enable USB debugging on your device from Developer options menu.
Make sure "Allow OEM unlock" option is selected.
Use the following set of commands via ADB/Fastboot:
adb device (this should recognize your device)
adb reboot bootloader (this will boot your phone into fastboot mode)
fastboot oem unlock *unlock key* (the part between * is where the unlock key goes)
The device will restart and then perform factory reset itself.
2. INSTALL CUSTOM RECOVERY IMAGE (Source : TWRP Thread by OldDroid)​
Download TWRP recovery image from HERE
Rename the downloaded file to recovery.img
Copy it to the ADB folder that you are using.
Use the command "adb reboot bootloader" like in Step 1 to boot into Fastboot mode.
Flash the recovery using "fastboot flash recovery recovery.img" command (without quotes)
You have now flashed a custom recovery onto your phone.​
3. ROOTING
Download Magisk installer zip file from THIS LINK . I had personally used v 13.3 .
Copy it to your SD card(I would suggest you to use a external card).
Switch off your device.
Boot into recovery mode by pressing Volume Up and Power Button together.
Once in, swipe to allow modifications.
Go to Wipe - Format Data
Then Go to Reboot- Recovery
You should be back into the recovery mode. Go to Install menu - Select storage - Install the Magisk zip that you downloaded.
Once it is flashed, you can Reboot to system.
Note: To confirm system wide root access, you can reboot to recovery and try to take a Nandroid backup. It should now be possible.​
If anyone happens to run into a bootloop or soft bricks the device, THIS THREAD by @aKp1 will come in handy.
Thanks to @OldDroid for his TWRP thread.

I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.

Going back to Stock = Unrooting
devilrulz4ever said:
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Click to expand...
Click to collapse
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.

amulbaby said:
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
Click to expand...
Click to collapse
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?

devilrulz4ever said:
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
Click to expand...
Click to collapse
Don't worry . It's the same. File name doesn't matter.

amulbaby said:
Don't worry . It's the same. File name doesn't matter.
Click to expand...
Click to collapse
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Sent from my Honor 8 Pro using XDA Labs

adriansticoid said:
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Click to expand...
Click to collapse
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.

amulbaby said:
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
Click to expand...
Click to collapse
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Sent from my Honor 8 Pro using XDA Labs

Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem

adriansticoid said:
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Click to expand...
Click to collapse
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.

rexinriot said:
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
Click to expand...
Click to collapse
Yes magisk will solve your problem. Phhsuperuser doesn't allow you to grant permissions to any app that tries fiddle with system partition. If you are already rooted , go back to stock and follow the steps outlined.

amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
Dafuuuuq. I waa scared all along because of that. I didn't know things changed in Honor 8 Pro. Thanks a lot.
Sent from my Honor 8 Pro using XDA Labs

amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.

devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You flashed Magisk while encrypted?
Sent from my Honor 8 Pro using XDA Labs

devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.

adriansticoid said:
You flashed Magisk while encrypted?
Click to expand...
Click to collapse
Have you managed to root your device using Magisk yet?

amulbaby said:
Have you managed to root your device using Magisk yet?
Click to expand...
Click to collapse
Not yet. Maybe I'll try tomorrow.
Sent from my Honor 8 Pro using XDA Labs

amulbaby said:
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
Click to expand...
Click to collapse
I wiped data, flashed Magisk v13.3 and then v14 after a successful boot (without wipe).

Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..

rexinriot said:
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
Click to expand...
Click to collapse
Stay with 130. Surprisingly, rooting by this method still allows OTA to come in.

How can I root Samsung Galaxy A5 2016 with Android 7.0

So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help

botetta said:
So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help
Click to expand...
Click to collapse
Flash the latest TWRP recovery via Odin. Download magisk/super su. Go to recovery, put the files you downloaded and flash. Done

sm-a510f said:
Flash the latest TWRP recovery via Odin. Download magisk/super su. Go to recovery, put the files you downloaded and flash. Done
Click to expand...
Click to collapse
Thanks! But doesn't flashing TWRP require an unlocked bootloader? (and unlocking it wipes the phone as far as I know) Or is there a way to flash TWRP without unlocking the bootloader/wiping the phone?

botetta said:
Thanks! But doesn't flashing TWRP require an unlocked bootloader? (and unlocking it wipes the phone as far as I know) Or is there a way to flash TWRP without unlocking the bootloader/wiping the phone?
Click to expand...
Click to collapse
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data

sm-a510f said:
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data
Click to expand...
Click to collapse
Thanks, I'll try it out

sm-a510f said:
No you just need to unlock the OEM in developer settings and go to download mode to flash the recovery. You will lose guaranty but no data
Click to expand...
Click to collapse
Could you please link me the TWRP and the SuperSU that supports Samsung Galaxy A5 2016 7.0? :angel:

For model SM-A510F/FD/Y/M use this guide: https://forum.xda-developers.com/sa...overy-samsung-sm-a510f-fd-exynos7580-t3314399 . For model SM-A510 use this guide: https://forum.xda-developers.com/sa.../twrp-3-0-0-0-galaxy-a52016-sm-a510f-t3313781
---------- Post added at 09:51 AM ---------- Previous post was at 09:42 AM ----------
Also you aren't allowed to post questions in the General section. Look at the sticky post

botetta said:
Could you please link me the TWRP and the SuperSU that supports Samsung Galaxy A5 2016 7.0? :angel:
Click to expand...
Click to collapse
TWRP : https://forum.xda-developers.com/sa...overy-twrp-3-1-0-0-samsung-galaxy-a5-t3606792
Super SU : https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you want to play games like Pokemon go or Super Mario run, you will need magisk instead of superSU

Now, I followed the instructons, and I was able to root my phone succesfully. (Thanks )
In case someone reading this thread wants to know I used:
Odin 3.10.7
twrp_3.0.2-1_sm-a510_mm_1816
SR3-SuperSU-v2.79-SR3-20170114223742.zip
It all worked fine, no data loss, no wifi/camera error, no nothing, but when I turned off my phone, It wouldn't boot back anymore, It said "custom binary is blocked by FRP Lock"
As I've read, this is because I turned off OEM Unlock after rooting, but I'm not sure about this. Appearantly, if I'd leave it on it'd not cause this problem
Since then, my phone is working again, I just had to flash the Stock ROM, and I (fortunatly) didn't lose any data.
But obviously now my root is gone too. Could someone who has tried this confirm that it indeed works (boots up) normally if I leave OEM Unlock on forever?
CrystalGTX said:
Also you aren't allowed to post questions in the General section. Look at the sticky post
Click to expand...
Click to collapse
Sorry about that

botetta said:
Now, I followed the instructons, and I was able to root my phone succesfully. (Thanks )
In case someone reading this thread wants to know I used:
Odin 3.10.7
twrp_3.0.2-1_sm-a510_mm_1816
SR3-SuperSU-v2.79-SR3-20170114223742.zip
Click to expand...
Click to collapse
I've sent you the latest twrp and super SU, why did you choose another one ? They are working perfectly (pm if you want to upgrade your TWRP)

sm-a510f said:
I've sent you the latest twrp and super SU, why did you choose another one ? They are working perfectly (pm if you want to upgrade your TWRP)
Click to expand...
Click to collapse
Well, that's what the other guy sent, I had to choose one of them. BTW, do you always have OEM Unlock turned on, or have you turned it off. If you have it on, I'm pretty sure it's not the TWRP version, it's that I turned OEM off. If it boots without OEM on for you, then I guess I screwed it up, and I should have used the other version

botetta said:
Well, that's what the other guy sent, I had to choose one of them. BTW, do you always have OEM Unlock turned on, or have you turned it off. If you have it on, I'm pretty sure it's not the TWRP version, it's that I turned OEM off. If it boots without OEM on for you, then I guess I screwed it up, and I should have used the other version
Click to expand...
Click to collapse
Next time take my links they are up-to-date. Yes you always need the OEM unlock on, TWRP are nothing to do here.

sm-a510f said:
Next time take my links they are up-to-date. Yes you always need the OEM unlock on, TWRP are nothing to do here.
Click to expand...
Click to collapse
Okay, I'm not sure if I'll try root again, I might, and if I do, I'll use the newer versions, if you say they work perfectly. But the main problem wasn't the older version here, but that I turned off OEM, I guess.
And thanks for all the help, appreciate it

botetta said:
Okay, I'm not sure if I'll try root again, I might, and if I do, I'll use the newer versions, if you say they work perfectly. But the main problem wasn't the older version here, but that I turned off OEM, I guess.
And thanks for all the help, appreciate it
Click to expand...
Click to collapse
Well, If you want to turn off the OEM unlocking and be still rooted. You need to flash stock recovery after rooting. I've never tried it cause I don't care that much. Anyway you don't loose anything if you end up with frp lock. Again flash stock ROM you are good to go. And I've A5-510FD android 7.0 rooted. You may also want to backup to your Samsung account in case you mistakenly format your phone you can restore. That's what I always do.

botetta said:
So, I'd like to root my phone, but I've never done something like this. I've once rooted a phone with KingRoot, but I don't wanna do that again, since that's a pretty shady app. I'd like to root it the normal way, with SuperSU or something.
Also, I don't wanna lose any of my data. I know that anything can go wrong, but I'd just like a method that generally doesn't wipe your phone.
Thanks for any help
Click to expand...
Click to collapse
The best way is to flash Cf Auto root that is compatible with your device using Odin PC.
Download a exact version of CF AUTO ROOT for model number of your device.
Run Odin on your pc and thenConnect your phone to Pc with usb and then go to download mode(Turn off your phone>hold Volume down and Home button and Power button together, a new page will be shown press volume Up for confirmation.
Then press on AP In Odin and select the CF AUTO ROOT file and then press start the process will be started.
Be aware that in this way you will lose your warranty for ever due to Knox warranty void will be tripped and there is no way to return it to back.

UPDATO said:
The best way is to flash Cf Auto root that is compatible with your device using Odin PC.
Download a exact version of CF AUTO ROOT for model number of your device.
Run Odin on your pc and thenConnect your phone to Pc with usb and then go to download mode(Turn off your phone>hold Volume down and Home button and Power button together, a new page will be shown press volume Up for confirmation.
Then press on AP In Odin and select the CF AUTO ROOT file and then press start the process will be started.
Be aware that in this way you will lose your warranty for ever due to Knox warranty void will be tripped and there is no way to return it to back.
Click to expand...
Click to collapse
On the contrary. The best way in my opinion is flashing SuperSU with TWRP.
The reason is TWRP is your safety net should anything go wrong. You will always be able to boot to recovery regardless of the Bootable state of the device.
The whole device can be backed up and restored in minutes as long as /data encryption is not in force.
Then SuperSU can be flashed.
While CF-AUTOROOT is the goto root for simplicity and beginners it's not the preferred way.
Root is rather pointless without a custom recovery to go with it imo.
Once you've rooted the stock recovery becomes dead in the water and useless.

hello everybody!
I'm new here and want to root my Samsung Galaxy A5 (2016) and try some custom ROM.
Here is my phones details:
-Samsung Galaxy A5 (SM-A510F)
-Android 7.0
-Security patch: 1 April 2017
Also on Settings > Software Update, I have set manual update and there is a notification about one new software updates (last check 11/08/2018).
Do you know if its a Operation System update or just a security patch?
Should I do that update or will cause any problems with rooting and custom ROM?
What TWRP should I use and what custom ROM?
Any good guide?
Thanks in advance

Terranti said:
hello everybody!
I'm new here and want to root my Samsung Galaxy A5 (2016) and try some custom ROM.
Here is my phones details:
-Samsung Galaxy A5 (SM-A510F)
-Android 7.0
-Security patch: 1 April 2017
Also on Settings > Software Update, I have set manual update and there is a notification about one new software updates (last check 11/08/2018).
Do you know if its a Operation System update or just a security patch?
Should I do that update or will cause any problems with rooting and custom ROM?
What TWRP should I use and what custom ROM?
Any good guide?
Thanks in advance
Click to expand...
Click to collapse
im like him, any news guys?
any way to root the phone?
thanks!

mironkraft said:
im like him, any news guys?
any way to root the phone?
thanks!
Click to expand...
Click to collapse
Enable "Developer Options" on your phone and enable "OEM Unlock" (Don't disable it ever.)
Go here https://twrp.me/samsung/samsunggalaxya52016exynos.html
Download the latest twrp file (Use the links that says "Primary Download US/EU") (Currently it's twrp-3.2.3-0-a5xelte.img.tar 14/8/2018)
Go here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the latest Magisk file (Currently it's 16.0 / 16.7 if you want to use beta 14/8/2018)
Download Odin
Boot your phone into download mode (Volume Down + Home Button + Power Button)
Plug your device to your computer and open Odin
Go to "Options" tab in Odin and disable "Auto Restart"
Select the TWRP file you have downloaded (Click AP!!!)
Start...
When it's done DON'T BOOT TO SYSTEM YET, boot into recovery!!! (Volume Up + Home Button + Power Button)
Now you should have booted into TWRP
Go to "Install" tab and flash the Magisk file you downloaded
Boot into your system.
You have successfully rooted and installed TWRP to your device. (Hopefully)

TanByv said:
Enable "Developer Options" on your phone and enable "OEM Unlock" (Don't disable it ever.)
Go here https://twrp.me/samsung/samsunggalaxya52016exynos.html
Download the latest twrp file (Use the links that says "Primary Download US/EU") (Currently it's twrp-3.2.3-0-a5xelte.img.tar 14/8/2018)
Go here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the latest Magisk file (Currently it's 16.0 / 16.7 if you want to use beta 14/8/2018)
Download Odin
Boot your phone into download mode (Volume Down + Home Button + Power Button)
Plug your device to your computer and open Odin
Go to "Options" tab in Odin and disable "Auto Restart"
Select the TWRP file you have downloaded (Click AP!!!)
Start...
When it's done DON'T BOOT TO SYSTEM YET, boot into recovery!!! (Volume Up + Home Button + Power Button)
Now you should have booted into TWRP
Go to "Install" tab and flash the Magisk file you downloaded
Boot into your system.
You have successfully rooted and installed TWRP to your device. (Hopefully)
Click to expand...
Click to collapse
Thanks for your response.
That about the software update notification?
Do you know if its a Operation System update or Security patch update?
Should I run it, before root and install a custom ROM or better leave like this?

[Q] Bootloop after May security update

Hey everyone, I need some help.
I have Magisk installed, and wanted to preserve root acces throughout the update (may security patch, ~80MB). I used this guide to do it, uninstalled Magisk, installed it on 2nd slot during phase 2, rebooted: bootloop. Stuck in an endless cycle: the kernel loads, but always reboots during the andorid one boot animation.
I'm looking for a way to make it functional while not losing my data, or a way to copy my data to a PC before flashing.
What can I do now?
Thanks in advance.

Flash stock ROM
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....

Indiangautam said:
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Click to expand...
Click to collapse
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.

droidx8 said:
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
Click to expand...
Click to collapse
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....

Indiangautam said:
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Click to expand...
Click to collapse
Well let's not do that then, there could be another way... Thanks anyway!

droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
As you wish....but if want to try my process then definitely your phone will bootup

droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
You can choose to not wipe your data.
It's the "flash all except storage.bat"
You can download the last firmware here
http://en.miui.com/getrom.php?r=333&m=yes&app=false
You must have fastboot on your PC windows or Linux
So if you have a Windows just search how to install fastboot on Windows there's some great one on xda
Unzip the firmware open the flash all except storage bat
Remove both lines that contains
-OEM unlock
-OEM lock
Otherwise your data will be wiped and as you use magisk you want an unlocked bootloader
Open a powershell windows where the .bat file is
Then type without the quotes
"./flash_all_except_storage.bat"
Flashing procedure will take a few minutes on system partition but don't freak out
Once it's done reboot you'll be on 9.5.11 ROM version
You'll receive a 60mb ota to have the last one which is 9.11.13
You can boot TWRP to flash magisk now
And on next update download the last firmware
9.5.13 should be on the first link I gave you (there is always a delay between ota that are just patch and a full firmware that contains all the files)
Flash the boot.img or just reflash the ROM like above apply ota and reflash magisk
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there

Dead-neM said:
You can choose to not wipe your data.
It's the "flash all except storage.bat"
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Click to expand...
Click to collapse
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.

droidx8 said:
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
Click to expand...
Click to collapse
Really nice to hear. Have fun with this little Beasty device