Develop Bugs

Samsung Galaxy Tab S7 Model SM-T875 finally Rooted

Hello. I have managed to Root My Samsung Galaxy Tab S7 Model SM-T875 with KNOX value 0x1 and no custom recovery has been installed. I am linking an image from Root Checker
bit.ly/3kOE6NW
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
Only for SM-T875
If you have any other models, let me know, I will patch their boot.tar and provide link for the same
Steps for root :
Download and install the latest version of Magisk Manager
Make sure you have an unlocked boot loader
On your PC, download Odin and put your S7 into download mode
Flash the tar file listed here
I am linking the exact boot.tar image I used
bit.ly/3j4mYDw
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
In Odin, select the AP option, make sure ur tab is connected in COM1 and then select the boot.tar file. Once flashed, you have to restart your device.
NOTE
Once this boot.img file is flashed you will get this an error saying your device is not on official firmware and you will have to hard reset your device, go ahead and hard reset your device, you might think its in bootloop but it is not. Once hard reset is done, your device will boot twice, make sure to press the power button each time to skip the unlocked bootloader warning. Once done, set up your tab as new one. Now Magisk Manager will not be installed on your device. For root , go ahead and install Magisk Manager again and this time Magisk will be installed in your device and your Knox value will be 0x1 and warranty will be void and device will be rooted
If any questions, please feel free to ask
Hope this helped you

Did someone confirmed?*I wait to got the root before to buy this model specifically

T870
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..

Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
just copy and past the provided link address he gave into your browser and download

jionny said:
just copy and past the provided link address he gave into your browser and download
Click to expand...
Click to collapse
The link is for the t875 version mate.. i need image file for t870

Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
Sure, here ya go
bit.ly/33DC7GM
If this img file is not flashing, make sure to tar it using 7-zip and then flash from ODIN.
This is the boot.img from the latest version of Android Q (release Sep 1) so make sure you're on the same version before flashing this.
Let me know if this worked or if you need the boot file for any other version
also, sry for bitly link, am not trying to profit out of this, once my 10 posts are complete, i'll post direct download links.
Thx for understanding

umibuzu said:
Did someone confirmed?*I wait to got the root before to buy this model specifically
Click to expand...
Click to collapse
Not that I should be saying this, but if you want to know, I have done the same steps on both of my Tab S7's and bot are working while being rooted. If you still want someone else to confirm, im totally fine with it. Thx for replying tho.

Sushantydv said:
The link is for the t875 version mate.. i need image file for t870
Click to expand...
Click to collapse
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291

Could you do t878?

jhill110 said:
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291
Click to expand...
Click to collapse
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.

rosrog said:
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.
Click to expand...
Click to collapse
Unfortunately no.

