Database Users

[SM-P905] Upgrade to Rooted Official Lollipop 5.0.2 - can be downgraded

** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7 (of course the language can be set to English after installation). This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before June 2014 and root it with Towelroot).
2- FlashFire app v 0.17 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Procedure
1- Make a back up of all your files.
2- Download your Lollipop ROM from Sammobile and unzip the .zip file to get the tar.md5 file. Copy the tar.md5 file to your sdcard.
3- Run FlashFire. Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
4- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Also choose Highly recommended but optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
5- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open process cache and uncheck all the items. Open EverRoot and select Inject SuperSU and unckeck the other options.
6- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage.
7- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, followed by the rest.
8- Tap the Reboot box and select Reboot to Recovery.
9- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
10- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Troubleshooting
If after the upgrade you suspect something does not work, install Flashfire on your rooted lollipop and start from step 4 again.
If you experience random reboots freeze or otherwise disable knox and update programs.
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.

najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
This has been tested with the Italian firmware released on 4/30/2015, PDA: P905XXUABOD7, CSC: P905ITVABOD7. This method should however work for other Lollipop releases as they become available in your region. This method does not trip the knox flag.
Requirements
1- Rooted KitKat (the easiest way to get root is to flash a ROM dated before July 2014 and root it with Towelroot).
2- FlashFire app v 0.16 or higher: The only way to get it is by following the instructions at: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
3- SuperSU update zip version 2.46 or higher.
Procedure
1- Make a back up of all your files
2- Download your Lollipop ROM from Sammobile, unzip it and copy the tar.md5 file to your sdcard
3- Download SuperSU update zip and copy it to the sdcard.
4- Run FlashFire.
5- Tap the +, Flash Firmware Package, and select the tar.md5 file. It will scan the file and opens a menu of option to choose.
6- Choose: Boot, Recovery, System, Cache, Preloaded/Hidden.
Optional: Modem Firmware (modem.bin) and Firmware (NON-HLOS). If you select these you should answer NO when it asks you "You are flashing both normal and ..."
The rest should be unchecked. Now tap the check mark at the top right corner of the dialog box.
7- When that is done, FlashFire adds two items to the list of actions: Process Cache and EverRoot. Open each one and uncheck all the items under both
8- Tap the + again and choose Wipe. Select System, Dalvik, and Cache. I highly recommend that you check 3rd party apps too, which will erase your existing apps and settings but it will give you a clean install. Do not select Internal storage unless you want your internal SD card erased too.
9- Tap the + again, Flash Zip or OTA, and select the SuperSU update Zip. Leave Automount unchecked
10- Tap and hold to move the boxes containing the actions to get them in this order: Wipe, Flash Firmware Package, Flash Zip or OTA, followed by the rest.
11- Hit the FLASH sign at the bottom of the page and hit OK. THE SCREEN WILL GO COMPLETELY BLANK DURING THE FLASHING OPERATION. Do not freak out. This is a bug in the tool and will hopefully be fixed in a future version. After 5-10 minutes your tablet reboots. If it takes longer than 20 minutes something is wrong.
12- During the first reboot it may take 5-10 minutes before you get the initial setup dialog. (If it takes longer than 20 minutes something is wrong.) Complete it and you will be on rooted Lollipop.
TiP: Settings -> General -> Security -> Security Policy Updates -> Uncheck Automatic Updates, and also Settings -> General -> About Device -> Software Updates -> Uncheck Auto Updates
Downgrade
If you are not happy with the results, or something goes wrong, download a KitKat firmware from Sammobile and flash it in ODIN. Make sure to clean cache and data in recovery.
Click to expand...
Click to collapse
Thank you very much for this!
I wonder if could you please attach the odin files as you did with 4.4.2 thread.
Thanks in advance.

I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.

perce_ption said:
I guess Xposed will not work on our lovely Touchwizzed-Lolipop device?
Please let me know if anyone tried it.
Click to expand...
Click to collapse
Don't need to try.... Straight from the developer...
https://github.com/rovo89/XposedTools/issues/3#issuecomment-96386801

Screenshots
Please can u post screenshots for the updated apps or launcher!!
I have sm-p901

Thanks. Follow the instructions exactly and everything works.
PS: Set from Singapore.

works great, thanks
(sm-p905) italy.

Impossible
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!

