Database Users

[Guide] Rooting G800F on Marshmallow 6.0.1 + getting Xposed framework

UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.

weird enough all those files where already on my pc. i just wanted to know if it would work

it says no root

Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?

kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work

I also have 6.0.1 Germany DBT but this didn't root my s5 mini

Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk

Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.

Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.

kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.

Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me

Does this root trigger the knox counter?

Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works

i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you

Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.

Can someone help me? I did it like in the tutorial but it does not work. Thanks all

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.

thanks for answer. Now it work with Version 2.8.0

Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.

Custom Rom For Samsung J2 (J200H) S7 Experience Custom Build

Hey There ...........
Introducing My New Rom : S7 Experience Custom Build
Built V1
Based On Stock 5.1.1 Lollipop Rom
Warnings :
1. You are now Void your Warrenty …….
2. Backup all your personal apps and important data to avoid loosing them …
3. Do all steps perfectly And carefully ……
4. I am not responsible for any mistake and Brick your phone ….[/SIZE]
Features :
1. Only For J2 2015 3G Variants
2. Android 5.1.1 Lollipop
3. Based on latest J200HDDU0APE1/APJ3 firmware
4. Deodexed
5. Medium Deboalted
6. Zipaligned
7. Signed
8. PreRooted
9. Added Busybox,SU.d and Init.d Support
10. S7 Style Statusbar
11. S7 Music Player
12. S7 Themed Apps
13. Xposed Enabled Zip Added
14. All Apps Are Updated
15. Fx Root Explorer
16. Sony Movies Added
17. S7 Wallpaper
18. S7 Icons
19. S7 Sound And Bootanimation
20. And More ...
How To Install :
1. Download Zip file Of the Rom From Link Given Below
2. You Mast Have TWRP Recovery on your device.(Letest TWRP is Given In attachments)
4. Copy the S7 Experience Custom Build.zip toYour SD card
5. Turn off Your Phone And press home button+power+Volume up button at a same time
6. Aftar apearing TWRP recovery go to install and install S7 Experience Custom Build.zip file from sd card you downloaded before
7. Now reboot system and wait for approximately 5 minutes.
9. Now you are good to use this rom ......
[For Xposed Install xposed-v78.0-sdk22-arm-custom-build-by-wanam-20151116.zip after installing rom given in the attachments]
Downloads :
https://drive.google.com/open?id=0B0rTXdhaTd2MV2szTEYtQWVIeVU
Credits :
@ASSAYYED –for his best ever kitchen.
@ashyx - for his Twrp
@me - For building Rom
Contact Me :
On Facebook Only Send Massages
www.facebook.com/almamun512

Thanks
Nice rom the rom like realy galaxy s7 I very like this

Great work . I will soon test it By the way is there theme support and if not are you planning to do it????

ad. said:
Great work . I will soon test it By the way is there theme support and if not are you planning to do it????
Click to expand...
Click to collapse
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.

almamun512 said:
Actually Theme Option Is Enabled But Its Not Change Everything, I Dont Know Why, But thing Is Our Framework Doesn't Suppot That.
Click to expand...
Click to collapse
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do

ad. said:
ok but my phone stick in bootlogo when i tried to install xposed it said unable to mount system ?????? what to do
Click to expand...
Click to collapse
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g

almamun512 said:
Did You clean Insall It ?
Do Wipe/Advance Wipe/system,data,delvik,catch
Then Install
Make Sure Your Device Is J200H 3g
Click to expand...
Click to collapse
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon

Will it wrk on j200g?

ad. said:
I tried both clean and dirty flash but no sucess ...
I got where the problem is...
system is not being fully extracted . There lacks many folders like priv-app in system partition .
I installed another zip file and noted that every thing is working well the system got fully extracted.
Maybe the problem is in updater-script Hope you can fix it soon
Click to expand...
Click to collapse
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot

almamun512 said:
Can you send me a picture of the error or something.
There Should be no problem in updater-script
Also send me your about devices screenshot
Click to expand...
Click to collapse
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify

ad. said:
http://imgur.com/GYMLjJL
here's the ss about phone and i cant send picture of error but I'm sure the problem was caused due to the problem in system
The flashing had went smoothly but when i tried to boot to system i got atuck at samsung galaxy j2 screen and on checking system via twrp file manager i gound ther lacked different things.
I don't know if its the problem of my twrp or else I'm thinking of giving one try to flashify
Click to expand...
Click to collapse
What Rom Are U Using Stock ?
I Dont think so.
Anyway Its strongly Recommended to be on letest Stock Rom Before Flashing My Custom Rom.
Nobody Having this Problem Like You.
And Use the TWRP I gave in attachment.

Not working....
Sent from my SM-J200H using XDA Free mobile app

wow this rom is better than i expected

in twrk recovery i got msg regarding it succeeded. but after that my mobile is still booting showing samsung j2 android. pl help me.

finally got it
Best rom out till date.
thanks @almamun512

No superuser access
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?

Nikeshsml said:
I flashed this custom rom today and i like the new UI. But there is no superuser preinstalled although it said installing superuser when flashing the rom. I also installed supersu later using twrp but it says " Your device is unrooted."
How can i install superuser and gain root access ?
Click to expand...
Click to collapse
I didn't experienced that problem. The phone was rooted only SuperSU app was missing which I installed.

Good day sir. I appreciate your hardwork creating the rom. :good: Will it work on a j200bt rom?

GREAT ROM
Beautiful Rom and fast but the problem i faced was the wifi reconnecting every 2 minutes and cant customize the rom by apps like gravity box ....
battery is friendly and i hope to make update for this vertion of S7 because the S8 Randomly restart without any reason
thanks a lot from my heart .

Rom can be flash in samsung J200GDDUZAQF6
PLEASE REPLY ME

[GUIDE] 2 Minutes Magisk installation, Best Method +OTA

Hey hey hey !!! I'm back for a new method, for flash Magisk without patched_boot.img or select current-slot etc, just by do 2 things. And it works for all phone version, Sable, Beta.... ( We use TWRP temporarily, so after the process, TWRP is gone)
Credits :
Me for the idea.
@Frustrated Indian the tester.
@TingyiChen for this nice TWRP.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about features
included in this GUIDE before using it! YOU are choosing to
make these modifications.
Of course first you must have the drivers installed on your pc. And an unlocked bootloader + unlock critical partition, if it is not, follow this procedure :
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
- And follow phone on screen steps to validate unlock bootloader...
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
Downloads :
- TWRP here
- Magisk Latest Beta / Stable (if you prefer) zip
- Magisk Uninstaller zip
Steps :
- Download TWRP
- Copy it to your pc adb folder
- Rename it to twrp.img
- Download Magisk Installer
- Download Magisk Uninstall
- Place these 2 folders on your phone storage
- Reboot phone to fastboot
- Open fastboot command prompt on your pc
- Type "fastboot boot twrp.img" without quotes
- Your phone will boot twrp
- Decrypt data with your pin if needed
- Click install and select the Magisk Installer zip, swipe to confirm
- Wait for the process
- Reboot
That's it !! You now have root on your phone, and TWRP is gone.
If you have issues you can uninstall Magisk with the Uninstaller zip.
For OTA just uninstall Magisk using Magisk Manager, by flash the stock boot.img to your current-slot, or using the zip and flash it like the Magisk Installer.
Check my other thread, Part 3 : OTA for more informations.

-reserved-

I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?

After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773

Magisk link not work.

kishd said:
After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773
Click to expand...
Click to collapse
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.

SpectraFun said:
Magisk link not work.
Click to expand...
Click to collapse
Fixed. sorry it was an issue when we click links using XDA phone app. Have a nice day.
Matteo

Adairo said:
I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?
Click to expand...
Click to collapse
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).

Atlas/ML said:
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.
Click to expand...
Click to collapse
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.

kishd said:
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.
Click to expand...
Click to collapse
flash stock kernel has no sense. that's why it doesn't work. if you have issue you should just flash boot.img or flash magisk uninstaller in twrp like magisk zip. sometime hex kernel cause some issues . for me with all version tested, with help of the maintainer @draco I'm not able to boot fine. I have a green glitchy screen etc, and after some boot my device screen stuck on black screen.

