yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10] Zirila:
no luck so far.

I reinstalled TWRP before dirty flashing updated rom, but I get the following errors:

(in my case, old LOS was now installed and active on B)

I reinstalled TWRP to ramdisk, then tried to install new LOS.zip, this is the result:

Active Slot: B
Flashing A/B zip to inactive slot: A
Step 1/2
Step 2/2
Error applying update: 5 (ErrorCode::kPostinstallRunnerError)
Updater process ended with ERROR: 1

When I manually switch to Slot: A with fastboot, i get:

Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Active Slot: A
Flashing A/B zip to inactive slot: B
Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended with ERROR: 1

After these attempts I tried to install new LOS from scratch, wiping and formating all data, after a few attempts I got it starting, a new default encryption was set up for /data.

I then tried to restore my old LOS /data partition from my previous backup, but then the ROM loads infinitely.

I still found absolutely no working method of dirty flashing a new LOS version. I start to believe there is no way to keep data on updates beside 3rd party tools that backup each app individually (which always misses a few things in the end..)
[Redmi Note 10] Fire1511:
Can I install on redmi note 10 5g?
[Redmi Note 10] Subhan.:
Well sorry that you had to face that

But from this version you will be able to dirty flash and I'll keep that covered I also have to dirty flash to test the roms

Also I will suggest to use LOS recovery tbh

You will face the twrp issues for almost all roms

So its better to stick with the rom recovery

If you need twrp you can use the fastboot boot command
[Redmi Note 10] Zirila:
I finally managed to "dirty flash" to the latest version.. but that was rather a clean flash.

I tried installing the latest LOS version after clean flashing MIUI and that alone was very adventurous with many a/b errors and again clean flashes.

but in the end I was able to boot the latest LOS rom and it could set up default encryption keys for /data and stuff.

After that, I restored my TWRP nandroid backup from the previous LOS rom. not all, just the /data partition.

So I had: clean, latest LOS rom + my previous /data.

It didn't start at first (loaded endlessly) but I found out that the problem was Magisk with my signature spoof module, which was tailored for the previous LOS rom version. I build one for the new version and replaced the module (updated services.jar in /data/adb/modules/sspoof). Then it finally booted up completely.

However, many system settings were reset, so I had to manually adjust them again. But that wasn't so painful, as losing my data.

a few things I noticed immediately after it started up:

with the latest version the Quick Panel has suddenly only 2 lines of icons in it's most dropped down state. before it was 3 lines (that was better imho). a few icons are missing too that were there before, something like "black and white for reading"-icon.

next thing I checked out was exFAT support, and indeed, this version got it covered. I wiped my ext. sdcard and inserted it again, the rom automatically formated it as exFAT (it did fat32 before). great!

unfortunately, USB Debugging is still always auto-enabled on every boot, and when you connect to the PC it always asks for USB-debugging authorization. as mentioned earlier I consider that as security risk - this still needs fixing.

otherwise, I'm happy it's working now. just too bad for the amount of time to get there.

ah and yes.. you might be right, I'll try LOS recovery next time.. I'm just not sure whether it works so well with installing magisk and I want to make nandroid backups, but if that also works with fastboot twrp, then I'll give it a try.

when I've already TWRP recovery installed, how am I supposed to get LOS recovery back? Re-flashing the los rom.zip almost certainly leads to a/b flash errors in TWRP... is there a way to extract only the los recovery img that I can flash?
[Redmi Note 10] Subhan.:
Well I wanted to release it with a user build but I had some issues in building the user build so that will be a bit late but it will be there soon

I actually have my exams starting so thats why I rushed the release a bit...

And yeah I made a bit of qs panel tweaks..

Icons are missing? Oh well will check that too hopefully will be be fixed by next build
[Redmi Note 10] Subhan.:
And you can flash los recovery from the main post
[Redmi Note 10] Zirila:
no problem, exams go first. I'm happy about any fixes in the future, though :)

Ah! I should have remembered that, thanks for the hint
[Redmi Note 10] shadowstep:
THREAD CLEANED

Just a friendly reminder to keep it civil, on-topic and refrain from putting fuel to fire by responding to posts that you think are offensive or hateful. Just report if you feel something isn't right and let us take care of it for you, so that we can make your experience on the forum better. :)

Regards,

shadowstep

