yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
Seeing quite some people report this. Maybe it has something to do with TEE. Let's hope a fix is found soon.

Trusty TEE | Android Open Source Project

source.android.com

"There are many other uses for a TEE such as mobile payments, secure banking, multi-factor authentication, device reset protection, replay-protected persistent storage, secure PIN and fingerprint processing, and even malware detection."
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nick069tf:
Ok thank you very much then it's not my fault :D
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Sven_van_vessem:
Hi! What worked for me when installing the Pixel Experience and having the same issue is to flash the firmware of your region on https://xiaomifirmwareupdater.com/firmware/alioth/ This is a MUST if you came from an older version of Lineage or simply haven't updated the firmware yet. (Don't worry, flashing won't factory clean your device).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nick069tf:
Good day,

and how do I do that? could you possibly write me a tutorial ? I do not know myself so well there
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
Install LineageOS on alioth | LineageOS Wiki

wiki.lineageos.org

According to their instuctions you need to extract the firmware zip and install each image in fastboot. But I think you should be fine just flashing the zip in recovery. Far easier.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nick069tf:
do you have a video showing how to do it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
I do not.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nick069tf:
Okay can you give me a step by step guide? because as I understand it then all data will be deleted
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] user0u:
This won't delete any data because this is a firmware installation not a ROM installation. Firmware is around 140 mb whereas ROM is far larger, around 4 to 7 GB.

You only need to download the firmware zip file and flash it in a custom recovery. I prefer orangefox.

-Boot into orangefox recovery using "fastboot boot recovery.img" (Extract the recovery.img from orangefox zip file)

-Once the phone boots the recovery, locate the firmware zip file in your phone and flash it. Should only take a few seconds.

-Reboot and you're done.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] fxmiko:
that'd happen when the blob and firmware version doesn't match, flash the recommended firmware by the maintainer of the ROM
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Nick069tf:
It worked, thank you very much :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] NoirBird:
Flash firmware, I've had the same issue with Project Elixir.

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[LG Stylo 3 Questions & Answers] Trace.Oneil:
Good day,i have searched XDA for this specific model with no luck and internet searches also are'nt of any real help so i thought i'd ask here and hope that someone has some answers for me.

I am looking to bootloader unlock,root and install a custom rom and twrp recovery on a LG Stylus 3 M400Y that i have here. It has Android 7.0 installed and uses a MediaTek chipset from what i can make out. Other than that it seams really similair to the LG Stylo 3.

If anyone can please point me in the right direction with regards to all the above for this device i would be really grateful. I woud really like to update it to Android 10 at the very least if possible but there is no conclusive information anywhere for this device.
[Touch Diamond, MDA Compact IV General] Lord_BlackAdder:
I have tried it on both stock rom as well as cooked rom and found similar issue with MS Exchange email:

An email message that was sent by the phone to another receipient successfully. But the mail still sit on the Outbox. So the next time the Exchange mail was synced, the same message was sent again. I have to manually delete the mail from the Outbox.

Has anyone have similar issue? Any fix?
[LineageOS Questions & Answers] xdabuntu:
Hello

Has anybody found a ROM (LineageOS or similar) for DORO 8050 and could successfully flash it?

Thanks!
[LineageOS Questions & Answers] SigmundDroid:
https://www.expertreviews.co.uk/mobile-phones/1413683/doro-8050-review

Don't get me wrong but I doubt anyone would prefer the work of flashing over getting a new phone.
[LineageOS Questions & Answers] xdabuntu:
Thank you for your comment. This could be right. But if you already received one second hand and would like to have the benefits of LineageOS, it is still worth :), I think.
[LineageOS Questions & Answers] SigmundDroid:
Lucky you! Still plenty of luck finding a working LOS ☘️ Perhaps seeking/asking at other Snapdragon 215 like Nokia 1.4 can help...
[LineageOS Questions & Answers] xdabuntu:
Thank you for the tip! But I am bit hesitant to flash a ROM not tailored exactly for the device. I don't want to brick it 😊. And I am not a pro.

