yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 13C (4G) / Poco C65] mvikrant97:
How to Unlock Bootloader on Redmi 13C - MIUI​

View attachment 6108965

Downloads

Android ADB and Fastboot Drivers	MI Unlock Tool 7.6.727.43	Reserved	Reserved

Prerequisites​

Backup Your Data: Unlocking the bootloader will erase all the data on your device. Ensure you back up important data.

Enable Developer Options:

Go to Settings > About phone.

Tap on MIUI version 7 times until you see the message "You are now a developer".

Enable OEM Unlocking and USB Debugging:

Go to Settings > Additional settings > Developer options.

Enable OEM unlocking and USB debugging.

MI Account:

Please use ensure that you use a working SIM card in order to sign in, into your MI account.

Then ensure your device is connected to a MI account.

Stable Internet Connection: Make sure your PC and device have a stable internet connection throughout the process.

Steps to Unlock the Bootloader​

Download the MI Unlock Tool:

Visit the official MI Unlock Tool download page: MI Unlock Tool.

Download and extract the tool on your PC.

Log into MI Account on Unlock Tool:

Open the MI Unlock Tool on your PC.

Log in with the same MI account that is linked to your Redmi 13C.

Power Off and Enter Fastboot Mode:

Power off your Redmi 13C.

Press and hold the Volume Down button and the Power button simultaneously to enter Fastboot mode.

Connect your device to the PC using a USB cable.

Connect Device to MI Unlock Tool:

The MI Unlock Tool should detect your device. If not, ensure that the necessary drivers are installed.

View attachment 6108890

Start the Unlock Process:

Click on the Unlock button in the MI Unlock Tool.

Read the disclaimer and warnings, then confirm to proceed.

View attachment 6108891

The tool will start the unlocking process, which may take a few minutes.

If this is your first attempt, you might encounter a waiting period (up to 168 hours). The tool will notify you if you need to wait. If this happens, reattempt the unlocking process after the specified period.

View attachment 6108892

Reboot Your Device:

Once the unlocking process is complete, your device will reboot automatically.

If it doesn’t, you can manually reboot by pressing and holding the Power button.

Post-Unlock Steps​

Set Up Your Device:

After unlocking, your device will perform a factory reset. Set up your device as you would for a new phone.

Re-enable Developer options and USB debugging if needed.

Verify Bootloader Status:

To confirm that the bootloader is unlocked, go to Settings > Additional settings > Developer options.

You should see OEM unlocking as enabled and the status should indicate that the bootloader is unlocked.

View attachment 6108894

Important Notes​

Warranty: Unlocking the bootloader may void your warranty. Check with the manufacturer for specific warranty terms.

Security: With the bootloader unlocked, your device may be more vulnerable to security threats. Be cautious about the apps and ROMs you install.

By following these steps, you should be able to unlock the bootloader on your Redmi 13C using the official MI Unlock Tool. Enjoy the enhanced customization and control over your device!
[Xiaomi Redmi 13C (4G) / Poco C65] problemathic:
thanks bro for the guides. detailed guide. nice
[Xiaomi Redmi 13C (4G) / Poco C65] shamzil:
after flash my redmi 13c goes to fastboot mode only.unable to unlock bootloader as well
[Xiaomi Redmi 13C (4G) / Poco C65] mvikrant97:
Flash the correct ROM on your device.
[Xiaomi Redmi 13C (4G) / Poco C65] shamzil:
i tried all the available roms of each and every country given but still getting the message unable to flash in locked state
[Xiaomi Redmi 13C (4G) / Poco C65] mvikrant97:
Then it will need Authorised flash.
[Xiaomi Redmi 13C (4G) / Poco C65] r0ge1:
I am getting an apply to the community message. What does apply to the community mean?
[Xiaomi Redmi 13C (4G) / Poco C65] mvikrant97:
Are you using Hyper OS?
[Xiaomi Redmi 13C (4G) / Poco C65] r0ge1:
Yes, what is hyperOS.
[Xiaomi Redmi 13C (4G) / Poco C65] tirsasaki:
why do you have to wait 1 week?
[Xiaomi Redmi 13C (4G) / Poco C65] d_g_m_2000:
you need to download an app in playstore

View attachment 6119213

in the app... you need to setup your device as "global region" (if your device is globar rom... if isn't, i don't know)

