yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] pxrave:
Hey dude you plan to release cr7 security updates too until cr8 major bugs fixed? Thanks
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Klen2:
Regarding the teams bug, it happened to me also on Derp once, but when I installed it other time and tried, it worked normally...
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] HueyT:
Great job. Works great for me. Thanks 👍
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] nkhater:
I tried to uninstall it and reinstall the Teams App, still sounds the same, can you please tell me about your experience and how did you fix it? Thank you
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Addy-95:
no only cr8
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] Klen2:
Sorry, I didn't write it clear. I meant after I did clean flash of the ROM some other time, Teams were working. Reinstalling Teams didn't help
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] C.Sprite:
Any screenshots? I'm considering to move to cr but idk how it looks .
[OnePlus 7T ROMs, Kernels, Recoveries, & Other Deve] CraigHardy:
Looks like any other a12 rom, similar customization options as derp
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Hello everyone:

Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.

Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (

) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.

I would appreciate, please, if you help me.

A greeting and thanks in advance.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Try to follow this guide to the letter.

How to flash a stock rom [alioth]

Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...

xdaforums.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Hey! Thank you for the soon reply. I have read the tutorial quickly, but i will reread slowly as soon as i can. Anyway, i think that i have tried with all this and the errors persist. But, as i have said, i will re read slowly and let you know what happened with with my retry following your instructions.

Thanks a lot!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] finalgravity525:
Put miflash and rom on local disk C.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx a lot for the help! I have tried these two options, and it gives me the "file is too large" error.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Fiend, would yo be so kind to provide me the exact link to de file of "SDK platform tools", please? The page you gave me is a little bit chaotic. Thx in advance!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
If you have followed my guide to the letter and it gives you an error again, try changing the USB port, or the cable, or with another pc, if it has intel cpu and win10 it is better. Try to download the rom again from one of the sites linked in the guide.

I have attached sdk for Windows:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx a lot for the file and for all your help. What do you think about "the file is too large" error? I have read over there that is relationed with Hard Disk FAT 32 format, but i have NTFS.

Thx in advnace.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Honestly, this has never happened to me and it is the first time that I have ever heard this error. I know that the fat32 file system does not allow the storage of a single file larger than 4gb, but this does not seem to me to be the case. In addition to the advice I have already given you, such as downloading the rom again, or a different version, change usb port, cable, and do it all over again, you could try using the february 2021 version of miflash, I do not know what to think. It could also be a conflict on your pc, if you can't use another one try to create a small partition and install a clean version of win10 Otherwise I don't know ...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx a lot one more time, friend.

Do you think it could affect (if there is any difference) using cmd or using MI Flash? Do you think that wanting to close the bootloader or not can influence on the success flashing? Do you think it can influence to use MIUI GLOBAL or MIUI EEU, which is the one that corresponds to me, or not?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
No problem bro!

There is no difference between cmd and miflash, because miflash performs the same operations that the script on cmd does, I don't think that's the problem.

I don't think it even depends on closing the bootloader, also because it is a command that is done at the end of the ROM flash. (I wouldn't close it unless absolutely necessary. I advise you to do it only with the original rom of the phone, like if you bought it with global, close only with global and not with eea, it could go into brick, even if some have succeeded.)

I have changed region a couple of times, bought it with rom eea and flashed the global and went back to eea without problems (without blocking the bootloader) so it shouldn't cause any problems.

More than anything else, I think it's a conflict in your pc system, maybe in the drivers. I would try to make a partition in the hd and install win10 and everything you need for the flash and see if it works. What pc are you using?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx one more time for your help and patience (are you spanish or spanish speaker?).

I'm using a Huawei Matebook D, with an Inter(R) Core(TM) i5-7200U CPU @ 2.50GHz 2.70 GHz, 8,00 GB RAM Memory. I have never ever had any issue with the performance of my PC.

Anyway, yesterday night i followed your guide, firstly i tried the "1) How to flash a stock rom using miflash", but when i refreshed in order to check if MIFlash detected my Phone, a strange little window error appeared ("Unhandled exception from the application. If you click Continue, the application will ignore this error and try to continue. If you click Quit, the application will close immediately"). So, when if i clicked "Continue" and i tried to refresh again, the error reapeared, and when i clicked "Quit" MiFlash closed. I recognize that i didn't do the "Disable driver signature enforcement in windows" step (is it mandatory?).

Due to this unexpected error, i tried the way "2) How to flash a stock rom using cmd",with not doing, again, i recognize, the "Disable driver signature enforcement in windows". So when i flashed from the cmd, unlike all the precedent tries doing with this way, the rom started flashing succesfully. All seems to going perfectly, but when the process arrived to the 7/10 poing, i had an "super flash error" (actually, the cmd screen specified me one concrect error, but i was a little bit nervous and didn't copy it; i think was (or it was something like) the "sparcecrclist error", but i'm not very sure). The rom, then stopped flashing, the phone was blocked (as the other precedent failed times) at fastboot mode, and i could only recuperate it by flashing the Xiaomi.eu room.

