yashsingh1/xdaforums huggingface dataset:
[OnePlus 11] user2332:
OnePlus 12

KSU -> LKM kernel

Netflix won't start -> Netflix error 15001 (-93)

liboemcryptodisablerodm_26_magicmount -> I installed it but no change

magic_mount_extend_latest -> I installed it but there is no change and I think this is for older Magisk version.

Suggestion, idea?
[Realme GT Neo 2] Lord Sithek:
Courtesy of @erikdrozina - he is the Developer

OctaviOS is an AOSP-based ROM focusing on unique and smooth UI

with handy features.

OctaviOS is a reborn of Pie-based PearlOS.

* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROM and/or kernel.
* You do this at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

​

CLEAN FLASH :

• download and flash TWRP recovery

• go to the recovery, then wipe Dalvik/Art Cache, Metadata, Data, Internal Storage and Cache partitions. After this format Data partition and reboot to recovery

• flash the ROM

• (optional) flash Magisk and Disable Force-Encyrption (DFE)

• reboot to system

DOWNLOAD

​

• LineageOS

• AOSP

• SuperiorOS

• Pixel Experience

• ExtendedUI

• HavocOS

• CrDroid

• FluidOS

• @TheMalachite for the base trees

• others that I forgot to mention

​

OctaviOS Source

Telegram General Group

Telegram Device Group

Telegram Device Channel

​

REPORTING BUGS

As soon as the problem occurs, take a logcat!

How to take logs:

1) use an app like Matlog (root needed), start recording in the app, reproduce the bug, save the result in the app and share it in a post here or on the Telegram Device Group

2) from the PC: use adb logcat > log.txt command, reproduce the bug and then share the log.txt file

How to get ramoops:

• reboot to recovery before booting into system again

• open the terminal in the recovery

• type in the terminal cat /sys/fs/store/console-ramoops-0 > /sdcard/ramoops.txt

• boot into system and share the ramoops.txt that you'll find in the storage root folder

​

OctaviOS for realme GT Neo2 5G

Device Codename: bitra

Maintainer: @erikdrozina

Build Type: Official

Device Tree

Kernel Source

ROM OS Version: 13

ROM Kernel: Linux 4.19.157

ROM Firmware Required: C.09

Based On: AOSP

VERSION INFORMATION

Status: Stable

Current stable version: 4.1

Build Date: 13/02/2023

Size: 2.1 GB

Source changelog: here

SELinux status: Enforced
[Realme GT Neo 2] Lord Sithek:
RESERVED
[Realme GT Neo 2] rafaelpcosta:
finally something actually properly working for the realme gt neo 2. currently my daily driver, not looking to change any soon. cheers!
[Realme GT Neo 2] rtkpX:
Any previews?
[Realme GT Neo 2] Lord Sithek:
From Telegram I know you flashed already 😅
[Samsung Galaxy S23 Ultra] zagnut12345:
I'm curious if anyone knows the compatibility of a US Verizon s23 ultra and T-Mobile's network. I assumed they would be compatible as long as its carrier unlocked however I'm having issues getting my Verizon s23 ultra to accept my t-mobile sim. Any insight from someone with more experience is welcomed.
[Samsung Galaxy S23 Ultra] EtherealRemnant:
Verizon locks the phone for 60 days. After that, you're good to use whatever SIM you choose (you may have to flash the U1 firmware to get all features working though).
[Samsung Galaxy S23 Ultra] zagnut12345:
Its unlocked I manage about 40k in devices so they unlocked it for me without much hassle but they cant answer why my t-mobile sim isnt working.
[Samsung Galaxy S23 Ultra] EtherealRemnant:
That sounds like it's still locked to me? Are you using the pSIM or the eSIM? There have been some reports recently that the pSIM gets unlocked and the eSIM remains locked to the original carrier but if you're trying to use the pSIM and they say it's unlocked, I don't know.
[Samsung Galaxy S23 Ultra] zagnut12345:
The esim is verizon and the psim is t-mobile. Ive had small issues in the past with devices not being able to take full use of the network etc. but not flat out not working.
[Samsung Galaxy S23 Ultra] EtherealRemnant:
Yeah that's strange. On paper it definitely should work.
[Samsung Galaxy S23 Ultra] zagnut12345:
Ty for the replies. If I figure something out ill post back, in meantime I'm going to try and flash U1 and see if that helps.
[Xiaomi 11T Pro] Idk828182:
Hello! I am new here and wanted to port a rom to my 11TPro which has SD888 Chipset and the rom I want is from Oneplus9RT which also has SD888 so I was wondering if porting oxygen OS of this device is possible on the 11TPro and if it is then how?