then in settings you need to apply to "unlock bootloader"... you will need to wait (the app tells you how much, don't remember if 3-5 days).

after that time, ask again to unlock your bootloader... an then continue with the tutotiral of this thread (prerequisites step 4)

*do it at your own risk.. don't blame me if brick your device... xD
[Xiaomi Redmi 13C (4G) / Poco C65] avid69:
hi but if i do this after i can enable LTE CA on redmi 13c 4g? Because now if i go in engineering mode and i try to enable LTE CA ON, if i click set my smartphone doesn't save it.
[Xiaomi Redmi 13C (4G) / Poco C65] NOSS8:
Use:

⚙️How to unlock bootloader on Xiaomi HyperOS(all devices).

Only for GLOBAL devices. 1/Check here that your device is Global and not CN with a Global ROM. https://www.mi.com/global/verify/#/en/tab/imei ------------------------------------------------------------------------------------------ Requirements...

xdaforums.com
[Xiaomi Redmi 13C (4G) / Poco C65] Greenstuff4:
I live in the United States and no carriers really support the bands on this device. Is there some way to get past this to unlock the device?
[Xiaomi Redmi 13C (4G) / Poco C65] NOSS8:
Nope, HW level, not really compatible with the Bands in the USA.
[Android Q&A, Help & Troubleshooting] jsoltan226:
So, i've recently managed to unlock the bootloader of an OPPO A12 using mtkclient, and dumped and reversed the bootloader "little kernel", and found that modifying it doesnt break anything. I managed to find the exact variable used to determine the verified boot state (GREEN - LOCKED, YELLOW - LOCKED with custom root of trust, ORANGE - UNLOCKED and RED - LOCKED but verification failed) and patched it to always be GREEN. And indeed, when booted into twrp, in /proc/cmdline androidboot.verifiedbootstate is green. However, when trying to boot the normal system, dm-verity verification failed (obviously) and the device boot loops. I managed to reverse and patch that part of the kernel, however after 1. Compressing the kernel back using gzip 2. creating a boot.img using mkbootimg with the same args as stock 3. Flashing it back the device appears dead, failing before even showing the logo. If force-rebooted to recovery using key combos everything works there. After looking at the code of lk I suspect that there might be some issue with the dtb, as that's what appears to be loaded earlier than display init, and it depends on which image is being booted. I've been trying to get it to work for a couple of days now, to no avail. Also, the device is running android 9 on chipset MTK-6765 with Boot header version 1, although version 2 on the recovery image also appears to work. Since i also found a function "send_root_of_trust_info" in lk and know how to patch it my end goal is to pass STRONG integrity on the device, but im stuck at this stupid roadblock. I also dont have any equipment nor experience to read the UART logs that the bootloader produces, so i really have no idea what's failing. Can anyone help me with this one?

Edit: my host device is linux x86_64 and im confident that im using the right tools, as creating a bootimg from the stock uncompressed kernel and flashing it works.
[Android Q&A, Help & Troubleshooting] Renate:
Yeah, UART would be your friend in such a case. Look into it.

On Qualcomm with Secure Boot you can't just patch abl/aboot

I guess that Mediatek doesn't do this?

I know you said Linux, but if you have Windows around you can use my imgutil.exe (in the sig) to do a quick check on your boot images.

C:\>imgutil /v /l boot.img
Header2: 1,660 (0000067c)
Kernel: 15,345,443 (00ea2723) 00001000
Ramdisk: 1,149,496 (00118a38) 00ea4000
DTB: 290,066 (00046d12) 00fbd000
Signature: 896 (00000380) 01004000
Padding: 83,865,600 (04ffb000) 01005000
Command: console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0x4a90000 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 swiotlb=2048 loop.max_part=7 buildvariant=user
Read ramdisk, 15 files
drwxr-xr-x avb
-rw-r--r-- 1032 avb/q-gsi.avbpubkey
-rw-r--r-- 1032 avb/r-gsi.avbpubkey
-rw-r--r-- 1032 avb/s-gsi.avbpubkey
drwxr-xr-x debug_ramdisk
drwxr-xr-x dev
-rw-r----- 5281 fstab.default
-rw-r----- 5295 fstab.emmc
-rwxr-x--- 1524536 init
drwxr-xr-x mnt
drwxr-xr-x proc
drwxr-xr-x sys
drwxr-xr-x system
drwxr-x--x system/bin
-rwxr-xr-x 848456 system/bin/e2fsck
[Android Q&A, Help & Troubleshooting] jsoltan226:
Thanks for your reply! As you suggested, I tried using imgtool.exe and the results are rather interesting...View attachment 6109027

As I suspected, the DTB is just not there (even though i didn't remove it from the patched image...), and the ramdisk is also broken, I have no idea why honestly
[Android Q&A, Help & Troubleshooting] Renate:
Oh. So try using imgutil.exe to replace "payload" (the decompressed part of kernel).

My philosophy is, if you want to change something don't take it all apart first.
[Android Q&A, Help & Troubleshooting] jsoltan226:
Worked first try, although I haven't tried patching the payload yet, but at least it definetly failed on dm-verity! Yeah, google's tools (mkbootimg) don't really give you the ability to do that unfortunately (I think it was made just for automatic assembling of images while building android, use in modding was not their priority)... But your tool actually does its job perfectly without the user having to play with it for hours on end! That's quite rare tbh, I actually thought I would have to go through the effort of writing something like myself! Huge respect and thanks!
[Android Q&A, Help & Troubleshooting] Renate:
You can also extract "ramdisk" as just the compressed block and see what it looks like.
[Android Q&A, Help & Troubleshooting] jsoltan226:
I know what's in the ramdisk (it's just magisk) and I also know that the original stock image doesn't even have a ramdisk
[Touch HD Windows Mobile ROM Development] rhtizzy:
Are there any cooked roms out there that have the TF3D musicplayer problem licked?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] fhnsamin:
I have installed the HyperOS EU rom on my Poco F5. Everything has been fine but recently, I found out that the AR services like Maps Live View, Pokemon GO and other apps and games doesn't work. Google maps shows me this error.