It was very sad, because i really thought that in this time i would succeed. I don't really know what to do. I got really scared, because that "super flash error" terrified me, but fortunately nothing bad happened thanks to the succesfull flash of the Xiaomi.EU rom. I could flash the rom stock again, in order to copy here the exact error i had on "7/10" step, but that "super flash error", which i have never had, really scares me. It seems like you are my only help here and, anyway, following your guide has been has been the nearest point of installing the stock rom succesfully.

I would love to hear from you again.

***EDIT: that MIFlash error never happened to me preciously. I used the last version which was on the link of your guide.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Ciao! no i am not spanish, but i love spain and i have been there for six months and i speak some spanish, however i am sardinian, italy.

So, disabling driver signing in Windows is essential to be able to correctly install unsigned drivers such as those present in the miflash program.

Sparse crclist It happened to me as an error, I solved it by downloading the rom again and unzipping it and renaming it with a small name and no spaces in the miflash folder and then it successfully flashed and special characters like $ # & etc.

I asked you which pc you use because some users with pc with amd processor the miflash program gave problems, even if you use the front usb ports or usb3.1, hence the advice to use rear doors and 2.0.So try to follow the guide to the letter by changing the usb port and downloading the fastboot rom again, I am sure that sooner or later you will be able to flash the rom, or at least I hope so. I too got scared when that error appeared to me.I hope it works, and what you tell me more and more makes me think that it is a conflict between miflash and the system. Happy flash bro!

Also try the February 2021 version of miflash, I used that. They have recently updated it and I haven't tried it, maybe the bag is his fault.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Ok, i will repeat the guide adding the step of driver disabling driver signing.

And i have checked the device administrator and, of my 3 usb ports, two of them are "3.0 - 1.0", but ¿how can i know which of the 3 are the 3.0? Sorry about my inexperience. And thank you a lot.

***EDIT: And when you mention "renaming it with a small name and no spaces in the miflash folder", you refer to the rom's folder or the rom (.bat) properly said?

***EDIT(again): And all the difficualties couldn't be related to the fact of the "Rollback" problems, because i'm trying to get back from Android 12 to Android 11? i don't know.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] RollDload:
Ok. follow the guide it should work with the February 2021 version of miflash.

Generally the USB 3 ports are of a different color, usually blue or light blue, the 2.0 are black.

Don't worry, no one is born with infused wisdom 😜

When I say to rename the folder, I am referring to that of the rom, I generally use the version like 12.5.6 or in any case choose a name that has no spaces or special characters such as% $ # etc.

The anti rollback is only present on stock roms so you don't run the risk if you switch from custom like xiaomi.eu. i also checked the stock miui 13 china and it is not active on this phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] JJeamy:
What your bootloader status now..?, you can check it by typing fastboot command "fastboot oem device-info"

did you remember exactly of what the stock rom version (detail MIUI version including region code) that came from the phone before you flashing it..?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx a lot for your interest in helping me. This is what i had with that command:

fastboot oem device-info

(bootloader) Verity mode: true

(bootloader) Device unlocked: true

(bootloader) Device critical unlocked: true

(bootloader) Charger screen enabled: false

OKAY [ 0.007s]

Finished. Total time: 0.008s

And the the exact rom version vas MIUI 12.5.7 (EEA).

I would thank you any help from you. Thx in advance.

***EDIT: MIUI 12.5.7 GLOBAL (EEA).
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] DroidEditor:
Well i hope you got the answer till now case u havent got the solution please refer for the firmware flash to global or the initial firmware .. yes it will make xiaomi.eu rom into a bootloop the go for the flash by the images folder but not the actual folder and do flash in fastboot mode & not in oem mode that will brick the device also just in case things turn back swith to aosp and then firm flash back again this is the nth solution for the error this has nothuing to do with NTF or FAT32 format

\

in case the solutions request for a thumbs up to the post

Regards

DroidEditor

845192am@gmail.com
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] JJeamy:
No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom

Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble

So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?

What windows version..?, windows 10 or 11..?

did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?

i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Tukan41:
Thx a lot for trying to help me!

-The rom i have download, yes, is POCO F3 EEA V12.5.7.0.RKHEUXM.

-My Windows version is Windows 10 Home.

-Yes, yesterday i tried to flashing with "clean all", i mean, without trying to close bootloader nor maintaining internal storage.

Mainly, i used the guide which Rolldload kindly provide me, except the "Disable driver signature enforcement in windows 10", and my flashin went gone until the flashing 7/10 phase, where the command window gave me a "super flash error", and all ended there.

I hope all these information serve you.

