Android 11 beta

[fards]

New build.

Still A11 beta 2

http://bigota.d.miui.com/20.8.12/miui_UMI_20.8.12_9537d44452_11.0.zip

 

[pelayogrgi2c]

With xiaomi.eu rom with android 11 impossible to install magisk. Does anyone have the chinese rom with android 11 and is it capable? to know if it is the fault of masgisk or xiaomi.eu

 

[fards]

With xiaomi.eu rom with android 11 impossible to install magisk. Does anyone have the chinese rom with android 11 and is it capable? to know if it is the fault of masgisk or xiaomi.eu

Magisk.
Read the threads on magisk to see how much will have to change for Android 11

 

[fards]

http://bigota.d.miui.com/20.8.13/miui_UMI_20.8.13_6f7b639d70_11.0.zip

Listed as weekly build.
Seems stable although it looks to me like they've reverted to an A10 framework. Couple of my apps that didn't like A11 due to an API change are working again after using this. The apps didn't update.
Something odd going on.

 

[letfly]

http://bigota.d.miui.com/20.8.13/miui_UMI_20.8.13_6f7b639d70_11.0.zip

Listed as weekly build.
Seems stable although it looks to me like they've reverted to an A10 framework. Couple of my apps that didn't like A11 due to an API change are working again after using this. The apps didn't update.
Something odd going on.

I tried 20.8.7, 20.8.12 and 20.8.13, I dont know why I always get error 7.

 

[fards]

I tried 20.8.7, 20.8.12 and 20.8.13, I dont know why I always get error 7.

Can you try to get logs from twrp? We can see what's going on then.

 

[fards]

20.8.13

Developer option to boot a dsu works with this build.

Takes a while to download the latest gsi from Google, but it then gave me option to boot into it and it booted beta3 aosp..

Obviously fingerprint and few other bits not working, and it reverts back to miui on reboot.

But a nice easy way of trying aosp build...

 

[B!GBOY]

20.8.13

Does the screen always switch back to 60hz on the china beta rom?
I'm using EU weekly builds and have this problem: After every boot i have to switch to 60 and then back to 90 to set the refresh rate to 90

 

[fards]

Does the screen always switch back to 60hz on the china beta rom?
I'm using EU weekly builds and have this problem: After every boot i have to switch to 60 and then back to 90 to set the refresh rate to 90

Or drops to 60 and sticks after reboot.

Neither situation is correct.
It's supposed to be dynamic and changes to 90 when needed..

 

[letfly]

Can you try to get logs from twrp? We can see what's going on then.

I attach log here. 20.8.13 with error 7 and 20.8.6 is normal.

 

[B!GBOY]

Or drops to 60 and sticks after reboot.

Neither situation is correct.
It's supposed to be dynamic and changes to 90 when needed..

yes, it sticks to 60 and I have to switch to 60 and back to 90 to fix it. Are you sure about it being dynamic? I read something about samsung being the first one to implement that in the new note 20.

I attach log here. 20.8.13 with error 7 and 20.8.6 is normal.

That looks familiar that's the problem i faced when trying this rom post #100 I gave up and switched to xiaomi eu builds, at least they work

 

[fards]

yes, it sticks to 60 and I have to switch to 60 and back to 90 to fix it. Are you sure about it being dynamic? I read something about samsung being the first one to implement that in the new note 20.

It even says it on the fresh rate setting screen!

 

[fards]

I attach log here. 20.8.13 with error 7 and 20.8.6 is normal.

Those aren't logs, they are screen shots. Liga are obtained via adb.

They also show that twrp didn't decrypt, that's the reason nothing flashed. None of the partitions were mounted as a result. K

Did you boot twrp or flash it? . If you fastboot boot twrp then it handles fbe and can decrypt fine.
If you flash twrp it doesn't decrypt.