View attachment 6108910

I have Google AR services installed.

View attachment 6108911

Is there any way to fix this??
[Honor 60] RioxZG:
I'm Upgrade my phone to MagicOS 8.0

Because im saw Google services Support

But now, I don't saw anything google services. What can i do. Im need some help

View attachment 6108916
[Android Q&A, Help & Troubleshooting] edinbruh:
Hi, I have a rooted shield tablet with android 7. Of course it doesn't have the new API for rumble with bluetooth gamepads, but nvidia implemented their own rumble API for their nvidia controller from 2017, and if an application uses that API (e.g. moonlight) it works.

I have a 3rd-party bluetooth controller that can emulate various gampeads like sony DS4, Android gamepads, and xbox series s controller. On modern devices (e.g. pixel 5) the rumble works in DS4 mode, but of course not on the shield tablet as it has android 7.

Is there any way to add rumble support for this device? Maybe by "emulating" an nvidia controller? Or by "adding" support for the new APIs using root?
[Redmi Note 11 (spes/spesn)] Cygne Noir:
View attachment 6108849

LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform. To learn more, visit the official website.

Issue :

HEVC encoding​

"Hey Google" on another device like headphone

Lags on recent pages

Tell me

Downloads :

ROM + recovery : here​

Vanilla version only. If you want gapps, download MindTheGapps package here​

Installation :

First installation :​

Clean flash is recommended.

Where path/to is the location of the downloaded files.

For the gapps, after flashing LineageOS, read the instructions on the recovery, then flash the package via adb sideload.

Update :​

Or local update via Updater if version signed with the same keys

​

Credits :

LineageOS - support project

crDroid (for device's sources) - support project

@ap4ss3rby for his help

Sources :

LineageOS : https://github.com/LineageOS

Device Tree : here (A big thank you to the crDroid team - original DT)

Vendor : here (A big thank you to the crDroid team - original vendor)

Kernel : crdroidandroid/android_kernel_xiaomi_sm6225
[Redmi Note 11 (spes/spesn)] Ud4ba:
Is it ok to sideload upgrade the firmware to latest version?
[Redmi Note 11 (spes/spesn)] Cygne Noir:
Hi, I'm not sure I understand your question. Could you rephrase it? Otherwise, to anticipate, if you're coming from another ROM, it's best to perform a backup. You can try doing it without one, but you risk losing your data during the upgrade. Additionally, to avoid issues like boot loops, it's advisable to perform a clean flash
[Redmi Note 11 (spes/spesn)] Ud4ba:
Im coming from another ROM and im using realy old firmware of the device. Is it OK to use OS1.0.3.0.TGCMIXM ?
[Redmi Note 11 (spes/spesn)] Cygne Noir:
HyperOS, right ? If the bootloader is unlocked, I don't think there will be any problem installing LineageOS. Just follow the instructions and it should be fine. Remember to make a backup before. Perform a clean flash and enjoy !
[Redmi Note 11 (spes/spesn)] alaminkouser:
any hope for it to be official?
[Redmi Note 11 (spes/spesn)] Cygne Noir:
It is not planned at the moment
[Redmi Note 11 (spes/spesn)] gentano:
Hi, is the ROM signed with testkey or private/rlsey?

We need privkey for Play Integrity to work. I would recommend to mention signature in OP.

Might be helpful:

Signing Builds | LineageOS Wiki

wiki.lineageos.org

https://github.com/306bobby-android/crDroid-build-signed-script ("Works with crDroid 8.x+ or lineage19.1+")
[Redmi Note 11 (spes/spesn)] Cygne Noir:
Yes, currently with testkey since I use LineageOS without Google services and I have never really needed them. But I will do that. I will keep you updated !
[Redmi Note 11 (spes/spesn)] gentano:
No need to hurry, but thousand thanks for taking care!
[Redmi Note 11 (spes/spesn)] Cygne Noir:
Done. The files are available at the same link (latest release) or here. Dirty flash seems to work. Make a backup just in case ;)
[Redmi Note 11 (spes/spesn)] gentano:
You are crazy, thank you! ☺️
[Redmi Note 11 (spes/spesn)] VIS_HNU:
Is it safe to flash on daily driver
[Redmi Note 11 (spes/spesn)] Cygne Noir:
I use it daily without any issues, so I would tend to say yes
[Redmi Note 11 (spes/spesn)] Zylam Marex:
Hi Cygne,