AdjoX said:
can't even register at the website to download the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!!website to d
ownload the Rom. Its impossible to solve the puzzle- even though Ke done it 22 times!!! HELP!
Click to expand...
Click to collapse
did you try to register from a mobile device? If so try to register from a PC or a laptop and download the files there.

Thanks for the instructions.
Does anyone have a flashable bootloader package? From experience Lollipop is unstable with the old bootloader....at least it was on the N9005.
EDIT: Have successfully upgraded. Initially left the Apps and data but the tablet got stock on "checking connection" during the initial setup. A fectory reset did dix that but also cleared the internal Sd card

Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.

sudo.sh said:
Well, I did two simple steps: upgraded up to 5.0.2 and flashed http://forum.xda-developers.com/showpost.php?p=50498424&postcount=235 CF-Root via Odin. Works fine.
Click to expand...
Click to collapse
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.

najoor said:
Pleasee note that flashing CF autoroot trips your knox flag irreversibly, if that is important for you.
Click to expand...
Click to collapse
at the loading?

sudo.sh said:
at the loading?
Click to expand...
Click to collapse
The knox is knocked at the first reboot after the Odin flash. For you it shouldn't matter because you have already done it. Not a big deal. People have differing opinions about the consequences of tripping knox. I normally try to keep it unchanged on my devices but I don't have a personal opinion on that.

Yes, the Knox is knocked, and it doesn't matter for me.

sudo.sh said:
Yes, the Knox is knocked, and it doesn't matter for me.
Click to expand...
Click to collapse
Will this work for the 905V, Verizon with locked bootloader?
Sent from my SM-P905V using Tapatalk

Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.

aviator1 said:
Works fine, but I had a huge battery consumption until I flashed with Odin the Bootloader, the Kernel and the modem.
Click to expand...
Click to collapse
You don't need to flash bootloader, just make sure you flash the modem when you use flashfire.

I did flash the modem in flashfire, then observed huge battery consumption. After that I reflashed the modem plus flashed the kernel the kernel, but the battery went from 80 to 50% in less than two hours using it not more than 1/2 hour, then I flashed the bootloader and consumption was back to normal (approximately 1% consumption per hour in idle mode). I know that the bootloader shouldn't affect the battery consumption, but that's what happened to me.

I seem to be having an issue with the security. After following instructions, upon boot I get an error "System software not authorized by Verizon Wireless has been found on your phone."
Anyone have any ideas? I'm gonna try getting on a Windows computer and using Odin (I'm on linux)
Edit: I'm back on stock, seems this is blocked by the Verizon bootloader. It's a shame they feel the need to cripple such a good piece of hardware.
Thanks

sm-s903vl to verizon Sm-g900v firmware

Anyone think it be possible to flash the straight talk s5 sm-s903vl to verizon Sm-g900v 6.0.1 firmware in odin? it has the same fcc label as a verizon s5. Just wondering.

gbnm88 said:
Anyone think it be possible to flash the straight talk s5 sm-s903vl to verizon Sm-ng900v 6.0.1 firmware in odin? it has the same fcc label as a verizon s5. Just wondering.
Click to expand...
Click to collapse
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.

betzj911 said:
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.
Click to expand...
Click to collapse
can you please provide a short tutorial on how you exactly did it along with some download links? i found moto chopper but couldnt find any kernels online. im in the same boat but havent had any luck at all with root. i just got this phone and its running marshmallow 6.0.1 with model of sm-s903vl. i also wanted to ask that it did for sure worked with no issues of what you did. i accidentally used a kernel of a firmware before on my S4 from verizon and got a hard brick afterwards so im just trying to be cautious about messing with any kernels beings last time i did change a kernel to an earlier part, it gave the hard brick. i want to be sure that this wont do the same thing beings its going from kernel of 6.0 to .4.4. thanks

please let me know. so many people are wondering how to root this phone on 6.0.

Ditto!!!

I have been wondering about this myself. I know the verizon s3 custom roms would work on the straight talk branded s3.

Bump

Does anyone know the link to motochopper 1.1? I would be satisfied with just root privileges.

taymo said:
Does anyone know the link to motochopper 1.1? I would be satisfied with just root privileges.
Click to expand...
Click to collapse
just google it but motochopper alone doesn't give root. I've tried. I've also tried flashing the kernel and it fails so I'm not sure what the person did to get root using that program. Sorry. He won't reply to any messages ether for some reason.

