Database Users

Rooting help for OnePlus 6T 9.0.15

A little background: I was rooted before updating my OnePlus 6T from system settings, then after updating (through system settings) I no longer had root and TWRP recovery so what I did was flashed TWRP following this method now I do have TWRP recovery but I am not sure which method to follow for the root process, and I have few concerns as below:
Should I flash Magisk now if so which version and which method will work for 9.0.15?
Before flashing Magisk should I flash Magisk uninstaller as well?
Do I have to flash TWRP again after flashing Magisk?
I might be asking dumb questions but I don't want to mess it up.

Greetings.
Just straight up flash the latest Magisk version, worked for me. Flash it through TWRP.
Why would you flash magisk uninstaller? I mean, I suppose it's optional?
No, you don't have to flash TWRP again.
Cheers.

Flash Magisk.
Next time, without rebooting, use Magisk mod 'TWRP A/B retention script' (search for it in Magisk modules list) just after flashing OTA via local method, and then without rebooting yet, in Magisk manager install again Magisk selecting 'other slot after OTA' option. Then only you reboot, all babies intact and in good health

Problems with installing LineageOS 17.1

Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu

My LOS Install Guide
- Don't use TWRP 3.4.x. Use 3.3.1-32 (The latest 3.3.1 version.) 3.4.x will give you issues.

Thank you lot. Lineage ist booting =)

Thawu said:
Thank you lot. Lineage ist booting =)
Click to expand...
Click to collapse
I also just noticed you are trying to use a very old version of OOS (which also means old firmware). Why are you using 9.0.13? Perhaps this could be your issue.
I need to update my guide, but 10.3.5, and the latest weekly 9-3 work fine. One warning, I never did get the 10.3.5 fastboot ROM to work on either of my 6Ts. The 10.3.4 Fastboot ROM works fine, then I had to update to 10.3.5 using TWRP.
I asked if anyone else had problems with the 10.3.5 fastboot ROM in the fastboot thread but didnt get any replies...

I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu

Thawu said:
I started at first wit OOS 9 because of the latest (?) msm tool. I regocnized later, that it is crucial to update OOS to Android 10 what I did after I posted my question. I installed OOS 10.3.5 from oneplus.com via TWRP.
So all I had to do yesterday was to reinstall TWRP 3.3.1-32.
Your guide for installing LineageOS was by far the best I got. All the little explenations were the things I needed to understand, why the steps had to be done. So again thank you for your help and your guide which is really really good.
Greetings
Thawu
Click to expand...
Click to collapse
Also if you like themed TWRP @acuicultor and @ morphine1e1 have a really nice creation for OP6/6t here: https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752
It's latest twrp but I've been using it for months without any issues and I flash much more than a regular user. Installed LOS twice and all good.

或许你应该先升级到安卓10 再去安装lineage os 17

Thawu said:
Good morrning everyone!
i am a little bit helpless with my plan to flash LineageOS 17.1 onto my OP 6T. I started from LineageOS 16, which was rooted with Magisk.
With my first attempt I followed the instructions from https://wiki.lineageos.org/devices/fajita/install. I used the latest files from 20200903 of LineageOS. But after flashing temporarily the recovery, I ended up with a stuck in oem-unlock-screen. To fix it i used the MSMtool 4.0.59.
I flashed only boot and not boot_a or boot_b. So I tried it with that now. But I only got the same results. I was unable to boot into recovery. So again MSM Tool and unlocking the bootloader.
Then I tried to install it via TWRP. OOS 9.0.13:
1. booted into fastboot mode
2. booted TWRP 3.3.1.0
3. Wiped Data and rebooted into fastboot mode
4. booted again TWRP 3.3.1.0
5. installed LineageOS lineage-17.1-20200903-nightly-fajita-signed.zip
6. installed TWRP 3.4.0
7. rebooted into recovery
8. repeated 5. and 6.
9. rebooted into recovery
10. installed open gapps-nano
11. installed Magisk 20.4
12. rebooted the system
Result: Qualcomm CrashDump Mode......
I do not understand what I did wrong. In June I installed Lineage OS on another OP 6T and it worked fine with flashing the recovery to boot_a. But I do not know which OOS was installed. No I am trying it since hours and only end up in the above mentioned results.
What do I have to do? Thanks for your help in advance!
Greetings
Thawu
Click to expand...
Click to collapse
I install it on HTC u11.. but voice call speaker not working and Bluetooth voice speaker not working .

Samsung fastboot confirmed

I have successfully used fastboot to flash TWRP to my Tab S5e. Android 10 moved fastboot to userspace as fastbootd and if you have the right recovery it works on Samsung. I used Lineage recovery from local 17.1 build on my machine. Got curious about fastboot options in recovery and it works. Check this to better understand https://source.android.com/devices/bootloader/fastbootd Yep that is source.android link no joke. Device codename can be seen in screenshots.

Does this mean we can flash TWRP Recovery and then just root it with flashing Magisk via TWRP recovery? Thanks.

IngoPan said:
Does this mean we can flash TWRP Recovery and then just root it with flashing Magisk via TWRP recovery? Thanks.
Click to expand...
Click to collapse
Sort of, if you already have LineageOS or another custom ROM that supports it. Stock samsung does not support fastbootd. AOSP based roms should have it as of android 10. It also requires the recovery be compatable. Lineage recovery provides access current TWRP did not. It is explained here https://source.android.com/devices/bootloader/fastbootd . It's a neat trick but not for initial root or custom recovery, still same as always you have to have it before you can get it. It does not replace Odin and the same steps are required as always to root or install twrp on stock Samsung. But once you have access it works to flash magisk_patched.img on LOS which can be good since Lineage 17.1 does not have official su support.

How to do TWRP after magisk is flashed

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

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.