Please help me

And thanks for reading.
[Xiaomi 11T Pro] Shapalapa:
A ROM typically requires a lot of work for it to be compatible with a device. You can't simply grab any ROM and flash it to another device. There are other aspects when it comes to hardware such as the cameras, sensors, components for Wi-Fi/Bluetooth etc.

First before you can make any modifications, you of course, have to unlock the bootloader by using a tool provided by the manufacturer. For Xiaomi, you need to first pair your Xiaomi Account to the device by going into the Developer options in settings and then use their Mi Unlock tool to submit the request. You will have to wait around 7 days in order to be able to unlock it. After that, you now have the option to install a custom OS

Do note that due to the bootloader being unlocked, apps that check the bootloader status such as banking apps and streaming apps may not work anymore. But there are ways to make them work by patching the SafetyNet/Play Integrity API.
[Android Head-Units] nest0r:
Atoto A6 PF installed yesterday and all was good until late in the day the menu stopped opening. I click the icon and it flashes a sound icon over the menu icon for a brief second before nothing else happens.

I’ve tried disconnecting the power harness in an effort to hard reset it and soft reset it to no avail.

Will try to update firmware soon but I don’t have access to putting the file onto a usb drive at the moment, as ridiculous as that sounds. And I did download the file through the browser but can’t experiment opening the file since I can’t access the menu > file explorer.

Any ideas??

Attached a video here:
[Android Head-Units] nest0r:
Managed to successfully factory reset the device again and that solved it. Not sure why it didn’t take the first time.
[Android Head-Units] TorstenH:
Maybe you could describe the reset procedure in more detail?
[Android Head-Units] nest0r:
Sure, it was just going through something like Settings > User Accounts > Reset, and it did a factory reset of the device.

The weird part was that I did that once already and it simply restarted the device to the same state instead of actually resetting it, so I was like uh oh what now.. Tried it again and it worked correctly.
[Android Head-Units] bigmike76:
I had thie same thing happen with my app drawer. I factory reset it and it worked fine for a couple days, then out of seeming nowhere, it started doing it again. I just did another factory reset but I have a hunch it's just a matter of time and it'll happen again. I would like to find a permanent solution. Hows yours holding up?
[Samsung Galaxy Tab S8] Daxorp:
Hello,

I'm root of course, is there a way to hide the 1st entry of Android parameters "Samsung account"? Deactivate related apps does not. It does nothing when I click on it but it's still showing.
[Samsung Galaxy Tab S8] PlutoDelic:
Good Lock > Registar
[Samsung Galaxy Tab S8] PlutoDelic:
Let me google that for you
[Samsung Galaxy Tab S8] Daxorp:
Some people still use Google? wow...

You should Google for better privacy search engines!

OK, thanks but no, my goal is not to install 2 more apps to reorder the parameters menu, but to deactivate the right apps for the menu to hide by itself (if possible, it generally does this because some apps add the menu, so no app, no more menu.)
[Samsung Galaxy Tab S8] PlutoDelic:
Here's a screenshot from the app. It's from my phone, but i use it on my Tab S8/S7 too

The apps are from Samsung btw. Alternatively, you're out of options.
[Samsung Galaxy Tab S8] JanBoyGamer23:
Hope this helps my guy:

adb shell pm uninstall --user 0 com.osp.app.signin

this will remove samsung account functionality almost completely. I suspect you know how to use adb. Just note that some buttons in system apps might break
[Samsung Galaxy Tab S8] Daxorp:
No, it's already deactivated.
[Samsung Galaxy Tab S8] Stogie87:
Amazing! Thanks for mentioning this app. I didn't know, that there is something to customize the settings menu.

I wanted to get rid of the remote service entry since i removed tips app and finally you gave me the solution. Thanks!
[Samsung Galaxy Tab S8] JanBoyGamer23:
If its deactivated then it will still appear, you have to uninstall it
[Samsung Galaxy Tab S8] Daxorp:
I read that we can't anymore uninstall system apps. Swiftbackup doesn't allow it.

adb shell pm uninstall really uninstall or it's only "marked uninstalled" and reversible?
[Samsung Galaxy S23 Ultra] mmafighter077:
It's there any way to lessen the saturation of the picture without having to go into pro mode. Most of the colors in the photo are okay but the reds almost glow. I've never minded Samsung saturation but this is a bit much. Just not sure what settings that I could change to adjust this. Below I've attached S23U vs Pixel 7 pro. Pixel is more realistic.View attachment 5840403View attachment 5840401
[Samsung Galaxy S23 Ultra] blackhawk:
Post processing red channel contrast curve edit on a color calibrated monitor.