Bump

I found this thread. I am having no luck with it but I am also not as experienced as some... Can someone test this out and let me know if the root method works for them?
https://forum.xda-developers.com/galaxy-s5/general/straight-talk-galaxy-s5-t3318898

HOW TO FLASH G900V (KK 4.4.4) on the SM-S903VL, AND ROOT IT!
betzj911 said:
I've tried using the said firmware starting from an update all the way to the full tar.md5. No luck. All I get is errors. Being straight talks with Wal-Mart, I believe Wal-Mart bought out the rights to the phone and have had the thing locked down tight. But not impossible. I was able to get root using motochopper 1.1. I noticed that even though it wouldn't let me flash any firmware it would let a kernel module slip by. So I used the kernel module for the G900V_ NCG 4.4.2 and was able to root using mottochopper followed by Supersu . After all that I rebooted into download mode and reflashed the Ph3 kernel mod.
Click to expand...
Click to collapse
ODIN will NOT allow FLASHING the BOOT.IMG/ABOOT of the G900V firmware due to the
bootloader being locked down on SM-903VL ( Secure Boot Enabled won't accept G900V kernels! )
But you can downgrade to SM-903VL Factory Test 4.4..2, which allows you to get ROOT!
Once ROOTED & BusyBox is installed, you can "flash" the system/cache IMG's thru the ADB shell as ROOT.
You will end up with SM-903VL 4.4.2 Kernel + G900V KK 4.4.4 System ROM ( Can be rooted with TowelRoot )
KingRoot is only used to Root the Factory Test FW. Once you "flash" the G900V files, you will lose root
(ie. KingRoot is wiped from phone, along with all other data) Simply use TowelRoot to root the G900V FW.
( You will need WIFI or DATA for TR to work though! )
================================================== =================
The Steps I used to go from SM-903VL MM 6.01 to ROOTED G900V KK 4.4.4
( See original posts here: https://forum.xda-developers.com/galaxy-s5/general/downgrade-to-4-4-2-factory-test-t3530449/page8
================================================== =================
download the official stable version of ODIN 3.12.3 here: http://samsungodin.com/
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick ) https://drive.google.com/open?id=0B4...mkyZkNIMVhrOUk
Download & downgrade to the factory test 4.4.2 SM-903vl ( Using ODIN , use "AP" button for the .MD5 file )
link: https://drive.google.com/open?id=0B4...ndnaWN1cGZ2Snc
root using KINGROOT PC version (windows) - INTERNET REQUIRED for KR to work! here: https://kingroot.net/thank-you-for-d...t-for-windows/
*** NOTE: YOU MUST HAVE STABLE INTERNET CONNECTION for KR to work!. Exit & run KR again if no root.
after ROOT successful, manually install stericson version of busybox: here: https://www.apk4fun.com/apk/6139/
( copy apk to internal SD via PC mtp & install it from MY FILES )
*** install phoneinfo.apk if your LTE DATA does not work - BEFORE "flashing" G900V rom!!!!
The STEALTH-LTE does not appear to work in G900V, so if you need to fix APN
do it now!
download the G900V KK 4.4.4 firmware here: https://www.androidfilehost.com/?fid=23991606952607146
or https://samsung-firmware.org/download/Galaxy S5 (Verizon)/858s/VZW/G900VVRU1ANK2/G900VVZW1ANK2/
(Windows use simg2img https://github.com/KinglyWayne/simg2img_win)
(Linux use a package manager to install simg2img)
Unzip the G900V KitKat Files to a folder, and then:
( use the simg2img command to CONVERT the IMG.EXT4 system & cache files to .IMG format )
use simg2img on cache.img.ext4 also ( *** temporarily rename it to system.ext4.img)
put the ext4 files in the same folder as simg2img.exe
open terminal or CMD prompt, then type:
simg2img system.img.ext4 system.img
simg2img cache.img.ext4 cache.img
then copy the system.img & cache.img to your INTERNAL SD card
next run these commands from linux terminal ( or Windows CMD prompt ):
adb shell
su
stop
dd if=/sdcard/cache.img of=/dev/block/platform/msm_sdcc.1/by-name/cache bs=10485760
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=10485760
**** Then exit the adb shell by typing exit (enter) 2 times to get back to command prompt, then
adb reboot recovery
let recovery do its thing, then when it reboots and is on the samsung boot screen
quickly do another
adb reboot recovery
then do a wipe data (Factory reset), then reboot
( I downloaded these APKS manually on PC, & copied to SD. WIFI will work on phone, but not DATA until you fix APN! )
install TR.APK ( Towelroot 3.0 ) and ROOT your phone https://towelroot.com/tr.apk
install stericson busybox-free ( found it here: https://www.apk4fun.com/apk/6139/ )
install the PhoneInfo.apk and FIX the APN for LTE data to work (Link on this page FIX APN SETTINGS post)
install XPOSED INSTALLER 2.6.1 ( KITKAT ) if you want xposed - google it
install SElinuxToggle.apk from XDA to be able to change SElinux to Permissive - google it
install SuperSu from playstore, upgrade binary & disable knox - Normal Mode ( as theres no custom recovery )
install ViperFX & ViperXHifi ( The BEST AUDIO MOD by far! Nothing can touch this! ) - google it
install a file manager with root capabilites: Rename the ContextProvider.apk in /system/priv-app/ folder to ContextProvider.apk.old
you should have ROOTED G900V normal KK 4.4.4 rom with XPOSED & Viper4Android Audio
Everything should work, EXCEPT for the FINGERPRINT SCANNER
MOBILE HOTSPOT works!
=========================================
phoneinfo.apk instructions:
Download Phone Info app to SDcard: http://apk.center/down_Phone-INFO-Sa...apkcenter.html
When it boots sideload phone info.apk from SD Open Phone Info app Click on Secret Codes Click launch STEALTHMODE Click LTE APN SETTINGS Hit the + to add APN
Enter the follow information;
Name=Verizon Internet APN=TRACFONE.VZWENTP Proxy=(LEAVE BLANK) Port=(LEAVE BLANK) Username=(LEAVE BLANK) Password=(LEAVE BLANK) Server=(LEAVE BLANK) MMSC=(LEAVE BLANK) Multimedia message proxy=(LEAVE BLANK) Multimedia message port=(LEAVE BLANK) MCC=311 MNC=480 Authorization type=None Click menu in right hand corner and save Select new APN APN type=default,dun Bearer=Unspecified Mobile virtual network operator type=None
Click menu in right corner save. Select new APN reboot phone.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
This info did not come from me. I just copied & pasted it from the URL given above, so I do not take any credit for this.
If this works for someone, post a reply
=====================================================================
*** I DO NOT TAKE CREDIT FOR THIS... I PUT ALL THE PIECES TOGETHER FROM DIFFERENT SOURCES ***
But, did want to share the steps used in more detail to do this! Thanks XDA Members!!!!
---------- Post added at 04:42 PM ---------- Previous post was at 04:08 PM ----------
If you are feeling ADVENTUROUS, you could experiment using Lollipop or Marshmallow G900V system/cache IMGs instead,
following the instructions above ( AT YOUR OWN RISK of course )
You would need to GOOGLE to see if the version of G900V can be rooted first, though.
This may or may not work using the S903VL Factory Test KERNEL 4.4.2 ( BOOT.IMG ) with LL/MM - IDK.
IDK if flashing the ORIGINAL STOCK MM 6.01 KERNEL ( BOOT.IMG ) after ROOTING would give better performance,
or end up causing loss of ROOT.
Any Guinea Pigs out there willing to try? lol.
link to G900V stock fimwares: https://samsung-firmware.org/model/SM-G900V/
(I did flash the MODEM.BIN of the Original SM-903VL MM 6.01 by extracting it from the AP-md5 file, making a .TAR of the modem.bin,
and flashing it using ODIN AP mode. It appears the MM modem is faster than the 4.4.2 Factory test version BTW )
---------- Post added at 04:50 PM ---------- Previous post was at 04:42 PM ----------
taymo said:
I found this thread. I am having no luck with it but I am also not as experienced as some... Can someone test this out and let me know if the root method works for them?
https://forum.xda-developers.com/galaxy-s5/general/straight-talk-galaxy-s5-t3318898
Click to expand...
Click to collapse
I have posted a way to get ROOT on SM-S903VL and convert it to G900V KK 4.4.4.
I have been using it for awhile now and it works great. ROOTED, XPOSED, MOBILE HOTSPOT, etc WORKS.
Just the FIngerPrint scannner doesnt work ( due to mismatched KERNEL / SYSTEM ROM versions )
ALL ELSE IS GOOD!

DeepPurple72 said:
download the SM-903vl 6.01 stock image ( in case you need to recover / de-brick )
Click to expand...
Click to collapse
The Link that you have is dead. Can you repost the link?

gamer82987 said:
The Link that you have is dead. Can you repost the link?
Click to expand...
Click to collapse
I don't have this device but, I did a little searching for the correct and updated links for the downloads from those instructions.
Keep in mind that I don't have this device nor had provided those instructions but, some of those links are outdated as well as not being correctly formatted.
The following is just a list of a handful of the correct and updated links and not all of them since there's a few still good.
PLEASE only use them in place of the others but, still use those instructions
ODIN 3.12.3
https://androidfilehost.com/?fid=745425885120703496
SM-903vl 6.01 stock image:
https://drive.google.com/file/d/0B4954IfsDiYKUmkyZkNIMVhrOUk
Factory test 4.4.2 SM-903vl:
https://drive.google.com/file/d/0B4954IfsDiYKendnaWN1cGZ2Snc
KINGROOT PC version (windows):
http://king.myapp.com/myapp/kdown/img/KingRootSetup_v3.5.0.1157_105203.exe
BusyBox (Stericson):
https://www.apkmirror.com/apk/steph...ericson/busybox-stephen-stericson-60-release/
G900V KK 4.4.4 firmware: here:
https://androidfilehost.com/?fid=746010030569954769
Phone Info app:
https://www.apkmirror.com/apk/vndng...ne-info-★samsung★-3-5-9-android-apk-download/
The SELinux Toggler App (Discontinued)...
Use the SELinux Switch App:
https://androidfilehost.com/?fid=890129502657595824
SuperSu:
https://androidfilehost.com/?fid=889964283620755129
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Thank You!
I will try these out tonight. Thanks!

Root, recovery and custom rom setup for Galaxy S5 (SM-G900I)

Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.

just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method

Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.

^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh

Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.

Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!

Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.

[ROOT] SM-G532F/G532G/G532M - Galaxy J2 GRAND PRIME PLUS (2016)

Below you will find my procedure to root the SM-G532F/G532G/SM-G532M Galaxy J2 GRAND PRIME PLUS/ Mediatek MT6737T.
This will root your device with SR3-SuperSU-v2.79-SR3-20170114223742
This procedure may work for previous and future firmware releases or it may not, however it is intended for the firmware versions as posted below. If you encounter issues simply flash the stock boot image included with the download.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
STATUS: Tested working
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the respective files below:
For SM-G532F based on AQD1 firmware- root_and_boot_sm-g532f
For SM-G532G based on AQC4 firmware - root_and_boot_sm-g532g
For SM-G532M based on AQD2 firmware - SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_31517
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to DOWNLOAD mode then connect your USB cable.
◘ 4. Run ODIN and place either SuperSU-v2.79-SR3_rooted_boot_sm-g532f_AQD1.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532g_AQC4.tar or SuperSU-v2.79-SR3_rooted_boot_sm-g532m_AQD2_3151 as is in the AP slot. Don't change any options and hit START.
◘ 5. Wait for the device to flash and reboot.
◘ 6. Install the SuperSU apk from Play store and you should be rooted.
◘ 7. Have fun!
Credits: ME, @Chainfire and my tester @ShaDisNX255
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU

I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!

ShaDisNX255 said:
I wish I could try this out
I've got the M variant, but it's good to know a recognized contributor is somewhat interested in this device.
Keep up the good work!
Click to expand...
Click to collapse
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.

ashyx said:
There isn't actually any difference between models except region, so it's likely any one of these boot images may work.
However I will look at the M variant also.
Click to expand...
Click to collapse
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"

ShaDisNX255 said:
I'd totally test it out if you include a file for the M variant.
I would flash newest firmware first, flash the file that you would upload and see if it works.
I am currently rooted on "G532MUMU1APIG" firmware.
I think the newest available firmware for me is "G532MUBU1AQA3"
Click to expand...
Click to collapse
AQD2 is the latest.
Leave it with me.

ashyx said:
AQD2 is the latest.
Leave it with me.
Click to expand...
Click to collapse
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing

ShaDisNX255 said:
Aaaah yes, that is correct.
Sorry, I was looking at my carrier's specific firmware update (TCE G532MUBU1AQC1 is the last update they have sent out)
Count me in for testing
Click to expand...
Click to collapse
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.

ashyx said:
Follow the procedure above: https://www.androidfilehost.com/?fid=745425885120735954
NOTE: Not always required, but if your device is using encryption it may be be necessary to format the /data partiton AFTER flashing the boot image for the device to boot.
.
Click to expand...
Click to collapse
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?

ShaDisNX255 said:
I'm fully backing up and will proceed to test this root method.
I will be back in a few minutes
---------- Post added at 06:22 PM ---------- Previous post was at 05:37 PM ----------
After installing SuperSU apk from the play store, I open it up (expecting to get something regarding updating binary) but instead I get a message: SuperSU Binary occupied
I'm guessing this means I am not rooted?
Click to expand...
Click to collapse
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/

ashyx said:
Are you using magisk or some other root application?
I also suggest to install V2.79 apk as the latest Supersu updates are having issues.
http://www.apkmirror.com/apk/coding...79-release/supersu-2-79-android-apk-download/
Click to expand...
Click to collapse
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
Click to expand...
Click to collapse
Also, this seems to have broken my IMEI. I got IMEI unknown

ShaDisNX255 said:
Aaaah, that was the issue. I downloaded SuperSU from the app store which was 2.82. Now that I downloaded 2.79 it opens and I do get the message to update binary. However, I get a pop up message saying that KNOX has been detected, if I should try to remove it. Wether I select "Never" or "Ok", I get an error saying that the instalation failed, that I should reboot and try again. No luck after a couple of reboots.
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
Also, this seems to have broken my IMEI. I got IMEI unknown
Click to expand...
Click to collapse
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?

Not work for my phone
Everybody help me please

AlexEvans6 said:
Not work for my phone
Everybody help me please
Click to expand...
Click to collapse
What does that actually mean?

ashyx said:
The problem is once the bad version has been installed it doesn't automatically get removed by rolling back and the binary won't update, but you should still have root.
All this has been documented in the supersu beta thread.
https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
To start afresh delete su.img from /data then just reboot or wipe the /data partition in recovery.
Regarding the IMEI issue. This is related to a kernel/firmware mismatch.
You should be running the AQD2 firmware.
Which firmware are you currently running?
Click to expand...
Click to collapse
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.

ShaDisNX255 said:
I am running (or was) AQA3 since that is the firmware I have downloaded to my computer at the moment. I am trying to download the firmware from samsung-firmware (AQD2) but it seems my download keeps getting cancelled and sammobile doesn't have AQD2 yet.
Went ahead and took it a step forward and re-flashed stock AQA3 via Odin, set it up again and flashed your file and same thing happened. It asked me to update binary, tried updating binary and states that it fails, not before, once again, requesting me to remove Knox.
I will once again try to download AQD2 firmware but I don't think it would make much a difference (or it could, you never know)
Tried it also with the APIG firmware I have that I originally rooted with and asked me for a password after booting your file even with OEM unlocking turned on.
Click to expand...
Click to collapse
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?

ashyx said:
Is your data partition using encryption?
Im also a little confused regarding the binary update. It doesn't usually ask to disable Knox unless you have root.
Do you have root irrespective of updating the binary or not?
Click to expand...
Click to collapse
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?

ShaDisNX255 said:
I am not sure about how to answer both questions as I'm not sure how to check if the data partition is using encryption or I do not know what exactly do you mean if I have root irrespective?
Click to expand...
Click to collapse
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.

ashyx said:
OK what I mean is, regardless of whether the binary updates or not do you have root?
Do any root checkers or apps gain root privileges?
Unless you've disabled it then it is highly likely your device is encrypted. Encryption causes all sorts of issues with root.
It can be removed by wiping data in recovery but this will wipe everything on internal storage.
Click to expand...
Click to collapse
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?

ShaDisNX255 said:
By wiping everything on the internal storage, you mean everything including media and such, correct?
I always thought that wiping the /data partition only meant everything related to the operating system, not the actual "internal" sd card, though in this phone's case I think they're one in the same.
This phone doesn't have a custom recovery and flashing the firmware I have (AQA3) for some reason has no recovery at all!
Anyway, yeah I tried a root checking app and it didn't detect root.
I will try once again with a root checker app and flashfire to see if either detects root with SuperSU 2.79 and without updating binaries and then try them again after I've tried to update binaries and failing.
My AQD2 download keeps getting interrupted again and again, do you know any other reliable source to download it beside samsung-firmware?
Let me give it a try and I'll give you a heads up.
BTW, how can I disable encryption?
Click to expand...
Click to collapse
Data is the internal storage. It's separate from the system partition where the OS resides. Wiping data basically makes your device factory fresh as it wipes all user apps, settings and media.
In stock recovery it's labelled factory reset.
Every firmware has a recovery even the one you mentioned or your device just wouldn't boot.
If root apps are reporting not rooted then there is an issue somewhere. Quite likely it's encryption on the data partition that's causing the issue.
To remove encryption it is required to wipe data in recovery after flashing the boot image.
If it still doesn't work without encryption then I'm a little unsure of what the issue is as this procedure works just fine on Snapdragon and Exynos devices. It may be some kind of mediatek weirdness.
In any case I have an alternative method which should work, but involves an extra step.
At some point I will be looking at compiling twrp for this device, but I'd like to work out this root issue first.
For fast downloads go to updato.com

ashyx said:
What does that actually mean?
Click to expand...
Click to collapse
Idk help me please

Failed to root my Samsung Galaxy S10+. G975F/DS. Boot-loop after root.

Hello all !
I followed this tutorial on how to root my Galaxy S10+ : https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/ but there are 2 problem:
1st: At the Step6, the file name isn't exactly magisk_patched.tar but magisk_patched-25200_xLm0q.tar. Is this a problem ?
2nd: at Step 10, when I want to exit the Download Mode (Volume Down and Power button for over 7s), the phone get in a boot-loop (which I found online that it means the phone can't find a proper OS to boot on)
How can I know what I'm doing wrong ? I have a doubt on the stock firmware I found on Frija:
my phone is a G975F-DS and there is no "G975F-DS" but only "G975F"
I can't use Phone Info Sam because the link is broken/the app doesn't exist anymore ? When I type *#1234# the CSC code is G975FOXMGHWA3. I searched OXM but couldn't find anything on Frija so I search and I've read that OXM is not the correct CSC Code so I went to Software INFO and in the Service provider software version it's written ...SM-G975F_OXM_XSP... so I chose the XSP firmware and did the root with it until the phone boot-looped.
My service provider now in KT in Korea, does it make a difference ?
Thank you for reading me
Edit: I found Phone INFO ★SAM★ 3.8.5 By vndnguyen on APK Mirror and it says " Firmare's CSC Code: XEF" and "Active CSC Codes: XSP". Which one is correct ?

Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.

First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk

windows4droid said:
First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk
Click to expand...
Click to collapse
Isn't it the same as Step 6 from the tutorial ?
V0latyle said:
Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.
Click to expand...
Click to collapse
May I ask a trustful tutorial on how to do it please ?

Constantine1711 said:
Isn't it the same as Step 6 from the tutorial ?
May I ask a trustful tutorial on how to do it please ?
Click to expand...
Click to collapse
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made

windows4droid said:
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made
Click to expand...
Click to collapse
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip

V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
Yes, you can try twrp
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com

Edit: see below

V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.

Constantine1711 said:
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?

V0latyle said:
What version of Magisk are you using and where did you download it from?
Click to expand...
Click to collapse
I got the v25.2 from magiskmanager.com/

Constantine1711 said:
I got the v25.2 from magiskmanager.com/
Click to expand...
Click to collapse
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.

V0latyle said:
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.
Click to expand...
Click to collapse
Oops ... what's the risk ? Should I reset my phone again ?

Constantine1711 said:
Oops ... what's the risk ? Should I reset my phone again ?
Click to expand...
Click to collapse
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.

V0latyle said:
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.
Click to expand...
Click to collapse
Is it possible to check if an apk is different from the github one ? Like a code checker or something. I'm so tired of reseting my phone it's been a week I try to root it ...
Otherwise, maybe I'll try with an other tutorial.
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
Is this one a good one ?
Is it just me getting older or rooting a device got much more complicated than before ? (I use to root PSP/playstation2 and 3 in the past)
I missed having full control of my device so I thought to root my phone but it's seems so complicated for so little reward
Edit: I tried to follow the official Magisk tutorial but I failed so I'm just gonna stop trying here. Sorry for wasting your time guys !