yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] roshan2989:
Guys another question ,i have already root my phone and installed Sultan kernel.

how to keep root and update ota?

this is the method i did, not sure whether is correct or not.

1.Disable all the magisk module, reboot

2.Reboot to boot loader, sideload OTA

3.then i take new factory image boot.img patch with magisk

4.flash magisk boot.img,reboot

5.Flash Sultan kernel

6.enable all the module (Play Integrity Fix, Playcurl and Shamiko)

7.reboot. Done

Once i did that, my Play Integrity is good except for Safe Attestation, the CTS Profile Match is Fail.

all my banking apps working fine here

You guys got any root method?
[Google Pixel 8] Koeties:
PixelFlasher. Here on XDA and in the Pixel8 section.
[Google Pixel 8] MasonJames1988:
voiding warranty isnt a thing with pixels, revert back to stock and its fine. samsungs however, trip knox permantley which is what voids warranty. ist anything like that with pixels
[Google Pixel 8] Nick_101d:
What do you use to get that?
[Google Pixel 8] Ćwirek:
This module:

GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui

Magisk module to enables pixel exclusive features and ui - Kingsman44/Pixelify

github.com

or this ROM:

[ROM][14.0_r53][OFFICIAL] Evolution XYZ 9.2[07/18/2024]

Google Pixel 8, 8 Pro & 8a [Shiba][Husky][Akita] Pixel UI, customization and more, we are Evolution X! Joey Huab - Founder/Lead Developer Anierin Bliss - Co-Founder/Co-Developer Akito Mizukito - Co-Founder/Project Manager Reach us on...

xdaforums.com
[Google Pixel 8] InfinityBelow:
Pixels... nope
[Google Pixel 8] hellmo_luciferrari:
Well, I truly this comes down to use case and preference. For most non-technical, standard users, I would say stay stock as a blanket statement.

However, there are features that I get from running a rooted LineageOS install with a custom kernel, that I could not have on stock.

For me the pros of having a rooted device are (but not exhaustive in any way):

Custom Kernel (I use Despair Kernel) mainly for better thermals because I run lots of magisk modules and programs that run in the background

Hosts based Ad Blocking via AdAway

AFWall+ which is a firewall that requires root privileges

Magisk Modules such as: A-GPS SUPL replacer, Sysemless Hosts, WireGuard Command Line Tools

While this may seem like a short list, it accomplishes many of the things I wish to accomplish
[Google Pixel 8] SideSkroll:
HI, im using a pixel 8a. Im guessing it would be the same procedure?

Would you be so kind as to point me to the right thread for doing that?

Ive been searching for a while and all I found was pixelify but I THINK it doesnt support A14?

Anyway, I would really appreciate a "for dummies" guide if there is one.

Thanks.
[Google Pixel 8] SideSkroll:
Works on A14? (It says 7 to 13)

Im only interested in the unlimited gphotos.

Thanks.
[Google Pixel 8] AggresiveSoldier:
Look in the submodules of pixelify.

There is a V2 for Gphotos, thats what im using and seems to work
[Google Pixel 8] SideSkroll:
Thanks for replying.

So I can just install the gphotos module and thats it?

One more thing, do I lose anything by installing it? Like I dont know, magic editor, memories, etc?

Thanks again!
[Google Pixel 8] Renate:
Reason to root: To get rid of stupid things that the OEM put in, both apps and "features".

Also to properly set distinct keylayouts / keymaps for different devices.

Sure, with Accessibility and Alt-Space you can switch between layouts / maps.

But with custom kl / kcm you can have keyboards or Bluetooth controllers always just do the right thing.

I have an English keyboard, a Russian keyboard and BT remotes and they just work without switching.

Magisk is great and clever, but do a mount and see how many mounts it required to replace an itty-bitty file.

I try to run Magisk-less.
[Google Pixel 8] kerngehirn:
I'd root my device in a second if banking apps weren't a problem.

In my opinion rooting is more interesting than ever, since Google and other manufacturers keep limiting the possibilities to change things you don't like.
[Google Pixel 8] hellmo_luciferrari:
Using banking apps on root is possible (and in my experience quite easy to do.) With many ways to accomplish root depending on your phone, and methods of hiding root.
[Google Pixel 8] kerngehirn:
Tried everything on my oneplus 6. Until I finally gave up and unrooted. A week ago I got my pixel 8 and I wasn't planning on rooting because of that experience.

