yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] aswin_a_s:
PixysOS v7.3.2 Unofficial

Changelog

* Signed build with private keys (data wipe recommended)

* Added safetynet fingerprint updater

* Updated libs from NOS v2.6

* Updated kernel and qcom components

* Based on 14 QPR3 with july 2024 asb

* Switched to Carriersettings

* KernelSU is included

* Added AOD while charging

* Added extreme battery saver and scheduling

* Added back quick tap gesture

* Improved volume panel style ( Android 15 Beta )

* Added glyph music visualizer qs tile

Known issues

* Circle to search is broken

* Play integrity might be broken on clean install . Head to Settings>PixysLabs>Play integrity update fingerprint to fix

Builds : https://dl.aswinaskurup.xyz/PixysOS/Spacewar/

If you liked my work. Consider donating to help me cover my server costs
[Nothing Phone 1] aswin_a_s:
Its added back on latest build
[Nothing Phone 1] aswin_a_s:
PixysOS v7.3.2 new update

New Features

🔅 Brightness slider position customisation

🔐 More Lockscreen Pattern sizes

🔍 More search features in launcher

🎮 Revamped Gaming mode with more features

🔎 Search selector for supported regions

Fixes & improvements

🌄 Fixed AI wallpaper generation

📶 Fixed manual network selection

Downloads : https://dl.aswinaskurup.xyz/PixysOS/Spacewar/

Liked my work ? Donate me

* incremental can be used if you are in the last build and system is unmodified

download and sideload in the updater for this time

* OTA will be available from next build
[Nothing Phone 1] deadspark:
@aswin_a_s Would it be possible for the Emergency button available on lockscreen to be moved to a corner like it is on NOS?

Like so:

I'm asking for this because the current Emergency button is exactly where the fingerprint sensor is and sometimes when the screen is ON and you try to hold on the fingerprint sensor quickly for example while pulling the phone out of your pocket with thumb on the sensor already, it just calls the emergency number. This happened with me multiple times and on many ROMs except NOS because of the emergency button position being on the sensor. It would be nice if that button was in a corner and in smaller size like in the image attached. (only if it's possible ofc)