Thank you for the great rom, just installed it and going through the setup. Feels really smooth and stable. Ran into a bit of an issue though, double tap to wake doesn't seem to be working. I've got it enabled in settings and tap to sleep, tap status bar to sleep all working, just not tap to wake. This phones had tap to wake issues in its early life for custom roms, there was a fix developed for it, as far as I know, perhaps the rom needs this fix. Thank you for your time and effort. Also I've got Nikgapps Full Installed, if that makes any difference.
[Redmi Note 11 (spes/spesn)] Cygne Noir:
just tested it and it's a common issue. I will look into it. I will keep you updated !
[Redmi Note 11 (spes/spesn)] Zylam Marex:
Thank you, appreciate it, but please take your time, no rush of any kind. Take care.
[Redmi Note 11 (spes/spesn)] Cygne Noir:
Fixed. See latest release ;)
[Redmi Note 11 (spes/spesn)] Cygne Noir:
And thank you for your feedback !
[Redmi Note 11 (spes/spesn)] ElectricxX:
Hello Cygne!

Are you planning to create a telegram channel for support and suggestions? It's not very convenient here on the forum. Thank you for the long-awaited ROM!))
[Windows 11] xXx yYy:
This thread has nothing to do with Windows 11 itself, it is aimed at all Windows 11 users who do video editing.​

​

Enhance videos with the Power of Artificial Intelligence by using Audials Vision 2024 SE June edition​

Audials Vision 2024 Special Edition is a helpful tool if you have low-resolution videos you want to refine. It perfectly works on Windows 11 24H2 Pro. Have tested it!

Here are some potential benefits:

Improved video resolution: Audials Vision claims to upscale videos to higher resolutions, making them look sharper on high-definition displays.

Smoother motion: The software might be able to reduce stuttering and frame rate issues, creating a smoother viewing experience.

Enhanced colors: It could improve the vibrancy and richness of colors in videos.

Basic video editing: Audials Vision may include some video editing tools, allowing you to perform simple tasks like trimming or cutting clips.

Face restoration: This feature could potentially improve the quality of faces in videos, making them appear clearer or younger.

The Audials Vision 2024 Special Edition supports the video formats webM, MP4, HVEC, H.264, MOV, AVI, MKV and WMV in FullHD or 4K and converts videos in the background. The SE version is almost an all-rounder for videos. It can index and manage videos and fill smartphones, USB sticks and online service storage with media, which means great flexibility.

Take note that this software - an application developed by Ashampoo, a reputable German software company founded in 1999 - may utilize significant system resources, especially during video processing tasks. Be aware of its impact on your system performance.

App's system requirements:

OS	Windows 11 64-bit (Windows 11 24H2 recommended)
CPU	1.5 GHz CPU (minimum)
RAM	4 GB (minimum)

Screen shown when 1st time run:

View attachment 6108926

BTW: I am neither an employee at Ashampoo nor in any other way connected with Ashampoo, nor do I receive money or other benefits for opening this thread here.
[G1 Android Development] fuchsmi:
Hi,

I understand what the SPL is and what the difference of the SPLs available are.

But I don't understand what the recovery image is and what it is for.

What is happening by flashing the recovery image? What is the difference between the original and the modded recovery image?

Thanks,

Michael
[G1 Android Development] jashsu:
The recovery image is Android platform's primary method of updating the system software. If you were to update OTA, it would reboot into recovery to perform its task. The bootloader (SPL) also happens to be another way to flash system software, but it is not officially supported or endorsed. Furthermore, the recovery is device-agnostic, but the SPL is device-specific.

