Database Develop

Help with Treble ROMs

I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks

Try to install the stock recovery and ramdisk.

+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.

After I flashed a treble gsi, I need to flash stock recovery?

Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.

ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry

Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.

ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.

XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP

ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.

XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3

Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!

Made an OB1 Magisk Patched boot.img

7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Don't install TWRP yet. The people who are infinitely smarter than I am will make a TWRP that will work for OB1, and that's way above my pay grade. I hope this helps someone.
[Tutorial] How to flash a new boot.img via Fastboot
Hey Guys, since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode) If you have fastboot already installed on your...
forum.xda-developers.com
Here's how to use it.

getting 'unable to parse kernel log' error

peachypickle said:
getting 'unable to parse kernel log' error
Click to expand...
Click to collapse
it worked fine for me.

How install oxygen os open beta 1 android 11 with keep rooted? Any video tutorial?

it's not too bad...
Install the OTA
Go to magisk manager and pick install.
pick install to inactive slot (after OTA)
make sure you don't have any modules enabled that may be incompatible.
reboot
when the 11 TWRP drops, you can install it as a magisk module to gain custom recovery back

Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.

spheady said:
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
Click to expand...
Click to collapse
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.

spheady said:
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
Click to expand...
Click to collapse
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?

LokifiedMee said:
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
Click to expand...
Click to collapse
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun

Crazyinsanejames said:
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Click to expand...
Click to collapse
Ohh couldn't find Orangefox dual boot's post today so here is the twrp file. It's not really worked on right now and has option to flash magisk on R11 Pass but the copy of magisk is no good on the R11 OS but has magisk. 20.4 option for a Q10 is, when it IDs it. You'll see. The script options. PS orangfox dual booting with three different drives rocks. Also it has a app manager and a magisk mange GUI. Almost forgot beta 10 version 17-19 will not successful y flash this twrp. But any other copy for the phone on xda or OnePlus.com work fine. It's a encryption variety problem. If your password becomes corrupt (only on OS can have password type security on a dual boot setup... I got away with using the same password on both OSs for a minute though. ) in the root partition thiers a directory called Ffiles, with .zip you can flash while TWRped to fix a few things like that. Other than that let me know. Lol I want to mention Evey time you flash an OTA or anything that will alter the work this twrp installs, you need to flash the file afterwards, before rebooting. And reboot after flashing it so everything links up. Of coarse you can select to reboot right back to recovery. Best luck I couldn't find their post on xda so that's why I typed up so much. Lol I'll be funny again I don't know who this stuff on how to downgrade really but thiers a Windows tool that has capibillities err what ever to flash a OTA of 10 in fastboot mode. Anyways no worries. It's called all-in-one flash tool. Works on maney OnePlus phones. Maybe for encrypted data partitions. I run unencrypted stuff I do not like encryption on any electric devices.

aNGERY said:
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Click to expand...
Click to collapse
I just want to say thank you. I tried the new magisk update and it didn't work. I could get to recovery and figured I had PB1 for Andoid11 anffd I would flash to gety baclk to working. Of course I lost root, but was able to get it back with magisk_patched_Ei056.img flashed to boot. It works fine. Can hang with root until TWRP gets updated.
VERY APPRECIATED.

Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!

Crazyinsanejames said:
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Click to expand...
Click to collapse
Well found out thevendor.img didnt work lol. Anyways heres cheap trick i found if your not on an OS with twrp
http://Link removed

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
I'm pretty sure it's insinuated that it's pertaining to OOS11. Don't be willfully obtuse.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
35090 for Android 11 on the OnePlus 7 pro will not work without decrypting it.

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
actually I take that back.
Download TWRP for guacamole
Download TWRP Open Recovery for guacamole
dl.twrp.me
Here you go, 3.5.0_9-0 is the one release on 12/28. Install it and let us know how you like it!

spheady said:
Lol nice it worked. Lol it also
Ty tried for fun. Think thos thread is for ppl trying to boot a .img file of twrp. Can this flash via fastboot. So twrp to twrp I think ill keep my dual boot Twrp its not so basic.ty
Click to expand...
Click to collapse
You can reboot to recovery from the OS with this twrp installed?

After rooting G9+ & installing an unofficial LineageOS 18.1, root was lost & need help getting it back

I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.

Have u tested lineage, is
everything working fine?

UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.

doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?

Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.

UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)

Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)

Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.

doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel

There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro

The ROM in the O.P. works.​
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).

M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!

I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know

[Recovery][UNOFFICIAL TWRP 3.5.2_9 for Samsung SM-T710]

