Develop Bugs

[OREO]-[TWRP][3.2.3-0]-[RECOVERY]- XA1 Ultra [G3221]

Code:
[COLOR="red"][CENTER][SIZE="4"]##DISCLAIMER##[/CENTER]
I am not responsible for any damage at your Device. This is all at your own risk.[/SIZE][/COLOR]
Code:
[COLOR="Blue"][SIZE="5"]This version is the first version so it's UNSTABLE[/SIZE][/COLOR]
Hi all,
I've searched for a recovery with the Oreo firmware and nobody shared any of them... So I hope it helps you.
I share this recovery relase builded with TWRP Builder app only for the G3221 line. At the moment it can not be used for flash operations in /data partition due to error in the filesystem but you have the ability for all the others partition, except /data. (For more, see the spoiler)
Note:
- For who need another model recovery, try to request with
the app, like me. It's all explained in link, scroll down and click on download the app.
https://twrpbuilder.github.io
OR
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Requirements:
- Rooted phone
- TWRP Builder app
- Oreo Firmware
WHAT WORKS:​- Installations of /system partion scripts
- All type of bakup except /data
- All type of reset INCLUDED /data
(Ex: when you repair the /data filesystem, convert it from EXT4 to EXT2 and back to EXT4 (ATTENTION: YOU WILL LOSE ALL DATA!) , will guarantee the correct functioning of the /data partition.
Installation:
- Open the TWRP Builder app
- Sign In
- Select the RECOVERY button and download the file
- Go back, select the FLASH button and select the downloaded file
- Once it finish try to reboot in recovery :highfive:
Click to expand...
Click to collapse
Credit goes to:
- @TwrpBuilder -
for making this possible
- @kirito9 -
for developing this build​

I got bored
SPLT said:
Code:
[COLOR="red"][CENTER][SIZE="4"]##DISCLAIMER##[/CENTER]
I am not responsible for any damage at your Device. This is all at your own risk.[/SIZE][/COLOR]
Code:
[COLOR="Blue"][SIZE="5"]This version is the first version so it's UNSTABLE[/SIZE][/COLOR]
Hi all,
I've searched for a recovery with the Oreo firmware and nobody shared any of them... So I hope it helps you.
I share this recovery relase builded with TWRP Builder app only for the G3221 line. At the moment it can not be used for flash operations in /data partition due to error in the filesystem but you have the ability for all the others partition, except /data. (For more, see the spoiler)
Note:
- For who need another model recovery, try to request with
the app, like me. It's all explained in link, scroll down and click on download the app.
https://twrpbuilder.github.io
OR
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Requirements:
- Rooted phone
- TWRP Builder app
- Oreo Firmware
WHAT WORKS:​- Installations of /system partion scripts
- All type of bakup except /data
- All type of reset INCLUDED /data
(Ex: when you repair the /data filesystem, convert it from EXT4 to EXT2 and back to EXT4 (ATTENTION: YOU WILL LOSE ALL DATA!) , will guarantee the correct functioning of the /data partition.
Credit goes to:
- @TwrpBuilder -
for making this possible
- @kirito9 -
for developing this build​
Click to expand...
Click to collapse
I got bored had a few beers. And FLASHED this image on g3223.
CONFIRMED WORKING AND WAS ABLE TO ONCE AGAIN BRING THIS DEVICE TO NEW HEIGHTS!!!
Can't say it'll work for others. But i was able to flash magisk flawlessly and my xa1 ultra will be running modules once again.

lonewolfbtown said:
I got bored had a few beers. And FLASHED this image on g3223.
CONFIRMED WORKING AND WAS ABLE TO ONCE AGAIN BRING THIS DEVICE TO NEW HEIGHTS!!!
Can't say it'll work for others. But i was able to flash magisk flawlessly and my xa1 ultra will be running modules once again.
Click to expand...
Click to collapse
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:

SPLT said:
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:
Click to expand...
Click to collapse
No I do not have data working

SPLT said:
Cool! Do you have the /data partition mounted in recovery?
PM me and I will add it to the thread. :good:
Click to expand...
Click to collapse
lonewolfbtown said:
No I do not have data working
Click to expand...
Click to collapse
Ok, I've already contacted and informed the developer... We just have to wait.

hey can you help me please about how to flash that twrp, I`ve been trying to flash it but I keep getting the same error the boot loader doesnt work when I try to get into recovery, pressing volume down and power button

michael990 said:
hey can you help me please about how to flash that twrp, I`ve been trying to flash it but I keep getting the same error the boot loader doesnt work when I try to get into recovery, pressing volume down and power button
Click to expand...
Click to collapse
Did you get it?

[RECOVERY][Unofficial][amami] TWRP 3.4.0

Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22

Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release

Reserved

Backup to microSD seems to be working fine (haven't restored anything yet):good:

I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0

115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!

bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).

115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.

bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.

I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:

Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?

Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)

@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.

tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).

