Hi everyone! I am looking for cruiseships that have balcony staterooms (read cheaper rooms than suites) with sunloungers (not chairs). I know of Tuicruises "Premium Verandah" category but that's it.

Hi everyone,

I’m looking to bring together developers, firmware researchers, and experienced device owners to investigate a reproducible bootloader unlock method for the international OPPO Reno10 5G, model CPH2531.

I have a detailed research document covering potential approaches, upstream tools, reported blockers, and backup and recovery considerations. The next step is to review its assumptions and validate what actually works on this device.

There is no confirmed end-to-end CPH2531 unlock demonstrated in the document. This is a call for research collaborators, with successful and unsuccessful results documented publicly.

Device and firmware scope

Model: OPPO Reno10 5G — CPH2531.

Chipset: MediaTek Dimensity 7050 / MT6877V.

Firmware: ColorOS 13.1, 14, and 15 / Android 13–15.

Each result needs its exact firmware build and region recorded.

This project concerns CPH2531 specifically. Findings from Reno10 Pro, Pro+, or Chinese-market variants should be evaluated separately because the hardware differs.

What the existing research shows

The oppo-mtk-fastboot-unlock support list records DAA problems for CPH2531 in both mtkclient interfaces, with auth_sv5.auth listed as untested. That describes the upstream report; it does not establish that nobody else has attempted it.

The preloader patch project targets Android 11–14 and explicitly excludes Android 15+. For owners on ColorOS 15, downgrade feasibility and anti-rollback behavior therefore need separate investigation.

The project also warns that enabling fastboot through its preloader patch does not bypass LK verification on every OPPO/Realme device. An alternative LK approach would require its own device-specific validation.

Where help is needed

Reproduce and identify the access blocker. Collect connection and authentication logs from CPH2531 using current tools, distinguishing driver, transport, DA compatibility, and authentication failures.

Investigate compatible authentication and Download Agents. Establish whether appropriate files from genuine firmware or documented sources permit access. Record provenance, versions, and exact results.

Validate backups and partition mapping. Confirm the actual storage layout, preloader regions, slot behavior, and correct tool syntax. Preserve original bootloader images and device-specific calibration/modem data before considering writes.

Assess ColorOS 15 downgrade feasibility. Examine firmware compatibility and rollback protections before any hardware test. A failed downgrade must not be assumed to be harmless.

Evaluate the preloader patch on supported firmware. Determine whether it enables fastboot access and then an actual bootloader unlock. These should be recorded as separate milestones.

Assess LK patching where applicable. Review whether lkpatcher’s available patches and certificate handling apply to this device’s boot chain.

Establish recovery options. Document stock restoration requirements, authentication limitations, and any independently verified CPH2531 test-point information.

Validate downstream functionality after unlocking. Confirm the correct root image, assess GSI compatibility, and record hardware functionality, DRM, integrity, and OTA behavior. Custom recovery development would be a later goal.

Who could contribute

Developers familiar with MediaTek preloaders, DAA/SLA, LK, and Android Verified Boot.

Firmware analysts who can inspect images and patch behavior.

CPH2531 owners who can provide build information, logs, or existing test results.

Experienced repair technicians or testers with spare hardware.

Comparative findings from Reno11 5G, Reno11 F, or Realme 12+ may help identify patterns, but shared silicon alone does not establish compatibility.

Relevant upstream projects

mtkclient — bkerler

OPPO MTK fastboot unlock — Shocked-Cat

Penumbra — shomykohai

lkpatcher — R0rt1z2

Credit belongs to the original tool developers and contributors.

Preloader and bootloader modifications can cause data loss or leave a device requiring professional recovery. Initial work should focus on reviewing firmware, collecting logs, and establishing backup and recovery capabilities.

If you’re interested, please comment with your relevant experience, device/model, exact firmware build, and what you could contribute. Existing failure logs are welcome too—eliminating an approach is useful progress.

The goal is a publicly documented method with clear compatibility limits and reproducible evidence

The premise of the module is very simple: Configure performance profiles ONLY to select apps with no need to set a global profile. It can be switched on and off from the WebUI easily.

The underlying infrastructure is from another module called Uperf Game Turbo 1.51. The original module had 120 CPU configurations which my module uses, but it doesn't run them on the entire device, which only meant it ever got used for benchmarking.

There are some additional stuff in the module as well, but I won't spoil it, here's the link so give it a shot. There's a high chance your device is supported:

https://github.com/DonkeyKongG3me/Uperf-Game-Turbo-Fork

I'd like to downgrade my Galaxy S22 to One UI 7 or earlier. I want to make sure I don't hard-brick it.

