Develop Bugs

MIX 3 PE GSI fastboot flash succeed

https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Followed this, and the key is:
You must flash A/B GSI, not A only, though treble APP says it's A only!
I failed for flashed A only GSI before.

mansonstein said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Followed this, and the important things are:
1. Must flash A/B GSI, not A only!
2. Flash this just like Pixel "On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)"
I failed for flashed A only GSI before.
Click to expand...
Click to collapse
Can you report on what works and what does not? Seems you're the first person put a GSI ROM on the Mix 3, so congratulations.

audio, but can be fixed easily, and bt media also fixed. Now just double tap to wake
wifi camera...all work

mansonstein said:
wifi camera...all work
Click to expand...
Click to collapse
How's the camera quality (using gcam, of course)?

How so you restore your Mix3 to factory without fastboot Rom?

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
It's a good point

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
Don't know what do you mean, It just works. Using PE daily now

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
Now there are fastboot roms, only developer 8.11.8.
I thought I saw a stable previously, either I was mistaken or they removed it.
Xiaomi EU has released 8.11.8 also.
TWRP?

I just got my mi mix 3 today, unlocking the bootloader is telling me I need to wait 72hrs. At least that's better than waiting a month. Once that's done, I'm going to be flashing this ROM asap. @mansonstein is it still running well for you as a daily? Any issues/concerns/comments on how this ROM is running. And can you link to the PE ROM that you used specifically, there's a couple floating around.

mansonstein said:
Don't know what do you mean, It just works. Using PE daily now
Click to expand...
Click to collapse
How well does it work? What's the battery like without miui twerks. Which camera are you using.

Now, jut some small bugs on PE
1. touch fingerprint is just like ''Enter'' on PC keyboard when typing. can't change it with Button Mapper or other Apps.
2. No DT2W in kernel auditor.
3. Button mapper doesn't work when screen is off, can't play next track with volume button.

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
There is Chinese version, just change language to 中文 in MIUI.COM

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
james1089 said:
How well does it work? What's the battery like without miui twerks. Which camera are you using.
Click to expand...
Click to collapse
Battery is fine, but can't tell weather it's better than MIUI, Google Camera also works

May I ask what GSI rom are you using please?
I noticed there are things like Lineage OS or Omni rom and such.
Thank you!

kezzuki said:
May I ask what GSI rom are you using please?
I noticed there are things like Lineage OS or Omni rom and such.
Thank you!
Click to expand...
Click to collapse
I say this mix 3 stuff is gonna be fun, I know for a fact some devs are gonna buy this phone fook OPxx

So I did this, got PE to boot, and to let everyone know, at least with me, there are no fingerprint gestures in the gestures settings (ie swipe down to bring notification panel), the sound is distorted, and I can't seem to get signal above H+, where in MIUI I was getting 4G. I have the 6/128 version and located in Canada. Anyone else having issues? If so, what did you do?

mansonstein said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Followed this, and the important things are:
1. Must flash A/B GSI, not A only!
2. Flash this just like Pixel "On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)"
I failed for flashed A only GSI before.
Click to expand...
Click to collapse
Hi, but treble check shows it's a A only type of device. screenshot attached. Any idea why is it so??

dragon-tmd said:
How so you restore your Mix3 to factory without fastboot Rom?
Click to expand...
Click to collapse
james1089 said:
It's a good point
Click to expand...
Click to collapse
billamin said:
Hi, but treble check shows it's a A only type of device. screenshot attached. Any idea why is it so??
Click to expand...
Click to collapse
I know, that's why I flashed A only and failed, just flash A/B.

billamin said:
Hi, but treble check shows it's a A only type of device. screenshot attached. Any idea why is it so??
Click to expand...
Click to collapse
It's because MIX 3 is system-as-root device.
https://source.android.com/devices/bootloader/system-as-root
Google forced system-as-root for the devices shipped with Pie.
Before this change, only A/B devices were system-as-root and phh-treble was named a-only and ab, but now a-only device also can be system-as-root device.
You can check if your device is system-as-root by running "getprop ro.build.system_root_image" in adb shell. If it's true, it's system-as-root device.
So now
The img file named "aonly" is for device which has only one partition for system AND is not system-as-root device
The img file named "ab" is for system-as-root device (A-only and A/B insensitive)
Also Google says "non-A/B devices must keep the /recovery partition separate". This is why Mi MIX 3 has recovery partition even though it's system-as-root.

AndroPlus said:
It's because MIX 3 is system-as-root device.
https://source.android.com/devices/bootloader/system-as-root
Google forced system-as-root for the devices shipped with Pie.
Before this change, only A/B devices were system-as-root and phh-treble was named a-only and ab, but now a-only device also can be system-as-root device.
You can check if your device is system-as-root by running "getprop ro.build.system_root_image" in adb shell. If it's true, it's system-as-root device.
So now
"aonly" is for device which has only one partition for system AND is not system-as-root device
"ab" is for system-as-root device
Click to expand...
Click to collapse
So does it mean Mix 3 supports seamless updates with two copies of each partition??

