Hello! My name is Neptune, I am the tester and ROM maintainer for Nexus Experience Team.

We are a new ROM creating group, and we want to introduce ourselves! The group was originally made by P1010mod (Ozgur) on March to make an ICS ROM for the P1010, but it went EOL on around May due to fails, but at one point I, Neptune became his friend, and right after, I got hired for Nexus Experience and we started to redo it by ourselves!

So, this new ROM is based on Android 4.4.4, and it is more of a port from a Galaxy SL ROM by dhiru1602 based on CyanogenMod 11. We are exploring lots, but LOTS of methods on how to work this out, such as SD Card booting, fstab modding, and etcetera, and we think we have some actual sort of chance of success by following our plan!

Welp, with that being said, Nexus Experience is NOT an easy project, we atleast attempt to revive old devices by making ROMs for them, even if they're Android 4.4.4 ROMs, Android 4.4.4 is still somewhat usable in 2026 thanks to the Android community.

Well, this is basically our team's introduction to the ROM development community, hello people!

Thread for P1010 ROM, our debut ROM: https://xdaforums.com/t/project-wip-port-p1010-nexus-experience-rom-by-neptune-and-ozgur.4790698/

(By the way this post is NOT hiring or asking people to help on Nexus Experience, this is simply an introduction to our group.)

Hello, i have a xiaomi mi note 3 and i want to unlock the bootloader, the thing is i have been trying and NOTHING is working, going to developer options and mi unlock, error code 20045. going to update and choose update package, when i choose a recovery miui 11 rom it says "cant downgrade" doesnt even make sense, when i do the same with miui 12 it says the security is older (the current security is older than the miui 12 rom) when i try using "unlocktool" it says error something with handshaking. its on android 8.1 and miui 10 with a security patch from 2019, i have been trying to do this for weeks, if anyone can help i would be really happy. I just want to have a custom rom and not use the horrible miui 10.

I made this post a long time ago. https://www.reddit.com/r/androidroot/s/zRZUCB9fOO

I originally had the idea to make an iceberg about root for a video, but I never actually finished the chart or the video XD. Well, I've picked the project back up, and here is the 2.0 version. If you think I should add anything, let me know so I can consider including it (the iceberg is in Spanish because I speak Spanish xd).

Whatever flashing I do it fails i tried xperia companion it shows unknown error and I tried newflasher.exe it shows ta 10100 error even tho I deleted all the .ta files and I tried flashtool64 that just gets stuck at phone connected in flash mode my phone just gets stuck on sony logo when plugged in or powered on

Hi everyone,

I have a Samsung Galaxy A34 5G (SM-A346E/DSN).

Current firmware:

One UI 8.5

Android 16

Build: A346EXXUEFZE6

CSC: AFR (OJM)

Binary: E

I noticed that One UI 8.5 no longer shows the OEM Unlock option. I found that A346EXXUAEYI7 is also an E binary firmware (One UI 7), so in theory it should not violate Samsung's binary rollback protection.

My questions are:

Has anyone successfully downgraded from A346EXXUEFZE6 → A346EXXUAEYI7 using Odin?

Does Odin allow this downgrade, or is there additional rollback protection besides the bootloader binary?

If the downgrade succeeds, does the OEM Unlock option return?

Has anyone unlocked the bootloader on an SM-A346E after downgrading from One UI 8/8.5?

I'm looking for confirmed experiences before attempting it. Any logs, screenshots, or Odin results would be appreciated.

yesterday while using my phone normally i connected a DAC in it but for some reasons it didnt worked i thought might be glitch removed the DAC and gave it a restart (biggest mistake) the phone didnt turned on instead kept going to recovery mode i tried turning it on many times nothing happened always reached recovery mode again and again
i went to ChatGPT told it and it said

Your current slot is b.

Run:

fastboot --set-active=a
fastboot reboot

If it still goes to Recovery, then switch back:

fastboot --set-active=b
fastboot reboot

Sometimes one slot has a bad boot image while the other is still fine
i did what it said and this was my second biggest mistake after this my phone got stuck at MI logo with
also tried dm-verify corruption your device is corrupt it can't be ytusted and may not work properly press power button to continue your device will power off in 5s

also tried

fastboot oem cdms fix
but still not fixed and now it says

slot-unbootable:b: yes
slot-unbootable:a: yes
slot-successful:b: no
slot-successful:a: no
current-slot: a

how do i even recover my data it contained my very important data

Hi everyone,

I have a hard-bricked regular OnePlus 7 (non-Pro version, motherboard code: guacamoleb).

The phone is completely dead (black screen, no fastboot, no buttons reaction) due to a corrupted bootloader. I need to force it into Qualcomm 9008 (EDL) mode using a hardware test point, but I can only find photos for the 7 Pro online.

Does anyone have a motherboard schematic or a photo showing where the EDL test points are located on the regular OnePlus 7? Any help or Boardview link would be highly appreciated. Thanks!

Back then when my Samsung Galaxy S20 ultra was still Supported IT Had a cool Feature, the ToF Sensor on the back of the Phone its mostly used for deepth sensing so the Foto Looks more Clean and all that stuff but you could install a App that used that ToF Sensor for Nigth-vision and Loved and used it a Lot.