Forum Moderator
[Redmi Note 10] Akshay Bhai Delhi:
This rom has poor Ram management issues. ( Games closes from background without a seconds )

Battery is not bad . But still need more improvements.
[Redmi Note 10] Subhan.:
Ok I'll check those stuff again once after I am done with my exams

Hopefully it will be fixed in next update
[Redmi Note 10] machotom:
Anyone experiencing calling issues with this rom? I installed it yesterday, previously I was on 12.0.4 global rom. Whenever somebody calls me, the screen remains black if it was locked before and I can't pick up the call. If the screen is not locked, then the phone rings but I can't see the dialer app showing the call screen, cannot do anything. I can make calls but still cannot see the dialer app with the calling related buttons. Thanks!
[Redmi Note 10] Subhan.:
You have to set the phone app as the default phone app from settings first

Then the call screen will appear
[Redmi Note 10] machotom:
Lol that was an easy fix thanks :)
[Redmi Note 10] Zirila:
I evaluated this issue a bit further.

it seems this feature currently *only* works, when the phone has sim-lock AND screen-lock turned off. Then the phone starts automatically and boots up completely to the homescreen. if then the alarm clock starts, it is also playing the alarm sound.

it doesn't do so if you have either sms-lock or screen-lock turned on. it seems to be necessary for the alarm clock to work, that the phone boots up completely.

now the question is:

is this normal behaviour? or should it also work when the phone boots up only to the sim-lock screen?

I think it doesn't make much sense if it only works on a phone that is completely unlocked, nobody has that..

so I guess this is maybe an issue that needs also fixing *if* official lineageos versions work also on locked phones. (I don't know, someone with a phone with official lineageos needs to tell us)
[Redmi Note 10] Zirila:
regarding the alarm clock, i quote something from the AOSP FBE documentation:

FBE and Direct Boot isn't that new in 2021, but it seems like it is actually the problem with the alarm clock in this LineageOS version.

Probably, the alarm-clock app isn't Direct Boot aware or is not available in Device Encrypted (DE) storage, and therefor can't ring the alarm upon boot until the user would enter the credentials to unlock the userspace and data.

@Subhan. maybe you can take a look at this if you find the time, I guess this would work if it gets rolled out correctly, but you probably know more about the options than me
[Redmi Note 10] nierewa:
Two questions:

1. There are two versions of Lineage in OP, VANILLA Lineage and GAPPS Lineage.

Whats the different?

2. Can I use TWRP 3.5.2 to flash Lineage?
[Redmi Note 10] Zirila:
1. Vanilla is clean, blank Lineage ROM without any additions. GAPPS lineage already includes google apps and services. (if you are experienced user, I'd recommend vanilla + microG, otherwise use gapps lineage, or vanilla without google if you don't need google stuff)

2. Yes. you can use nebrassys TWRP alpha, but there might be some trouble installing/updating ROMs as it's still not fully working.

Read this:

https://xdaforums.com/t/rom-11-0-un...mi-note-10-mojito-sunny.4285859/post-85231083

and if you don't want to install LOS with TWRP you also might try installing LOS with fastboot and this script:

https://xdaforums.com/t/tool-flash-recovery-roms-through-fastboot-mojito.4300957/
[Redmi Note 10] nierewa:
Ok. Thank's.

It says: 1. Extract Fastboot OTA Tool. Put the ROM zip in it's root.

ROM is meaning LineageOS.zip?

Does the bootloader remain unlocked?

I made a backup with twrp from data partition before.

If I flashed Lineage, can I resore data with twrp or can this break something? Or does Lineage not start then?
[Redmi Note 10] Zirila:
of course, lineageos is your chosen ROM, therefor rom zip is lineageos.zip.

bootloader remains always unlocked until you chose "clean and lock" with MiFlash tool.
[Redmi Note 10] Zirila:
if you make a backup of MIUI data partition, you can't restore this to a LOS data partition, these are 2 different ROMs.

even backup up and restoring data partition of only LOS is tricky. you can find infos about that in the TWRP thread.
[Redmi Note 10] Subhan.:
Ok so I def will look into it and if I find a fix i will def add it but it wont be included in this update instead the one after this update

For the next build, there are some optimizations, partition size for flashing gapps, microg or the recovery related zips, aptx etc
[Redmi Note 10] Zirila:
I'm excited for anything that improves the situation :)

do you plan to provide a flashable microg zip for spoofing and flashing the apps?

i think the most wanted features currently are working methods for troubleless upgrading and a video recording fix.
[Redmi Note 10] Subhan.:
1)(This update) This time I will make sure the dirty flash works I will do a dirty flash myself first from the last release(but with Los recovery)