Also, the download link is timing out :(
[Samsung Galaxy Core 2 Questions & Answers] alfanveykov:
I have problem when rooting this phone trough magisk patched boot mode.

Method 1 :

Extract boot.img.lz4 from firmware > decompress to boot.img >patch via magisk > flash with odin in AP section.

Method 2 :

Directly patch AP_A260GDDSCAUJ2_CL15641782_QB44812985_REV00_user_low_ship_meta.tar.md5 with magisk > flash magisk_patched-26100_v8rhs.tar with odin in AP section.

Here my full details about my phone :

Model: SM-A260G

Name: Galaxy A2 Core

Country: Indonesia (XID)

OS Version: Android 8.1.0 Oreo

Build Date: 25-10-2021

Product code: XID

SM-A260GDDSCAUJ2

5 Files: BL, AP, CP, CSC, Home

Device Codename : a2corelte

I have done enabled developer option OEM UNLOCK and reset all data.

Update :

The main problem is in the download mode KG State : Prenormal,I must change to KG State : Checking

To change KG State, I found simple tutorial here :

Change date to manual > connect wifi/data > update from menu option until device is registered > check developer option again , if OEM Unlock enable, Ready to flash boot.img from odin.

I have done flashing boot.img patched by magisk, but it seems newer magisk doesnt work here, im using magisk delta got blank screen after flash boot.img

Update :

I have success rooting this phone.

Step By Step :

1. Download the AP_A260GDDSCAUJ2_CL15641782_QB44812985_REV00_user_low_ship_meta.tar.md5

2. Path the file with Magisk 2004 ( I have blank screen issue after patch with new magisk 2600 )

3. Make sure developer option OEM UNLOCK is enabled, or you can see in download mode KG State : Checking not KG State : Prenormal, to enable it : Change date to manual > connect wifi/data > update from menu option until device is registered > check developer option again.

4. Flash with odin in AP Section.

5. Reboot and setup the phone, goto step 3 again and make sure OEM UNLOCK is enabled.

6. Open magisk app and setup first use, this will reboot your phone once. ( If oem unlock is not shown in developer option, your phone will failed to boot )

7. Done

I have check in this xda forums no one have develop twrp or custom rom for this device also in other community platform ( Telegram Group, Reddit ).

I just stuck here with only root.

Anyway thanks for help me ZG098.
[Samsung Galaxy Core 2 Questions & Answers] ZG_DEV:
Are you sure that you unlocked your bootloader using fastboot or any tool ?

+ patch the whole AP file using magisk with noooooo extracting, only patch the AP file and then flash it with the other stock rom files, disable "auto-reboot" in odin, flash, boot into recovery and wipe data and that's all.
[Samsung Galaxy Core 2 Questions & Answers] alfanveykov:
I have update my thread, now Im able to flash boot.img but now after flash my phone got blank screen.

Waiting my phone battery empty ( because my power button doesnt work).

After this i try your suggestion to disable "auto-reboot" in odin, flash, boot into recovery and wipe data.
[Samsung Galaxy Core 2 Questions & Answers] ZG_DEV:
*blank*
[Samsung Galaxy Core 2 Questions & Answers] ZG_DEV:
You can force shutdown (escape from this blank screen) by pressing all buttons for 10 seconds, try booting into download mode by keys, or boot into bootloader by pressing vol.up + vol.down and release when connected to pc. A blue screen will show up with some options, press "download mode" to get into it
[Samsung Galaxy Core 2 Questions & Answers] alfanveykov:
Thankyou for your help. i have done rooting this phone.
[Samsung Galaxy Core 2 Questions & Answers] ZG_DEV:
Congrats 👏
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
OrangeFox Recovery Project

/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

OrangeFox Recovery for the Oneplus 6T

Download (for Android 12, 13 ROMs) (OOS11 Based)

Boot it with: fastboot boot OrangeFox-R11.1-Unofficial-fajita-V5.img

Then it can be flashed to the phone from within Orangefox with "Flash current Orangefox" option.
​

Take a look at this Post from TWRP in regards of Backup and Restore or here from the Orangefox wiki.

Spoiler content hidden.

ROM Flashing instructions:

(take a look at the Spoiler above if you need to switch OOS Firmware Base for your ROM

)

From OOS to custom ROM

- Boot to Orangefox

- Format data

- Switch slot

- Reboot to recovery

- sideload/flash ROM

- sideload/flash Orangefox.zip

- reboot to recovery

- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)

- Reboot to system

From custom to custom ROM

- Boot to Orangefox

- Format Data

- sideload/flash ROM

- sideload/flash Orangefox.zip

- Reboot to recovery

- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)

- Reboot to system

For Updating a custom ROM

- Boot to Orangefox

- sideload/flash ROM

- sideload/flash Orangefox.zip

- Reboot to recovery

- Flash Magisk (Magisk can be installed through Fox addons - Install Magisk as well)

- Reboot to system

Source Code: https://gitlab.com/OrangeFox

Device Tree: https://github.com/Wishmasterflo/ofox_fajita

Wiki/FAQ: https://wiki.orangefox.tech/en/guides

OrangeFox Version: R11.1

Version: V5

Last Updated: 10-Jul-2024

​

Changelog

R11.1 V5 10-Jul-2024

- Updated with latest Orangefox source changes

- some small adjustments to the device tree

Credits

* bigbiff for decryption

* Pranav Talmale for decryption

* CaptainThrowback for original tree

* mauronofrio for original tree

* BillGoss for Backup and Restore

* TWRP team

* OrangeFox team
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Screenshots

View attachment 6024153View attachment 6024154View attachment 6024155
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
reserved
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Extreme_Ninja2099:
Will this work on crDroid v9.10 on my 6T?

Update: I just flashed Ofox and it works! I had to reflash magisk after flash ofox and everything works fine!
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
6t A14, everytime I try to flash the zip it says error: this is for OnePlus 6t, you are using "fajita." It boots into it just fine, decrypts with pin, but if I flash from within using flash current ofox it flashes but won't boot, it just goes into fastboot. Flashed OOS 11 to both sides again manually and tried sideloading the zip again and same error
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Ohh yeah. I guess I need to update/adjust the device detection script.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
Thank you sir! I went to edit it myself but I must have edited it incorrectly somehow because it still detected fajita.