Some banking apps worked. But some didn't. And the ones that worked occasionally stopped working and I needed to look for a Ne fix.
[Google Pixel 8] hellmo_luciferrari:
Your mileage may vary, but what I use is:

Play Integrity Fix

Playcurl

Zygisk Next

Shamiko
[Google Pixel 8] kerngehirn:
Well it's been already almost two years I think. I'm not up to date with what's possible. But back then I think I tried everything that was not too time investing.
[Google Pixel 8] generalculprit:
PIF has a built-in fingerprint by now, so you don't need playcurl.

If the one remaining public fingerprint (sailfish) gets banned, PIF is hopefully updated. Playcurl can do no more.

With your setup you will achieve Device Integrity by spoofing your device to Droid Guard but that doesn't mean a (banking) app can look for other criteria. Or even ask for Strong Integrity.

Oh, and you loose RCS.
[Google Pixel 8] hellmo_luciferrari:
Cool, I can get rid of playcurl. I haven't passed strong integrity. Never tried to pass that.

I don't need RCS. I don't use texting for much of anything.
[Google Pixel 8] generalculprit:
You can't with unlocked bootloader. 😉

Agreed.
[Google Pixel 8] hellmo_luciferrari:
That's why I never tried! It doesn't gain me any features I would use even if I could spoof that.

As much as I wanted RCS to take off, it didn't. And I would much rather have more secure ways of chatting.
[Google Pixel 8] aap7:
I use call recording (it's legal in my country but disabled by Google for some reason) and YouTube ReVanced.

For my both features justify rooting and Google Wallet and banking apps work fine after using Magisk Hide and Play Integrity Fix.
[Google Pixel 8] a_petrov303:
can you please provide link to this thread?
[Xiaomi Mi 5 Guides, News, & Discussion] Kiwyy Tech:
I found a port of MIUI 13 for Xiaomi Mi 5

It only requires unlocked bootloader and TWRP installed

ROM link 1: MIUI 13

ROM link 2: (if 1 doesn't work)MIUI 13 (2)

Good luck putting it on. It will have bootloop, but it is fixed by format data from TWRP.

View attachment 6093005View attachment 6093004
[Xiaomi Mi 5 Guides, News, & Discussion] roirraW "edor" ehT:
<Moderator Note>:

Hi @Kiwyy Tech,

Please read the stickied thread at the top of every section regarding what can do in the Development section: only your own Development.

Sharing other Developer's work is allowed, but only in the Xiaomi Mi 5 Guides, News, & Discussion section as long as the particular Development doesn't already exist on XDA, and you give full credit to whoever did the work.

I've moved this thread because of this.

@jack sonny,

First, your post is off-topic to this thread, so I've deleted it, but it's also against our rules to promote things like that.

Please don't respond to me here in this thread. If you have any questions, send me a PM instead.

Thank you,

@roirraW "edor" ehT
[Touch Pro, Fuze ROM Development] Dillsnik:
I know, I know....

but i am not a flash junkie and don't want my first experience with the TP to be flashing 10 roms. I'm just looking to get a decent one (preferably not a black theme :)) and run with it to get to know touchflo and the device. Thanks!
[Touch Pro, Fuze ROM Development] Sleuth255:
There's a good Wiki associated with this device. Get to know the chefs then start reading their threads. Took me about an evening to find what I was looking for.
[Touch Pro, Fuze ROM Development] mchapman007:
Just my opinion but, NATF's all the way! And the FuzeBerry of course....
[Touch Pro, Fuze ROM Development] duke_stix:
Hi there

Ive coome over from the hermes camp too (although its still running)

i would personally reccomend the lantis os roms but again, and you'll see this all over xda, you will only find the best rom for you after flashing a few

and theres only really a handful to try!

good luck and make sure you've hardspl'd and have your stock rom and radio versions written down or backed up just in case you have to do a warranty return! saves u the hassle of trying to hunt it down in the panic!
[Touch Pro, Fuze ROM Development] Reefermattness:
You should try them all, so you can see what the difference between a good and bad rom is. Each rom is built different for different so not all roms may suit your needs..... but i agree on Lantis OS being my favorite right now.
[Touch Pro, Fuze ROM Development] remoteshoppe:
I personally tried Romeo, NATF and Proven and decided to stick with Proven.

I had problems with the screen shutting off during calls with Romeo.

I experienced TF3D lag with NATF.

Proven has been rock solid and I like the Diamond tweaks he's incorporated.
[Touch Pro, Fuze ROM Development] Black6spdZ:
if you don't like TF3D go with Da_G.. I'm actually running a VGA version of HTC Home on mine.. love the speed.
[Touch Pro, Fuze ROM Development] pandaboyy:
Thread like these usually get closed pretty fast, I'm suprised that yours last a day :p

It's really all depend on what you like, they are all great. For the past few days, I've tried many of them. And to be honest, there is no BEST one. It's really depend on what you need and what you like.

Da_G is has the cleanest ROM NaTF's

Elite RC2 Is fully loaded with a new feeling

NATF Is stable, and GPS lock is pretty quick (update very often)

Proven, it's like Elite with less Applications and function (cleaner)

Romeo is very stable

.... Those are what i've tried

Check the Wikki in sticky post.
[Touch Pro, Fuze ROM Development] Black6spdZ:
I think it is a good question that should come up from time to time.. sure everyone has their personal preferences but for a new person wanting a quick rundown on the most current ROMS to date.. just saving the guy some time downloading and flashing all those different ROMS. anyone here flashed all released ROMS to date? ;)
[Touch Pro, Fuze ROM Development] stixnstownes:
I also went from the Hermes (8525) about a week and a half ago. Fuze was my christmas present :D.