Regards.
[Touch Cruise ROM Development] Pietpuk107:
Does something like USBTOPC exist for Polaris? Can I install the version that is available for the HTC Diamond?
[Touch Cruise ROM Development] gregy74:
And why you need this. You have internet sharing.

1. program, internet sharing

2. USB, network connection must be your defoult connection

3. connect

Now just plug USB to polaris and PC. PC will install some drivers.

And that is all.:)
[Touch Cruise ROM Development] signfinder:
USBTOPC - replace wm5torage or softick card export.
[Touch Cruise ROM Development] firiel:
There was a version included on touch-it 3.5 but didn't work for me
[Touch Cruise ROM Development] MaTT_RnD:
Agree, a was install USBtoPPC Opal's version and nothing changed in system preferences
[Touch Cruise ROM Development] gregy74:
Sorry, my mistake.

I would also like to know, how can I use 12MB/s data transfer in Polaris.

Softic Card export is really slow and WM5 storage don't work.
[Xiaomi Mi 11 Ultra] bounti:
Hey all,

Is navigation (swipe) gestures a possibility on third party launchers such as Nova Launcher on MIUI13? Whether allowed by the OS or via adb command?
[Xiaomi Mi 11 Ultra] bounti:
Anyone??
[Xiaomi Mi 11 Ultra] mervs2402:
Nope.
[Xiaomi Mi 11 Ultra] ZedeN:
If anyone is still struggling with getting gestures to work on root and/or non-root devices:

- Download Full Screen Gestures from play store

- Open the app, give all permissions it asks (draw over apps), give it accessibility, lock the app in your recents and make it "no restrictions" for battery saver

- configure app as you like

- Go into your MIUI settings, find gestures (they are under Home Screen > Default Launcher > System Launcher > System Navigation) and hide full screen indicator under gestures then enable buttons.

- Change your launcher to be Nova or anything else

- enjoy semi broken experience

You should have gestures that work 90% of the time. To make them work 99.9% of the time and hide the nav bar:

- Give Full Screen Gestures accessibility shortcut (hold both volume buttons to toggle the gestures on/off if they stop working)

- Get Tasker from Play Store

- Give tasker all required permissions. Tasker can do it easily with root, otherwise you can use permission helper or set them yourself.

- using Tasker, create a task:

<TaskerData sr="" dvi="1" tv="5.14.6">
<Task sr="task2">
<cdate>1628889756751</cdate>
<edate>1643032037802</edate>
<id>2</id>
<nme>Hide Navigation Bar</nme>
<pri>7</pri>
<Share sr="Share">
<b>false</b>
<d>Temp hide navigation bar</d>
<p>false</p>
<t></t>
</Share>
<Action sr="act0" ve="7">
<code>235</code>
<Int sr="arg0" val="0"/>
<Str sr="arg1" ve="3">force_fsg_nav_bar</Str>
<Str sr="arg2" ve="3">1</Str>
<Int sr="arg3" val="0"/>
<Str sr="arg4" ve="3"/>
</Action>
<Img sr="icn" ve="2">
<nme>cust_scrubber_normal</nme>
</Img>
</Task>
</TaskerData>

- Place shortcut to that task on your home screen.

If the nav bar ever appears, use the shortcut to hide it again.

If you use Tasker to hide the Nav bar, be careful, sometimes full screen gestures stop working and you can get stuck in an app/window with no way out apart from reboot.

Feel free to automate the Tasker task to hide the navigation bar at reboot/ any other condition.
[Xiaomi Mi 11 Ultra] mapleshadow:
GOOD！！！
[Xiaomi Mi 11 Ultra] Ltmax:
I'm not fan of how are we approaching this workaround. Gestures definitely should work with 3rd party launcher. C'mon Xiaomi
[Xiaomi Mi 11 Ultra] Bartos81:
They will not work because they are part of the launcher, not the system.
[Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,] Jubscleisson:
PixelExtended ROM for Samsung Galaxy N10/+/+5G [d1&d2s&d2x]

Please read whole post before downloading

*** Disclaimer
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing
any custom ROMs and/or kernels. (Bricked devices, dead SD cards,
thermonuclear war, Seal mad or you are getting fired because the alarm app
failed…)
* YOU are choosing to make these modifications, and you do it at your own risk.
if you point the finger at me or anyone else for messing up your device, you haven't
done what we told you to do.
* Please do research if you have any concerns about features included in your ROM

What is this?

PixelExtended ROM (or PEX for short), aims to combine Pixel goodies with some essential features missing in Pixel Experience, delivering a ROM that promises you stabilty and a large amount of features at the same time. The ROM will keep it's Pixel ideologies it's primary focus and wont stray into the dark and deep void that is bloat.

Our mission is to offer maximum possible stability and security along with essential and useful features for proper functioning of a device.

Based on Android 11 (R)

Whats working?

Wifi

RIL

Mobile data