I thought adding OnePlus 6t and Oneplus6t would do the trick but perhaps I needed to remove the fajita line all together?
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Hmmm strange. I just checked my repo for Oneplus6T Orangefox and there I have in the script that it set the device name etc to Oneplus 6T so fajita should not be set there somewhere.

Strange that it still detects your device as fajita instead of Oneplus6T.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
Sorry, I had it backwards. It says this recovery is for fajita, you are using OnePlus 6t. It still doesn't make sense to me though.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
A while back I did the conversion to make the device into the McLaren version, so when I install OOS or even use MSM tool, the device boots with all McLaren features. You think that would have anything to do with it?
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
I tried going back to 13 to see if it was somehow related to the ROM, so I went ahead and booted your Orangefox which always works when I boot it, and then I did a full backup which worked great. I proceeded to sideload Elixir A13 which also worked fine, and immediately tried sideloading the Orangefox zip and got the error again.

I formatted and loaded the zip onto the device and flashed, and also tried from a usb stick. I removed the device check all together in the Anykernel file by zeroing it out, and it still happened. I then used the previous build v2 since it's a14 compatible and same thing happened. Twrp zips work fine, as well as PitchBlack recovery. I mention that only to help to try an narrow down the possibility of what it may be, assuming it's related to something that Ofox does during installation that neither TWRP or PBRP do.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
ahh ok yeah. Then I guess oos and the roms are checking for fajita instead of Oneplus6T. So I need to adjust theae settings in Orangefox.

Sent from Pixel 7a using ReLabs
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Yeedatoy:
Okay cool. Sorry for getting it backwards at first. Didn't mean to throw you off.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] koobie777:
im getting a lot of errors here lol it's been awhile but my partitions may be broken from messing around with the windows install idk i cant even wipe data and when i did flash it with the install this fox version i get crashdumps

View attachment 6058570View attachment 6058571
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Is that when you try to flash Orangefox? I guess flashing the Orangefox zip file does not work that way. You need to boot the Orangefox img file and then flash it with the option "Flash current Orangefox" from within Orangefox itself.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] koobie777:
Ok "Flash current Orangefox" worked but now when i try to flash a rom i gives error 7 kinstalldeviceopenerror. flashing stock seems to work though. lots of develpment has been going on here it seems since i left. im back because i bricked my oneplus 10 pro haha
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] koobie777:
forgot to mention i was trying to flash Project Elixir but it's also still not letting me format data with same error as above in second SS so i had to use TWRP-3.6.2_11-OP6xT.img to format data then boot back into orangefox and it allowed me to format data again but that is only a temp fix any other time i wanna format data i get the error. i was also able to flash SuperiorOS.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Will build and upload an Updated Orangefox recovery for the Oneplus 6T tomorrow.

I just created updated builds for OP8 series and OP11.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Updated Orangefox Recovery R11.1 V4 for Oneplus 6T :)

Changelog

R11.1 V4 23-May-2024

- Updated with latest Orangefox source changes

- Based on OOS11 Firmware