Project Treble & S10+

So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:

I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.

Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.

Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....

Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.

NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.

uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's

NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.

uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho

Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]

thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.

sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.

NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value

thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename

NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting

vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.

In the meantime, is someone running GSI as a daily driver?

sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.

[REDMI7] [ONCLITE] LR.Team TWRP-3.3.0-REDMI7-CN-wzsx150

I have to tell you :This is the first working TWRP I've found. This os not my work. Just sharing it in Redmi7 Recovery section.
It contains English and Chinese only.
Download link: https://mega.nz/#!TpojlSIA!ymMSB9wBHiza9kSAzqO-8idkuv5mRsvMXQ5rno4Z-so
Redmi 7 special edition TWRP Chinese and English modified optimization version
build date: 2019.4.20
modell: red rice 7, redmi 7
developer: wzsx150
team name: LR.Team
Installation:
Unlocked bootloader required
Working ADB and FASTBOOT connection required
The usually way: with fastboot flash recovery redmi7.img command
after successfully process do not restart the device
type fastboot reboot (do not press enter)
press and hold the volume up button
now press enter
press and hold the volume up button until the fresh TWRP starts
Quote from the Chinese website:
pre-brush into the third-party rec, must unlock the phone! ! Again, the brush machine is risky, please be cautious!
1. This rec supports data partition automatic decryption , encrypted data can be used normally under rec. The official system defaults to encrypting data partitions.
2. This rec supports the official full-page card swipe, but it may cover twrp; when upgrading automatically, you can remove the checkbox of the setting > auto-restart option for easy operation.
3. The bootloader must be unlocked to be able to brush into a third-party rec.
4. Built-in advanced > root system / clear root function.
5. Built-in advanced > remove dm checksum and cancel the forced encryption function, through certain operations, you can remove the official data forced encryption (understand people naturally understand how to operate, because avb2.0 exists, this function may not be normal).
6. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc. (some functions may cause the system to fail to enter, carefully operate).
刷入第三方rec前，必须解锁手机！！再次提醒，刷机有风险，操作请谨慎！
1.本rec支持data分区自动解密，加密的data不用格式化也能在rec下正常使用。官方系统默认是加密data分区。
2.本rec支持刷入官方原版全量卡刷包，但可能会覆盖twrp；自动升级时，可以去掉设置>自动重启选项的勾选，方便操作。
3.必须解锁bootloader才能刷入第三方rec。
4.内置高级>root系统/清除root功能。
5.内置高级>去除dm校验和取消强制加密功能，通过一定操作，可以去掉官方的data强制加密（懂的人自然懂怎么操作，因为avb2.0的存在，该功能可能不正常）。
6.防止被官方rec覆盖的功能：root系统、签名boot、去除dm校验、取消强制加密等（部分功能可能导致进不去系统，慎重操作）
Source: http://www.miui.com/thread-23429227-1-1.html
Do not forget! And be aware of it! No one has commanded you to change your phone!
No one has forced you to do this. So, you take every step at your own risk! Full responsibility lies with you!

Awesome! Thank you so much! You Rock!

I installed and works!

MalyMikrus said:
I installed and works!
Click to expand...
Click to collapse
Of course it works. If it wasn't working, I wouldn't have shared it.

JulianJenner said:
Of course it works. If it wasn't working, I wouldn't have shared it.
Click to expand...
Click to collapse
have u try rooting the phone with this twrp?

Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.

Thanks !, I have to wait 15 days to unlock the bootloader, and try the twrp with miui eu, do you know if any developer is working in any kernel or rom? Regards!

JulianJenner said:
Yepp. My MIUI Stable is rooted now.
But, after Magisk19.zip you need a DmVerityForcedEncrypt.zip too!
https://mega.nz/#!6xpgQazL!RZALbnhhR8xEiri_7ljivVBZd2RhZYbQSmWd-tTgwtc
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
This wasn't needed for me.
I just fastboot flashed the twrp.img file, rebooted into recovery mode (aka TWRP), and then flashed the Magisk v19 zip file.
rebooted and magisk was installed properly, twrp is installed properly

Okay. That is good!
I think zip is needing if you flash stock miui rom, with this twrp...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.

Can you post the dt and source please?

Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.

JulianJenner said:
Dev.Team is the chinese LR.Team.They never give out information. Neither device tree nor other...they never share it.
I've mentioned source, where I found it (on first thread).
This is not my work, I just shared.
This is Recovery section of Redmi7. ...and this is a Recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.
Click to expand...
Click to collapse
yea, but to publish a thread in this 'development' section, you need to follow XDA rules, which means the source code has to be published as well