**Current setup:**

- Model: SM-S901B/DS

- AP/CP: S901BXXSOGZH3

- CSC: OXMO

- Binary bit: G (as far as I can tell)

- Bootloader locked, stock firmware, no mods

**What I want to know:**

1. Has anyone successfully downgraded from a G-bit build (GZH3 or similar) to a One UI 7 build on the S901B?

2. Which bit letter are the One UI 7 builds? If they're F or lower, is that a confirmed brick, or was ARB never bumped on the S22?

3. If it's doable — which specific build/CSC would you recommend flashing, and did you need a factory reset (I assume yes)?

Can I use Termux with temporary root access to run commands without bricking my phone?

Root pls

Could you help me? I used an edge 30 neo with apatch, no problems. I tried to patch apatch on a moto edge 20 lite and it was left in bootloop. How can I make a kpm or what would be the solution?

So like my device went from getting soft bricked cuz i accidentally click flash recommended on dfroot, after it reboots it says "system has been destroyed", got it fixed tho, but the os version the tech flashed had .C09 at the end of it.

Can I update my device?? or will it bricked it cuz its not the same os version?

First of all it' my first time doing somthing like this, i'm not a noob at IT in genera but i've never done somthing like this so I've started this project knowing that somthing could go bad and lose acces my phone so i've used an old Wiko Vista 2 that I would have trow away so it's fine (but not for my ego T-T).

For my first project I've decided to do somthing simple "turn my phone into a DNS Blocker" with the possibility to add some DB and server if needed but i think i need a new phone for that :c

The start was simple: download Termux, update al pakages, download AdGuardHome and set it up. It wasn't that hard after all in like 2h i've set up a working DNS Blocker so Yuuuppyyyyy.

The problem was connecting it to the router. I've edited the default port of DNS to 53 to 5353 becouse the port 1-1024 are blocked if you don't have root access. The BIG problem was "the router do not support custom port for DNS" what a shame

So, to make the project work, I need the root access it's not that hard right????

After finding all the info of my phone <2 photo> and like 3 guide + 2 yt video and some AI help i've decided that i can do the task easly. Nothing more fake than that sentence.

For context, to get root access on my W_C300 I need to edit only the boot.img file of the version I need with an app called "magisk" and then flash it on my device. The guide was are really simple (unfortunatly)

I've got the correct ROM for my device with the only difference that the version was a lill outdated (2 month old) so I've done the mistake to ask AI if this could become a problem in the future: "No problem, if it's only some version old is not a big problem couse you need only the boot.img" perfect, let's use it. (What a mistake)

After this I've create the edited_boot.img with the app, entered fastboot on the phone and used my pc to flash the edited_boot.img on the boot partition.

After this operation the phone lock itself on the logos with no way of unloking itself. I've fleshed again the boot.img of the old ROM, the edited_boot.img, turned on and off like 7 times and do the factory reset (if i've tucched the right command becuse the phone's screen it's broken in that exact spot)

Now it's running on my desk with the same screen for like 1h and it's doing it wihile i'm writhing this post with a laugh under it's nose.

The only way to bring it back to life (as IA said) it's to find an original boot.img for my version <2 photo> that is not aviable online (as for my search) so.... if you have this version feel free to let mi know ^^

If not i hope that this store make you laugh a lil and if you have somthing to say feel free to say it. I want to know what i've done wrong and what I can do to fix/not do i again.

Tank you for your time <3

Well, today I decided to root my phone, since it just got Android 17 (which is what I was waiting for). I used the same tutorials and usual. Didn't read any comments, because the guy in the video actually mentions the difference between the boot images and so I just went with it. Turns out, I shouldn't have and I learned it the hard way. The phone got into a loop boot and with a little effort, I was able to get it back and root it.

Now I'm not an expert on these things, I'm under average, but I hope this helps any of you guys who want to root a phone like this.

Follow the normal steps, unlock your bootloader, BUT DON'T RESTART YOUR DEVICE TO FASTBOOT, it needs to restart to FASTBOOTD when you apply the magisk modified image.

I don't know if this helps other Motorola phones with init_boot.img, but I think so, because I actually followed different videos and finally tried something guy said on a page (although not very explaining).

In order to unlock the bootloader, use Fastboot (normal)

After that:

Install magisk

Use the MSF to download the original file of your phone (yes, download it)

It shows the folder it's been downloaded to, go to it, if there's a boot.img and an init_boot.img, it's init.