I have T875 TabS7 brand new I have Build number
QP1A.190711.020.T875XXU1ATI4 and device says upd are available ATJ4 Something. with october patch. The boot image you have linked is of which firmware ?. Should I update and then root.
EDIT:
Anyways i followed this guide by Dr ketan for rooting which i used for my Note 20 Ultra and it didnt work with patching AP file method.
https://forum.xda-developers.com/galaxy-note-20-ultra/how-to/guide-how-to-root-n20-ultra-t4147023
So i downloaded the latest firmware which was ATJ4 my CSC version was CAC so i downloaded same firmware from SAMFW(super website with downloads resumable via google drive option.
1. I extracted boot.img.lz4 from AP file of stock firmware downloaded and made a TAR file of it with 7Zip
2. Put it in phone and used magisk manager on tab to patch this file
3. Copy back to PC and flash via odin 3.14.3 in AP tab and uncheck auto reboot in ODIN
4. Booted straight into stock recovery and wiped/factory reset
5. Now i have root on Tab S7 T785.
Here is a link to boot file patched for TAB S7 N985 LTE Latest ATJ4 Firmware .
http://www.mediafire.com/file/mhss32jmt1b1oza/Patched_BooT_ATJ4_TAB_S7_N985.zip/file

Possible to Root SM-T878U ?

Smoker1 said:
Possible to Root SM-T878U ?
Click to expand...
Click to collapse
Yeah it might be.

I have gotten a TWRP up and running on my Galaxy Tab S7 but it's not functioning properly, I'll post the stable version here in case I figure out one haha.

I have the Tab S6 and I love it. I am thinking to buy the Tab S7+. I was very quick to root the Tab S6 and did not take much notice of the Knox trip. Is there any sell value if the tablet cannot have certain apps working such as secure folder? I understand even if you unroot and relock the bootloader then knox is still going to be changed to 0x1
My Tablet still seems to be 0x0 though.

CamronCamr said:
Yeah it might be.
Click to expand...
Click to collapse
Any luck on this? I also was dumb enough to get this T878U from ATT. I realize I have a signed locked bootloader. Is there any hope for us? I'm fairly technical and can follow directions

I'm in the same boat. Att locked out usb and wifi tethering. A rooted device would be very helpful.

Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.

Is this possible for the SM-T978U?

legokangpalla said:
Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.
Click to expand...
Click to collapse
On the latest Samsung Tab S7 T875 Stock firmware Android 11 and one UI 3.1 , i have it rooted with Magisk V22 , widevine is L1, and safetynet passed .
Running with following magisk modules
1. Magiskhide props Config (Just install no config set
2. Riru
3. Riru Edxposed
4. Universal safetynet Fix V2.00 Test version 2 Thanks to kdrag0n

Stuck on last step of getting root

I used Odin to flash a patched maigsk tar. Then did a factory reset. I then installed the Magisk apk. But it never gave "additional setup required". Root is not present.
Only problem I can think of is, I couldn't find a download for my exact firmware ( G985FOXM5CTKF ) so I used Australia's to extract the AP from. Should I have actually flashed the Australia firmware before flashing the patched magisk?

Anatart said:
I used Odin to flash a patched maigsk tar. Then did a factory reset. I then installed the Magisk apk. But it never gave "additional setup required". Root is not present.
Only problem I can think of is, I couldn't find a download for my exact firmware ( G985FOXM5CTKF ) so I used Australia's to extract the AP from. Should I have actually flashed the Australia firmware before flashing the patched magisk?
Click to expand...
Click to collapse
Flash twrp and then flash magisk.zip?
Better to have twrp to eventually recover after a bad magisk module install, if that ever happens, which is not that hard to do
I would have posted links to help but you did not mention what device you have.

twismo1 said:
Flash twrp and then flash magisk.zip?
Better to have twrp to eventually recover after a bad magisk module install, if that ever happens, which is not that hard to do
I would have posted links to help but you did not mention what device you have.
Click to expand...
Click to collapse
So flash TWRP with Odin, then flash Magisk .zip with TWRP? I have a the SM-G985F model.

Anatart said:
So flash TWRP with Odin, then flash Magisk .zip with TWRP? I have a the SM-G985F model.
Click to expand...
Click to collapse
Exactly. Flash twrp, boot into twrp (with pc connected!) And transfer/install magisk.zip
MAKE SURE U HAVE EXYNOS
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20/S20+/S20 Ultra
Team Win Recovery Project 3.4.0 Exynos ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants. Special Notes: 1. DON'T...
forum.xda-developers.com

twismo1 said:
Exactly. Flash twrp, boot into twrp (with pc connected!) And transfer/install magisk.zip
MAKE SURE U HAVE EXYNOS
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20/S20+/S20 Ultra
Team Win Recovery Project 3.4.0 Exynos ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants. Special Notes: 1. DON'T...
forum.xda-developers.com
Click to expand...
Click to collapse
OK thanks I will attempt this. According to the linked guide I need to " format data in twrp and install multidisabler". Why is this necessary and what does multidisabler do? Usually having your phone encrypted is a good thing...

Wow that actually worked. Thanks a lot, having root is very important to me

Anatart said:
Wow that actually worked. Thanks a lot, having root is very important to me
Click to expand...
Click to collapse
Awesome!
No problemoo

Question OP9P ROOT working with new 12 Open Beta build?

So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.

nickdagriff said:
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
Click to expand...
Click to collapse
cant root dp2
will cause cash dump everytime

FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
Do you know why

encoded

FizzyAps said:
encoded
Click to expand...
Click to collapse
Do you think I should just throw myself off a building?

i mean its beta what did you except lol

I was just hoping to be able to test it and root it like every other open beta.
What about twrp

You cant flash anything at this time
It will cash dump

FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?

Burt Squirtz said:
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Click to expand...
Click to collapse
Yes I tried rooting both and they both end In cash dump

FizzyAps said:
Yes I tried rooting both and they both end In cash dump
Click to expand...
Click to collapse
How did you try though? Install to inactive slot, AND adb? Or just one of the other?

flashed patched img on both slots

FizzyAps said:
flashed patched img on both slots
Click to expand...
Click to collapse
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

ENCODED, NO METHODS WORK....

I rooted successfully with a Chinese tool
It works on both OOS12 and ColorOS12

Burt Squirtz said:
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I used this method to root last night and can confirm it works on OB 1 A12. I did the vbmeta part before flashing boot.img and didn't do the vendor_boot part at all.
https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/ this is the guide I followed.
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.

ecera said:
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
Click to expand...
Click to collapse
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.

terlynn4 said:
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
Click to expand...
Click to collapse
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.

ecera said:
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
Click to expand...
Click to collapse
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.

terlynn4 said:
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
Click to expand...
Click to collapse
It probably does boot a bit faster. Like you said that message is an extra few seconds. To me its not really noticeable, maybe to someone else it might be.

Question Flash recovery on Galaxy A52S 5G without data loss

Hello, I have a galaxy A52s 5G and I'm trying to bypass pattern lock so I don't lose data by factory resetting. USB debugging is disabled and bootloader is not unlocked.
I can access download mode/stock recovery but that's about it. Doesn't seem like there's an official TWRP either. Is there a way to flash a custom recovery? Would flashing A52 4g's TWRP work? If not, what can I do

Arobase40 said:
Flashing A52 4g's TWRP onto a A52S 5G will lead to a soft brick phone !!! ^^
Someone else pretended he/she built a working TWRP for the A52S 5G but it doesn't work at all and even didn't test it him/herself before releasing it.
Another guy accepted to be a guinea pig but he bricked his phone by the way... ^^
We are all waiting after such a TWRP but there is none atm.
I'm myself trying to build one but I don't have enough time to build it because I don't have a good Windows PC and I don't feel comfortable with Android studio yet !
I have the source code but I have to put all things together so unless someone else build a working one you have to wait after it as we all do... ^^
Click to expand...
Click to collapse
Once someone builds a working version, would I be able to simply flash it using Odin in download mode or would bootloader need to be unlocked? Because otherwise I'm not sure what to do

Arobase40 said:
You can't install a TWRP without unlocking the bootloader anyway.
Click to expand...
Click to collapse
Is it worth trying to flash Aroma file manager through download mode? I'm not sure if aroma is compatible with any device

Arobase40 said:
This is a very old and dead project ! So you're on your own if you still want to use it.
Click to expand...
Click to collapse
It would supposedly allow me to delete gestures.key. I dont know what else to flash since theres no TWRP

u can try to use samsung find my

Arobase40 said:
Flashing A52 4g's TWRP onto a A52S 5G will lead to a soft brick phone !!! ^^
Someone else pretended he/she built a working TWRP for the A52S 5G but it doesn't work at all and even didn't test it him/herself before releasing it.
Another guy accepted to be a guinea pig but he bricked his phone by the way... ^^
We are all waiting after such a TWRP but there is none atm.
I'm myself trying to build one but I don't have enough time to build it because I don't have a good Windows PC and I don't feel comfortable with Android studio yet !
I have the source code but I have to put all things together so unless someone else build a working one you have to wait after it as we all do... ^^
Click to expand...
Click to collapse
I am using this guide - https://www.droidwin.com/create-port-twrp-recovery-android/
But at step 7, the fstab.devicename_or_chipsetname file is missing.
And how do we edit default.prop file? Tried with notepad++, root explorer android, but the file only has a single line as
!<symlink>ÿþp r o p . d e f a u l t

Abhishek Junghare said:
I am using this guide - https://www.droidwin.com/create-port-twrp-recovery-android/
But at step 7, the fstab.devicename_or_chipsetname file is missing.
And how do we edit default.prop file? Tried with notepad++, root explorer android, but the file only has a single line as
!<symlink>ÿþp r o p . d e f a u l t
Click to expand...
Click to collapse
Try get from kernel

oli231 said:
Try get from kernel
Click to expand...
Click to collapse
There is a mistake in the guide. It's not 'default.prop', it's 'prop.default' in step 6 (13)
So after all the work, I got TWRP booting. But it's only booting, no touch response.

Arobase40 said:
I'm trying to build one from source code but I still have errors so might be some things missing.
I'm still working on it...
Click to expand...
Click to collapse
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.

Abhishek Junghare said:
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.
Click to expand...
Click to collapse
Search on firmware and Samsung kernel

Arobase40 said:
What do you want me to do with a recovery that is not working for you ??? lol
I already have the device tree for A528B as source code but need to know how to include it in a Android tree source code : omni, cm or aosp..., but I need to know what is missing to build it and get it working... ^^
Click to expand...
Click to collapse
I am not building from source code like you. I took TWRP from A52, as the two devices are very similar. Then followed the guide - www.droidwin.com
I don't have any technical knowledge about this. It booted somehow. No boot-loop. But there is no touch response. And I don't OTG nearby, so couldn't test with a mouse.
Yes, ofc. You would know better. I am not a developer. I was only trying with that guide.

Abhishek Junghare said:
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.
Click to expand...
Click to collapse
Arobase40 said:
This is what I said : no touch response so simply useless as you won't even know if processes behind the touch options are even working... ^^
I remember someone else who pretended he/she will build a TWRP without source code but with some kind of "kitchen" and released it in this section but didn't even test it him/her/self. Someone else tried it but it didn't work. Then we never got any feedbacks from he/she... ^^
Click to expand...
Click to collapse
I never said that I am building TWRP for public. I was only trying for myself. The recovery.zip attached in the previous message is just the stock recovery backed up from TWRP app as it has some missing files from recovery extracted from the stock firmware.

Abhishek Junghare said:
I never said that I am building TWRP for public. I was only trying for myself. The recovery.zip attached in the previous message is just the stock recovery backed up from TWRP app as it has some missing files from recovery extracted from the stock firmware.
Click to expand...
Click to collapse
Build.prop can get out from rooted phone

oli231 said:
Build.prop can get out from rooted phone
Click to expand...
Click to collapse
https://www.droidwin.com/create-port-twrp-recovery-android/
It's default.prop in the guide. Build.prop is different right?
I am only following that guide. I don't know about how to build TWRP from source.

Abhishek Junghare said:
https://www.droidwin.com/create-port-twrp-recovery-android/
It's default.prop in the guide. Build.prop is different right?
I am only following that guide. I don't know about how to build TWRP from source.
Click to expand...
Click to collapse
NOPE! Build.prop is on A52s no from this website, on this website is incorrect

oli231 said:
Build.prop can get out from rooted phone
Click to expand...
Click to collapse
I got the Build.prop. Thanks.
How do I get fstab.samsung (or similar fstab.----) It's not in the recovery.img

Abhishek Junghare said:
I got the Build.prop. Thanks.
How do I get fstab.samsung (or similar fstab.----) It's not in the recovery.img
Click to expand...
Click to collapse
fstab is in kernel

How To Guide How to flash A pixel experience GSI for Samsung A52s [UPDATED]

How to flash PE+ GSi
1. Unlock Bootloader (LINK) how to
2. Download TWRP from LINK And Disabled VBMETA LINK Thanks To @BlackMesa123 for disabled VBMETA
3. flash TWRP
4. Turn phone into Recovery
5. Format DATA partition
6. download PE+ any version, i recommend PE 13.0 LINK Thanks to @ponces for Best GSI
7. Flash Gsi using TWRP, Install zip install img and select GSI image.
8 flash GSI via TWRP flash flash SYSTEM
VOLLA, you have PE+

oli231 said:
YES! i did it! now i have a pixel for this phone
Click to expand...
Click to collapse
@Arobase40 @ALWA7SH6 @bobfrantic

Yay!

Reserved

Geoperson8 said:
Yay!
Click to expand...
Click to collapse
Look for tutorial

Great job! Is everything working?

NickDeveloper said:
Great job! Is everything working?
Click to expand...
Click to collapse
Yes, but VoLTE not working and hotspot

Arobase40 said:
Well, it's fine your did flash Pixel Experience rom on your A52S, but I don't understand what is your contribution in the development and the building of this ROM ???? ^^
If it's a work done by someone else then this thread should not be treated as "Development" but at the best as "How To Guide" since you brought more materials since your first announcement. Naming the dev or the modder would also be welcome...
Click to expand...
Click to collapse
Ah yes, sorry, now i'm changing

Arobase40 said:
Any responses to my other questions ?
Click to expand...
Click to collapse
And recovery is not TWRP, just normal modded with FASTBOOT

Arobase40 said:
Ok but again what this recovery stands for and why it is needed to flash it ?
Then you said : "Step 2. download TWRP APP"
so where do we get this TWRP compatible with A52S 5G (A528B) ??? ^^
I guess there is a misunderstanding somewhere...
Click to expand...
Click to collapse
So, TWRP App is required that you flash another recovery

Arobase40 said:
Ok but again what this recovery stands for and why it is needed to flash it ?
Then you said : "Step 2. download TWRP APP"
so where do we get this TWRP compatible with A52S 5G (A528B) ??? ^^
I guess there is a misunderstanding somewhere...
Click to expand...
Click to collapse
If I understand OP correctly, the TWRP app can also flash other images. He uses the TWRP-app as an alternative to flashify or TWRP/CWM/recovery to flash a modded recovery(.img) which enables fastboot.

Thread cleaned!!
For the love of Pete one and all! Is it too much to ask for a little respect and tolerance from and towards each other?
While we always enjoy spirited debate, I still, even after 11 years on XDA, don't understand why discussions must resort to rudeness and name calling when disagreements occur.
So Please, as a simple request, I am asking you all to please keep disagreements relegated to PM's, or take the fight to FB, IG or wherever, so you can impugn each other as much as you want
since this rudeness and disrespect will not be tolerated on XDA as XDA Rule 2.3 clearly states.
Your cooperation is greatly appreciated, and expected, as per the Forum Rules. It's just that simple my friends.
-Regards: Badger50
Senior Moderator

oli231 said:
Tutorial how to flash PixelExperience
Step 1. Root your phone
Step 2. download TWRP APP
Step 3. flash recovery via TWRP
Step 4. download Pixel Experience
Step 5. Flash using Fastboot, command fastboot flash system system.img
Step 6. Go back to recovery and wipe data
Step 7. reboot to system and volla, you have Custom ROM
Click to expand...
Click to collapse
when was TWRP made for this phone and has anyone tested it if it works?

Arobase40 said:
For what I understand this TWRP is simply an application from which you could flash another custom bootloader but it can't be use as a stand alone TWRP you can't flash with PC Odin and you can't boot on it to do backup and restore of the whole android system or flash another custom rom. ^^
Click to expand...
Click to collapse
I think he meant TWRP app where he said TWRP, the app discussed earlier. Currently there's no twrp or other recoveries (besides the one that OP says to flash which supposedly is a modded version of stock recovery that would enable fastboot on this device (going by the posts in this thread, I'm holding off unlocking BL and tripping Knox untill there's actually things available to flash))

screen said:
(besides the one that OP says to flash which supposedly is a modded version of stock recovery that would enable fastboot on this device
Click to expand...
Click to collapse
That's correct! This is moddeed version of stock recovery with enabled FASTBOOT

Does anyone has already a few days with the ROM? How's everything working for you?

MuyKurioso said:
Does anyone has already a few days with the ROM? How's everything working for you?
Click to expand...
Click to collapse
Yes, everything working without hotspot and VoLTE

oli231 said:
Yes, everything working without hotspot and VoLTE
Click to expand...
Click to collapse
May I ask about the source of this ROM ?

anhyeuviolet said:
May I ask about the source of this ROM ?
Click to expand...
Click to collapse
GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
Script and patches for building PHH-Treble Pixel Experience - GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
github.com

so i flash twrp then flash ur recovery after sideload the rom with fastboot? it is right?