Although the chance seems slim, I hope someone knowledgeable will help with a ROM for this DORO.
[LineageOS Questions & Answers] SigmundDroid:
Nonono, didn't mean that but I thought you find "someone knowledgeable" there, ie some ultra-nice dev?
[Google Pixel 6 Pro] vikramanananda:
My Google Pixel 6pro get in to new issue

One day suddenly caller not able to hear my voice unless I switch to loud speaker ,

My google Assistance, Recorder, Meet, Whats up all facing same issue,

But Mic Test Apk (Mic Test - Instant audio Check) can pick my voice & record my voice well

Any one facing this issue

Or anyone have found any solution.

I hate to use Bluetooth Devies for calling purpose
[Google Pixel 6 Pro] fil3s:
Just use Android flash tool

I'm giving root a break for a while, using shizuku. I think my phone is much more stable without root.
[Google Pixel 5 Questions & Answers] _euphonic_:
How can I instal TWRP on Pixel 5 (unlocked bootloader)??

I've got some errors

Why it is "not allowed to flash recovery"

And what differences is between slot A or B?
[Google Pixel 5 Questions & Answers] V0latyle:
Pixels do not have a recovery partition. The recovery kernel is compressed and lives in the boot image. Because TWRP does not support compression, it cannot be installed. If the TWRP image is written to /boot, it will overwrite the system kernel, resulting in a device that will only boot to TWRP, until the original boot image is reflashed.

The proper way to use TWRP on a Pixel is live boot: fastboot boot twrp.img

This tells the device to load TWRP into memory so that the user may perform desired functions; upon reboot, the device will boot normally.

However, most flashing operations can be performed by ADB from bootloader or fastbootd, obviating the need for a custom recovery

The A/B slot scheme is for seamless system updates. This allows the device to update "on the fly" without extended downtime.

The legacy method with a dedicated recovery partition (e.g., Samsung) requires the device to reboot into recovery to update the system, as the system cannot be updated while running. Having two slots eliminates this problem, as follows:

Pixel is running on one slot, let's say it's slot A with the July update.

When the August update becomes available, the device downloads, unpacks, and installs the update to the B slot

When installation is complete the device then reboots to the updated slot, in this case slot B, booting into the August update. Upon successful boot the B slot is marked as valid, and the device will continue to boot from that slot after every reboot.

When the next update (September) becomes available, the process starts over again - while running on slot B, the system downloads and installs the update to slot A.

If at any point the updated slot fails to boot, the device will revert back to the original slot.

This has the following benefits:

Contrast this with legacy A only devices (like the aforementioned Samsung) where:

Updates can only be installed in recovery, requiring extended interruption of user activities; the device cannot be used during the update

Updating can take quite some time, 5-10 minutes or more

If an OTA update fails to apply, the device will fail to boot

If an OTA update is applied but fails to boot, the device is unusable until manually reflashed

Any errors will result in update failure, which may cause the device to fail to boot

Updates have to be downloaded entirely, then unpacked and installed by recovery kernel, which requires free storage space

The update must be held in cache until the device is updated, taking up space

If the boot image is corrupted, the device will fail to boot

Hope this helps explain things.
[Google Pixel 5 Questions & Answers] simplepinoi177:
MOD ANNOUNCEMENT​

THREAD CLOSED​

@_euphonic_ , As you have posted this in another thread , per Forum Rule 5 (quoted below), this thread is closed as it is a duplicate post. As it states in the rule, "As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer." "You can bump your unanswered question once every 24 hours" and thus "Duplicate threads and posts will be removed", as this post/thread is.

I have copied @V0latyle 's response to your post to that thread for continuity. Please continue your discussion there where you originally posted; which one can find in the URL is below.

https://xdaforums.com/t/recovery-teamwin-recovery-project-redfin-official.4240711/post-88904909

I hope you understand are amenable to this,

simplepinoi177 FSM

XDA Developers Forum Rules said​

5. Create a thread topic or post a message only once, this includes external links & streaming media.​

As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.​

You can bump your unanswered question once every 24 hours

Duplicate threads and posts will be removed