PLEASE BEFORE YOU decide to try this recovery, you MUST read all of post 1 and 2 (about 3 minute read). If you think this is an unreasonable request, then stop reading now and find another recovery. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this software.
BACKUP YOUR DATA BEFORE trying this TWRP.
Source code
Kernel source
https://github.com/retiredtab/android_kernel_samsung_universal5433
Device tree
https://github.com/retiredtab/TWRP_gts28wifi/tree/main/gts28wifi
TWRP source code (built using minimal manifest TWRP 7.1)
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Download TWRP from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/
Installation Instructions
You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP.
Note I do NOT run Windows OS so there are no provided instructions on how to install TWRP using Windows. There's lots of tutorials and videos online on how to install TWRP via Windows. Do your own research. If this is unreasonable to you, don't use this TWRP. Questions regarding how to install TWRP using Windows/odin will go unanswered.
You need to boot the T710 into download mode. Power off. Press home button + power + volume down (farthest away from power button) at the same time. Let go when you see "Warning" text on the screen, then choose volume up to continue. Your screen should now show "Downloading... Do not turn off target"
Linux users can use heimdall to flash this recovery. For example,
Code:
heimdall flash --RECOVERY TWRP_3.5.2_9_SM-T710_20210719_Unofficial.img
After flashing the recovery image, you must boot into recovery immediately (using the hardware key combination) to run TWRP, otherwise the Samsung software will overwrite TWRP and you will have to start over again. I usually am already pressing the recovery hardware key combination while the recovery image is being flashed. The flash process will be very quick (a few seconds at most).
The recovery hardware key combination is home button + power + volume up (volume up is closest to the power button) all pressed at the same time.
Updates
Unless Android 12 or LineageOS 19.0 requires some mandatory changes to TWRP, this will be the only TWRP build I make for the forseeable future. There will be no planned updates to 3.5 unless there's a major bug or security vulnerability. The only time you need to boot into TWRP is to upgrade the custom rom.
I have been using this TWRP since Aug 19, 2021.
The "official" TWRP T710 ALL have broken MTP and adb in every version which is why I built my own despite reporting these problems to the maintainer.

Reserved.

Thank you so much for this! I teared my hair out for many, many hours thinking I had issues with drivers on my PC why adb or MTP never worked in every official TWRP release I've tried... I thought I'd give yours a try and voila! It works! Beautifully so.
Thank you, thank you, thank you!

Whenever i flash this specific build of TWRP my tab instantly bootloops.

cammykool said:
Whenever i flash this specific build of TWRP my tab instantly bootloops.
Click to expand...
Click to collapse
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.

retiredtab said:
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
Click to expand...
Click to collapse
Sorry. Was a quick type. And I've done a bit more troubleshooting. The older builds with broken MTP seem to boot perfectly. But flashing the build outlined here seems to get the tablet stuck at the Tab S2 screen. The only place it can go is DL. system won't boot again unless I reflash a system image. The tablet was still on a build of 5.1.1 though and I know these modern recoveries probably don't expect that so i am letting it update the stock stuff now.

Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!

cammykool said:
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
Click to expand...
Click to collapse
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/

retiredtab said:
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
Click to expand...
Click to collapse
Thank you! That was actually the plan! Running it now and posted in the other thread!

Thank you for nice work, I've installed it on my T715, it works very well, just now my device is recognized as T710 too. Could you please provide a build for T715? As the function of adb/mpt doesn't work on all of twrp for T715 too.

Was running LoS 16 and decided to update. Went to stock 7.0 then LoS 18.1 using this version of TWRP without any problems or the issues some other versions of TWRP have! Thanks

Question Realme C25Y RMX3269 ROOT

We can root in an easy way without unlocking the bootloader
I think this method works with all versions realme
Don't forget to activate OEM unlocking From Developer options
1-You must install drivers:
Realme USB Driver - Realme Firmware
From here you can download USB driver for realme mobile phones. The given USB driver is supported only for the Windows operating system
realmefirmware.com
Realme USB Driver - Google Drive
drive.google.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download SPD Flash Tool R26.21.2801 - Official SPD/Unisoc Flash Tool
Download SPD Flash Tool R26.21.2801 to Flash Stock Firmware on Spreadtrum Smartphone and Tablets.
spdflashtool.com
2-You have to unpack the ROM using SPD_Upgrade_Tool
https://www.gsmmafia.com/ Here are the ROMs
After completing the extraction, make a patch for the boot With Magisk-v24.3
You will get a rooted boot file Replace it with the old boot
In the end, flash the device and you will notice that you have the root
I am attaching an explanatory video

not the group you looking for but thanks for sharing this

gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
thanks.

gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
How can we create realme c25y group in xda

Excuse me I want to ask, will this delete all internal data?

Doly12 said:
Excuse me I want to ask, will this delete all internal data?
Click to expand...
Click to collapse
yes.

Yo, how did you flash it?

Biglet0w said:
Yo, how did you flash it?
Click to expand...
Click to collapse
spd flash tool
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.

Hi
When I try to call the emergency numbers, I can't, it says that the credit is not enough to make the call
I rebooted and flashed according to the video you posted, but it didn't work
I changed the chip but the same problem remains
Can you give me a solution to this problem

my phone recognize sim but when call people it said cellular is not available, when i use my sim in other phone it work normal, i try flash the rom again but spd tool said error !!!GSM Cali in phone is not calibrated.Reserved[7]:0x00000000,[ID=0x2] pls help

i have rmx3269_11_A.18 and its not on gsmmafia this build number what i do please help

Can i install twrp from c25 or c25s

Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?

Reyproject said:
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Click to expand...
Click to collapse
1) I don't think so.
2)Yes.

JA sunny said:
1) I don't think so.
2)Yes.
Click to expand...
Click to collapse
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?

Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
I think you need to have the bootloader unlocked to boot into custom img

elokuba said:
Can i install twrp from c25 or c25s
Click to expand...
Click to collapse
Don't

Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
Can you please check if this works
File
XDA forum

JA sunny said:
Can you please check if this works
File
XDA forum
Click to expand...
Click to collapse
What does it do?

Reyproject said:
What does it do?
Click to expand...
Click to collapse
removes the black bar on the notch/punchhole side that you see on some apps and games when the phone is in landscape. I'll root my phone if this works.