Ok.
I thought this recovery is an important thing for Redmi7 users...
If not...okay...delete this thread...or move to an indifferent section. No problemo...
小米MIX标准版4GB128GB银色MIUI10中国开发者9.4.25.

how can I flash stock recovery?? Where i can find stock recovery?

IczYn said:
how can I flash stock recovery?? Where i can find stock recovery?
Click to expand...
Click to collapse
On every stock ROM zip and on every stock TGZ file...

JulianJenner said:
On every stock ROM zip and on every stock TGZ file...
Click to expand...
Click to collapse
OK but why when i try download stock rom i cant do this?

Thread closed on OP's request.
LTT

Confused about TWRP

I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?

mankokoma said:
I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?
Click to expand...
Click to collapse
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.

the_weird_aquarian said:
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.
Click to expand...
Click to collapse
am using orangefox.. does it say why kernel and modules work. but lately i have a flashable zip of ringtones and they dont appear in phone or in folder.
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
mankokoma said:
I got the redmi note 8 gingko 4/64 and wanted to ask which TWRP is actually the "best". Installed the "original" and it seems to work fine, but read here and there that the one of mauronofrio is recommended. What would you suggest?
Click to expand...
Click to collapse
i think original or stock from twrp doesnt have other features example convert partition to f2fs. ect. other have all this. oreangefox have alot of features.

raptorddd said:
am using orangefox.. does it say why kernel and modules work. but lately i have a flashable zip of ringtones and they dont appear in phone or in folder.
Click to expand...
Click to collapse
You mean flashable zip is not shown in internal storage in orangefox menu from where we browse files to flash??

the_weird_aquarian said:
You mean flashable zip is not shown in internal storage in orangefox menu from where we browse files to flash??
Click to expand...
Click to collapse
if i flash kernel it works. if i flash magisk for root it works. i mean you boot into OS and kernel is installed and so is magisk. if i flash a zip that has ringtones they dont install they do not show up in phone ringtones or in folder its like its not placing the files to system partition. but if i use official twrp flashable zips do install and show up in phone.. i have tried both oreangefox and pitchblack both wont flash those zips i mentioned.
seems like something got messed up . i was in rn5 whyred using orange fox.. then magisk 20.2 was released anad orangefox got update.. after that update it didnt install those zips.. then another update was released in a day. and still dont flash those zips. at that time i reverted to the old orangefox i had and that one worked.. so last friday i unlocked bootloader and encounter the same as in whyred orangefox doesnt install the zips i mentioned.
strange that no one has reported already.

raptorddd said:
if i flash kernel it works. if i flash magisk for root it works. i mean you boot into OS and kernel is installed and so is magisk. if i flash a zip that has ringtones they dont install they do not show up in phone ringtones or in folder its like its not placing the files to system partition. but if i use official twrp flashable zips do install and show up in phone.. i have tried both oreangefox and pitchblack both wont flash those zips i mentioned.
seems like something got messed up . i was in rn5 whyred using orange fox.. then magisk 20.2 was released anad orangefox got update.. after that update it didnt install those zips.. then another update was released in a day. and still dont flash those zips. at that time i reverted to the old orangefox i had and that one worked.. so last friday i unlocked bootloader and encounter the same as in whyred orangefox doesnt install the zips i mentioned.
strange that no one has reported already.
Click to expand...
Click to collapse
hmm that seems weird. Did you create the zip yourself or downloaded from somewhere?

the_weird_aquarian said:
hmm that seems weird. Did you create the zip yourself or downloaded from somewhere?
Click to expand...
Click to collapse
created myself. been using for long time. and ginkgo official twrp does place the files in the folder and shows in phone ringtones.. weird very weird,

raptorddd said:
created myself. been using for long time. and ginkgo official twrp does place the files in the folder and shows in phone ringtones.. weird very weird,
Click to expand...
Click to collapse
My experience with self-made (and third party updater-zips) is, that you have to mount the system and vendor partitions manually before you install the updater-zip.
Have you tried this already? For me that's the way it works.

the_weird_aquarian said:
Follow this guide to see why twrp fails in some cases and the solution to overcome twrp issue.
Click to expand...
Click to collapse
I have read your guide very carefully and thanks for that! Don't get me wrong, but has nothing to do with my question. My device is encrypted and yet there has not been any problems with the original TWRP and encryption or something similar.
My question was if there are any known problems or issues with the original TWRP and is it for that reason necessary to change to another one like Orangefox or the one of @mauronofrio?