Yeah that's a pain.

Your display may be part of the problem. Set display to "natural" setting. The vivid setting will cause this. Regardless if it's cam or the display calibration is sort in the air.
[Samsung Galaxy S23 Ultra] mmafighter077:
Oh dang. I take this back. The pictures looked more vivid because I was viewing it in the sun. Coming back inside, the pictures look more how I like it. 🤦🤦
[Samsung Galaxy S23 Ultra] blackhawk:
Yeah try to avoid using in direct sunlight as it's hard on the display. In sunlight the vivid setting may help reduce washout. Don't know if it auto toggles that on for bright viewing conditions for that model or not. Sort of looks like it does...
[Samsung Galaxy S23 Ultra] GroovyGeek:
Turning off scene optimization in camera settings will help some. You can also change the saturation after the fact with an image editor. Google photos has that built in. Also turn on raw+jpeg in pro mode and use pro mode for high value shots.
[Samsung Galaxy S23 Ultra] Dayuser:
Still after looking these pictures via PC screen i can say that first picture is too much saturated than second picture.
[Samsung Galaxy S23 Ultra] mmafighter077:
You're right. It's slightly more saturated than I would like but it's better than what I was seeing in the direct sunlight.
[Samsung Galaxy S23 Ultra] GroovyGeek:
Saturation of most scenes is on the aggressive side, but the sky on a sunny day is ATROCIOUS. The blue is way way way too saturated and dark, and very difficult to correct in post.

The only way I have found to fix saturation via a permanent setting is in pro mode.Click the icon in the upper write of the screen, adjust saturation (-5 works well IMO), tweak other things (I brought up the shadows to +8, highlights down to -5, contrast down to -3). Then go to settings and under "Settings to remember" make sure that mode and filters are selected. You will have to always shoot in Pro mode for this to have effect, I think. Alas a saturation adjustment is not available in regular mode.

BTW I tried gcam with allegedly "natural processes xml" and it was the same fugly blue sky.
[Introductions] rsXda2017:
I'm a software developer (mainly C++) and owner of various (older) Android smartphones. Especially Samsung S5 LTE (klte), S5 plus (kccat6) and S5 neo (S5neolte). I'm very interested in how to keep older smartphones up to date. So coming from lineageos.org I landed here as some older devices lost their official Lineage OS support. How can I contribute to keep (older) smartphones up to date?
[Introductions] galaxys:
Welcome to XDA and enjoy the forums information!🙂💻📱

Check out your specific devices forum sections for information

Cheers!
[Motorola Edge+ (2022)] limpet:
Motorola reps say: "the motorola edge+ 2022 does not support 5G on AT&T. It will however support 4GLTE/HDVoice (VoLTE)".

This matches the information at: https://www.motorola.com/us/smartphones-motorola-edge-plus-gen-2/p?skuId=747

But I'm not sure the carrier compatibility listed there is very meaningful...much of it seems contradictory. I wonder if the document was produced by lawyers rather than engineers.

I'd appreciate any information about AT&T data on this phone. What works and how to set it up.
[Motorola Edge+ (2022)] PartyHatter:
AT&T does work, but as Motorola says 5g isn't supported, though it'll certainly show up that it can, but a speed test said otherwise, so if you're looking for a 5g I wouldn't get this
[Motorola Edge+ (2022)] EddiePR:
View attachment 59167595G works for me
[Motorola Edge+ (2022)] cooki3monst3r77:
I get 5g, no problem. I'm in Ohio, on at&t.
[Motorola Edge+ (2022)] jlee860:
I don't get 5G here in Chicago with ATT. I get "5gE" though which is just ATT 4G LTE 2nd iteration on their network. Not the samething though.
[Motorola Edge+ (2022)] n2locarz:
Hey guys, I recently purchased the Boost Mobile Edge plus 2022 for$190. Got an unlock code on eBay for $1.70 and use AT&T unlimited 5G no problem

Variant XL2201-3.

Hardware version: PVT2