I tried NATF's ROM for about a week and had many problems, which i seemed to ignore because of all its good feedback. I then tried Lantis OS and had no problems at all, I am still currently using it. No errors and speedy fast.

My suggestion is Lantis OS for the moment, but NATF is suppose to be releasing his v4.0 ROM sometime today or tomorrow so you should look out for that as well.

Good luck with your fuze and your flashing, and enjoy that beautiful VGA screen that i loved when i got it compared to the Hermes :)
[Touch Pro, Fuze ROM Development] Sleuth255:
I don't think that XDA-developers ever had any problems with folks discussing ROMs and their xp with the various flavors in a rational manner. We usually end up shutting down threads because the first reply is "Use search you id10t!" followed by general thread degeneration.

Anyhoo.. normally I'm one of the chefs, but with this device I've found that Da_G's direction mirrors the way I'd be going anyway. He's more interested in technical improvements to the GDI, GPS etc than in all the additional apps. I'm pretty confident that he's well on his way to creating a solid base ROM that's free for anyone to work from. Exactly what I would have done. Why re-invent the wheel?
[Touch Pro, Fuze ROM Development] zrspige:
This is what these kinds of threads are supposed to be like! As stated by a couple people previously, normally these get dismissed and/or flamed. When people ask these types of questions, usually they are not asking (at least the smart ones aren't) which ROM the SHOULD flash, but rather what is your experiances with the ones you have used.

I understand how confusing it may be trying to decide which one to use - they all look the same as far as applications that are cooked in. Only difference aesthetically are the different themes and that alone is not a deciding factor for me.

Just as everyone has stated - just try some out and see how they feel to you. ie button mapping, folder layout, apps installed, speed, etc. I personally like Aruppenthal's RRE ROM but that's just my 2 cents.

FYI: From what I've seen, EVERY ROM has its own bugs/quirks that may or may not annoy you.
[Touch Pro, Fuze ROM Development] mumboender:
Any chance you could post the version your using? I can't seem to find a VGA version and I am getting ready to get rid of TouchFlo 3D. Or post the thread you got it from.

Never Mind....I found it in the Diamond Forum...
[Touch Pro, Fuze ROM Development] iScott78:
I second the Lantis OS. I am using it as well. It is very fast and stable. I had problems with NATF's as well. But I will try NATF's v4.0 when it is released.
[Touch Pro, Fuze ROM Development] At0mAng:
Not to get off the subject of this thread but which HTC Home VGA are you using? I am using one called PJ HTC Home VGA which is pretty good but wanted to try something different if it is better...
[Touch Pro, Fuze ROM Development] mumboender:
The one I'm using is a cab called htchome2.cab that I found in the diamond forum...works fine but the media player tab does not work.
[Touch Pro, Fuze ROM Development] mumboender:
And I have been using either Lantis or DaG Rom's....I use Blackberry Connect which adds lag to the fuze anyway but it seems to affect these Roms the least. I would be interested in hearing what Rom's Blackberry Connect users are fond of as it seems to make a big difference.
[Touch Pro, Fuze ROM Development] treoreloaded:
i too just got my Fuze from Kaiser. right now im using RomEOS and really like it. i might try the Da_G because i really dont care about TF3D.
[Galaxy Tab S2 Android Development] retiredtab:
Release notes

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Jun 23, 2024

1. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-06"

2. Whatever LineageOS changed since May 5th build. About 22,000 files needed to be recompiled.

May 16, 2024

1. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-05"

2. Whatever LineageOS changed since Apr 5th build. About 6,000 files needed to be recompiled.

Apr 15, 2024

1. Initial 20 ALPHA public release.

2. Incorporates Apr 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-04"

3. If you are coming from stock rom or an older LineageOS version (example, 18.1), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 20.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240415-UNOFFICIAL-gts28vewifi.zip

Release notes

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Apr 15, 2024

1. Initial 20 ALPHA public release.

2. Incorporates Apr 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-04"

3. If you are coming from stock rom or an older LineageOS version (example, 18.1), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 20.
[Galaxy Tab S2 Android Development] NightLord:
thanks for carrying on the development!

Im using the previous build by @thefanum on a T719, will try this one too.
[Galaxy Tab S2 Android Development] friedsonjm:
Works like a charm!
[Galaxy Tab S2 Android Development] Schaagi:
Dear retiredtab and team

Many thanks for your tireless efforts on the various Galaxy tablets. Thanks to you, these older but still very useful tablets continue to work. I have now expanded my stock with the T713, T810, T813 and T550. The only thing missing is the T555, but thanks to you and RGarrido03, it has also arrived at Android 13 / LineageOS 20.

I'm already hoping and looking forward to future updates.
[Galaxy Tab S2 Android Development] NightLord:
Wroks like a charm also on the T719 :)
[Galaxy Tab S2 Android Development] moloko01:
Perfect!
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-20.0-20240516-UNOFFICIAL-gts28vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