works fine, thank you!

bavmouse said:
works fine, thank you!
Click to expand...
Click to collapse
I'm glad to hear it, enjoy

Atlas/ML said:
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).
Click to expand...
Click to collapse
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2

Adairo said:
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2
Click to expand...
Click to collapse
I recommend you to use magisk and install systemless xposed.

Atlas/ML said:
I recommend you to use magisk and install systemless xposed.
Click to expand...
Click to collapse
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition

Adairo said:
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition
Click to expand...
Click to collapse
okay, give me results if it works. good luck

Atlas/ML said:
okay, give me results if it works. good luck
Click to expand...
Click to collapse
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device

Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
hum, interesting

I'm on September update and want to update to the October one, I've tried doing everything in Part 3 but no success. Any solution that let me keep my data?

Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
Xposed will not work untill we get a deodexed stock rom or custom rom

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 !

(S4 GT-i9506) TWRP for Android 13 ?

Hi, so my phone is running Android 13 (LineageOS 20.0) and i have TWRP (3.5.2_9-0) installed, recovery was working before flashing Android 13 but now it wont boot for some reason (stuck on TWRP splash). I think i need an higher version of TWRP. If anyone could help or provide a link it would be really helpful. (Also my phone is currently rooted using Magisk)

VistaSlayer said:
Hi, so my phone is running Android 13 (LineageOS 20.0) and i have TWRP (3.5.2_9-0) installed, recovery was working before flashing Android 13 but now it wont boot for some reason (stuck on TWRP splash). I think i need an higher version of TWRP. If anyone could help or provide a link it would be really helpful. (Also my phone is currently rooted using Magisk)
Click to expand...
Click to collapse
LineageOS uses its own recovery. If you wanted to keep TWRP, you should install it in the second step after ROM.zip.

ze7zez said:
LineageOS uses its own recovery. If you wanted to keep TWRP, you should install it in the second step after ROM.zip.
Click to expand...
Click to collapse
Unofficial LineageOS 20.0 Android 13
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com
I installed LineageOS from here, but there is no install steps :/

VistaSlayer said:
(...)
I installed LineageOS from here, but there is no install steps :/
Click to expand...
Click to collapse
Install LineageOS on ks01lte | LineageOS Wiki
wiki.lineageos.org
The developer does not need to describe the method and variant of installation. It is up to the potential user to find the way and learn it.

ze7zez said:
Install LineageOS on ks01lte | LineageOS Wiki
wiki.lineageos.org
The developer does not need to describe the method and variant of installation. It is up to the potential user to find the way and learn it.
Click to expand...
Click to collapse
In fact, it installed succesfully (phone was on Android 5 ATM) and now TWRP wont boot bcuz it needs to be an updated version but i cant seem to find it. TWRP 3.5.2 wont boot under Android 13, i need 3.7.x

VistaSlayer said:
In fact, it installed succesfully (phone was on Android 5 ATM) and now TWRP wont boot bcuz it needs to be an updated version but i cant seem to find it. TWRP 3.5.2 wont boot under Android 13, i need 3.7.x
Click to expand...
Click to collapse
TWRP doesn't need any android to boot as it uses the recovery partition (in case of S4). All it needs is access to the data partition to save the configuration.

ze7zez said:
TWRP doesn't need any android to boot as it uses the recovery partition (in case of S4). All it needs is access to the data partition to save the configuration.
Click to expand...
Click to collapse
Weird, i cant get TWRP to boot but Lineage Recovery works

VistaSlayer said:
Weird, i cant get TWRP to boot but Lineage Recovery works
Click to expand...
Click to collapse
How did you flash TWRP?

ze7zez said:
How did you flash TWRP?
Click to expand...
Click to collapse
Tried Odin Mode and Official TWRP APP

VistaSlayer said:
Tried Odin Mode and Official TWRP APP
Click to expand...
Click to collapse
Try this Lineage 18.1 first and see if everything works, because everything should work.

ze7zez said:
Try this Lineage 18.1 first and see if everything works, because everything should work.
Click to expand...
Click to collapse
The TWRP from this post boots on Lineage 20, thanks for your help