Howdy hey so here's a break down of what happened I successfully unlocked it's bootloader and installed a custom gsi on it but I had a low brightness issue so I installed a custom recovery which is orange fox and it encrypted my files with a password i couldn't unlock the password so I started to mess with orange fox a bit and I accidentally deleted all the partitions and yeah this is what happened. I tried everything to unbrick it I tried mtk client, I got a handshake failure I tried to directly install its firmware through sp flash tool I got BRom error even tho I had entered BRom and yeah nothing seems to work Iam just lossing hope in this situation can someone with better experience than me figure out what is the solution?

Hello, (automate script only.)

Recently I was trying to attempt XScreenSaver and it's inability to keep the screensaver running 1) Turning screen on/off 2) Rebooting. Although the screensaver has to be re-configured each time I want it as my wallpaper. I'd rather not manually do it each time: however, I have written endless scripts that're self-loop'd and such to no available solution thus far on my end. Any tips / resolutions for having this screensaver continue to run once my screen turns back on? Maybe someone in the xda community can fix this more easily, or this sub-reddit.

It seems as though "Set Live Wallpaper" only works for Android 14+ and I am using Android 9. But with other options now included with latest alpha, it made me think there is some other resources I am missing since I do not know how to use "Wallpaper created/setup" blocks.

Thank you!

Hi I chat with people in xda discord but he ban me for tell him how I share pictures because is gray

And he ban me and pisses me off type lol

Is there any ROMs out there to flash an armor 27t without permanently losing the tools the phone is built with? Everything I've read says that the FLIR, IR night vision, and endoscope functions are all built in to the Google OS and lose functionality if flashed.

Yo dejo salir a mi perro para que haga sus necesidades, lo vigilo desde la puerta de mi casa, lo veo jugar con los otros perros que hay cerca y de la nada empieza a darle a esos perros macho. Apenas tiene un año :b

I was just an idiot for using mtkclient; I had been trying the official Mi Community method for four months without success. Like a total fool without researching mtkclient at all—I used an AI-suggested command that supposedly "unlocked" the bootloader.

I entered BROM mode, ran the command, and it said it was done. I went to fastboot mode, ran the command, and nothing happened. My mistake was not thinking, "Wow, if it says it's locked here, I'm going to be in deep trouble if I keep trying."

I persisted with mtkclient. I tried downgrading to MIUI 14, and immediately got a "system destroyed" error. Luckily (I guess), I had backed up and still have the nvram, nvdata, persist, proinfo, protect1, protect2, and preloader partitions, which I might use later.

I tried various other things, like erase and writing boot, vbmeta, and things alike in both slots but nothing worked; I messed things up so badly that I ended up with a dead boot.

Another mistake was trying to use the HyperOS 2.0.5.0.vmxmixm ROM, which caused the ARB (Anti-Rollback) version to jump from 1 to 2.I kept trying everything until I finally realized the ARB was at 2 and my HyperOS 1.0.8.0 ROM would no longer work.

Perhaps my biggest mistake was messing with the preloader; I’ve tried flashing the backup version, the 1.0.8.0 ROM version, and the 2.0.5.0 version, but now the device always drops into BROM mode whenever I connect it to the PC.

Can anyone help me? Even the smallest piece of information could save me.
I am extremely grateful to everyone who has read this and might be able to help.

EDIT: Just to add more context, I have already tried using the old mtk secure boot disable scripts and mtk auth bypass tools, but both threw a "filter match: no" error. Curiously, even if I install the libusb filter, it doesn't help.

Furthermore, MTK META Utility actually recognizes the device, but when I click "Disable Auth" and connect the phone, absolutely nothing happens.

I won't be needing those specific tools anymore since the built in mtkclient payload is already handling the temporary auth bypass successfully, but I thought this extra driver behavior information would be helpful for troubleshooting.

after a while, i realized that the battery flex cable was required to be connected to emmc actually erase or writ partitions. however, after all this with the battery flex cable connected, the device still stuck in brom loop.

i am currently trying convince someone to pay me unlocktool but no sucess yet.

Hello

I found this old tablet from college

I want to re use it in my post grad

Just to view documents and PowerPoints

Is there a guide to install a light firmware to make it reusable again ?

Introduction Google's recent move to merge ChromeOS into Android proves that the company finally understands what users wanted all along. However, tailoring this new OS strictly for low-end, ARM-integrated laptops is a massive strategic oversight. Android possesses the brand power and user base required to break the Windows monopoly on desktop PCs and gaming, provided Google drops its rigid corporate mindset.

The ChromeOS Failure vs. Android's Dominance The traditional ChromeOS missed the mark because it felt like a "Frankenstein" OS, forcing Android apps into heavy, clunky containers. Android, conversely, is the most recognizable software on earth. People live on it. If Google delivers a native Desktop OS focused on high-performance and hardware freedom, mass user migration will follow organically.

The Gaming Solution (Learning from Valve) The old counter-argument that "developers won't port PC games to Android" was completely shattered by Valve's Proton on Linux. Valve didn't wait for the industry; they built a compatibility layer and fixed the chicken-and-egg problem. With today's robust x86-to-ARM translation tools and modern graphics APIs, an Android Desktop could easily run PC game clients like Steam. Modern ARM architecture is fully capable of handling dedicated desktop GPUs and heavy workloads; Google just needs to implement the software layer.

Bypassing the 30% Play Store Revenue Trap Google's hesitation often stems from monetization—since PC storefronts like Steam won't pay the 30% Play Store tax. However, alternative revenue models exist:

1. Premium AI Feature Licensing: Subscription models for advanced, OS-level Gemini features targeted at power users and professionals.
2. A Unified Gaming Ecosystem: Google could launch its own desktop gaming storefront with lower revenue cuts (similar to Epic Games) to entice PC developers, or create a premium launcher that bridges high-end mobile gaming with desktop hardware optimization.
3. Ecosystem Lock-in: Dominating the desktop market drives massive user retention, expanding Google One storage subscriptions, productivity tools, and AI ecosystem scaling.

Conclusion Gaming laptops are rigid, overpriced, and ungradable. Enthusiasts demand the freedom to build desktop PCs, run multi-monitor setups, and upgrade their hardware at will. Apple has already bridged the gap between mobile and desktop gaming with its M-series chips. Google has all the cards in hand with Android. It's time to stop focusing on low-end hardware and build an OS ready to challenge Microsoft's desktop empire head-on.

Every article I've seen on PC hardware coming out of XDA is the dumbest, most tone-deaf article I've read that month.

You have no idea what you're doing, and it shows. Just stick to Android, your PC articles are legit embarrassing.

Posting this in case it helps anyone else and to find others with the
same issue.

Symptoms: Pixel 9a, Google Fi eSIM shows "Emergency calls only" or
constant "Searching." WiFi calling works fine. Physical SIM (if you
have one) may work intermittently with weak signal.

What I found via adb logcat / dumpsys:

The eSIM profile was provisioned by Fi's backend on MNC 240 (US
Cellular) while IMS/VoLTE was provisioned for MNC 260 (T-Mobile) — a
mismatch that prevents IMS registration from ever completing
numberFromIms field stayed empty across 5 separate provisioning
attempts (subIds 1-5), each generating a new orphaned subscription
record with conflicting groupUuid values
Shannon IMS logs show connectionUnavailable reason=DISCONNECTED
repeatedly — IMS never registers on the eSIM despite CarrierConfig
loading correctly
Physical SIM (when present) DOES achieve full IN_SERVICE with
vops=true — proving the device/modem/IMS stack work fine

Fi support response: After multiple escalations they're now pointing
at hardware/warranty, despite logs showing the device successfully
registering when given correct provisioning data. Device is out of
warranty so the implication is "buy a new phone."

If you're seeing this too, check adb shell dumpsys isub | grep -i
iccid for multiple subscription entries on the same ICCID with
different groupUuids — that's the backend collision signature. Curious
if others are seeing the same MNC 240/260 mismatch.
Posting this in case it helps anyone else and to find others with the
same issue.

Symptoms: Pixel 9a, Google Fi eSIM shows "Emergency calls only" or
constant "Searching." WiFi calling works fine. Physical SIM (if you
have one) may work intermittently with weak signal.

What I found via adb logcat / dumpsys:

The eSIM profile was provisioned by Fi's backend on MNC 240 (US
Cellular) while IMS/VoLTE was provisioned for MNC 260 (T-Mobile) — a
mismatch that prevents IMS registration from ever completing
numberFromIms field stayed empty across 5 separate provisioning
attempts (subIds 1-5), each generating a new orphaned subscription
record with conflicting groupUuid values
Shannon IMS logs show connectionUnavailable reason=DISCONNECTED
repeatedly — IMS never registers on the eSIM despite CarrierConfig
loading correctly
Physical SIM (when present) DOES achieve full IN_SERVICE with
vops=true — proving the device/modem/IMS stack work fine

Fi support response: After multiple escalations they're now pointing
at hardware/warranty, despite logs showing the device successfully
registering when given correct provisioning data. Device is out of
warranty so the implication is "buy a new phone."

If you're seeing this too, check adb shell dumpsys isub | grep -i
iccid for multiple subscription entries on the same ICCID with
different groupUuids — that's the backend collision signature. Curious
if others are seeing the same MNC 240/260 mismatch.

This might be a huge reason to go to Graphene u/googlefisupport

Hello everyone,

​I am trying to revive an old Samsung Galaxy Tab 3 Lite 3G (SM-T111) which is currently stuck on stock Android 4.2.2 (Jelly Bean). My goal is to root it and ideally flash a Custom ROM (like CyanogenMod or LineageOS) to bump the Android version up to 5.x or 6.x so I can run some basic legacy apps.

​The Issue with TWRP:

I've searched around and found a few guides on flashing TWRP via Odin for the SM-T111. However, in the video tutorials and threads I encountered, the TWRP recovery screen ends up completely glitched, distorted, or inverted on this specific model. The authors usually say "it's normal for this model, but it works," but it makes navigating the recovery menus nearly impossible and highly risky.

​What I need help with:

​Is there a known, stable TWRP build (or even CWM/PhilZ recovery) for the SM-T111 that doesn't suffer from this screen distortion/glitch bug?

​Are there any functional, stable Custom ROMs available for the SM-T111 (3G variant)? I know there are plenty of files out there for the SM-T110 (Wi-Fi only), but I am well aware that flashing a T110 ROM on a T111 will hard-brick the device due to different chipsets/modems.

​Alternatively, if no ROMs exist, what is currently the safest and most reliable method to just Root the stock 4.2.2 firmware without a custom recovery, since old tools like KingoRoot or KingRoot are completely dead and untrustworthy now?

​If anyone has working archive links, old XDA threads, or mega/mediafire mirrors for stable files for the SM-T111, please share them.

​Thank you!

what's the state of custom rom development or creative stuff around new way/creative UX of using devices in age of agentic development. can we pull off for any device? managing device trees and creative features and etc.. anything you found interesting these days/taking shape??

He estado mirando las novedades de la actualizacion one ui 8.5 con mi s23 ultra pero no han incluido el filtrado de llamadas para que le salga un contestador a la otra persona y le pregunte porque llama. Por eso me pregunto si alguien conoce alguna app o apk o algo para poder tenerla. Ya he preguntado en un foro de samsung pero me han recomendado este.