May 16, 2024

1. Incorporates May 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2024-05"

2. Whatever LineageOS changed since Apr 5th build. About 6,000 files needed to be recompiled.
[Galaxy Tab S2 Android Development] Ipaqman01:
Thanks. This release works great on my T713.
[Galaxy Tab S2 Android Development] gingerbeardman:
Thanks, build 20240516 all well and good on my T713 (which I recovered from FRP lock using: FRP bypass > OEM unlock > factory reset > TWRP > wipe & install)
[Galaxy Tab S2 Android Development] gingerbeardman:
I noticed this:

https://www.reddit.com/r/LineageOS/comments/qai9g9/_/hh4yuoo

which references this single line config change to prevent shutdowns

msm8976-common: Change default I/O scheduler to noop again · syphyr/android_device_samsung_msm8976-common@d435176

This reverts commit f00a3529063f3def37bd3be601cb06263ac019ac. Still issues with bfq and not being maintained. <6>[18559.203457] [3: mmcqd/0: 282] ------------[ cut here ]----------...

github.com

setprop sys.io.scheduler "bfq"

becomes

setprop sys.io.scheduler "noop"

I checked and this revert/change isn't in the source as I see it.

android_device_samsung_msm8976-common/rootdir/etc/init.qcom.power.rc at 351d5e137eea29df088de4b4cd38c2080f41bd74 · syphyr/android_device_samsung_msm8976-common

Contribute to syphyr/android_device_samsung_msm8976-common development by creating an account on GitHub.

github.com

Also I've ordered a new battery
[Galaxy Tab S2 Android Development] retiredtab:
Before I answer this in depth, I assume your post above and below is because you're seeing "random" reboots. If yes, for now, all I can say is that I've used my T813 running 20 for 18 months now (started January 2023). In 18 months, I've never experienced a random reboot and my used device can easily go down to 3% battery.

My public 20 build has been out almost 1 year now and while a couple of people have reported "random" reboots, in both cases, both were due to a degraded battery. You can search/read this at

