Installing Magisk v14 on galaxy s4 gt-i9515 - Galaxy S 4 Q&A, Help & Troubleshooting

Hello friends, I am trying to install Magisk on a Galaxy s4 gt-i9515, non-rooted, with TWRP recovery device.
I tried both methods described in the official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both tries failed. I will now explain in more detail what I've done.
Before, note that I have a TWRP recovery of the state before flashing any zips/boot.img s, so I am constantly going back to the previous state which passes safetynet.
First try:
I simply took the magisk-v14.zip file and installed through TWRP. The installation had no errors and in the end TWRP claimed "success". TWRP asked me to reboot now.
I clicked on "Reboot", and then TWRP told that "My device is currently not rooted" and asked if I want to install root or reboot anyways. I rebooted anyways (I didn't let TWRP install his own root).
When the device boot up, I got into magisk manager, but sadly it was written that I am not rooted, and I don't have a magisk installed. Now, it also failed to pass safetynet.
At this point I used my Backup and got back to the state which I could pass safetynet (I've checked it again to make sure).
Second try:
I got the boot.img of the stock firmware I am currently using (I recently flashed this firmware, so it has to be the right boot.img).
I got into Magisk Manager and patched the boot.img. Magisk patched it into a file called "patched_boot.img.tar".
I got into download mode on my device, and flashed the .tar file via ODIN (AP option, ODIN version 3.12.3).
The device rebooted after the installation was "complete" according to ODIN: <OSM> All threads completed. (succeed 1 / failed 0).
When the device booted up, I entered the Magisk manager, and still, no root + no magisk installed. This time tho, it passed SN.
I used my backup again.
Now I am stuck. I really don't know what can I try anymore. Please suggest me ideas.

Up. I still need answers.

i have mnanaged to install latest stable version of magisk using latest twrp 3.1.1.0, and root management is in function. however, i cannot install any magisk module, tested xposed api21 but it does not install, also greenify4magisk still nothing to be noticed, unfortunately as there is yet no response i suppose its a lost cause, well lets just root manually supersu or things like that.

hi, Samsung S4 i 9505 I have not solved with Magisk and I don't even try "patched_boot.img.tar" the problem in it is apk and not the file it TWRP starts I remember apk EdXposed 2 years ago there were failures I thought about installing stock firmware/Rom with Frja Tool we talk about android 10/11 is android 5.0.1 I think there is only one way is SuperSu this root does not pose problems there is a saying: the more cooks around a dish, the more they ruin it"

I was able to install Magisk v24.3 today on my Galaxy S4 Mini LTE (GT-I9195) using partially the "Patching Images" method and TWRP 3.2.3. I had Magisk v23 installed but since a couple of weeks ago it kept crashing. So, I did the big mistake of uninstalling it to update to the latest version. It costed me half a day around this.
I could not flash zips in TWRP recovery (it always failed with Updater process ended with ERROR:1)
1 - Get a copy of the boot.img (for this step I had to find the installation file of my ROM. I did not know for sure which was it since it was installed 2 years ago. I have an AOPK based ROM and all the files from their website are not available anymore. All I could find was an older one on androidfilehost "aokp_serranoltexx_pie_unofficial_2020-01-18_1053.zip". Uncompress this zip to get the boot.img file.
2 - Copy the boot.img to your device filesystem.
3 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash boot.img, reboot
4 - Download and install the latest Magisk v24.3 apk
5 - Press the Install button in Magisk app (this means pressing the second “Install”, the one on front of App.)
6 - It should ask you to choose “Select and Patch a File”. Search and select the boot.img
7 - If all goes well, it should create a file named magisk_patched_[random_strings].img
8 - Power on the phone with "vol down+home+power" to enter TWRP, choose Install, Image, and flash magisk_patched_[random_strings].img, reboot
9 - Reboot and confirm in Magisk app if it says “Installed 24.3 (24300)“.
Now I get a warning "Your device needs additional setup for magisk to work properly... reboot" when entering Magisk, but it seems to work fine.
I have a bottle of champagne saved for the day when windows laptops are miniaturized and android is discontinued from the market. Bootloaders, recoveries, ramdisk, getting root, knox, odin, oem unlockings, CSCs, APs, customs kernels, adb, vbmeta, adoptable storage, se policies, fastboot modes, download modes... damn. They couldn't make it more complex if they tried.

Related

Having Problems Trying to Root / Flash TWRP

Hey all, I've spent my entire night trying to get root on my new OnePlus 5 so that I can transfer all of my data from my Nexus 6p over through TitaniumBackup, but for some reason I am having weird issues.
I've followed Funk Wizard's guide on unlocking the bootloader and getting a custom recovery to root, but that's when weird things began to happen. I flawlessly was able to get TWRP running the first time through since it was similar setup to how I got everything working on my Nexus 6p. Once I tried booting back into the ROM though after flashing Magisk, the boot failed and rebooted back into recovery. This kept happening no matter what I tried to do. TWRP also was failing to flash the full Oxygen OS zips as well. I tried flashing stock recovery over TWRP to see if that would let me flash the zip, but then it stuck me back in TWRP afterwards despite overwriting it. I updated the TWRP to the "last latest build" which allowed me to flash the zip and boot back into my ROM successfully. However, then I tried going back into the recovery, it defaulted to the stock one again rather than the TWRP I had before. I reflashed TWRP but it keeps getting the stock OnePlus 5 recovery consistently. I am unsure of what to do. :\ I have to switch back to my old battery-failing phone for the time being. I'm not sure what I'm doing wrong.
Drivers work; manually forced the ADB driver for fastboot. Device just OTA'd to 4.5.3 a few moments ago; I am still getting the same issue. I also tried the latest TWRP but it still achieved no results whatsoever. All of my flashing is done through fastboot.
Hi I red your problem tho I am new here I successfuly rooted my OnePlus 5.
I think that the problem is either not using proper rooting zip's or bad drivers so I will tell you how I rooted mine.
I reccomend using this tool so you will be sure 100% that you have the ADB, Fastboot and necessary Drivers.
https://forum.xda-developers.com/showthread.php?t=2588979
Those are the files that I used(The Magisk zip file and the recovery):
https://mega.nz/#!AA8FGLZR!63Q4HGrAoIlNlwR_NVj8Rbq4RKoPKaEnHLtHuEW3o94
I do not remember from where I downloaded them, neither I can find them from my messy history cuz I searched a lot for them around the internet, so I upload them for you!
Magisk link:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
So basically I went to my phone's settings unlocked Developer options by spamming the build number so I can get there and enable OEM unlocking and USB debugging. After that I rebooted my phone into fastboot mode like I just normally turned it off and hold the power button and VOL+ key. after that I connected my OnePlus to the PC using the DASH cable. You should download beforehand the TRWP and latest Magisk.zip so you can root it using Magisk I have not tried using SuperSU. So you basucally flash the TWRP using the "fastboot flash recovery twrp-3.1.1-0-oneplus5.img" command in my case and you transfer the Magisk Manager and zip file on the phone later so you can root. Then you just flash Magisk's latest zip file or use mine. I do not remember if I manually installed the Magisk Manager APK file tho I have it downloaded on my PC gonna zip them real quick with the recovery and uploade them.

Help from Rooting to Xposed, rookie explanation

Hi guys. I had a multiple day struggle and all the manuals were only partial, so I try to summarize all the steps taken to unlock my phone, root it with magisk and install Xposed SDK28.
1) Unlock bootloader
It takes time and I had to wait that mentioned 168h (it may differ) and there is nothing you can do about it on your K20/9T
I used the official xiaomi unlock tool, latest version, and followed all the steps there.
2) Install TWRP
Oh god, on this phone it gave me headache and I almost bricked my phone and it convinced me to write you a manual just in case you are lost as I had been. Here you go.
There are three versions of TWRP on this forum and I selected the Chinese one (no greek nor russian)
After unlocking the bootloader, I only flashed the twrp (no other files, just the img with the rom) and then did fastboot reboot.
It stucked on booting. Here I pressed volume up and power and it took me to the newly installed TWRP. This didn't work with an other TWRP than Chinese. I ended up in the bootloop to fastboot only.
Then I installed the ROM. In my case Pixel Experience, latest version. The manual mentioned in this forum tells you to install Magisk together with your ROM. It again caused a bootloop on my device, so I wiped my device in TWRP, installed clean Pixel Experience ROM, and let it boot without magisk and permissive.
I checked via root checker if my device is rooted. And it was not.
3) Root via Magisk/SU applicable
Then I downloaded
Magisk Manager 7.3.2.apk and installed it with confirmation in settings that I allow the whatever file manager to install apps from unknown source.
In the Magisk Manager I downloaded a zip with Magisk and rebooted to TWRP (turn off the device, and then volume up and power)
I flashed the zip downloaded by that manager - no wipe
rebooted back to system and checked the root. Rooted.
4) Xposed
Download Magisk manager 7.3.2.
Install modules via Magisk Manager
- Riru Core v19.4 or higher
- Riru - EdXposed v0.4.5.1._beta(4463) (YAHFA)
restart your device
Then install EdXposedInstaller_V2.2.4-release.apk and check if it works.
restart your device and you can start installing modules. Even Gravitybox (P) works!
I really hope I briefly helped you guys. Viva la modding and enjoy your cool Xiaomi. Thanks to all the contributors on xda, thanks to them I was able to summarize this little manual.
In case you stuck somewhere and need to recover anything such as boot.img or any other shananingans you did with your phone, as I did too, you need to download the miflash tool, in this case the latest version didn't work so I used 2014.05.09.0, and downloaded the official fastboot rom davinci_eea_global_images_V10.3.7.0.PFJEUXM_20190602.0000.00_9.0_eea_eab1d1cc52, flashed it with miflash (around 6 minutes), stucked again in bootloop, rebooted to TWRP via volume up and power during the bootloop, and followed the steps from flashing the TWRP (after MiFlash it has only the default MiRecovery) and installed my ROM.

Rooting SM-T380 with Pie

I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!
I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.
Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..
Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.
Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.

Rooting Help

I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..

Install TWRP via official app after you have root with magisk?

Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.
alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery​
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version
refer to post #8
Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)
With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?
patch the tar file

Categories

Resources