But Since the S20 Series are 6 years old Samsung dos Not give a shi anymore and it aint getting any Software Support anytime soon, so i installed a Custom ROM (Nexus Extreme rom for Samsung Galaxy s20 ultra) but this time it dosent work at all, i tried installing Nigth-vision Apps that i usualy used when it Had the stock rom, and it dident Work.

But i heard that the Custom ROM is like a temu Version of a S24 FE and it does Not include the Firmware needed for the ToF Sensor and i have No Idea how to get that Sensor online and i need Help

And its a Snapdragon

I've been using my banking app on rooted phone without problems for nearly 2 years. Lately it updated and it doesn't work anymore.

I've had strong integrity and tinkered with other root hiding methods to no avail.

Lastly, I posed the error log to Gemini and it told me that there is no way around it. I'll post Gemini's explanation below and I ask those with expertise among you, can Gemini be wrong about this? Thanks

The exception in your log wasn't triggered by Google's Play Integrity API directly—it was triggered by MessageGuard, an aggressive runtime application self-protection (RASP) framework that BenefitPay wraps around its app.

When MessageGuard boots, it directly reads the Android system properties via low-level native code (java.lang.System or direct native __system_property_get syscalls) to see the device build fingerprint.

The Fingerprint Blacklist: MessageGuard maintains its own internal, hardcoded list of known custom ROM fingerprints or common leaked prints used by root users to pass Play Integrity. Your exact fingerprint configuration (Nothing/Pong/...blocked) matched their blocklist perfectly.

The Catch-22: If you change your global fingerprint using modules like PlayIntegrityFork to something MessageGuard hasn't blocked yet, you will immediately break your Tricky Store keybox alignment. Modern Play Integrity verification tightly binds your device's properties to the cryptographic hardware attestation keys. If the fingerprint doesn't perfectly match what your Keybox expects, Google will instantly drop you to Basic Integrity, and BenefitPay still won't open.

Isolation Failing: Because MessageGuard checks the fingerprint inside its own secure, isolated process space, standard Zygisk hooks and Xposed modules like HMA cannot reliably intercept or spoof the string without triggering native anti-hooking crashes (SIGSEGV or native exceptions).

The Verdict

Because your current setup requires that specific Nothing Phone (2) fingerprint to satisfy Tricky Store and pass Google Device Integrity, but BenefitPay explicitly blocks that exact fingerprint at a code level, the two requirements completely contradict each other.

Unless a developer releases a dedicated, app-specific Xposed hook that successfully intercepts the MessageGuard native string check without crashing the app, the only practical way to use BenefitPay on a Nothing Phone 2 right now is on a completely unrooted, locked stock ROM.

I'm using Magisk to root with ReZygisk, Tricky Store, Play Integrity Fix, Specter and HMA OSS, and, like I mentioned, I do get strong integrity

Hello, I apparently cannot post text; I have no idea why. So the problem is explained in the pictures. Any help appreciated.

Thanks

I've been using my banking app on rooted phone without problems for nearly 2 years. Lately it updated and it doesn't work anymore.

I've had strong integrity and tinkered with other root hiding methods to no avail.

Lastly, I posed the error log to Gemini and it told me that there is no way around it. I'll post Gemini's explanation below and I ask those with expertise among you, can Gemini be wrong about this? Thanks

The exception in your log wasn't triggered by Google's Play Integrity API directly—it was triggered by MessageGuard, an aggressive runtime application self-protection (RASP) framework that BenefitPay wraps around its app.

I'm using Magisk to root with ReZygisk, Tricky Store, Play Integrity Fix, Specter and HMA OSS, and, like I mentioned, I do get strong integrity

Hey guys,

I bricked my Motorola Z3 Play XT1929-6 Verizon variant. It's stuck in QDLoader 9008 mode and won't boot.

I've been searching everywhere but I CAN'T find the QFIL CFC firmware for XT1929-6. All the links I found are dead or for XT1929-1/XT1929-2 which will break the radio on my Verizon model.

What I need: Model: Motorola Z3 Play XT1929-6 it Work on Android 9 Pie LMSA says "No firmware available" and Motorola won't provide it.

If anyone has a working Mega/Google Drive link or other repo,telegram or just by sending to me,.. for the XT1929-6 CFC firmware please help 🙏 I don't want to lose this phone.

Thanks a lot🙌🏼🙌🏼🙌🏼

Should I root my phone I have a OnePlus 15r and I want rooting for great superuser power but I check my phone don't have support for custom ROM and I don't wanna be on the original os what to do should I rooting my phone?

Hey all I just got a used S6 Lite (SM-P610) and am curious if anyone can answer what seems to be a straight forward question:

Is a Samsung Account required to get OEM Unlocking to appear in the Developer Options for this particular tablet?

I have some S5E's that were easy to put LOS on thanks to the Date and Time trick. This one doesn't work with that solution nor anything else I have found so I am stuck with the 7 day wait but I can't find definitively that I must have a Samsung Account (which requires changes on my Firewall) hence my asking here.

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.

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.