mankokoma said:
I have read your guide very carefully and thanks for that! Don't get me wrong, but has nothing to do with my question. My device is encrypted and yet there has not been any problems with the original TWRP and encryption or something similar.
My question was if there are any known problems or issues with the original TWRP and is it for that reason necessary to change to another one like Orangefox or the one of @mauronofrio?
Click to expand...
Click to collapse
Hi..if you read the guide then you might know by now the problem with official twrp is the bootloop in decrypted devices..you can't flash miui OTA with twrp...if you're on encrypted device with twrp then you have to flash full rom...other than that official twrp works just fine

mankokoma said:
My experience with self-made (and third party updater-zips) is, that you have to mount the system and vendor partitions manually before you install the updater-zip.
Have you tried this already? For me that's the way it works.
Click to expand...
Click to collapse
right i found that out yesterday after manually mountinf system partition it works.. but in many years ive never had to do it like this. it was just flash zip.

raptorddd said:
right i found that out yesterday after manually mountinf system partition it works.. but in many years ive never had to do it like this. it was just flash zip.
Click to expand...
Click to collapse
yeah, had this never before either until redmi note 5 and now 8
Any idea why you can't switch off the light in TWRP?

mankokoma said:
yeah, had this never before either until redmi note 5 and now 8
Any idea why you can't switch off the light in TWRP?
Click to expand...
Click to collapse
well orangefox on whyred happened after the latest 2 new updates.. then happens in ginkgo.
no none that i tried cant turn the screen off..if all are the same then is a problem that will stay or fix later i do not know. also kernels all are alike in kernel kcal is broken.. no sound control... i feel no big differnece with whyred.

raptorddd said:
well orangefox on whyred happened after the latest 2 new updates.. then happens in ginkgo.
no none that i tried cant turn the screen off..if all are the same then is a problem that will stay or fix later i do not know. also kernels all are alike in kernel kcal is broken.. no sound control... i feel no big differnece with whyred.
Click to expand...
Click to collapse
the only differences were the reasons I bought it: much better Camera and two SIMs plus sdcard... that's it and it feels good.

What you have to wipe for flashing this ROM?
Data, System, Vendor, Cache.
All of them, right?

General Found TWRP 3.5.0 for Redmi K40 (POCO F3)

So I just found a TWRP 3.5.0 file (I don't know who made this) from QQ ydss (China). Yeah I actually doing a leaking this file for you guys so you could have a try if you want to
Download here (GDrive)
Translated from Chinese:
The model structure is the factory (OEM) Android 11's structure. Partition structure is the latest virtual-A/B and doesn't have recovery partition, this is a special point.
Support latest Magisk Root.
This is the first beta build, please use the command "fastboot boot xxxx.img" to start using the recovery.
Support Dynamic Partition Plugins, auto-decrypt is not supported, you need to format Data to access to Data manually.
Sorry for bad English!
P/S: I will not response as your device is bricked, do it at YOUR OWN RISK

Link is working now, I forgot to enable public sharing, sorry guys

now not unlock phone still wait unlock to test

waiting for the 7-day restriction xiaomi bleat lifting

twrp boots up but this IT does not support decryption yet. You can't install anything yet

Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space

And does the version work?

bringchen said:
Chinese K40 users have done twrp3.5. They can swipe the temporary image of twrp into the mobile phone, but they can't decrypt it. I try to format the data and use the computer's ADB push / sacrd/ xx.zip It will prompt that the mobile phone is out of space
Click to expand...
Click to collapse
It just the interface test for sure, and flash is pretty useless right now until there would be a ROM support it
And that's could be a long while that we have to waiting for big-hands devs

CHGICEMAN said:
And does the version work?
Click to expand...
Click to collapse
Of course bruh, how could I put here if it doesn't work??

DumbHokage said:
Of course bruh, how could I put here if it doesn't work??
Click to expand...
Click to collapse
and why is everyone saying that this twrp has no decryption and does not work? who is lying?

any update to this version sir?

Hey, guys, has anyone tried this twrp to read USB devices?

T-HeaD said:
and why is everyone saying that this twrp has no decryption and does not work? who is lying?
Click to expand...
Click to collapse
And don't u read the italic description above???

Hopefully there is an official twrp

This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.

Alpha Another said:
This recovery working properly, I got the phone on March 4 and unlocked it on March 13 and used this to flash into magisk.
It can't unlock the data partition, but you can use otg to flash zip.
Click to expand...
Click to collapse
Wow how can you get the phone that early, is literally the sametime those reviewers are getting the phone to be tested.

When do we can expect an offical TWRP version?

bl3d2death said:
When do we can expect an offical TWRP version?
Click to expand...
Click to collapse
It probably never will,
they are not even for older models

DeathStroke47 said:
This twrp is ****. It can't flash xiaomi.eu rom from otg.
Click to expand...
Click to collapse
Ure stupid, it's a fastboot option not a flashable rom.
Please applaud me

............delete