https://xdaforums.com/t/unofficial-rom-alpha-lineageos-20-for-sm-t813-may-16-2024.4600493/

Now I know all my talk is about T813 and you have a T713, but 99.9% of the code is IDENTICAL between the two. I've only had the T713 for 2.5 months now and I have NOT seen any random reboots.

So change your battery first and then see if the random reboots continue. OR revert back to stock and see if you get random reboots. If yes in stock, the it's your battery.

PS. The correct link for the 20 source code is

https://github.com/retiredtab/msm8976-common/blob/lineage-18.1/rootdir/etc/init.qcom.power.rc#L200

As you can see, it's still bfq. If you want to change it to noop as a test, that's easy to do. Let me know if you want to change it and I can write the instructions up. The change would take about 5 minutes of your time.
[Galaxy Tab S2 Android Development] gingerbeardman:
Yes, please. I'll try your method before swapping my battery.

I will say that I've changed the scheduler on my device using software running as root, and since I've not seen any random reboots on my battery (no idea how degraded it is as I just bought the device, but safe to assume "at least some").

Also, unrelated, i am seeing disk access errors in an app (https://koreader.rocks won't load dictionaries) which they think is due to something being missing or wrong with the Lineage build. See here "It might lack proper SELinux contexts" I can't comment as I don't know enough.

I tested the last official Lineage build, lineage-16.0-20210215-nightly-gts28vewifi-signed.zip from here https://archive.org/details/lineageos20210217 and indeed koreader dictionaries work just fine.
[Galaxy Tab S2 Android Development] retiredtab:
1. Backup your data in case something goes wrong.

2. Boot into TWRP.

3. Touch Mount, then System (so it mounts the /system directory)

4. Open a terminal window/command prompt on your local PC.

5. # shell into TWRP

adb shell

6. # use vi to edit this file

vi /system/vendor/etc/init/hw/init.qcom.power.rc

# change "bfq" to "noop" on line 200

# save file

7. Reboot back into OS

8. Once Android OS is up and running verify noop by

adb shell getprop | grep sys.io.scheduler

If you're wondering if I'm going to make noop the default now instead of bfq, the answer is no. As I've stated, I've never had random reboots in 18 months of use. There's been no other wide spread reports of the same.

HOWEVER, I will keep this in mind, and IF I run into random reboots and changing to noop solves the problem, then I will make noop the default.

I don't want to make a change where bfq has worked for 18 months to something different unless I have some confidence that it works for the same amount of time. If noop works for you, then great and there's no need to change the battery and risk damaging the device.

The T713, even if you just bought it, is a device nearly 9 years old. The battery, even if unused, will degrade over time.

I buy used tablets. Nearly 10% have degraded batteries where at 50% or less, I get random reboots or it just shuts down. One device even at 90% battery when playing a certain game will shutdown.

Now I'm not saying it's 100% battery in your case because I did give options in my earlier post on what to try (changing bfq to noop and reverting back to stock).

If you believe SElinux rules are at fault, you have 2 options.

Option 1

1. enable developer options, usb debugging and rooted debugging.

2. Open a terminal window/command prompt on your local PC.

3. # shell into Android OS

adb root

adb shell

setenforce 0

getenforce

The above will change the OS into permissive mode. Retry your app. If app doesn't work, then try below.

Option 2

1. Backup data.

2. Boot into TWRP.

3. Download

https://github.com/AdrianDC/kernel_.../master/release/kernel_permissive_patcher.zip

This will patch the boot.img to load the kernel in permissive mode. I've used the above several times and it works.

4. Use TWRP to flash kernel_permissive_patcher.zip

5. Reboot into Android OS. SElinux is now permissive at boot time.

6. Retry app.

If app works, then run

adb pull /sys/fs/selinux/policy && adb logcat -b all -d | audit2allow -p policy

and post the outuput of that here.

To return back to enforcing mode, just reflash the previous rom you were using and it will overwrite boot.img.

PS. The comment about working on "official" vs "unofficial" doesn't always hold true. I have a device running "official" LineageOS 18.1 and Supercell mobile games will NOT work. I'm not the only one to report that as well so it's not "user" error. However, the same games work on my "unofficial" LineageOS 18.1 and 20 T813 builds.