115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now

Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?

tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.

115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.

New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.

tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.

[TWRP][ TWRP 3.3.1-3 Huawei MediaPad M3 Lite ]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP - 3.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09
​
Instructions :
1. This new TWRP must be installed ONLY on your device running LOS 17.1 with TWRP 3.3.1-0 !
2. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
3. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !

Reserved
*** reserved ***

Can't do anything with TWRP
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?

Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...

surdu_petru said:
Please, can you install twrp 3.2.0 ? And check to see if you have the same issue ...
Click to expand...
Click to collapse
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?

Roswellien said:
Installed 3.2.0, worked as expected, attempted to directly update to 3.3.1-1, issue returned. Went back to 3.2.0, worked again, flashed 3.3.1-0, issue came back. At a loss at this point. Is there something I am missing here?
Click to expand...
Click to collapse
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.

No luck.
surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. If you want to use the new twrp, please install LOS 16.0 in twrp 3.2.0 and from now you can update twrp without issues.
Click to expand...
Click to collapse
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
---------- Post added at 02:34 AM ---------- Previous post was at 02:21 AM ----------
Roswellien said:
Got 3.2.0 installed and working. Wiped and flashed LOS 16.0, stuck in boot loop. Repeated and boot loop again. I've never had this many problems flashing ROMs before. And like an idiot I was in such a rush I didn't backup first. Gonna see if I can sideload a different room and get it running.
When I use the wipe in 3.2.0 there's a whole bunch of things in /data it fails to wipe saying access denied. Any ideas?
Click to expand...
Click to collapse
Strike that. Did the wipe again when I got home. Didn't error out, flashed again and booted fine. Looks like I'm all good! Thanks everyone!

Update to 3.3.1-2 !
Hello !
There is a new update of TWRP to 3.3.1-2 !
Only minor updated, including new kernel for Android 10 & syncing with the last code source of TWRP to improve stability
Also was fixed FBE encryption !