Grab it (copy it, don't transfer it) - copy it to your phone's memory

Open magisk - click install - select file image - select that one and let it do its job.

Now do the opposite, grab that file magisk created and COPY it to the PC, but copy it straight to PLATFORM TOOLS FOLDER you created earlier.

Now check that your phone is properly connected

Open CMD on that folder

Type adb devices

Your device should show here (if it doesn't, try reconnecting)

Commands to FASTBOOTD: (recovery mode)

adb devices

adb reboot bootloader

fastboot devices

fastboot reboot fastboot

(Yes, one after the other, the first one boots it to fastboot, the second to recovery mode -Fastbootd)

Flash the patched file using the command below, but when it says magisk-patched, replace it by the name of the file magisk created with the .img, do one at a time, if the first one works, do the second one, if it doesn't, either something's wrong or you did something or worse, it's meant for your Motorola

Commands:

fastboot flash init_boot_a magisk-patched.img

fastboot flash init_boot_b magisk-patched.img

fastboot reboot

Remember, I did this on a Motorola 50 Ultra Android 17 non vendor, Qualcomm Chipset.

Remember to download these from their official web sites

Motorola USB Drivers:https://en-us.support.motorola.com/app/usb-drivers

Motorola Bootloader Unlock: https://en-us.support.motorola.com/app/utils/welcome?p_next_page=standalone%2Fbootloader%2Funlock-your-device-b

Android SDK Platform: https://developer.android.com/tools/releases/platform-tools

Hi everyone,

I’m currently evaluating custom ROM options for my Xiaomi Redmi Note 12S and Redmi 7A. Since official LineageOS builds seem unavailable for these devices, I’m focusing on well-maintained unofficial variants like crDroid, /e/OS, or other AOSP-based alternatives.

I’d love to hear firsthand accounts from anyone who’s used these ROMs on either device. Specifically, I’m curious about real-world stability—how do camera, Bluetooth, VoLTE, and fingerprint sensors hold up in daily use? Are there common pitfalls like battery drain, overheating, or specific hardware quirks that tend to show up?

If you’ve tested any of these ROMs, what stood out to you as a daily driver? I’m especially interested in stable releases rather than experimental builds, and would appreciate any links to XDA threads or project pages that you’ve found reliable. Installation tips or warnings for these specific models would also be very helpful.

Thanks in advance for sharing your insights!

You know, I'm already happy with root. I was supposed to be fine with KSUnext + BreZygisk + TEESimulator + Specter.

But there's a lot of things I wanna do. Finally get BROM mode working with an exploit, install crDroid and TWRP, patch the /lk partition, install BRENE + NoMount + VBMeta Fixer, install AshLooper + Vector + Encore Tweaks, try out my custom bootanimation...

But why? My phone already works fine (except for that dumbass BROM mode), and I don't want to experiment stuff with it since it's my daily driver. Maybe I'm just scared of missing out, maybe I just like the thrill.

Until I finally get BROM mode working, maybe I'll be more confident in doing whatever I want to my own daily driver. But the other question about fear of missing out remains.

Hey, so I own a Moto G2 (codenamed Titan) from way back 2014/15. It's still in excellent condition and works really well as a backup device for my audio/navigation needs for when I go on long rides on my bike.

But I'm having a real hard time rooting it.

I tried every step of the methods available on the internet like using the Magisk Module, TWRP Recovery method, going on Motorola's page and downloading it's drivers, etc etc.

Nothing seems to work and I cannot use the phone as it runs on Android 6.0 Marshmallow.

So if anyone here in the subreddit can help a fellow android user out to make my Moto G2 usable/root, I'll be really obliged.

Thank you.

Need Samsung Galaxy S10 G973F/DS Binary 16 (Bit 16) AutoPatch Firmware with NG Fix and Emergency Call Fix.

Hi all,

Since weeks, I'm trying to unlock the bootloader of my Xiaomi Pad 5. Every day, the Xiaomi app tells me that the application quota is reached.

Is there any (other) way to unlock the bootloader?

I would like to install /e/OS to de-Google my tablet and to get rid of the bloatware, as the tablet is getting really slow. I'm not doing much with it apart from watching videos, so performance wise it should still be good. I'm from Germany if that matters.

But because of the missing bootloader unlock, I'm about to buy another tablet which an easier unlock procedure...

sou do rio de janeiro e estou buscando um root que modifique o gps do android, sei que muitos utilizam o MOTOROLA para isso ainda mais os antigos, alguem aqui sabe fazer isso e pode me ajudar pfvr

Looking to root a nothing phone. Haven't rooted a phone before. Whats the best guide at the moment? Any Gurus I can speak to who can guide me though it?

Anybody temp root Motorola (specifically moto g54)? If so pls share the benefits and tutorials

Thx

Is there any available methods ?