Latest firmware: s3shs32.12-41-4-4
[Motorola Edge+ (2022)] rawhide85:
Cm anyone confirm if this device has Wifi calling? Thanks in advance.
[Google Pixel 4 XL Questions & Answers] d1abol1cal:
Hey there, Hope everyone is fine. I have a pixel 4 XL 6/64 that was a running a version of android 12.xxxx something don't entirely remember that went completely unresponsive out of the blue. Doesn't turn on when holding the power button nor does holding power + volume up do anything. It was perfectly healthy with 70 percent battery when I last used it and set it down to come back in 5 minutes and see this happen. my device was oem unlocked with the bootloader unlocked and was also rooted. I was still receiving updates for android 13 which I was ignoring intentionally. Now when I connect my phone to my pc via usb it shows up as QUSB_BULK_CID:0404_SN:xxxxxxxx in device manager. From what I've read this indicates that it is in edl mode and I need a firehose to flash another rom image to the nand flash. I also see that older pixels come up with this QUSBxxxxx name in device manager and the 4 XL shows up with a different name, anyways this seems like a recurring issue with other people and since I live in Pakistan I can't get it repaired officially from google. I've got very less hope and I feel robbed. I wanted to know whether I can try anything to revive this phone as it had important data. I can see the firehose files on this forum but has it worked out for anyone else ?

I would really appreciate an experts response as I lack the required knowledge regarding this problem.

Thanks for taking out time to read this.
[Google Pixel 4 XL Questions & Answers] yizhen:
I also encountered the same problem, QUSB_BULK_CID: 0404_SN: xxxxxxxx, which is actually Qualcomm's 9008 mode. It's unfortunate that we have to meet in this way. I also sought help on XDA and couldn't find anything on Google.
[Google Pixel 7 Pro] SNUZ_NT:
Hello everyone,

since I've updated and rooted my P7Pro (with PixelFlasher tool) to the TQ1A.230205.002 the hotspot I create is not working anymore.

If I start the hotspot there is no error but if I try to connect to that hotspot from an other device (doesn't matter what for a device) it can't connect to it. The only exception is if I connect there from my Windows PC - it's connected but says "not internet".

Am I the only one with that problem ? Hopefully someone knows how to fix this ?

Thanks :)
[General Topics] eugene373:
So I've became the lucky owner of two of these devices, and after hosing one and having to rebuild from scratch I want to provide some helpful information on rooting, backing up the device and general info that may or may-not be needed! So let's start this party off right!

These commands posted are for the Linux terminal, add python if using windows or play with the command line of mtkclient to figure things out, I can't assume what everyone OS's are.......

1. get yourself mtkclient from here : https://github.com/bkerler/mtkclient

follow all the steps regarding setup regardless if on Linux or Windoze!

2. BACK-UP the Full device using mtkclient, doing so will save yourself a lot of aggravation that I endured during my endeavors! This will do a Full back-up of the device by partition and place in a single file for making restore painless.

Power OFF the phone

Issue the mtkclient command via Terminal

mtk rf flash.bin

HOLD VOL+ & VOL- and plug-in the USB-C, if done correctly the phone will go into brom.

Once done backing up ( Total Time is around 60 minutes or less ) we're going to issue the last command, this resets mtkclient safely)

mtk reset

2a. Restoring you're Device

Now we're going to issue THREE mtk commands, the first is, assuming you're working in the same directory you back-up the file to.

mtk wf flash.bin

Without un-plugging, issue the next to wipe all data for a full reset.

mtk e metadata,userdata,md_udc

followed by reset

mtk reset

In the extreme case I suffered, you need to let the phone die completely if unable to enter brom the normal way, once dead follow the process as if you just turned it off.

This situation came about while I began to figure out how to get twrp working on the device.

Total size of this back-up will be around 32GB, so store in a safe place.. Also, DO NOT SHARE THIS IMAGE WITH ANYONE!!!! It contains all of the phone's sensitive info (IMEI)
[General Topics] eugene373:
Now let's talk rooting with or without bootloader-unlocked.

The good new's about this device is we can use mtkclient to bypass unlocking the bootloader for flashing a rooted boot.img patched by Magisk, the bad new's is that the phone will default to boot_b and not the boot the root boot.img so unlocking the bootloader is a must.

adb install app-release.apk that is attached, this Magisk that is designed for mtk devices and frankly has worked the best for me, once installed we're going to back-up the stock boot with the following commands using mtkclient.

mtk r boot_a boot.img
mtk reset

this will be placed in you mtkclient directory and will need transferred to the storage for patching by the Magisk app. once done we will transfer the file back to our mtkclient directory.

boot once again back into brom and issue the command

mtk w boot_a magisk_patched.img
mtk reset

keep in mind that each patched boot.img will be named different so this is not a copy and paste thing currently.

however, if you want to install an already patched version of the boot.img you can download the attached boot.img, place into your mtkclient directory and issue this command

mtk w boot_a magisk_patched-23001_nx6U2.img
mtk reset

