Related
[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0
1) Unlock your bootloader . for complete unlocking process go here.
https://m.youtube.com/watch?v=sw675ipX-ds&feature=youtu.be
IT WILL RESET ALL YOUR DATA.
2) Turn on USB debugging on
3) Boot your device into bootloader mode
4) flash TWRP recovery v2.8.7 r5. http://forum.xda-developers.com/devdb/project/?id=11051#downloads
5) Boot into TWRP recovery
6) Flash supersu zip v2.62-3. http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
7) After succsesfull flashing wipe cache/dalvik cache . reboot system. If it asks to install Root. DO NOT INSTALL ROOT AT THIS STAGE.
8) wait till Boot finishes.
9) If you want to install Xposed Boot into TWRP recovery.
10) Flash Xposed installer xposed-v79-sdk23-arm.zip. http://forum.xda-developers.com/showthread.php?t=3034811.
Thanks for contributors of TWRP, Supersu and Xposed.
I am G-Root...ed
Thanks man!, being trying a lot with no succes... till now... Excelent Work :good:
abhijeetc9762 said:
1) Turn on USB ) .
Click to expand...
Click to collapse
do we have twrp for moto g turbo?
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
abhijeetc9762 said:
3) flash TWRP recovery v2.8.7 r5.
Click to expand...
Click to collapse
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
You don't have chance anyway after rooting. You have to have Flash the firmware again to receive OTA
Sent from my MotoG3 using XDA Premium 4 mobile app
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Tel864 said:
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Click to expand...
Click to collapse
In an earlier post you indicated that you can simply do a full unroot with SuperSU and receive OTA updates. Did that only apply to 5.1.1 and not 6.0?
Tel864 said:
I was able to d/l the update, but had to unroot to install the update. If you're using SuperSU to root, it's a simple matter to use the SuperSU app and do a full unroot, then just root again after the update.
Click to expand...
Click to collapse
Kakaroth89 said:
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
Click to expand...
Click to collapse
Same question. Coming from a Nexus 4 phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
EDIT (01-20-2016): Thanks for adding the missing unlock bootloader step to the instructions. I just ordered a Moto G yesterday.
pjc123 said:
Same question. Coming from a Nexus phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
Click to expand...
Click to collapse
To root you will need an unlocked bootloader.
Any one?
Rooted xt1550 with supersu 2.62 and then deleted moto bloatware, now phone stuck on black screen after rebooting. Any help abt deleting bloatware?
Seems fine..but
just done this and boot up looks normal but seems forever to boot up. It has not boot up yet, what is the estimated time to wait?
Does it matter if TWRP is configured as "Read Only" or not?
Tel864 said:
To root you will need an unlocked bootloader.
Click to expand...
Click to collapse
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Kakaroth89 said:
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Click to expand...
Click to collapse
No, all your data and apps will still be there.
Tel864 said:
No, all your data and apps will still be there.
Click to expand...
Click to collapse
I lost all apps and data when I unlocked bootloader.. I did not unlock until after the 6.0 upgrade.
MrTooPhone said:
Does it matter if TWRP is configured as "Read Only" or not?
Click to expand...
Click to collapse
Do no tick as read only.
Sent from my MotoG3 using XDA Premium 4 mobile app
OP updated for bootloader unlocking procedure
Sent from my MotoG3 using XDA Premium 4 mobile app
abhijeetc9762 said:
5) Boot into TWRP recovery
Click to expand...
Click to collapse
@abhijeetc Excellent instructions. One recommendation is to address the issue with the "read only" TWRP option. I am sometimes presented with this option during TWRP boot (not sure why this option is not presented every time since I never check "don't show again"). I am not sure if "read only" makes a difference or not. But I can confirm I was soft bricked after enabling read only and flashing 2.66. I did not wipe Dalvik/Cache either. I was successful with 2.62-3 but was not presented "read only" option either. Also, you may want to recommend a Nandroid back up prior to any attempt flashing root. Just a recommendation.
I notice under developer settings (tap Build Number a bunch of times in the "About Phone" section to access developer mode) it has the option "OEM unlocking - Allow bootloader to be unlocked" as an option. Does that make this process any easier or is it necessary? I bought my phone straight from motomaker.
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.
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.
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?
I have a v20 US996 (unlocked) that I'm getting ready to unlock the bootloader and then I'll want to root. I've always rooted with SuperSU in the past, but now there is also Magisk.
For our v20s (US996):
1) Should we use Magisk instead of SuperSU?
2) Is it as stable as SuperSU (without random reboots, etc)?
3) If 1+2 are "yes" then where can I find out how to root with Magisk safely without any problems?
Thanks!
I say yes to your first two questions. I accidentally upgraded to 10H on the 996 and I thought I was stuck with an unrootable phone. I had already had an unlocked bootloader and I used ADB to flash TWRP, flashed Magisk and boom. Rooted again. Been happy ever since. I don't have the exact thread for Magisk but if you Google I wanna say Magisk 14.0 you should be able to find it. Been working great for me. Hope that helps.
Anyone else's thoughts?
Also, will I still be able to use the 2nd screen?
And where can I find instructions specific to the v20?
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Sizzlechest said:
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Click to expand...
Click to collapse
Especially with chainfire retiring, now is all the more reason to use magisk only. I've been using supersu for the entire duration of my smart phones but I need to make the switch.
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
baldybill said:
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
GreenDinoXD said:
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
Click to expand...
Click to collapse
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
baldybill said:
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
Click to expand...
Click to collapse
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
GreenDinoXD said:
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
Click to expand...
Click to collapse
Please do, I don't want to mess up my phone.
It's never been unlocked or rooted. [Currently, I'm having trouble getting the unlock image from LG. ]
Okay i am going to copy the exact text that the person who helped me said. It is really well explained and he says the steps very clearly. To do a TWRP backup and restore it it's one of the main buttons on the screen, I highly recommend using an SD card. Use the select storage button to change between internal storage and the SDcard, just check the box for data, and that has all your apps and pretty much everything else. And when you do the kdz part below you can just restore the version f firmware and do the update that way and skip the ota. I copy and pasted most of the rest from the last time I typed this up.
Get a hold of LGUP and downloading the kdz, heres (https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817) a good thread on it, with even all the tools attached except the kdz, for getting on the older more stable twrp just flash flash it in fastboot (use lgup to restore the kdz which gets back to full stock, then use fastboot to get the info needed to fill out the form on LG's site(https://developer.lge.com/resource/mobile/RetrieveBootloader.dev), (basically this guide has it all listed out, plus once you've created an lg account and actually gotten to the form, the page with has directions too(http://www.droidviews.com/unlock-bootloader-on-lg-v20-us996/))
So heres how we're going to get twrp on here from a stock, but unlocked us996. You probably don't need the no-verity-opt-encrypt if also flashing supersu or magisk but I did it anyway to be safe.First get the latest version of no-verity-opt-encrypt.zip from here(https://build.nethunter.com/android-tools/no-verity-opt-encrypt/), and the stable version of Twrp-3.0.2-1-us996.img from a different directory on the same site(https://build.nethunter.com/test-builds/twrp/lge/), if you have an sd card in your phone put the no-verity zip on it ahead of time (and if you want to save a boot, put magisk on there too) (if not twrp should let you transfer it from your pc, but I havn't done it that way). So go ahead and reboot into fastboot (adb reboot bootloader) mode, then fastboot flash the_FULL_PATH_to_twrp-3.0.2-1-us996.img . once it successfully completes, until we flash the no verity zip in twrp if the phone boots into stock it will overwrite twrp and it will need to be reflashed in fastboot mode. So once you've flashed it the first time, pull the battery, wait a second, then put it back in, hold down volume down, hold the power button just until the LG logo appears, then let go of the power button, and immediately press (and release) it once while still holding down volume down, keep holding volume down until, if you've done it successfully, it will ask you to factory reset your phone (for future note, while twrp is installed this will NOT factory reset your phone), say yes both times and twrp will boot shortly.
From here, go to install, and then change to your sd card and install the no-verity-opt-encrypt.zip, then go back and hit wipe (in twrp), on the wipe screen, hit the format data button (the correct button will make you type out yes to confirm), from here twrp will be installed and not tampered with and you can safely install magisk or a custom rom, and/or boot back into stock.
I do not know where i downloaded magisk from but here is the latest version:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
I'm in a similar situation, with a fresh US996 factory-unlocked. Does this method (stock + magisk + twrp) preserve Android Pay / SafetyNet?
I switched from SuperSU to Magisk and now I can download Netflix from Play Store.
Switch away if you want to.
Thanks, GreenDinaXD, I'll give that a try after a while.
Thanks
GreenDinoXD said:
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
Click to expand...
Click to collapse
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
baldybill said:
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
Click to expand...
Click to collapse
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
With my experience from MagiskSU, absolutely, Magisk let's you use any anti-root app, like Snapchat, or Netflix, etc... So you don't need to go through the Xposed McCluster**** ordeal
GreenDinoXD said:
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
Click to expand...
Click to collapse
Are there stability issues with Magisk? Random reboots?
I'm curious since this is my everyday phone and I want it to be running decently. Thanks!