- Updated Magisk addon to Magisk V27.0
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] GheoLei:
I appreciate this, I quite like the Orengefox recovery so far :)
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
is this working as custom recovery for android 14 roms? I updated from LOS20 to LOS21 and TWRP does not work any longer, if TWRP is installed, the system won't boot
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
I have not tried it on Android 14, try if it works.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
doesn't work, u can "fastboot boot FOX.img" to make or recover a backup but u can not install it as permanent recovery, otherwise the system doesn't start, same as with TWRP :(
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Ahh ok got it.

Will check on that the next days.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
What exactly happens if you try to boot to system when Orangefox recovery is flashed? Does it come to the ROM boot logo and then just reboots again or does it just reboot to Orangefox recovery ?

Perhaps a Kernel issue. Let me do a new build later with updated Android 14 Kernel.

EDIT: OK I have done some adjustments to my device tree and will try later with a new build using a Android 14 Kernel. MY 6T is still using Android 13 crdroid. I have not used it so much, so time to update that as well.

Will do a new build and check on that later tonight.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
my op6t doesn't pass from bootloader screen when I have TWRP or OFOX flashed

thanks! looking forward to a functioning recovery.. it will be the only one for op6t on A14 as far as I know
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
OK I have done a new build V5 with a Android 14 custom Kernel now.

Have set that as pre-release now as my device is still on a Android 13 custom ROM at the moment.

Please check if it boots and works on Android 14, otherwise I will check on that again when I am at home again later today or tomorrow.

pre-V5 Changelog:

Updated with latest Orangefox source changes

Changed to custom Kernel (Android 14)

Download
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
fastboot boot recovery.img leaves me with a Qualcomm Crashdump on latest LOS21 OP6T
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Yes I had the same with the build with custom Kernel.

I just switched back to prebuilt Kernel and adjusted some things and uploaded a new build.

Its boots and works for me on crDroid Android 13.

Have not checked on Android 14 though.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Updated Orangefox Recovery R11.1 V5 for Oneplus 6T

Changelog

R11.1 V5 10-Jul-2024

- Updated with latest Orangefox source changes

- some small adjustments to the device tree

Download
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
I flashed it + Magisk and it did not work, same result as V4.. doesn't pass from bootloader

UPDATE: Now phone doesn't turn on at all
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Wishmasterflo:
Hmm ok. Not really sure why. Needs to check further on that tomorrow.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] t0ma5:
thanks for trying, looking forward to the final version, it would be the first custom recovery for op6 running A14
[Samsung Galaxy A32 4G] caddraaa:
so when i try to wipe on advanced wipe and wipe davlik,data,cache etc.. But when i wipe the system image it showes me an error (failed) and the rest worked but not the system image (trying to install lineage os 20 on it btw)

can someone know what it is about?
[Moto G40 / G60] castleofiron:
I want to build a recovery for g60, just modded version of stock, ik twrp and many other exist but i want to try.

It might not be possible but can one gain the verification from Motorola on other recovery.

So the can be flashed like a update, no need for unlocking bootloader, no format just easy upgrade.
[Moto G40 / G60] xdauser1620:
They won't sign your recovery with their keys because your recovery will be the security risk. If you want to run your own recovery unlock the bootloader.
[Redmi Note 10 Pro] fanix-uk:
Hi,

I want to install LineageOS v20 onto my Redmi Note 10 Pro. My model is: M2101K6G, which states that is is supported.

Info about sweet | LineageOS Wiki

wiki.lineageos.org

I am however slightly confused. When I go to Settings -> About Phone, the version of the ROM says the following:

MIUI Version

MIUI Global

14.0.1

But then under MIUI version it shows 14.0.1 (TKFZAAVC) - NOTE: ZA = South Africa.

According to the LineageOS 20 installation guide, I need to ensure that I have the correct firmware version loaded before flashing LineageOS ROM. https://wiki.lineageos.org/devices/sweet/install/variant1

For Global, it states that I need to flash Redmi Note 10 Pro Global V14.0.2.0.TKFMIXM, but as you can see, I currently have a "ZA" firmware (TKFZAAVC) installed and not a "MI" (TKFMIXM) firmware.

Would it be save to simply flash the required Global firmware version: Redmi Note 10 Pro Global - V14.0.2.0.TKFMIXM

as mentioned here? There is no mention of a TKFZAAVC firmware for South Africa, so I assume I need to install the Global? https://wiki.lineageos.org/devices/sweet/fw_update/variant1

According to the official XIAOMI Verification website I have the "International Version" (See attached image)

Thanks, appreciate the help.
[Redmi Note 10 Pro] Sheist!:
There is no SA download for firmware or MIUI ROM. It only offers the EA or Global regions. Yours says MIUI Global ROM.

It either means "don't risk it'" or get a 2nd opinion. https://xiaomifirmwareupdater.com/firmware/sweet/

Laptapper, do you know?
[Redmi Note 10 Pro] fanix-uk:
I think I found the answer here:

XiaomiWiki.github.io/wiki/About_custom_ROMs.md at master · XiaomiWiki/XiaomiWiki.github.io

Resources for Xiaomi devices, formerly hosted on r/Xiaomi - XiaomiWiki/XiaomiWiki.github.io

github.com

Looks like I have a "Reseller" rom. It makes sense, because when I did a "Factory Reset" after rebooting it automatically installed "popular" apps local to South Africa.

Based on the information in that wiki it seems that its safe to simply flash the official global. In fact, they recommend that you do. It would be good if someone can confirm that my conclusions here are correct.

Cheers.
[Redmi Note 10 Pro] Sheist!:
Interesting.

Were it me, I would say simply flash their firmware then proceed with the LineageOS installation. You won't brick your phone. At worst, you will be able to install the full Global MIUI and/or firmware later in recovery (or fastboot) and bypass the unoffiical SA ROM.

Good luck even finding a source for your SA Global ROM. :cowboy:
[Redmi Note 10 Pro] Ballbr8k3r:
I'm from SA, phones from vodacom, I did a global firmware update to 14.0.1 and installed sparkOS, then got rid of spark os " didnt like it" and reinstalled global Rom with no issues. just install a recovery like orangefox
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
I installed several firmware (OpenKirin on Android 9, LeaOS Android 11 + Syberia kernel) and I saw that on them the phone battery drains faster. I did 3 cycles of charge/discharge on both firmware.

Is there any custom on which the battery is consumed as on the stock firmware?

Or maybe I had to customize the firmware after installation.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
Try Havoc 2.9 (for Oreo)

Link

Yes, something by "CATUVA21" or "KingOfMezi" .
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
Thank you so much!

I will try to install Havoc.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
Maybe there are firmware based on Andoid 10-11 with a good autonomy?

Or only stock (or something based on stock) or havoc 2.9?

I just want to put something fresher than Oreo.

pardon my poor English

I'm using a translator
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
Unfortunately, not for devices runnig EMUI 8.0.

Havoc 2.9 is based on Pie :).

By the way, a higher version of android will not give you any benefit due to FW/HW limitation (except for the newer google patch).
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
Last question.

Does Havoc have gesture control on the system?

Or is it only on navbar?
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
It was three years ago, I don't remember the details.

But gestures are fixable with 3rd party apps.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
Maybe you can write a short instruction how to install it on the phone?

I have Huawei Mate 10 Lite RNE-L21 8.0.0.0.356

Doing a reset. I flash the system.img of the firmware via Fastboot. Then I do a reset via standard recovery and have a cyclic reboot in a circle.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
Yes, it's more complicated on RNE. If I remember correctly, I did it as follows (they were different ROMs, but I don't think it matters):

1. First of all flash flash service ROM for your regional variant (Cxxx) and EMUI 8 using dload method

2. Unlock the BL again, flash TWRP 3.2.1. by pretoriano80 (install it over eRecovery, it makes things easier :) )

Download

3. Decrypt data - flash in TWRP decrypt.zip

Link

4. Format data in TWRP, then wipe: dalvik, cache, data, system

5. Turn off.

Now you can flash Havoc in fastboot mode, and reboot the phone. Perform factory reset only if necessary (I'm not quite sure about this...)
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
I did it according to your instructions and now the phone hangs on the screen saver that the device is unlocked and will be turned on.

The phone hangs on the splash screen and does not boot up.

I guess I need to put the stock version down.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
As I said before, there are nuances when experimenting with the Mate 10 lite. Have a look at the thread on xda, maybe it will help you:

https://xdaforums.com/t/gsi-pie-r47...ab-arm-arm32binder64-updt-2019-09-14.3930030/
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
I managed to install havoc 2.9 after downgrading the stock firmware via dload from 346 to 333.

After flashing havoc according to your instructions and everything worked.

Thank you!

About the battery - time will tell how much better or worse than stock. As long as it's not worse.
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] maxim531010:
Rolling back to stock due to poor autonomy on havoc 2.9
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) Questions] -Alf-:
Probably missing deep sleep... It’s a pity.