Database Users

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.

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

TWRP for P580 running Oreo?

Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!

I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!

Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:

use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:

Latest twrp dose not worked on my device but this solution work fine

I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse

Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse

If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.

Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally

This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.

amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!

Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.

We should ask a dev to update twrp for android 8.1

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode

Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.

On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?

I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen

Magisk 23 to 24 ruined

Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.

[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html

Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8

xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.

try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .

xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.

Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!

Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?

xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?

As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.

xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯

xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img

magisk 24 is ****, it's bricking MediaTek powered Samsung phones

Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.