2)(Next Update) I have an idea but that might take some time(a dev suggested me to add anx in Los but I want to keep los as simple as possible)

So will check if any part or libs from anx can solve the video recording and will only add that

(No eta)I will try to check the micrgo spoofer too but well that might take time
[Redmi Note 10] Zirila:
alright!

I'd currently upgrade using TWRP or fastboot flash, but if it works with LOS recovery it should work with TWRP too (i hope). otherwise, flashing LOS recovery isn't that much of a deal either.

hm I think, it would still be better to provide a real clean vanilla image of lineageos and try to provide everything else as additional, flashable (magisks) .zips. some people might not trust the xiaomi proprietary camera libs if they were integrated into the vanilla image. that way users could decide between clean ROM and working camera. Though, I still expect the camera to work out of the box after some firmware upgrades in the future and that all this isn't necessary anmore.

if lineageos goes official anytime in the future, lineage.microg.org would automate the spoofing process without anyone needing to do extra stuff, that would be really cool too. as long as it's unofficial we can spoof it ourself with haystack and maybe provide a .zip for magisk for each update.
[Redmi Note 10] nierewa:
I flashed LineageOS with the Fastboot scribt.

Now the recevery isn't TWRP anymore but PE Recovery.

Can I reflash TWRP like explained in Teamwin tread
[Redmi Note 10] Zirila:
you always need to reflash any 3rd party recovery (like TWRP) after flashing ROMs. First fastboot.exe boot twrp.img, then install it to ramdisk. why is that so? read this once to understand:

How A/B Partitions and Seamless Updates Affect Custom Development on XDA

You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?

www.xda-developers.com
[Redmi Note 10] nierewa:
Ok. Now I'm happy :D
[Redmi Note 10] Subhan.:
Changelog (21/07/21):

• Dropped gapps variant

• Switched to User builds

• Increased system partition's size

• Included TWRP 3.5.2

• Set props for Rounded Gboard(If you install Gboard)

• Setup required props for userspace LMKD

• Switched Skia rendering backend to Vulkan

• Enabled force triple frame buffers

• Added bluetooth aptX blobs from redfin
[Redmi Note 10] Zirila:
reporting back after upgrading to this version.

I had LOS version of June installed along with TWRP 3.5.1 (both on A slot) and after excessive backups I tried upgrading by dirty-flashing to this LOS version of July.

Now I know from previous attempts, that LOS Recovery seems to be working better than TWRP for upgrades, my first step was therefor flashing LOS Recovery, overwriting TWRP.

I first thought I might try MPK99 custom ROM fastboot flash install script, but by the date trying, it was already abandoned due to (unknown?) technical difficulties. So I stick with recovery installation method.

I upgraded via LOS-Recovery and that worked just fine. I rebooted to recovery again, and it started up TWRP as it is part of LOS-rom.zip this time (I would still prefer LOS-recovery getting shipped with the ROM for real vanilla, though)

After rebooting to system, the first start finalizes the installation, and this is the -first time ever- that an upgrade successfully installed itself from previous Slot A to Slot B without troubles. After first ROM start and a reboot to TWRP all errors shown right after the upgrade in tWRP were gone. Fine!

Luckily, this time, the old magisk signature spoofing module from previous LOS version still works without needing to run haystack again, so actually everything seems to be working out of the box after upgrading and all apps and data is still there and working.

So far so good!

Now, a few things I noticed:

- USB-Debugging is still activating everytime after booting, despite disabling it in the dev-options (rebooting while connected to PC with usb cable -> automatically always establishes usb-debugging connection)

I'm not entirely sure if this is supposed to be fixed in this version by switching to "user builds". Or maybe it's a settings issue when upgrading from previous lineageOS version? maybe you can tell me.