For bootloader-unlocking, just follow the read-me file for more in-depth instructions, however this will get you going regarding the unlock.

boot back into brom and issue the following commands, if done correctly the bootloader is now unlocked. However this is needed for simple root, just flash the attached boot.img

mtk da seccfg unlock
mtk e metadata,userdata,md_udc
mtk w vbmeta vbmeta.img.empty
mtk reset
[General Topics] eugene373:
This particular guide is addressing Super.img read-writable, focusing on making all partitions write-able for the reason updating the phone with GSI Images or just needing access to add / remove files on the phone.

I found this post most helpful regarding super.img, as i had issue at first understanding boot-loops at first. https://xdaforums.com/t/tool-win-li...s-rw-in-super-partition.4120963/post-87112415

This is assuming you are now comfy with brom, familiar with using mtk and also on Linux.

I've already done all the work need for converting hex to dec, and is a start copy of my note's and the steps I took to get things working. I'll attach the file as well for off-line use if needed as well.

First we need to back-up the super.img from the brom using the following command with-in the mtkclient directory. make a copy of this before we begin and keep in a safe place!!!

mtk r super super.img

once done we will use this tool to break down the image's into readable partition's using linux.

https://xdaforums.com/t/tool-win-li...ake-partitions-rw-in-super-partition.4120963/

once you have your super.img placed into the new extracted directory, we're going to issue a command using terminal from said directory.

./superunpack.x64 super.img

next we're going to create THREE folders call system, vendor, product. ( Vendor & Product is optional if editing system only )

So lets start with system as most will only likely be editing that for rw access, so let's get down to it.

e2fsck -f system_a.ext4

resize2fs system_a.ext4 2G

e2fsck -y -E unshare_blocks system_a.ext4

e2fsck -fy system_a.ext4

sudo mount -t ext4 -o,rw system_a.ext4 system

now you're ready for system edits, once done we need to unmount the system using this command

sudo umount system

next we need to fix the system and resize it so we can add it back into the super.img following these commands.

e2fsck -fy system_a.ext4

resize2fs system_a.ext4 353376

once done we can use DD the system back into super,img, keep in mind this takes a very long time as it need to read the block and search for the offset that we're using.

dd if='system_a.ext4' of='super.img' bs=1 seek=2315255808 count=1447428096 conv=notrunc

once done we need to move the new super.img to our mtkclient folder, and flash using

mtk w super super.img
mtk reset

if done correctly it will boot with read / write access to the system partition.

again I've attached my notes that also include Vendor & Product to keep this thread to a minimum! however i will include partition sized and dd instruction here for vendor, product & system for short hand viewing on-line.

SYSTEM

e2fsck -fy system_a.ext4

resize2fs system_a.ext4 353376

dd if='system_a.ext4' of='super.img' bs=1 seek=2315255808 count=1447428096 conv=notrunc

PRODUCT

e2fsck -fy product_a.ext4

resize2fs product_a.ext4 461253

dd if='product_a.ext4' of='super.img' bs=1 seek=1048576 count=1889292288 conv=notrunc

VENDOR

e2fsck -fy vendor_a.ext4

resize2fs vendor_a.ext4 103509

dd if='vendor_a.ext4' of='super.img' bs=1 seek=1890582528 count=423972864 conv=notrunc
[General Topics] eugene373:
Last but not least, if anything this the most important part regarding Development.

Attached is the Project config make file, I've not currently tried to build this as I'm still digging into this device. However it is a nice Find as it has the build condition as well as the driver info.

some might recall this as a /proc/config.gz file but again we have no kernel source but clearly it's not impossible to build having all the info, but it's a long road.
[General Topics] lopestom:
I guess you haven't seen it yet but in any case I'll leave it (don't know for how long) for you to try.

As I didn't get an answer there, I came here to leave this brief message.

Good luck.

Cheers
[General Topics] eugene373:
I'll try it, been moving and still trying to find everything
[General Topics] _Aleks_:
Hi, Eugene. My MTK client doesn't know command "da" :(

Can anyone tell me if you had seen this error?

Maybe I need a different version of the client?
[General Topics] _Aleks_:
I tried to flash this magisk_patched.img into my phone.

I enabled OEM Unlock in the developer menu.

After flashing phone says it has a verification error.

Maybe it is possible to disable this verification?
[General Topics] _Aleks_:
EBreHuu', BbI cJIu4au'Ho Ha pyccKoM He roBopuTe? :)
[General Topics] eugene373:
You need to unlock, then flash my vbmeta that has been disabled, I'm using Linux regarding mtk da. I'll dig my laptop out after dinner and see which version I'm using.