Stock recovery image will only allow the flashing of officially signed update files. Modified recovery image flashes updates signed with the publicly available test keys. In addition, modified recovery partition may have additional features not present in the stock version, such as the ability to perform a nand dump.
[G1 Android Development] fuchsmi:
OK. Thanks for the reply!

So if I mess up my Android OS but the SPL and the recovery image is still working it's not bricked.

And if I mess up my recovery image and the SPL and Android OS with root shell is still working I can re flash it.

So if I mess up my SPL OR the recovery image and the Android OS at the same time I broick my phone.

Am I right with this?
[G1 Android Development] jashsu:
If you've made your Dream non-bootable but you can still get into Recovery, you can rescue it. If you've destroyed the recovery but you can boot, you can rescue it. If you destroyed the recovery and it's not booting but your bootloader works, you can rescue it. If you destroyed the bootloader then it's completely toast.

Lessons learned: don't start messing around with system files unless you know what you're doing! Follow in the path that others have already safely taken to avoid trouble.
[G1 Android Development] fuchsmi:
Is this true for all SPLs (G1Orig, Engineering & HardSPL) or only for HardSPL?

Michael
[G1 Android Development] jashsu:
It's true for all SPLs, but the ease of restoration depends on which SPL is installed. For example the G1 Original SPL would only let you apply a signed NBH file, whereas Engineering & HardSPL would allow you to flash back a nand dump.
[Magisk] hopeeeeee09:
Hi, can someone have a module how to fix this error when open app: This device is not safe, there is a risk of containing malicious code that interferes with the process.

What I do but all cannot fix this:

- Hideroot with this app (Zygisk-assistant)

- My rom already have fake lock bootloader

- Module Play Integrity Fix
[Magisk] Nergal di Cuthah:
What app? Do you pass play integrity? Is it detecting your custom rom? What device? What android version? What superusers (magisk? Kitsune? Alpha? KernelSU? A-Patch?)
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Furry👍:
Hello!!!

I wanted to ask if my splash screen could be changed back,

i had custom rommed the phone with s21 port, and the splash screen changed, will flashing the stock firmware put the original splash screen?
[Xiaomi Poco X6 Pro / Redmi K70E] Xocccie:
Hello,

I use a Xiaomi Poco X6 Pro with HyperOS and the standard Poco Launcher.

Can someone help me how to completely deactivate or turn off all animations? 🤔

I have already deactivated the animations in the settings and I have also set the animations to zero in the developer options. Unfortunately nothing helped.

When I start an app on the home screen, the new window opens and closes with animations. :(

Thank you so much!

Grx Daniel
[Xiaomi Poco X6 Pro / Redmi K70E] BeanLord:
I don't use the native launcher because it's bad, but there's an accessibility option to reduce animations, maybe that would work?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] MJ.nfl:
I just bouht a used Poco F2 pro and the strange thing is that when I enter fastboot there is no image of the little mechanic dude working under the hood of an android.

My phone just shows text "Fastboot" and nothing more.

Is that normal, I haven't seen that before?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] NOSS8:
It's been a few years since the little rabbit was replaced by an orange fastboot logo.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] MJ.nfl:
I didn't know that... Thank you for the answer, I tought that previous owner might have removed the logo...

Since my first and daily poco f2 pro has the rabbit, it was strange to see this fastboot logo.... Was Poco F2 pro in production so long that they had time to think about and change such small things?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] NOSS8:
I also had this model, depending on the age of the ROM it is possible that there is the rabbit then the update deletes it.

Perhaps they deleted it because of myxomatosis.:ROFLMAO:
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] MJ.nfl:
I think that's it.....

The phone I bought as a second device was on latest MiUI, as my daily driver is on custom rom based on Android 12...

Thank you for taking your time to help me solve this puzzle....

All the best...
[LG G8X ThinQ Questions & Answers] jdapp:
Is there a way to tighten the dual screen case hinge? Mine is a little floppy in the open position
[Touch HD General] vanna:
hello,

I'm encoding some dvd in mp4 format (x264 baseline + aac audio) and they play very well on my htc touch hd.

Now i want to embed the dvd cover of each movie into the mp4 file to see them in the HTC Album (in thumbnail view).

i tested Mp3tag and AtomicParsley but the HTC Album keep showing the first frame of each movie (generally a black frame). But the artwork is really in the mp4 file (i have tested with winamp or kmp player or other tag editor).

thanks for your help and sorry for the poor english quality
[Samsung Galaxy J5 Questions & Answers] Maulana1945:
I flashed wrong TWRP in my J500g And I Stuck on "Setup Connection" and failed in Odin while flashing firmware. Can somebody Help me?. (I bricked my Phone for 1 Month+)