Always post in an existing thread if a topic already exists, before creating a new thread.
[Android Q&A, Help & Troubleshooting] flixcrls:
Anyone have any news miunlocktools for macos and linux? cause i want UBL my xiaomi phone and i just have macos, if you all suggest me to install vb or vm, i already install it and download the windows, the windows in vb or vm cant update the driver, that why my phone cant detect in miunlock, i think that because i use m1 chip, and maybe the windows detect me use macos and m1 chip, anyone can help me please feel free for dm, i really appreciate your help, thank you. 😄
[Touch Diamond, MDA Compact IV General] Shogunichi:
I have the emobile touch diamond, Japanese version. I cannot figure out how to set my mp3s as a ringtone. It will only let me make .wma format into a ringtone. Can anyone help?
[Touch Diamond, MDA Compact IV General] Imyman:
The easiest way to set an mp3 as your ringtone would be to do it from within HTC audio manager. Play your mp3 file in audio manager, click on menu-->Set as ringtone. Trim your file to play not more than 40-45 seconds since most carriers cant play a ringtone longer than that. After you trim it, select set as default ring tone.
[Touch Diamond, MDA Compact IV General] Shogunichi:
Even if I play the track in the HTC audio manager the menu does not show "set ring tone" only allows me to add to playlist, properties, ect.
[Touch Diamond, MDA Compact IV General] Imyman:
Hmm......ok. Do this, take your mp3 file...and save it in the following location. Using file explorer go to my documents-->my ringtones. Save your file here. Now go to start-->settings-->personal-->sounds and notifications-->notifications-->incoming call. You should be able to see your mp3 file in the drop down.

Good Luck.
[Touch Diamond, MDA Compact IV General] bigbro168:
that works.. but if you hooking your phone to the computer using activesyne.. they have an option when you first sync it to see if you want to sync music as well...

if you did that.. your Phone My Document folder will show up on the desktop.. and you should be able to see a folder name My Ringtones there.. copy and paste the ringtons you want in there..

and now just go back to your phone.. under Notification.. you should be able to see your ringtones under the drop down like syedimran said
[Touch Diamond, MDA Compact IV General] Shogunichi:
Ya, something is different because it is a Japanese rom. It does have a ringtone folder, but the name is in Japanese. Even if I put files in there they do not show up in setting/personal/sounds and notifications/notifications/incoming calls drop down menu. It is very strange.
[Touch Diamond, MDA Compact IV General] Imyman:
Might I suggest flashing a nice clean english rom then. Its gonna save you a lot of rework and its easier this way. Ofcourse the choice is all yours. ;)
[Touch Diamond, MDA Compact IV General] Shogunichi:
How would I go about flashing the rom? Would everything else work ok?
[Touch Diamond, MDA Compact IV General] bigbro168:
Flashing a new ROM would cause everything other than the stuff in your internal storage deleted.

You can backup call history, sms, e-mails, contacts using this program call PIM Backup (search it on the forum you will see it, or go under the ROM development section click on the Dutty 3.5b Final post and in the first page he has a link to PIM Backup)

Just follow the instruction from the Dutty 3.5b Final post and you will know how to flash a new ROM

of course you can also choose other ROMs of you choice but the same instruction applies to all ROM
[Red Magic 8 pro] Anegorami:
So, I've finally got my hands on 8S and first thing I did in the morning - yeah, right - ROOTING.

Using the method posted in the https://xdaforums.com/t/root-redmagic-8s-pro.4617049/ I got as far as "Reboot. Done.". Except the reboot to system never came, ending me back into unlocked bootloader instead. So, ye, I'm stuck.

Given:

- ABL was successfully flashed using EDL mode (QFIL works just fine after a tiny bit of tinkering, was going to post some juicy screenshots into the mentioned thread laughing at everyone giving their $40 for nothing but, alas...).

- Bootloader unlocked (both unlock and unlock_critical).

What I've tried so far:

- Restoring init_boot_ab from the backup - no dice.

- Booting into recovery - no dice (sends me back to bootloader).

- Booting into EDL - works as expected (kinda useless now but still).

Finally, the data that is shown to me in the loader:

device info:
CPU SERIAL NUMBER - <serial number>
SECURE BOOT - yes
DEVICE STATE - unlocked
WARRENTY STATUS - VOID

P.S.: Secure Boot is what is concerning me the most, need someone with successfully rooted device to check if it should be disabled somehow.

P.S. II: "WARRENTY STATUS" is typed exactly how it's written. Chinese being Chinese.