4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-1.img"
Click to expand...
Click to collapse
Hello
Any manual for regular people how and where to do this? I don't understand where and how type this command.
Instruction is not clear

Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (

pasha4ur said:
Because your manual is useless I tried google and found Multi-Tool 8. I flashed img through it. If I tried load in TWRP device is stuck on this screen and nothing more
@surdu_petru, if you want donations then write usable manuals for real life regular people.
Yesterday I got unknown device and installed TWRP & Custom in 10 ninutes. Your manuals are not help at all. I spent hour+ and get nothing.
Looks like my device boots everytime in this TWRP now.
I donated your work even without using it. But no I'm so disappointed (
I made same with twrp_3.2.0-0. It works. Again 3.3.1-2 - nothing. Add notice about stock firmware to 1st message in topic. Time is killed (
Click to expand...
Click to collapse
Hello !
Please do not panic ... the problem is that you didn't read everything or maybe you didn't understand everything like it should !
So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Now, if you want to use LOS , you need to flash LOS 16.0 on this TWRP 3.2.0, and after that you are able to update TWRP/LOS as you like !
Good luck !
Warning !
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Photo camera still not working and also the battery does not seem to hold as much as in stock ( maybe you can read some feedback of other users on LOS 17.1 or Pixel Experience) ... if these are not an impediment to you, than you can start format data into twrp-3.2.0 in order to decrypt /data, reboot device into twrp from twrp in order to be able to use data as twrp already recommend and flash LOS 16.0 ! Later you can update TWRP to the last version and install some Android 10 Custom ROMs !
If you want after all this to return to stock, then this is a problem because I already tried without success ... so, that's why this "warning!"

So, your device is still in Android N, because you are on stock ... so you need to use ONLY TWRP 3.2.0.0 !
Click to expand...
Click to collapse
Please be very carefully before to flash LOS 16.0 into TWRP 3.2.0 because there is no viable solutions to return to Huawei Stock Firmware !
Click to expand...
Click to collapse
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (

pasha4ur said:
You should write this in 1st message in topic. Not on 2nd page.
Don't worry. My device is already dead in bootloop.
I will look for a service center or buy a new tablet after removing the quarantine in my country.
Great job! (
Click to expand...
Click to collapse
How is already dead ?? I see that you have installed LOS17.1, right ? ... So, I guess you re device it's ok !

So, I guess you re device it's ok !
Click to expand...
Click to collapse
After running encryption function it's in bootloop

Fix Data Partition Size !!!
Hello !
I will explain here how the partition /data should be resized in order to be able to Encrypt device on any custom ROM based Android 10 !
From the total of data size, we need to reserve 32768 bytes for encryption stuff.
First, your device should be running Android 10 with TWRP 3.3.1-2 installed ( if you are here, I guess this is already done - what follows is not for Android Pie or for another version of TWRP )
Connect USB cable and type : ( it doesn't matter if you are now on TWRP or a custom ROM based Android 10, btw, make sure you have already enabled "Android debugging" if you're not on TWRP )
adb reboot bootloader
Click to expand...
Click to collapse
You're now on bootloader mode, here only fastboot commands are allowed !
Determine total size of /data partition by typing this command :
fastboot getvar partition-size:userdata
Click to expand...
Click to collapse
Because there are three versions of data storage size : 16GB, 32GB & 64GB - the response to the above command will vary depending on the capacity of your device !
Something like this you'll see after above command :
partition-size:userdata: 0x5xxxxxxxx
finished. total time: 0.002s
Click to expand...
Click to collapse
Let's assign a name to this value, to make it easier to explain what to do next:
I'll call "sectors" the value "0x5xxxxxxxx" which means the total size of your data partition !
If you have any questions so far, then it's time to ask for help, before going any further: because we'll perform some operations with "sectors", and you should already understand what "sectors" mean ... basicly it's a value equale with the total size of youre data partition returned by fastboot !
How we actually interpret this generic number "0x5xxxxxxxx" :
The "xxxxxxxx" from "0x5xxxxxxxx" it's a base number 16 ( hexa) - and is made up of digits from 0 to 9 and also from letters from a to f !
This is just a random example in response to the above command :
partition-size:userdata: 0x5fb03abe0
finished. total time: 0.002s
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Convert "sectors" from hex to decimal using any converter online hex-to-decimal !
"sectors" it'll be now a number made up of digits from 0 to 9 !
Subtract now from "sectors", 32768 .... something like this : "new_sectors" = "sectors" - 32768
The new sectors "new_sectors" will be smaller by 32768 than the one convert from hex to decimal !
Now, this last value ("new_sectors") must be divided to 512 : "new_new_sectors" = "new_sectors" : 512
Let's go back to the "sectors", so we'll rename "new_new_sectors" to "sectors" , so the final value of "sectors" will be smaller by 32768 than the one convert from hex to decimal and also divided to 512 !
Finally, we can summarize all the above operations to this one :
"sectors" = (hex-to-dec(0x5xxxxxxxx) - 32768) : 512
Click to expand...
Click to collapse
As soon as you have the final value and everything went clarity, we need to format data under twrp with this final value of "sectors" !
Reboot device from bootloader mode :
fastboot reboot
Click to expand...
Click to collapse
Reboot device to TWRP :
adb reboot recovery
Click to expand...
Click to collapse
Warning : all data will be lose because we need to format /data :
In order to reformat data Unmount data & type those commands :
Unmount data : check "Mount" & under "Select Partitions to Mount:" deselect/uncheck "Data" !
adb shell
mkfs.f2fs /dev/block/mmcblk0p62 "sectors"
Click to expand...
Click to collapse
Instead "sectors" you"ll must introduce the value of "sectors" which is a number made up of digits from 0 to 9 !
Reboot your device again to TWRP in order to be able to use /data !
reboot recovery
Click to expand...
Click to collapse
That's ALL ... you can now install the new TWRP 3.3.1-3 ( please check OP for download ) with /data decrypt support and also the new LOS 17.1 ( released ) where you'll be able to Encrypt tablet without issues !
Warning :
Starting from now you should never format data again into TWRP in this way : Wipe -> Format Data !
This operation will remove "data" encrypt/decrypt support and your device will not be able to be encrypted under any custom ROMs Android 10 !

surdu_petru said:
Yes, only 3.2.0 it's working with stock Huawei Rom. [...]
Click to expand...
Click to collapse
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.

Oum said:
Hi there,
Could anyone please point me at the right direction to download TWRP 3.2.0 for Huawei MediaPad M3 Lite ? It seems I can't find it anywehre :/
Thank you very much.
Click to expand...
Click to collapse
Where else could TWRP 3.2.0 be if not in TWRP 3.2.0 thread ... logical, right ??

Roswellien said:
Some help would be greatly appreciated, I have unlocked my mediapad m3 8.0 lite, flashed twrp 3.1.1-1 but when booting into twrp it just sits on the flash screen. Any help?
Click to expand...
Click to collapse
The same thing's happened to me, but "twrp_3.2.0-0.img" worked on my device but the app does not recognize the recovery image (PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip) which I copied it onto external SD card such as /sdcard/download folder.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
surdu_petru said:
TWRP - 3.3.1-3 For Huawei MediaPad M3 Lite 8/10
The new TWRP 3.3.1-3 is required only for Android Q
Officially Supported Devices :
Huawei MediaPad M3 Lite 10 : ( code name Bach ) : BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 : ( code name Chopin ) : CPN-AL00/CPN-L0J/CPN-L09/CPN-W09
​
Instructions :
1. unlock bootloader
3. unlock OEM on Developer options
3. enter on bootloader mode :
( switch off your device then keep pressed volume down key when plug to USB cable )
4. flash TWRP recovery using the following command : "fastboot flash recovery twrp-3.3.1-3.img"
5. reboot to recovery ( please check this info after TWRP was installed - and before take any actions )
Downloads :
twrp-3.3.1-2.img
twrp-3.3.1-3.img
Working/ Not working :
- adb shell & mtp
- wipe, backup & restore
- USB-OTG ( need to reboot device to be able to use USB-OTG )
- install Android 10 ROMs
- install GApps Android 10
- FBE /data decrypt support working !
Source :
kernel source : https://github.com/Huawei-Dev/android_kernel_huawei_bach
Credit :
TeamWin - TWRP
LuK1337 for his help !
Mention :
We need this new update of TWRP 3.3.1-3 in order to be able to install GApps on Android 10 & encrypt/decrypt your device !
There is no reason to update TWRP - if you don' use custom ROMs based Android 10 !
Best regards !
Click to expand...
Click to collapse
I cannot flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip by TWRP 3.2.0.0. Do I need to flash LOS16.0 onto my device first and then update TWRP to 3.3.1.3 and then flash PixelExperience-10.0-HuaweiMediaPadM3Lite_2020-03-15.zip???

Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??

mc_simon88 said:
Hi guys i have no idea where i went wrong. When flashing TWRP, this message always comes up: "necessary to unlock frp! Navigate to settings> developer op)". Can you help me??
Click to expand...
Click to collapse
Yes, go to Settings->Developer settings->OEM unlock !

SOLVED This device only boots to recovery after "successful" custom ROM installation

Hi all,
I'm happy to accept help as--to the extent of my abilities--this Mi 10T Lite is bricked. But it's not hard-bricked yet! Since I'm completely green to the world of ROM flashing, it's simply an issue of me following instructions I do not yet understand and butting my head against it when the result deviates from the tutorial.
Issue
The problem is this: with the help of instructions on this forum and YouTube I'm able to successfully perform an installation of LineageOS. No errors occur. But then when I reboot the device it will automatically boot to recovery instead and then it seems as if the installation has been undone or was never carried out.
Details
TWRP build: twrp_gauguin_mi10tl-rn9p5g_mi10i_3.5.a10_05-03-2021_d-bl-l_fix-mtp-after-format
LineageOS build: lineage-17.1-20210205-UNOFFICIAL-gauguin
OpenGApps version: open_gapps-arm-10.0-nano-20210314
Things I tried and phone's behavior
• I have tried other ROMs. Because perhaps it's Lineage's fault, I thought. But the same problem occurs with any ROM I try to install. Successful installation -> boot to system -> back to recovery.
• I tried rolling back to the back-up I took. But when I restore it and reboot the phone, it gets in an endless reboot cycle until I enter recovery or fastboot mode again.
• I unsuccessfully tried reinstalling the stock ROM (the stable release of MIUI 12.0). The installation was aborted with the error: assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")). But this is a problem probably better suited for a thread on the Xiaomi community forum where the ROM is published. I would rather get LineageOS on my phone than going back to stock, but maybe this error is significant to the solution in some way.
• Looking for existing troubleshooting threads proved difficult because I'm not even sure what to look for. Googling "custom rom installs successfully but actually it doesn't" won't yield any results.
• I'm new at flashing custom ROMs. This is the second phone I installed Lineage on. The first phone was a Samsung Galaxy J3 and I succeeded without problem by simply following the instructions, so I'm even newer at troubleshooting for this. Be aware of that please!
The instructions I followed to try an install
Prerequisite: the phone's previous OS was MIUI 12, based on Android 10.
Wipe Dalvik / ART Cache, Data, and Cache.
Flash the ROM from the external SD card.
Flash OpenGApps from the external SD card.
Format Data.
Reboot.

After wiping everything can you go to the mounts menu and mount all partitions (mainly system data and cache)
As long as all partitions can be mounted the rom should flash assuming it's the right rom for the phone/firmware

Thank you for replying.
I'm using TWRP. And I found out that system was unchecked in the mounts menu all this time. As I understood it the only purpose for mounting a partition is to present it to a device connected via USB.
So when I check the checkbox for system to mount it, then after installation system is unmounted again. The console log mentions it unmounts system just before flashing. The result is the same: a "successful" installation and then reboot back into recovery without an OS installed.
How do I check what firmware version is currently installed on my Mi 10T Lite in recovery? It was fresh off the shelves, and it had the latest software installed as of March 20th.

CyanMatter said:
Thank you for replying.
I'm using TWRP. And I found out that system was unchecked in the mounts menu all this time. As I understood it the only purpose for mounting a partition is to present it to a device connected via USB.
So when I check the checkbox for system to mount it, then after installation system is unmounted again. The console log mentions it unmounts system just before flashing. The result is the same: a "successful" installation and then reboot back into recovery without an OS installed.
How do I check what firmware version is currently installed on my Mi 10T Lite in recovery? It was fresh off the shelves, and it had the latest software installed as of March 20th.
Click to expand...
Click to collapse
A rom zip should automatically mount partitions then unmount them after
The reason I asked for manual mount is to test there's no errors in mounting
Are you sure you're on android 10 and not android 11 as android 11 was out on the date you mentioned
This might also be the reason you can't flash stock firmware if you're flashing android 10 firmware when your device is already on android 11
In fastboot mode with phone connected to pc - in cmd/terminal type
fastboot getvar all
To get firmware version and device info

TheFixItMan said:
A rom zip should automatically mount partitions then unmount them after
The reason I asked for manual mount is to test there's no errors in mounting
Are you sure you're on android 10 and not android 11 as android 11 was out on the date you mentioned
This might also be the reason you can't flash stock firmware if you're flashing android 10 firmware when your device is already on android 11
Click to expand...
Click to collapse
I'm positive it's on Android 10, but you're making me doubt that. A search shows plenty of articles announcing Android 11 has been rolling out for this device indeed.
So if in theory this device is actually on Android 11, then I should be able to flash this ROM: https://forum.xda-developers.com/t/rom-unofficial-11-0-gauguin-dotos.4231683/

I downloaded the ROM based on Android 11 mentioned above, but when I try to install it this time it throws this error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
I don't understand what it means, I can find only one thread that mentions the error. In their case they solved it by formatting data a couple of times until it took. But it doesn't work for me.
EDIT: I just found out I can put a file, any random file, in my internal storage and have it disappear when I reboot to recovery. That doesn't make sense to me. That shouldn't happen, right?
EDIT 2: Disregard that. It seems to have been a weird blip because I can't reproduce it. It's strange because files I put in there disappeared without me wiping anything.

CyanMatter said:
I downloaded the ROM based on Android 11 mentioned above, but when I try to install it this time it throws this error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
I don't understand what it means, I can find only one thread that mentions the error. In their case they solved it by formatting data a couple of times until it took. But it doesn't work for me.
EDIT: I just found out I can put a file, any random file, in my internal storage and have it disappear when I reboot to recovery. That doesn't make sense to me. That shouldn't happen, right?
EDIT 2: Disregard that. It seems to have been a weird blip because I can't reproduce it. It's strange because files I put in there disappeared without me wiping anything.
Click to expand...
Click to collapse
All I can suggest is try flashing one of the latest stock firmware files via fastboot so at least you'll have a working device
V12.0.2.0.RJSMIXM or V12.0.1.0.RJSEUXM (download on pc)
Download latest MIUI ROMs for Mi 10T Lite - Xiaomi Firmware
The Xiaomi Mi Note 10 Lite is a full package and it can be found under $300. The curved 6.47″ AMOLED display and aluminum bezels give the phone a premium look without sacrificing functionality. It seems like Xiaomi Mi Note 10 Lite can be the best phone you can get for this budget. The AMOLED...
xiaomifirmware.com
Instructions
How to flash Xiaomi firmware via Fastboot & Recovery mode
Flashing your Redmi/Mi smartphone with Xiaomi official firmware (MIUI) will help you fix certain software issues on the phone. It also helps you to get rid of root and all modifications made to your phone system software. To upgrade, update or fix minor software problems on your phone, flashing...
www.leakite.com

TheFixItMan said:
All I can suggest is try flashing one of the latest stock firmware files via fastboot so at least you'll have a working device
V12.0.2.0.RJSMIXM or V12.0.1.0.RJSEUXM (download on pc)
Download latest MIUI ROMs for Mi 10T Lite - Xiaomi Firmware
The Xiaomi Mi Note 10 Lite is a full package and it can be found under $300. The curved 6.47″ AMOLED display and aluminum bezels give the phone a premium look without sacrificing functionality. It seems like Xiaomi Mi Note 10 Lite can be the best phone you can get for this budget. The AMOLED...
xiaomifirmware.com
Instructions
How to flash Xiaomi firmware via Fastboot & Recovery mode
Flashing your Redmi/Mi smartphone with Xiaomi official firmware (MIUI) will help you fix certain software issues on the phone. It also helps you to get rid of root and all modifications made to your phone system software. To upgrade, update or fix minor software problems on your phone, flashing...
www.leakite.com
Click to expand...
Click to collapse
Ok, so... funny thing happened. I followed this advice and it worked, I can boot my system into MIUI 12 again!
BUT when flashing the firmware, after 7 minutes the flashing tool reported an error and seemed to have aborted the process; status: error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done. Meanwhile, while I was worried it failed, the device actually rebooted into the stock OS.
Here is the relevant part of the log. The failed checkpoint does not seem to be crucial to the process. These are the last lines, and I masked my device code as I'm worried it's identifying information.
Code:
[02:13:37 {device code}]:info2:Rebooting OKAY [ 0.001s]
[02:13:37 {device code}]:info2:Finished. Total time: 0.001s
[02:13:37 {device code}]:begin FlashDone
[02:13:37 {device code}]:errMsg is null
[02:13:37 {device code}]:begin checkPoint
[02:13:37 {device code}]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[02:13:37 {device code}]:process exit.
[02:13:37 {device code}]:flashSuccess False
[02:13:37 {device code}]:isFactory False CheckCPUID False
[02:13:37 {device code}]:before:flashSuccess is False set IsUpdate:True set IsDone True
[02:13:37 {device code}]:after:flashSuccess is False set IsUpdate:false set IsDone true
Still, thank you lots for your help! At least I can use my device now. Next time I'll double check my software versions before flashing a custom ROM.

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/

Thanks for your hard work
All function has usable especially decryption.

Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.

Awesome, mate!

I've been waiting for this, thank you sir for your contribution!

@Nebrassy Nice work - tested on my crDroid working-build and all ok

I only can say thank you a lot!! I'll buy a beer

"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw

reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported

Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway

raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?

raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?

arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.

this works "out of the box" for poco f3 with miui 12.x?

Thank you

Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..

Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !

lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp

lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )

Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help