T720 Android 10 How to root Stock Rom - Samsung Galaxy Tab S5e Questions & Answers

I have installed latest android 10 stock rom. i tried using the magisk manager patch AP file method. i flashed the patched AP file CP BL and Twrp. tar in userdata on Odin.
TWRP 3.4.0.4 is installed but when i boot it gets stuck on samsung boot animation.
i tried flashing magisk zip from twrp and then it continuous bootloops to the Samsung bootloader image.
Do i root first stock and then install later TWRP?
Can anyone list out a short guide how to root Android 10 and aldo have TWRP with it.

I found the solution as
1. Install stock rom
2. follow root guide 1.0
3. Patch AP file with magisk manager
4. Download TWrRP App from playstore
4. Root stock rom
5 Install Twrp with the method in this link https://forum.xda-developers.com/tab-s5e/how-to/instal-twrp-p-c-galaxy-tab-s5e-sm-t720-t4072231.
6. Now I have stock rom rooted with latest twrp.
By the way also fixed device signature modified with magisk prop and busybox module and editing build prop to match device fingerprint error.
Moderators please kindly close this thread as solution found

Related

How to root STOCK Marshmallow

It looks like lot of people are trying to install the lastest SuperSU flashable zip through TWRP and they are being stuck at the bootloader screen.
The issue is in the SuperSU updater script , which can't detect the system and is trying to install root in system mode (it should use systemless mode)
For those users who are stuck at bootloader logo after flash supersu, is necessary to reflash stock rom and flash this SuperSU:
View attachment SuperSU-v2.78-201609011115_systemless.zip (I've edited the updater-script to force systemless install :angel
After flash this (updated to 2016-09-01), all updates can be installed directly from the store

How do I flash Magisk to my Meizu m3 note?

Each time that I boot the phone up into recovery mode and select the system upgrade option it tells me that the firmware is corrupt (for Magisk). I was able to get the latest version of Flyme (6.1.0.0G) flashed to my phone without the firmware corrupt showing, however, I cannot for Magisk. How do I flash Magisk to my phone without the firmware becoming corrupt?
Nox_ said:
Each time that I boot the phone up into recovery mode and select the system upgrade option it tells me that the firmware is corrupt (for Magisk). I was able to get the latest version of Flyme (6.1.0.0G) flashed to my phone without the firmware corrupt showing, however, I cannot for Magisk. How do I flash Magisk to my phone without the firmware becoming corrupt?
Click to expand...
Click to collapse
You cannot flash Magisk zip or any other zip from STOCK Meizu recovery.
You need custom recovery for it.
With STOCK recovery you ONLY can flash official Meizu firmware zips.
Only thing you can do is to root phone with root privileges option in Flyme account section in phone settings (you must have Flyme account created).
After you enable root privileges download Magisk manager APK from official XDA thread and install it(NOT ZIP,ONLY APK FILE!!!!).
And when you install Magisk Manager DO NOT TRY to install modules since you dont have custom recovery.

Proper Guide [TWRP] [ROOT] [Xposed] official versions only

please describe a full guide step by step for flashing official twrp, cf autoroot, xposed, magisk for mia1 and if possible give brief video description guides for all...
[email protected] said:
please describe a full guide step by step for flashing official twrp, cf autoroot, xposed, magisk for mia1 and if possible give brief video description guides for all...
Click to expand...
Click to collapse
1.Enter into fastboot mode.
2.fastboot boot twrp.img
3.In twrp recovery flash twrp-installer.zip file
4.Then reboot to recovery to install twrp permanently.
5 Download cf autoroot file from firmware.mobi according to your build number and flash zip file through twrp recovery to root your mobile.
6.Install xosed installer app and through that install xposed framework.
7.Enjoy your rooted mi a1.
nilkanth.marshiwane said:
1.Enter into fastboot mode.
2.fastboot boot twrp.img
3.In twrp recovery flash twrp-installer.zip file
4.Then reboot to recovery to install twrp permanently.
5 Download cf autoroot file from firmware.mobi according to your build number and flash zip file through twrp recovery to root your mobile.
6.Install xosed installer app and through that install xposed framework.
7.Enjoy your rooted mi a1.
Click to expand...
Click to collapse
Where to get twrp installer.. on official twrp site there is only .IMG file for 3.1.1-0 available
The procedure you have explained is for twrp by Mohan 3.1.1-1 which doesn't seem to work fine for me
[email protected] said:
Where to get twrp installer.. on official twrp site there is only .IMG file for 3.1.1-0 available
The procedure you have explained is for twrp by Mohan 3.1.1-1 which doesn't seem to work fine for me
Click to expand...
Click to collapse
twrp 3.1.1-1 (by mohan) working perfect. Use twrp installer from this thread. First ensure that boot image is unmodified . Flash stock boot for your build number and then install twrp as stated above. Unmodified boot image must to install twrp. Then root with magisk to retain ota.
nilkanth.marshiwane said:
twrp 3.1.1-1 (by mohan) working perfect. Use twrp installer from this thread. First ensure that boot image is unmodified . Flash stock boot for your build number and then install twrp as stated above. Unmodified boot image must to install twrp. Then root with magisk to retain ota.
Click to expand...
Click to collapse
I did root sucessfully by this method few days back but 3.1.1-1 is not able to flash some files and magisk is not updating in this...
Importantly when officially available twrp is there why to use modes...
If u have procedure to flash the twrp.img from twrp website please show me the procedure...
[email protected] said:
I did root sucessfully by this method few days back but 3.1.1-1 is not able to flash some files and magisk is not updating in this...
Importantly when officially available twrp is there why to use modes...
If u have procedure to flash the twrp.img from twrp website please show me the procedure...
Click to expand...
Click to collapse
https://twrp.me/xiaomi/xiaomimia1.html i want to flash but every time says failed while giving command
fastboot flash recovery recovery.img
pasted the img file in same folder
downloaded again to rule out corrupted file

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.

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