EDIT: Surprise, surprise, my ignorant stupid ass continues to descend deeper into the device firmware depths. After a bit of time, thinking, tinkering and failing I suddenly got an awesome idea: switch slot to B and try to boot from there. Guess what - now I'm stuck in EDL. After a bit of research it seems that most of the B side partitions are outright empty (filled with 0x00). So, my next question is - which ones I need to restore from A side to be able to boot back into bootloader, switch to side A and thus return to the previous, more favorable state.
[Red Magic 8 pro] kh.v:
First, congratulations on the unlock status, which mean have unlock successfully.

Secondly, so sad that you got bootloop, but dont worry, my friends, i got you !!

Download this, and you google translate for instruction. Press the 11 option, then you will be fine

Toolbox download:

https://syxz.lanzoub.com/b01f2iste

(password: d78d)

Use 红魔8系列工具箱by某贼V2.1.7z
[Red Magic 8 pro] aaa.bbb111222:
First thing you need to do it to backup persist partition. If you can also backup other partitions from slot a via EDL, it would be helpful as well (or download full OTA and unpack payload.bin via payload-dumper-go). Then you can probably write all these images to slot b and try booting once again.
[Red Magic 8 pro] Anegorami:
>all these images

That was the assumed course of action, my question was about saving some time and flashing only the partitions required to get back to bootloader. Well, thanks anyway.

Also, as far as I've looked, there is no 8S OTA packages yet neither a link to the stock firmware ROM (beside the Chinese one I've randomly stumbled upon), which would help a lot in my particular case (restoring the out-of-box state would be a miracle, no less).

...Does that even works on 8S?
[Red Magic 8 pro] aaa.bbb111222:
For bootloader you wouldn't need boot and super partitions, just abl/xbl/etc ones.

But really just backup persist first (and check that it's not empty and contain calibration data). It is likely that you might loose it while playing with edl and it's game over then (for fingerprint scanner at least).
[Red Magic 8 pro] Anegorami:
OK, after mirroring entire slot A to slot B (QFIL, my beloved), the console has finally managed to get to my phone through ADB:

C:\Users\User>adb devices
List of devices attached
<serial number> recovery

So, operation "FK, go back" successfully completed. Now, I'm in recovery mode, which is something. Will continue tinkering around, looking for clues. If anyone has some bright ideas (or just want to talk or maybe even support me, you monster) feel free to drop by and say hello.

Ninja edit:

>But really just backup persist first

Done, some data is present, which is good, I guess.

Another edit:

Tried

fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.bin
fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.bin

No dice.

Another another edit:

Tried:

fastboot erase userdata

...because I can. No dice.

Another another edit 2: Recovery Boogaloo:

Below is the list of every partition QFIL could dump for me (save for userdata). Note that since only A side had any data slot suffixes are omitted.

Spoiler content hidden.

Also, due to some file juggling and my natural karma original ABL partition backup is lost forever.
[Red Magic 8 pro] aaa.bbb111222:
I had similar issue then my phone straight up didn't boot to Android and only went to recovery. Fixed with reflashing all the partitions to v3.19 (mainly super and boot stuff) with fastboot and wipe.

Can you verify that all dumped partitions contain "sane" data?
[Red Magic 8 pro] Anegorami:
First of all, kudos to kh.v, 酷安@某贼 and the entire Chinese community. Thank you for existing.

OK, let's go.

After getting back to recovery I've flashed the original init_boot back, performed a Factory Reset and pressed REBOOT, with my fingers crossed. And, suddenly, the phone has presented me the OS. Welcome back to the world of living.

Sure thing, Magisk, install, open, patch, adb reboot bootloader, flash, bootloop. FK.

At this point I decided to take a break and explore the tool posted by kh.v. Inside the source batch scripts I've stumbled upon a rather interesting comment (near the mentioned 11 option):

Spoiler content hidden.

Spoiler content hidden.

...Seriously?

OK, nothing to lose,

fastboot flash init_boot_a magisk_patched-26100_wHrEh.img
Sending 'init_boot_a' (8192 KB) OKAY [ 0.169s]
Writing 'init_boot_a' OKAY [ 0.000s]
Finished. Total time: 0.200s

fastboot set_active a
Setting current slot to 'a' OKAY [ 0.022s]
Finished. Total time: 0.037s

fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s

...And the phone happily booted to the system.

What. The. Hell. Was. That?!

A was my primary slot 90% of time (10% of EDL hell on B slot, yeah) and yet I have to explicitly activate it AGAIN to get out from black-hole bootloader? IT DOESN'T MAKE ANY SENSE! (not for me at least)

Yet, now all the puzzle pieces has gathered. My futile attempts to restore init_boot were for naught because the loader was too selfish to let me go (yandere type joke here) and thus simply ignored my plea. What a load of crap.

Oh well, the case is closed, latest Magisk is installed and seems to be working. Hope my experience will be helpful to somebody. Take care, don't switch slots without probing the ground beforehand and learn from anything and anyone disregarding even the language barrier. The End.
[Red Magic 8 pro] kh.v:
Told ya :)