Using ADB you can adb shell twrp decrypt (and the correct password, there's instructions on twrp.me on how to use the command and convert a pattern to password). However if you've flashed twrp it still won't work.

I *think* that the stock recovery has newer fbe handing, that needs updating for Android 11 in twrp (along with dynamic partitions).
So fastboot boot twrp.img works for me

 

[letfly]

Those aren't logs, they are screen shots. Liga are obtained via adb.

They also show that twrp didn't decrypt, that's the reason nothing flashed. None of the partitions were mounted as a result. K

Did you boot twrp or flash it? . If you fastboot boot twrp then it handles fbe and can decrypt fine.
If you flash twrp it doesn't decrypt.

Using ADB you can adb shell twrp decrypt (and the correct password, there's instructions on twrp.me on how to use the command and convert a pattern to password). However if you've flashed twrp it still won't work.

I *think* that the stock recovery has newer fbe handing, that needs updating for Android 11 in twrp (along with dynamic partitions).
So fastboot boot twrp.img works for me

I only boot twrp. Twrp does not decrypt but it can flash previous rom like 20.8.6 and before, but newer rom can be flashed.

 

[B!GBOY]

Those aren't logs, they are screen shots. Liga are obtained via adb.

They also show that twrp didn't decrypt, that's the reason nothing flashed. None of the partitions were mounted as a result. K

Yes Data is not mounted but that's not the reason the flashing fails. Mine was able to decrypt data but still couldn't flash system.
The reason why in the other screenshot everything fails to mount is that after one failed attempt those partitions do not exist. they get created dynamically when flashing rom.

*me talking as if i understand this stuff

on another note i flashed the recovery and it is able to decrypt data but only with a pattern saying just incase

If i ever messed up my phone will try china beta and provide adb logs

 

[letfly]

Yes Data is not mounted but that's not the reason the flashing fails. Mine was able to decrypt data but still couldn't flash system.
The reason why in the other screenshot everything fails to mount is that after one failed attempt those partitions do not exist. they get created dynamically when flashing rom.

*me talking as if i understand this stuff

on another note i flashed the recovery and it is able to decrypt data but only with a pattern saying just incase

If i ever messed up my phone will try china beta and provide adb logs

Tonight, I will try adb to get log too.

 

[fards]

I only boot twrp. Twrp does not decrypt but it can flash previous rom like 20.8.6 and before, but newer rom can be flashed.

Without logs it's really just guesswork.

 

[fards]

Yes Data is not mounted but that's not the reason the flashing fails. Mine was able to decrypt data but still couldn't flash system.
The reason why in the other screenshot everything fails to mount is that after one failed attempt those partitions do not exist. they get created dynamically when flashing rom.

*me talking as if i understand this stuff

on another note i flashed the recovery and it is able to decrypt data but only with a pattern saying just incase

If i ever messed up my phone will try china beta and provide adb logs

Nope.. the partitions aren't created, they already exist.
They should get resized dynamically. Unless using an A/B system and Xiaomi aren't using that.

What would be good would be too bypass the silly beta check and use stock recovery.

 

[B!GBOY]

Nope.. the partitions aren't created, they already exist.
They should get resized dynamically. Unless using an A/B system and Xiaomi aren't using that.

not according to dynamic_partitions_op_list:

# Remove all existing dynamic partitions and groups before applying full OTA
remove_all_groups

# Add group qti_dynamic_partitions with maximum size 9126805504
add_group qti_dynamic_partitions 9126805504

# Add partition system to group qti_dynamic_partitions
add system qti_dynamic_partitions
...
# Grow partition system from 0 to 3947122688
resize system 3947122688
...

and also google's documentation:
"When applying an OTA, dynamic partitions are automatically created, resized, or deleted as needed. For A/B devices, there are two copies of the metadata, and changes are applied only to the copy representing the target slot."

What already exists is the super partition. That's also why if it fails and the recovery shows the mount error you can afterwards flash another rom and it will flash without a problem.
For example if you try china dev and it fails it is possible to try eu beta afterwards without doing anything else and there will be no mount errors

 

[fards]

not according to dynamic_partitions_op_list:


and also google's documentation:
"When applying an OTA, dynamic partitions are automatically created, resized, or deleted as needed. For A/B devices, there are two copies of the metadata, and changes are applied only to the copy representing the target slot."

What already exists is the super partition. That's also why if it fails and the recovery shows the mount error you can afterwards flash another rom and it will flash without a problem.
For example if you try china dev and it fails it is possible to try eu beta afterwards without doing anything else and there will be no mount errors

Twrp doesn't use that file. It can't handle dynamic partitions