GPS

Camera

Flashlight

Camera

Bluetooth

Fingerprint reader

Face unlock

NFC

Lights

Sound / vibration

Known issues

VoLTE/VoWIFI - not working for most Samsung devices, so no fix in the near future

Bixby button

You tell me​

Download:

ROM (d1) (d2s) (d2x)

Lineage recovery (d1) (d2s) (d2x)

Magisk (Download from here)

Gapps - DO NOT FLASH GAPPS, THEY'RE ALREADY INCLUDED

First time installation:

The same instructions as for installing official LineageOS apply, so the ones found here.

you CAN NOT INSTALL this ROM using TWRP.

You need to use the Official Lineage recovery provided by Linux4 (link in downloads section)

Installing Lineage Recovey (BL already unlocked):​

Odin:

Rename the downloaded .img to recovery.img and add it to a .tar archive using, for example, 7Zip

Flash the resulting .tar file in Odin

Installing The ROM From Lineage Recovery:

Lineage recovery - Factory reset > Factory reset & reset system partitions

make sure that all your zip ready for install via OTG/SD card/ADB

Lineage recovery - Apply update > Choose from sdcard > select the rom and install it

Install magisk .zip (change magisk.apk to magisk.zip if you installing via SD card/OTG)

Reboot to system!

Android OS version: 11

Security patch level: November 2021

Build author/Device Maintainer: Jubscleisson

Source code: https://github.com/PixelExtended

PixelExtended Developer: Aryan Gupta

Sources&Trees

ROM Source: (Link)

Device tree: (d1)(d2s)(d2x)

Common device tree: (Link)

Kernel: (Link)

Vendor: (Link)

Credits

@Linux4 - For making the trees and officialy maintaing them in LineageOS

@Orel6505 - For helping me all time!

Support Group Link

Liked the rom? Donate PixelExtended Developer
[Android Q&A, Help & Troubleshooting] raitchison:
So there's an app I've been using for many years: Simple Checkin for Foursquare

It's essentially a lightweight app/client for the once-popular Foursquare location checkin service.

The app has been abandoned by it's developer and hasn't been updated since 2016. I have searched but have not found another app to replace it (that works) so I still use it.

My daily driver for the past few years has been an LG V35 that's stuck on Android 8. It's actually been a great phone for me which is why I've kept it so long but is really starting to show it's age, some more modern apps are getting noticeably laggy.

I bought a new phone that came with Android 10 and it's good other than this particular app doesn't work at al. When I install (or launch it after clearing data) I'm given a warning that the app is designed for an older version of android and may not work properly before it prompts me to log into the Foursquare service, once that part is completed the app just crashes. Any time I try to launch the app after that it crashes immediately (never even loads the UI).

I've tried this on 2 different Android 10 phones and it's the exact same result. The app works fine on both Android 8 and Android 9.

I'm wondering if there's some kind of workaround for this problem or if I'm really stuck here. I have reached out to the developer of the app and he told me that he's not working on this app anymore and has no plans to update it.

Thanks in advance
[Android Q&A, Help & Troubleshooting] blackhawk:
Which phone?

The ancient freeware WPS office runs on my N10+'s Android 9 and 10. 10 hasn't caused many issues except it gutted Karma Firewall's valuable logging feature. On Samsung's at least scoped storage isn't fully active and Samsung has greatly modified Q to maintain functionality and the UI.

One reason I'll never load Android 11🤣

Overlay apps generally crash on Q...

Try checking all settings on the app.

Check accessibility permissions, does it need Administrator permissions?

Clear system cache and app data.

Try disabling the internet and see if it loads.

If so then find which app is diming it out and firewall block it.

Try temporarily disabling Google play Services.

Playstore may be another trouble maker.

Try reinstalling it with internet disconnected.

See what apks popup (running services/app cache) when you try to load it as that may give you a clue to the perp apk.

Play with it... may be a dead end or not.
[Android Q&A, Help & Troubleshooting] raitchison:
Thanks, I'll try that.

FWIW the two Android 10 phones I've tried are a Motorola One 5G Ace and a Unihertz Titan
[Android Q&A, Help & Troubleshooting] blackhawk:
Try using Apk Export to copy it. This is app I use, freeware.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Addy-95:
​

*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned

crDroid is designed to increase performance and reliability over stock Android for your device

also attempting to bringing many of the best features existent today

Features:: Click Here

Flashing Instructions:: Click Here (Thanks to @mukesh22584 )

Sources::

ROM: https://github.com/crdroidandroid

Kernel: Click Here

Download::

ROM: Click Here

Changelog:: Initial Build

GAPPS: Already Included

Visit official website @ crDroid.net

Donate to help our team pay server costs

crDroid Community Telegram

crDroid Updates Channel
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] ShevT:
Hi.

Device tree for "hotdog" are you using branch 11.0?