Dont worry my friend, i got your back :)
[Red Magic 8 pro] borygo77:
Does anyone experience magisk not opening after x period of time? I've even restored and started from scratch. Still won't open. Have to restart the phone and it's working for some time but when you kill it it won't reopen again 😒
[Red Magic 8 pro] aaa.bbb111222:
Even Magisk developers don't know what exactly causes this: https://github.com/topjohnwu/Magisk/issues/7164

I use the following commands (repeat last one few times untill it fails):

su
kill `pidof com.topjohnwu.magisk`
[Red Magic 8 pro] borygo77:
Yeah I've seen those issues on github.

Thanks anyway 😉
[Red Magic 8 pro] sleeping3119:
i have not nderstood it because in first post you already told that you tried changing slot and it made more worse.

Did you mean that before flashing patched boot check the current slot and after flashing set that current slot again ?
[Red Magic 8 pro] Anegorami:
The issue was that I've changed the slot to the inactive one (B, in this case) without probing the ground and end up attempting to execute some literal zeros. The magic happened when I set THE SAME ACTIVE SLOT AGAIN after the flashing (you can see that clearly if you check the console output, both flash and slot set target the same A slot).
[Xiaomi Mi 11 Ultra] Flower Sea:
Code:

* Your warranty is now void.

*

* I am 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 ROM

* before flashing it! YOU are choosing to make these modifications, and if

* you point the finger at me for messing up your device, I will laugh at you.

Introduction

If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

Features

Individuality

Security

Longevity

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

Installation

Detailed installation instructions:

Install LineageOS on star

Download link:

lineageOS 20

lineageOS 21

Recommended Google Apps package:

MindTheGapps (choose ARM64 13.0 zip)

More information can be found here

Donate to support development:

Donate via PayPal to FlowerSea

Donate via PayPal to LineageOS
[Xiaomi Mi 11 Ultra] Flower Sea:
• This is an unofficial version built separately for star（Mi 11 Ultra）

• The official version is only for Mars and does not support star, but considering that many people in the community use star, I decided to provide unofficial support for star
[Xiaomi Mi 11 Ultra] veimus:
Thanks for this ;)

Can this ROM be used as daily driver, or there is still plenty to fix on it ?
[Xiaomi Mi 11 Ultra] Flower Sea:
Yes, you can use it as daily driver if you don't consider the back screen
[Xiaomi Mi 11 Ultra] testina:
hi, is the last miui by Xiaomi.eu dev beta considered an official or unofficial build?View attachment 5984453
[Xiaomi Mi 11 Ultra] Flower Sea:
Xiaomi.eu doesn't count as a custom ROM, so you can start with Xiaomi.eu
[Xiaomi Mi 11 Ultra] veimus:
Just installed, there is a problem with fingerprint sensor, the backlight on the sensor is too dim to allow sensor to read my finger ? And I'm unable to set up it.

View attachment 5984689

UPDATE: After restart seams to works, but the sensor isn't that bright like on stock ROM.

UPDATE 2: Google Pay doesn't work
[Xiaomi Mi 11 Ultra] Flower Sea:
try this, what gapps are you using

https://github.com/FlowerSea0208/flower-ota/releases/download/test/lineage-20.0-20230823-UNOFFICIAL-mars.zip