How to do TWRP after magisk is flashed - Samsung Galaxy Tab S5e Questions & Answers

Basic information:
My Device: Samsung Galaxy Tab S5e, (SM-T725C)
Magisk: Magisk is installed, using falsh patched image.
TWRP link: https://twrp.me/samsung/samsunggalaxytabs5elte.html
Issue:
Now I wish to install TWRP to my device, but I can't. I followed the instruction on TWRP page, install TWRP app via google play, download the vbmeta.tar and flash it. Now I ended up with the result that I can't get into my system. (When I enter recovery, it's TWRP, when I boot normally, it just stays with samsung logo.)
I managed to reflash the magisk patched image and now I can boot into the system. But how can I flash TWRP, with magisk enabled at same time?
(I use TWRP to flash opengapps because google apps are not included in Chinese version of Samsung system)

LanhuaMa said:
Basic information:
My Device: Samsung Galaxy Tab S5e, (SM-T725C)
Magisk: Magisk is installed, using falsh patched image.
TWRP link: https://twrp.me/samsung/samsunggalaxytabs5elte.html
Issue:
Now I wish to install TWRP to my device, but I can't. I followed the instruction on TWRP page, install TWRP app via google play, download the vbmeta.tar and flash it. Now I ended up with the result that I can't get into my system. (When I enter recovery, it's TWRP, when I boot normally, it just stays with samsung logo.)
I managed to reflash the magisk patched image and now I can boot into the system. But how can I flash TWRP, with magisk enabled at same time?
(I use TWRP to flash opengapps because google apps are not included in Chinese version of Samsung system)
Click to expand...
Click to collapse
I dont know if this works with the latest update, but it certenly worked with android pie and the first android 10 update.
Edit 'I have just seen your device is a different number so may not work'
Instal TWRP without a P.C. for Galaxy Tab S5e (SM-T720) keeping stock ROM.
I wrote this guide because I had difficulty trying to instal a patched version of twrp through odin so I found this alternative way which worked very well for me. Please read all through especially the warning at the end before attempting to...
forum.xda-developers.com
Hope this helps
Ex tall

Related

Oneplus 5 TWRP and Root Issues

Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?

Re-Rooting 1+5 after OS 5.1.1 Update

So I tried updating to Oxygen is 5.0 ran into an install issue, stuck in boot loop. Lucky I had done a Nandroid back up and restore everything. The other night I decided to update to 5.1.1 thinking why not get Android 8.1.0 on my AWESOME phone. Downloaded update, placed in internal storage, booted into TWRP to do a Nandroid back up (due to issues with past update). Back up failed needed to clean drive. So I decided, phone works in Android 7.1.1, why can't what's not broken. Rebooted phone and somehow the update activated. I freaked since last time it failed and not stuck in a loop. This time update was successful but still got stuck in a boot loop. I plugged my phone to my computer and noticed all my files were gone on their install storage, no files / foldersI recognized (e.g. DCIM, DATA, DOWNLOAD, etc). Emailed One Plus and chatted with them. TWRP was gone and was back on stock recovery. Since all was lost I was asked to "Erase All". I did, rebooted and I'm now on 8.1.1 but all my stuff was lost. So I've done since searching and found FlashFire do to a Nandroid backup but need root. So my question is...
Can I re-root my phone without using TWRP but stock recovery and use FlashFire for my back ups? I am not going to flash custom ROM but if I need to flash something, wouldn't stock ROM flash anything on my phone (Magisk)?
If so, can anyone provide me with assistance on re-rooting my phone without TWRP.
Thank you
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Hi
To root your OnePlus 5, you must to follow carefuly the steps below and take your time.
1 - Make a full backup of your data
2 - Unlock the bootloader (Note that'll erase your phone)
3 - Install another recovery : TWRP. This one : https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download
4 - Flash the full rom Oxygen OS 5.1.1 : http://otafsg.h2os.com/patch/amazon...23_OTA_034_all_1804201219_3824995916a49ee.zip
5 - Install magisk : https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
6 - Clear cache / Dalvik
7 - You're all done, reboot the phone
8 - Once your phone has booted up, install magisk manager : https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Check this tread, that'll help you as well : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
vanzant83 said:
As far as i know you can't flash anything with stock recovery so you can't root. After flashing the stock os is normal that twrp is been erased by the stock. Just re flash the twrp. I mean, maybe i didn't get the problem, why you can't reflash twrp? If you do that flash twrp codeworx Universal with fastboot in the bootloader, boot in twrp, wipe cache/dalvik, flash magisk 15.3, wipe cache/dalvik, reboot system, update magisk to 16 with the app. I do that way and it worked
Click to expand...
Click to collapse
Hello, thanks for the info and yes, I did try flashing Magisk with stock recovery, while waiting for a reply and can confirm installation failed. So if I reflash TWRP, flashing Magisk using TWRP will work. Therefore, do you have instructions (step-by-step) on how to install TWRP. I have downloaded the latest TWRP image from their website (twrp-3.1.1-1 cheeseburger) onto my desktop. Bootloader is already unlocked as I was previously rooted under Android 7.1.
Thank you.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
vanzant83 said:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
This is the official guide step by step, scroll down until you find "flashing twrp" if you had already unlocked the bootloader ( you already did that right??? xD). Anyway about the recovery and magisk version. The guys in the 5.1.1 thread advised to flash magisk 15.3 instead the 16 and only after the system reboot to make the upgrade to 16 with magisk app (dunno why). But when i tried to do that the last version of twrp (3.1.1-1) failed the flash. So i flashed the twrp 3.1.1-0-universal and 15.3 magisk. I can confirm this combination work, i can't tell for other combinations.
Click to expand...
Click to collapse
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
jmoricone said:
Hello, I finally got some time to re-root my phone and was reading the instructions you provided and clicked on the download but they are TWRP 3.2.1.x and Magisk 16. Do you have the links for the files you used
Grazie
Click to expand...
Click to collapse
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Try this link, get the ZIP file from the version you want: https://github.com/topjohnwu/Magisk/releases/
In case you need, this the official section: https://forum.xda-developers.com/apps/magisk
vanzant83 said:
Sorry man i typed wrong, the one i meant was 3.2.1-0 Universal codeworkx, the fourth from up to down. About 15.3 magisk i dunno where you can find It, maybe try some google research, otherwise i can send It to you by email, is a little file
Click to expand...
Click to collapse
Hey there, sorry for the late response..but thank you for the assist..phone is rerooted..all is good..thanks again

Can't Root Samsung SM-T380

Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.
This is exactly the same problem that I've been having with my T380. I've flashed the stock rom and retried many different methods of rooting with Magisk but they all have failed. If you got it workiing, please tell me what made it work for you. Thanks!
These are the steps that I took using post by Winston Churchill as a guide:
1. Enable OEM Unlock
2. Use Odin to flash TWRP with twrp_3.2.3-1_sm-t380_oo_4119.tar on AP Slot
3. TWRP Wipe/Reformat Data then reboot to recovery
4. Install boot.img patched by Magisk using TWRP (I extracted boot.img from stock firmware and used Magisk to make patched boot.img)
5. Install Magisk.zip using TWRP (this didn't do anything, I had to manually install the apk later on)
6. Install Tab_A_2017_Pie_forced+encryption_disabler.zip using TWRP
7. Wipe Cache and Dalvik
8. Reboot System
I tried alternative approach for installing Magisk using this guide. It basically is extracting boot.img off your current device firmware and using Magisk to patch that boot.img. Then flash the patched boot.img using TWRP (it didn't work for me though)
These are the places I went to get my files:
https://forum.xda-developers.com/t/rooting-sm-t380-with-pie.4049951/ (Post by Winston Churchill)
https://forum.xda-developers.com/t/guide-comprehensive-t380-tab-a-2017-8-0-root-guide.3753203/
https://forum.xda-developers.com/t/twrp-3-2-1-1-root-tab-a-sm-t380-t385-10-02-2018.3747564/
Barto604 said:
Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.
Click to expand...
Click to collapse
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.
lewmur said:
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.
Click to expand...
Click to collapse
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A
Barto604 said:
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A
Click to expand...
Click to collapse
Try flashing Magisk23.apk with TWRP as if it were a zip. That worked with latest 11 ROM with T500.
Tried it, didn't work either, I think them latest security patch for this tablet block root or something, I'm literally stuck.

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..

gts4lv: magisk rooted twrp + stock works, but lineage19/20 boot loops

Hi,
Disclaimer:
First post here, sorry if opening a thread here instead of replying to, e.g.
https://forum.xda-developers.com/t/rom-official-gts4lv-gts4lvwifi-13-lineageos-20.4536203/
is not correct. I've read the forum rules, and searched for similiar issues with that device, but at a glance did not find something alike.
Appologies in advance if I did a mistake or overlooked something, I'll try to learn and do better next time.
Device: Samsung Galaxy Tab S5e LTE, SM-T725, gts4lv
Bootloader: unlocked
Aim: magisk rooted twrp in recovery, lineage20
Following these instructions, I'm able to root the latest stock rom with magisk, flash that via odin, and get a magisk-patched twrp recovery:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
https://twrp.me/samsung/samsunggalaxytabs5elte.html
(Details:
Get the current stock via frija, extract AP, patch via magisk on device, adb pull to host, flash stock with odin (magisk'ed AP,BL,CP,CSC).
Reboot device into stock, finish magisk app install. Reboot once. Device rooted. Installed TWRP app, granted root permissions to it, download twrp for device, patched image with magisk, flashed that to recovery via twrp app.
Sucessfully tested twrp, looks good.)
Trouble begins when I install lineage via twrp adb sideload, following
https://wiki.lineageos.org/devices/gts4lv/install#installing-lineageos-from-recovery
with the difference using twrp instead of lineage recovery.
Coming from the magisk-in-twrp-recovery rooted stock, I did a factory reset (wipe cache/dalvik cache/data), and twrp adb sideloaded the latest lineage20 for that device.
Console command outputs look good, no obvious errors. After the initial reboot, I got a recovery boot loop.
Going back to square one, reverting to magisk rooted stock using odin.
Then, I also tried sideloading lineage19, same result.
For the record: I initally started the lineage installation also flashing NikGApps or MindTheGApps (arm64), and the fdroid priviliged extension afterwards, but got the boot loop there.
I wiped system/data/cache/dalvik, went back to magisk-in-twrp-recovery rooted stock as described above and then tried with just lineage, but still a bootloop.
Do I maybe have to once again flash the AP with the VBMeta.tar via odin prior to moving from the rooted stock to lineage?
I am a bit hesitant to do so, because
https://topjohnwu.github.io/Magisk/install.html#important-notes says
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Not sure if the VBMeta step is only required to initally unlock the device.
I am thankful for any advice how to narrow down the issue.
Best regards
I tried to install lineage+twrp+magisk/root at the same time without great result as well.
I was able to install lineage and twrp, but when I was there it was impossible for me to "activate" Magisk
So I switched back to custom rom + twrp + magisk/root. All good, but that's not what I was searching for.
I installed Lineage from Odin, then flashed twrp. https://wiki.lineageos.org/devices/gts4lv/install.
Try this guide, if you'll have success please let me know how you did it.
See my post here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655
Issue is with patching twrp with magisk it seems. Use either stock Lineage recovery or follow instructions I posted.

Categories

Resources