Database Users

[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat

https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!

What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it

alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk

Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way

This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.

chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu

The only advice I can give to either of you is to try reflashing TWRP again

Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4

Well im glad it worked out for you in the end

It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2

How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.

This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.

alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?

I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.

1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.

s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks

chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems

Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?

pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.

help me guys I missed OTA update

Help me guys I got notification of new system update to lollipop and i pressed download before it finish it showed me that it's up to date and check now as if i was dreaming. And please do not tell me to flash the factory image

msadek122 said:
Help me guys I got notification of new system update to lollipop and i pressed download before it finish it showed me that it's up to date and check now as if i was dreaming. And please do not tell me to flash the factory image
Click to expand...
Click to collapse
what do you expect anyone to tell? wait until you see that notification again.

msadek122 said:
Help me guys I got notification of new system update to lollipop and i pressed download before it finish it showed me that it's up to date and check now as if i was dreaming. And please do not tell me to flash the factory image
Click to expand...
Click to collapse
I had the notification and downloaded it to install when i got time. Removed root and reflashed stock recovery etc. to do the update. But after a few reboots the notification just disappeared, and i haent seen it since... Hope it returns! I don't wanna sideload it, people are reporting bootloops and other wierd errors...

tommyhj said:
I had the notification and downloaded it to install when i got time. Removed root and reflashed stock recovery etc. to do the update. But after a few reboots the notification just disappeared, and i haent seen it since... Hope it returns! I don't wanna sideload it, people are reporting bootloops and other wierd errors...
Click to expand...
Click to collapse
Can you, please, tell me how you reflashed the stock recovery? Did you unlock the bootloader and loose data to flash it or not? I have CWM Recovery and I wnat to flash back the stock recovery, but I didn't find any solution on how to flash it without unlocking the bootloader and loose data, although I was able to install CWM with a locked bootloader.

veketash said:
Can you, please, tell me how you reflashed the stock recovery? Did you unlock the bootloader and loose data to flash it or not? I have CWM Recovery and I wnat to flash back the stock recovery, but I didn't find any solution on how to flash it without unlocking the bootloader and loose data, although I was able to install CWM with a locked bootloader.
Click to expand...
Click to collapse
I didn't loose any data.
First i used Towel-root to get root - not from the Play Store, google it.
Then I unlocked the bootloader with the app Bootunlocker from Play Store - it does it without loosing any data and without rebooting phone.
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Re-locked the bootloader with Bootunlocker
Uninstalled all apps that made system changes, like Xposed and BetterBatteryStats etc.
Removed Root with SuperSU cleanup function afterwards.
First time i rebooted i got a dead android with exclamation mark and some error message, but holding power to shut it down and turn it on agan, and everything worked.
I dont know if it will be enough for the OTA to install though, as even slight tampering will break it... I suspect that when/if i get the OTA notification and apply it, i will get the bootloop bug because of my tampering, but it's worth a shot I have a nandroid backup, so I can always go back and try sideloading the lollipop OTA or fastboot flashing the boot/system/recovery images (never tried that before though, so i don't know how exactly to do that, lol).
Has anyone tried to apply the regular OTA after rolling back system changes like above?

tommyhj said:
I didn't loose any data.
First i used Towel-root to get root - not from the Play Store, google it.
Then I unlocked the bootloader with the app Bootunlocker from Play Store - it does it without loosing any data and without rebooting phone.
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Re-locked the bootloader with Bootunlocker
Uninstalled all apps that made system changes, like Xposed and BetterBatteryStats etc.
Removed Root with SuperSU cleanup function afterwards.
...........
Thank you for your response! Maybe if I wasn't so hurried I wouldn't have installed 5.0 with factory image. After I posted the question I decided to make a clean install and I don't regret it.
Your explanation is good and thank you again for it! Maybe it will help someone.:good:
Click to expand...
Click to collapse

How to restore IMEI number on a official rom?

okay now I am starting to get lost and the guide for ''fixing your IMEI number'' caused my phone to soft-brick once again so it didn't really help
and yes I used the most recent SuperSU (stable) version V2.78 (I hope that is a correct version)
http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
my baseband gives a I think correct version but my IMEI number still is ''0''
Please!, can anyone tell me how to restore my IMEI number?

Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed

dempixels said:
Also my phone uses tries to use LTE connection like I have U.S. drivers (I don't know if it makes a difference since I am pretty much noob)
I find that just wierd.. sorry to bother you guys with all this, I just want my phone to be fixed
Click to expand...
Click to collapse
Did you try to make a complete reset of the phone?

Dio-Genes said:
Did you try to make a complete reset of the phone?
Click to expand...
Click to collapse
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.

dempixels said:
And how am I gonna do that?
the only thing I know and have done is: flashing a official rom on the device that's it
Click to expand...
Click to collapse
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486

Dio-Genes said:
EXACTLY!!! follow these instructions step by step. Take a look how many sparsechunk files are in the image that you download and proceed as advised. Take care to choose the right image for your device, also about country and so.
http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''

bablu048 said:
Download the zip from the oneplus link... extract it and read the "REEEEEADME.TXT" last paragraph how to type Imei in "RF_NV_manager.exe"...PM me if you need more help.
Click to expand...
Click to collapse
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.

dempixels said:
well that's just it, it requires root but it's always when I install superSU that my phone soft-bricks. it's the third time that happened.
Click to expand...
Click to collapse
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
Have you downgraded earlier??

dempixels said:
I've downloaded the EU image just how it was supposed to go, and installed it in correct order. even though it keeps saying ''Pre-flash validation failed''
Click to expand...
Click to collapse
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.

Dio-Genes said:
As far as I remember that happened to me when I tried to relock the bootloader at that moment. Did it work anyway? I mean, did it reboot? Which image did you choose? 5.1 or 6.x? Probably start with 5.1 as this was the original image for the device and later let it update via OTA. Be sure still to grab the appropriate image.
Click to expand...
Click to collapse
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
also some further info:
I think in the past when I tried to install the official stock rom. I accidentally removed/erased the EFS file. or some file that holds my IMEI information.
and now I practically have to re-write it (since.. well you can't just create a IMEI ID or Can I?). but it seems impossible if I look at it.
but I do have the original box with the original IMEI number.

bablu048 said:
Here use this su2.62-3 it will work. http://forum.xda-developers.com/showpost.php?p=64452858&postcount=1
And remember NOT TO RESTORE THE QCN OF ONEPLUS edit your imei using RFNVmanager only.
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Have you downgraded earlier??
Click to expand...
Click to collapse
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?

dempixels said:
According to the Motorola official developer forums I am not ALLOWED to install a android 5.X image when I last ran a 6.X android system. as the result could be that I could Hard brick my device
.
Click to expand...
Click to collapse
Sorry, that's beyond my knowledge.

dempixels said:
no I didn't downgrade earlier. (well i flashed a different logo.bin) but no I didn't downgrade.
so that means the superSU 2.78 does not work on android 6.X?
Click to expand...
Click to collapse
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.

bablu048 said:
Idk about su2.78... I have always used su2.62-3 ..it worked on lollipop and it works on MM.
What is the need of updating SU app, all it does is give 'root' permissions.
Click to expand...
Click to collapse
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that

dempixels said:
okay, because you have more experience rooting I am gonna ask you just to be sure.
correct me if i'm wrong:
first I have to flash twrp thingy
next I have to reboot android and copy SuperSU into my storage
then I have to reboot in fastboot and boot into twrp
in twrp I have to flash/install SuperSU into the system.
and.. that's it. so superSU practically roots my device?
oh and from what i've heard/seen I will not be able to update anymore? because when I installed/flash superSU I saw in the log:
''disabling OTA update survival'' or something like that
Click to expand...
Click to collapse
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
alright 2 final questions before I am gonna start the whole flashing again
1. does this superSU version work with 6.0.1? (just to be sure)
2.what does it backup to be precise? only the system or everything (probably everything)

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
YES!! it's rooted thanks for the guide but now... ermm.. how do I change my IMEI number?

bablu048 said:
Yes correct, After flashing twrp take a backup(to be on the safe side) then install su.
Click to expand...
Click to collapse
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?

dempixels said:
and.... nevermind.. it did not root!... what?
I don't understand I followed the steps on how to install superSU with systemless.. something and it all worked. but it did not root! how is that possible?
do I have to try it again?
Click to expand...
Click to collapse
you dont have su app even after flashing su2.62-3??

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?

Mi a1 bricked please help

I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).

DeadsetNub said:
I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).
Click to expand...
Click to collapse
Did you uninstall magisk through recovery or within magisk manager?

DeadsetNub said:
I unlocked bootloader and installed Magisk using twrp recovery mode, then I've uninstalled magisk like normal app and locked bootloader, after that my device was showing a pop up that "System got destroyed". Then I unlocked bootloader again, after this I was able to get into my system but I've face a problem after successfully boot, I wasn't able to turn on wifi, then I've locked bootloader again now I'm having touch issues as well like I can't touch exact part of screen. Please help me out ,(Tried mi flash, doesn't work, getting error)(Sorry for bad English).
Click to expand...
Click to collapse
Make sure boot.img and other firmware images and system images are from same release. Mostly you are facing firmware compatibility issues

WhatzIt2Ya said:
Did you uninstall magisk through recovery or within magisk manager?
Click to expand...
Click to collapse
firstly I've uninstall magisk like normal apps . app info-> Uninstall.

satishbmsce said:
Make sure boot.img and other firmware images and system images are from same release. Mostly you are facing firmware compatibility issues
Click to expand...
Click to collapse
How can I check it ? tbh I'm noob ?

DeadsetNub said:
firstly I've uninstall magisk like normal apps . app info-> Uninstall.
Click to expand...
Click to collapse
Well that's already a problem, the phone is still rooted. By locking the bootloader while the phone is rooted is a big no no. You'll cause all sorts of problems.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
DeadsetNub said:
firstly I've uninstall magisk like normal apps . app info-> Uninstall.
Click to expand...
Click to collapse
You need to download magisk uninstaller zip and flash it in twrp. If you still have twrp (with unlocked bootloader), flash it, boot the phone, relfash rom with mi flash tool.

WhatzIt2Ya said:
Well that's already a problem, the phone is still rooted. By locking the bootloader while the phone is rooted is a big no no. You'll cause all sorts of problems.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
You need to download magisk uninstaller zip and flash it in twrp. If you still have twrp (with unlocked bootloader), flash it, boot the phone, relfash rom with mi flash tool.
Click to expand...
Click to collapse
can you please tell me the procedure ?

DeadsetNub said:
can you please tell me the procedure ?
Click to expand...
Click to collapse
the thing is I'm having touch issue in TWRP mode as well.

DeadsetNub said:
How can I check it ? tbh I'm noob ?
Click to expand...
Click to collapse
If you are not sure. You can download a new fastboot stcok rom from MIUI website and flash it using MiFlash tool. Make sure that you select 'clean_all' option while flashing. You should not select 'clean_all_and_lock', that will lock the boot loader and it might lead to more issues

DeadsetNub said:
can you please tell me the procedure ?
Click to expand...
Click to collapse
I can't tell you the exact, because I never had this issue before, sorry.