- quick panel icons are still lined up by 2 rows instead of 3 rows in previous versions and some original LOS icons seem to be missing. (again, I'm not sure if this was supposed to be fixed in this version, or whether my older settings overwrite any changes made)

- I've got a phone with 64GB internal memory. On previous and latest version, System (all Slot A+B) takes already 19GB of space, leaving only 45GB free space for internal storage.

Is this supposed to be normal, how many space does your system take and how many space do you have available as free storage (excluding external sd cards)? It looks a bit much for me..

- camera bug still exists but I didn't expect otherwise. I also did not test any of the new kernels yet, but I think they won't change anything yet.

if I found something else I'll post more.

Thanks so far for the updates
[Redmi Note 10] MPK99:
Do you fond to use telegram ?

If so, you can contact us (literally all the devs) as we're available there 24x7 interacting with community users in runtime.

Here's the Redmi Note 10 Community

If you have any queries, tag us there & we'll reply to you instantly.
[Redmi Note 10] Zirila:
I'd join but sorry I'm not using telegram, I intentionally don't use any messengers that are tied to phone numbers. Maybe if you have a matrix channel/bridge. Or anything similar.
[Redmi Note 10] pnplusplus:
Thanks for the rom. Can you add 3 swipe screenshot?
[Redmi Note 10] Zirila:
been a few days on this updated LOS version now, and one thing really stands out.

battery performance was great before, but this version is phenomenal regarding battery life.

I'm on my 3rd day with average usage without charging and still have 50% battery left.

before I had 40-50% battery after 2 days. so it seems like something (vulkan switch?) is really pushing the battery life in this update.

coming from an old phone that only lasted for half a day, this is mind blowing.
[Redmi Note 10] Subhan.:
Welll about the usb debugging bug it only goes away with clean flash

I dirty flashed and clean flashed a no. of times to test and it went away only in clean flash

I kinda forgot about the qs panel....

Will try to fix in the next update

Afaik all custom roms on rn10 take about 19-20 gb in system

Well I will try to work on cam bug There is some other cam related background stuff that I have to work on too
[Redmi Note 10] Angenios:
I'm a newbie and I don't understand one thing: when I install this custom ROM, root access is already enabled? If yes, how do I install universal fix?

Thank you for your time.
[Redmi Note 10] Subhan.:
Nope, You'll have to root it with magisk yourself and then flash universal magisk there
[Redmi Note 10] Angenios:
And in order to install Magisk I only need to install it through TWRP, right? If yes, in what order do you suggest?

1. Install TWRP -> 2. LineageOS -> 3. GApps -> 4. Magisk -> 5. universal fix

Is it correct?

Thank you for your answer.
[Redmi Note 10] Zirila:
Ah, too bad about the clean flash and usb debugging.

Well, then I'll have to do a clean flash at some point in the future, I don't know when I'll try that yet. Big ups to you for testing and finding that out.

phew, 20gb system is pretty much, but if this is the new normal, well, it's what it's like...

no prob about the qs and cam bug, still happy about every feature and security update that you can bring up to the table!
[Redmi Note 10] Subhan.:
Well so about the built in twrp

Well first I wasnt able to compile user builds(Lineage doesnt have user builds officially)

With some changes I was able to compile but then wasnt able to boot to recovery so then I had two option either to go with userdebug builds or user builds with twrp

And well then I decided to go with user builds and builtin twrp
[Redmi Note 10] Nyakov:
I am on lineage-18.1-20210720-UNOFFICIAL-mojito-vanilla.zip

Just after bootloader unlock I flashed LOS recovery and then thru adb sideload I flashed zip firmware(it asked to reboot phone into recovery as part of flashing process)

Camcoder works fine, at x265 mode at least. I dont see real need for native cam app from xiaomi at this point.

Have problem with SD card formatted as extension for system storage.

After boot I get message that SD card is not connected. And I cannot see applications that was moved to SD card. Then it connects at some point by itself (but sometimes not, and sometimes it looses SD card in normal use) and applications became available again.

It will be nice to see Fdroid integrated with root extensions and MicroG. It will be nice to have flashable zips for this.

I actually prefer native LOS recovery.
[Redmi Note 10] Subhan.:
Well its either user builds with twrp or userdebug builds with los recovery

Rn I am considering of dropping twrp but will have to go with userdebug builds till I find a way to make los rec work in user builds but coz of a certain issue I might drop twrp
[Redmi Note 10] Zirila:
if next release is going to be a userdebug build, then I don't have to make a clean install anyway, as long as the usb debug option is still always on.

I wonder if it is possible to disable the default always-on usb-debugging option despite using userdebug builds? that way you could release userdebug and maybe we can still have usb-debugging disabled by default.
[Redmi Note 10] Angenios:
Hi, I've just flashed this ROM, alongside with Gapps nano and Magisk (which then I used for installing universal fix), but I've noticed that the proximity sensor is not working. Apps recognize that I do have a proximity sensor, but it doesn't work. I've tried with Phyphox and Sensor Test too, but it still doesn't work.

Oh, anyway, could you explain me how to get the native MIUI camera, please? I'd like to get it back since it worked fine for me.

Thank you in advance, have a nice day.
[Redmi Note 10] StaryMuz:
The proximity sensor works, it's just not very responsive. The phone has to be in a vertical position and even the point where to approach the phone is very limited.
[Redmi Note 10] Angenios:
Hi, I have to report a glitch: if I enable the option to display the network upload and download MB/s, it will end up being at the center right on the notch, thus I'll be unable to see it unless I rotate the screen. I suggest you to move this icon to the left, just as it works for MIUI users.

Thank you in advance for your time.
[Redmi Note 10] Zirila:
I have noticed the same problem sometime ago, but unfortunately this is a LineageOS problem imo. You'd have to report this issue to LineageOS issue tracker instead of the port-thread here. Maybe they'll fix it if it becomes enough attention.

@Subhan.

is it possible to make an update with latest security patch level of sept?
[Redmi Note 10] Subhan.:
Welllll I actually was gonna release with aug sec patch but waited for oss vendor (By Zidan) but that has 2-3 bugs(Not that big) that gonna get fixed soon

I will try for the sept security patch if I am able to get safetynet passed on that one before my server expires

Else will have release with aug sp
[Redmi Note 10] Angenios:
I have to report a bug: the inline controller of my headphones does not work well in this ROM. I can assure that it is not a problem of the headphones or of the smartphone, since in MIUI it was working and these headphones are new and work on other devices as they should. I can only pause and resume the music, but I can't increase or decrease the volume.
[Redmi Note 10] ShuvoGG:
Sending 'recovery' (131072 KB) OKAY [ 3.199s]

Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')

fastboot: error: Command failed

WHY SHOING THIS
[Redmi Note 10] StaryMuz:
Everything has already been written here, read it.

Redmi Note 10

The Redmi Note 10 is a 6.43" phone with a 1080x2400p resolution display. The Qualcomm SDM678 Snapdragon 678 chipset is paired with 4/6GB of RAM and 64/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 13MP. The battery has a 5000mAh capacity.

xdaforums.com

Our phone has no recovery partition. Recovery is now part of the boot.
[Redmi Note 10] OldNoobOne:
removing gapps from system apps and then will it boot after wiping cache partition?
[Redmi Note 10] MPK99:
Ofc. Why not.
[Redmi Note 10] OldNoobOne:
May I have your t.me id sir? I had some spooky questions :D ..if you dont mind sir
[Redmi Note 10] Subhan.:
But why

I mean Los is already Vanilla so no gapps
[Redmi Note 10] OldNoobOne:
If Gapps is BuiltIn into System Apps then if when we remove Gapps it is like removing system apps right? so thats why i thought when after removing built-in Gapps & clearing cache partition will the phone boot?

P.S- LOS is just too vanilla, it doesnt even have a button to reboot/poweroff from QS-Panel lol but will do for now coz other roms are pretty tough to flash on RN10 [Example-Derpfest got twrp error 1 on (dynamic_partitions_op_list)] and many Andro11 Roms seem to have bugs so I have to wait for RR11 (Resurrection Remix) maybe.
[Redmi Note 10] MPK99:
Install usb drivers & use my fastboot OTA tool.
[Redmi Note 10] OldNoobOne:
uhh..im giving up on derpfest but lineage 18.1 had booted well, derpfest also boooted on RN10 but the Lineage Recovery wont go and this A/B slot thing is not simple to boot. But llineage 18.1 is working well on RN10 . Will Fastboot OTA Tool help? Thanks in advance.
[Redmi Note 10] alonsoj636MW:
Can we expect another update?

I'm tired of all roms and i want something simple for basic usage

Thanks
[Redmi Note 10] MPK99:
I've re-owned lineage thread...

Will drop los by couple days. Crd by this week.
[Redmi Note 10] alonsoj636MW:
crDroid ... Great ! Thanks!!