I flashed TWRP via adb & booted into TWRP recovery via adb then:Hi folks,
just bought a new Note 11 NFC and would like to use LOS on it, waiting now for 168 hours to unlock it
Got confused by the link in the first posts pointing to a collection of boot loaders, none of which being an "official" LOS boot loader, but TWRP versions, SHRP, Orange Fox ,etc.:
Don't know which one to use and I recall soft bricking a Note 8 some time ago with TWRP - I had to use the official LOS boot loader first and only after writing LOS I was able to use TWRP. Apparently TWRP didn't know how to clean & handle the stock ROM partitions on that Note 8 when writing LOS on it.
Recovery for Xiaomi devices - Browse /spes at SourceForge.netList of relevant recovery in one placesourceforge.net
Basically I only need some backups from time to time and maybe installing some zip images from the bootloader . The simplest working TWRP would suffice for the long run, after installing LOS .
Still don't know with what to start, fearing I'll soft brick the phone - for which I couldn't even find a matching Stock ROM yet .. it's MIUI 13.0.3 - EU ... so I could repair it (flash Stock back).
Any help appreciated on the first boot loader to use.
Download link is dead too.
Thanks for the pointers. I'll use one of the TWRP versions you mentioned.I flashed TWRP via adb & booted into TWRP recovery via adb then:
Format data > Reboot recovery > Install ROM > Reboot recovery > Install Gapps > Reflash TWRP (if you needed) > Restart to system
In terms of TWRP version, twrp_3.6.1-spes, twrp-3.6.2-12.1-21.06.22 or higher should be fine. Anything above 3.6.0 I think is OK. Jabiyeff & Dblenk9 do 3.7* versions which should be OK too.
This link should also help: https://forum.xda-developers.com/t/...p-3-7-0-for-redmi-note-11-spes-spesn.4507819/
I took the images from the Telegram page:
Not sure about the latest build. I flashed last Nov/Dec so took the previous gapps build, tagged lineage-20.0-20221119 but with a build date of 16112022 when installed.I took the images from the Telegram page:
Which points to: the lineage-20.0-20221119* files on sourceforge.
Coduxer in Coduxer Hole#LineageOS #OSS #Spes #Spesn #T #Tiramisu #Microg LineageOS 20.0 Unofficial | Android 13 Updated: 19/11/2022 ▪️Gapps | Vanilla | MicroG ▪️Support Group ▪️Screenshots • November Android and Vendor security patch level. • Update kernel and blobs from SPESINGlobal V126.96.36.199-A12 (latest). • New...t.me
Didn't know that there are updates - thought the developer abandoned it ...
Thanks for the feedback. On the 20221119 build I did notice powering screen on/off sometimes requires 2 presses if I do it too quickly the first time but found that if I used the centre of my thumb to press, rather than thumb tip, it seemed happier. Maybe it takes just a fraction of a second longer to fully press rather than tap it. I don't use the fingerprint or d2w. The stock camera was OK but I switched to OpenCamera. I tried a few GCam mods but they crashed when selecting video.@mspL4
I started with the lineage-20.0-20230211* images and I can say all is working well. Meanwhile @Bareny posted the changelog.
There are some really bad issues with the power button / fingerprint sensor that drove me crazy. I was at the point of flashing the stock ROM back and sending the phone to Xiaomi for repair, considering the power button faulty.
It's only now I learned that these are known issues:
[ROM][REDMI NOTE 11/11 NFC - SPES/SPESN] PixelExperience [AOSP]PixelExperience for REDMI NOTE 11/11 NFC [spes/spesn] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum...forum.xda-developers.com
[Magisk Module][5X] A1 ROM Port Fingerprint Reader-as-a-button FixThis module aims to fix the Fingerprint reader-as-a-button bug found in the Mi A1 ROM Port for the Mi 5X. Click on the Downloads tab for the file itself :) Installation: Flash this module in Magisk Manager or with TWRP. Enjoy! XDA:DevDB...forum.xda-developers.com
... unfortunately I couldn't find the Magisk Module for inspiration - to try a workaround (a scripted fix at boot).
I was also unable to completely disable the fingerprint sensor (which I frankly don't need at all + the design is flawed badly - rubbing the finger on that button will destroy it really fast) by trying to follow these:
Completely disable the fingerprint sensorI don't really like all the hype about the fingerprint sensor, I'd rather like to have it killed down, so that it doesn't register any fingerprints. On a desktop Linux I'd simply modprobe -r theandroid.stackexchange.com
Disable Fingerprint Sensor - Android EmulatorHow to disable Fingerprint sensor in Android Emulator? I could not find any option in settings window or config.ini file. By default, all the emulators above SDK 23 have fingerprint support. I wouldstackoverflow.com
The problem is that this version of LOS has the driver apparently builtin in the kernel and I couldn't unload it.
The actual issues described - finger print sensor not activated in settings / no fingerprint registered, just simple PIN security on lock screen:
First, long pressing the power button doesn't always launch the PowerScreen.
Then, activating LongPress For Torch doesn't work properly. At the first long pressing nothing happens and when releasing the button the screen turns on. Only on the second try the screen remains off and the LED is turned on.
Finally, activating Double-Tap to wake the screen (really useful to save the power button from premature failure) also doesn't work properly. Here I spent some time trying to understand the logic.
If I suspend the screen and immediately (first seconds) double-tap it, the screen will wake up.
After a few minutes double-tap doesn't work anymore, but there's a workaround.
If I touch (and keep the finger contact on it) the power button (just touch - no pressing) then the double-tapping works. Also, if I double tap and immediately touch the power button , the screen will awake.
So either by touching the power button I unsuspend the screen touch sensor, or touching the power button (fingerprint sensor) is gating/required internally in the SW logic for the screen to wake up.
A simple fix - maybe disabling the fingerprint sensor would correct these issues.
Then there is the camera sensors (smaller) issue. I don't necessarily need the wide angle camera, the main camera is sufficient and I can take some steps back if I need a "wider angle", but the macro one is really helpful - a pity that it doesn't work. Not sure why it doesn't work - the device drivers should be available, the Pixel Experience image looks to have all camera sensors working.
At last, one glitch that is maybe common with some other phones too - Bluetooth and WiFi 2,4 GHz are not happy together. BT will disconnect the WiFi 2,4 GHz if the latter was already activated. I experienced this issue also on an older Samsung S3 Neo (Qualcomm SoC) with LOS16/17.
• Android QPR 2.
• March security patch.
• Update blobs from SPESGlobal V188.8.131.52-A12 latest, using A11 kernel.
• Fully fix goodix fingerprint issues (long press on power button and more issues, now all fixed).
• Allow enable/disable ripple effect on unlock. ripple effect also disabled by default now.
• Tweak device brightness settings.
Can you dirty flash over 221119 build? Would I have to reinstall Magisk & GApps?New update from yesterday, claiming to solve the fingerprint/power buttons problems mentioned above..
Download here: https://sourceforge.net/projects/lineageos-spes/files/Roms/
I flashed the latest LOS update with TWRP, had to reflash Magisk and also reinstall TWRP all these before rebooting.dirty flash yes according to the author in the telegram group.. magisk probably reinstall and gapps is included afaik
Give Graphene Camera a chance, too (mainly 'cause it seems more advanced/updated than OC in andoid camera libs exploiting):I've also switched to OpenCamera, mainly because the LOS Camera App wasn't using the flash to focus in darker environments, even if Flash was set on Auto or On.
I'll have a look when I get some extra time. I've used OpenCamera for some time now and got familiar with it, pretty "advanced" I must admit and working fine.Give Graphene Camera a chance, too (mainly 'cause it seems more advanced/updated than OC in andoid camera libs exploiting):
Releases · GrapheneOS/CameraModern camera app focused on privacy and security with QR & barcode scanning. - GrapheneOS/Cameragithub.com
*** Disclaimer ***
I am not responsible for any damage you made to your device.
You have been warned.
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.LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
LineageOS 20.0 (latest)This ROM does not come with GAPPS preinstalled! If you want to have a small set of Google Apps including the PlayStore, you have to install them manually.
Builds are now signed
Fix video playback
Fix camera video recording
Fix screen recording with sound
LineageOS 20.0 development has not finished yet and is at constant change. Features may added or removed upon later releases.
This is an alpha version, it will have bugs.
Wifi | RIL | Mobile data | GPS | Camera | Screen recording | NFC
Bluetooth | Fingerprint reader | Sound | Flashlight
Device shown as not certified (PlayStore)
Display may flicker
System Updater (You have to check for new builds manually here on XDA for now)
- Android OS Version: 13.0
- LineageOS Version: 20.0
- Security Patch: October 2022
- Build author/device maintainer: hecaex
- Device: Xiaomi Redmi Note 11 (spes/spesn)
Thanks I apprecitate that. I'm currently using the rom as my daily driver beside of the obvious issues which I hope to have solved around next week.Thanks a bunch hecaex, can't wait to try it next week despite the lack of kernel sources. I appreciate your efforts.