Database Develop

[BETA] TWRP 3.1.1 for Mi A1

Hey,
TWRP 3.1.1 Touch Recovery beta version is released for Xiaomi Mi A1.
Download - Go to downloads tab
Update:
1. Magisk v13.4 is working fine.
Workaround for Xposed:
Xposed is not installing through TWRP and when tried with App, still it's giving errors. So below is the temporary solution till we get a permanent one.
1. Don't flash TWRP. Just boot into it from bootloader by using command - fastboot boot recovery_name.img
2. Flash latest SuperSU zip.
3. Reboot to System.
4. Your phone will be rooted now and install Xposed through app.
Important:
1. Don't flash it, just boot into it.
2. If flashed, re-flash the latest stock boot image.
Instructions:
1. Download the twrp image and twrp installer zip
2. fastboot boot twrp-3.1.1-tissot-beta.img
3. Flash twrp-installer-tissot-3.1.1.zip
4. Reboot to recovery
Flash Magisk v13.4 built for Pixel devices by @Goodwin_c. Available in the downloads tab.
Issues:
1. Flashing SuperSU will break TWRP. SuperSU will work, but TWRP will be gone.
2. Xposed won't flash without modification.
Future update:
1. Make TWRP and SuperSU to co-exist
2. Compatibility with Xposed and Latest Magisk
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom recoveries, roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
XDA:DevDB Information
TWRP 3.1.1 for Mi A1, Tool/Utility for the Xiaomi Mi A1
Contributors
mahefooz4u, ravinder0003, Thanks to @Dees_Troy and TWRP Team
Source Code: https://github.com/mahefooz/android_device_xiaomi_tissot
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-15
Created 2017-10-13
Last Updated 2017-10-16

good work bro waiting for development to start

Great work!

Celebrations
The first step towards the good community has been taken

Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks

great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?

deepakmohank said:
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
Click to expand...
Click to collapse
Yes, Aroma installer is working

thank-you. Have you tried the way Pixel devices boot twrp, send twrp zip to internal, then flash?
---------- Post added at 11:28 AM ---------- Previous post was at 11:01 AM ----------
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?

Coolio

lakyman said:
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
Click to expand...
Click to collapse
Don't expect too much from now.
Wait for sometime as this is ported

Great work waiting for stable version... ?

great, thank you very much!!!
deepakmohank said:
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Click to expand...
Click to collapse
yea good question, I'd like to know about it too..

marhensa said:
great, thank you very much!!!
yea good question, I'd like to know about it too..
Click to expand...
Click to collapse
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312

Surprise!!!
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
Link:
https://www.androidfilehost.com/?fid=962021903579484616
Update Test 2: https://www.androidfilehost.com/?fid=962021903579484804
If it works, please don't forget to hit thanks...

deepakmohank said:
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Click to expand...
Click to collapse
No support for a/b system. Only active system can be reached
Thanks for great effort by devs

thanks for sharing~
hope it works~

Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.

ghpranav said:
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
If it works, please don't forget to hit thanks...
Click to expand...
Click to collapse
unfortunately it does not work
h**p://kephost-image.tk/files/64k6re0jfsp4zmienhkr.png

TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
Somehow Magisk is not yet working in Mi A1. Either flashed through recovery or other method, getting bootloop and other issues.

TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
If you know then Magisk is not supported officially for A/B partitons devices including Pixel

[ROM][S9+/S9][LineageOS 17.1][UNOFFICIAL][05-06-20][OTA]

What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020

temp

Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English

Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.

so everything good other than Android Auto? Well done!

Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?

geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.

How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:

..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?

Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6

Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.

Great, glad all went good for you

Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse

Great work! ROM works great, even Google pay is working good!

I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel

Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?

Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!

oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel

Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse

Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.

boot failed on galaxy m20

i tried to flash project sakura 5.1 with latest twrp which shows succeeded on terminal but it doesn't boot into system instead it booted into bootloader. i tried with older twrp and older versions of project sakura too, nothing worked. but the another rom called HariRom based on oneUI3.1 successfully flashed and booted normally to system. also i tried with another custom recovery called orangefox, which shows the boot cannot be located as error for all version of project sakura. can somebody help me with it?? i wish to install project sakura 5.1

ChapagainAB said:
i tried to flash project sakura 5.1 with latest twrp which shows succeeded on terminal but it doesn't boot into system instead it booted into bootloader. i tried with older twrp and older versions of project sakura too, nothing worked. but the another rom called HariRom based on oneUI3.1 successfully flashed and booted normally to system. also i tried with another custom recovery called orangefox, which shows the boot cannot be located as error for all version of project sakura. can somebody help me with it?? i wish to install project sakura 5.1
Click to expand...
Click to collapse
[EOL][ROM] [11] Project Sakura 5.1 [OFFICIAL] | VANILLA
does this rom have a working aod for samsung galaxy a40?
forum.xda-developers.com
Follow from here

Kenora_I said:
[EOL][ROM] [11] Project Sakura 5.1 [OFFICIAL] | VANILLA
does this rom have a working aod for samsung galaxy a40?
forum.xda-developers.com
Follow from here
Click to expand...
Click to collapse
i followed that in my first try which didnt worked and after that i tried other recoveries and versions of sakura . that didnt helped.
my phone is not rooted by the way

How to fix bootloops after coming from OneUI 3.x ports
1) Boot to TWRP
2) Download this vendor image
3) Install --> Flash image --> select image --> select vendor
4) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from here
5) Flash the ROM.zip

i did installed vendor img but didnt find the option to wipe vender. and also i have tried installing dm-verity zip too. idk what that did but it was installed successfully and still didnt booted to system
Kenora_I said:
How to fix bootloops after coming from OneUI 3.x ports
1) Boot to TWRP
2) Wipe Vendor
3) Download this vendor image
4) Install --> Flash image --> select image --> select vendor
5) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from here
6) Flash the ROM.zip
Click to expand...
Click to collapse

Actually no need i removed it.

So wiping vendor is in advanced wipe area in twrp. Dont reboot after it.
Then flash the image like i said.
Then flash the dm verity thing then flash the rom.zip

Kenora_I said:
So wiping vendor is in advanced wipe area in twrp. Dont reboot after it.
Then flash the image like i said.
Then flash the dm verity thing then flash the rom.zip
Click to expand...
Click to collapse
@Haridhayal i did installed it to my phone. version 5.2 actually. but its lagging, its overheating than stock rom while gaming. And mainly it crashes whenever i try to add security lock neither of the security option works . and i played call of duty mobile for some time and it quit automatically after some like 10 to 15 min. also the camera UI is terrible altho it captured well. and my phone did support fast charging on stock rom which now doesnot supported by project sakura. it takes almost 4-5 hours to get fully charged. what the hell happened with that?

ChapagainAB said:
@Haridhayal i did installed it to my phone. version 5.2 actually. but its lagging, its overheating than stock rom while gaming. And mainly it crashes whenever i try to add security lock neither of the security option works . and i played call of duty mobile for some time and it quit automatically after some like 10 to 15 min. also the camera UI is terrible altho it captured well. and my phone did support fast charging on stock rom which now doesnot supported by project sakura. it takes almost 4-5 hours to get fully charged. what the hell happened with that?
Click to expand...
Click to collapse
So it worked? It booted?
Yes, some features arent supported for some custom ROMs. Keep in mind custom ROMS won't perform like stock. Stock ROMS are made by people with the correct tools and 100% knowledge about the specific phone you are using sooooo....

LineageOS 20.0 (Android 13) for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 ALPHA

Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 20 for our Samsung Galaxy Note 10.1 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a ALPHA build, also on the LineageOS side, so don't install it if you want a complete and stable rom and don't report my already listed bugs!
Here you can see how far everything is working for now.
Spoiler: Whats working
N8000, N8010, N8013, N8020:
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
GPS
Wifi
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
RIL
sec_keyboard docking station
much more...
Spoiler: Whats not working
Random reboots
Long screenshot
SD-Card can't be formatted as internal storage, this will cause a bootloop
Network monitoring because of missing eBPF support
Spoiler: Links
TWRP
ROM Mega
Gapps, I don't recommend them, use the smallest package
Magisk zip file
Spoiler: Changelog
15.01.2023
06.03.2023
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
https://androidfilehost.com/?fid=7161016148664799666
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs?
Now you can use my app to access all boeffla sound configurations.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N8000/N801x/N8020][BETA] LineageOS 20.0, ROM for the Samsung Galaxy Note 10.1
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Alpha
Created 2022-11-02
Last Updated 2023-03-06

*reserved

Thats amazing... will test this this out when you get the ROM uploaded as it seems to be missing at the moment on both the ROM Mega Link and the AndroidFileHost Link. Thanks

samsum26 said:
Thats amazing... will test this this out when you get the ROM uploaded as it seems to be missing at the moment on both the ROM Mega Link and the AndroidFileHost Link. Thanks
Click to expand...
Click to collapse
Mega is fine here.
@html6405 beautiful work as always

anjarys said:
Mega is fine here.
@html6405 beautiful work as always
Click to expand...
Click to collapse
It is now thanks very much... the folder was empty earlier, much appreciated

everything working fine at my end.
I'm using LOS20 + Magisk+BigGapps Magisk module. the setup quite stable and performance is usable.

I could install the Rom OK but cannot do the Magisk part as it wants to Update but fails to install from .apk file it downloads and updating the app needs the other update or it says something like it acts as though it is not installed so couldn't do the 3. Enable Zygisk in Magisk (Step). I used MindTheGapps-12.1.0 on the last 19.1 LineageOS so will go back to that for now as I know what I'm doing with that one

samsum26 said:
I could install the Rom OK but cannot do the Magisk part as it wants to Update but fails to install from .apk file it downloads and updating the app needs the other update or it says something like it acts as though it is not installed so couldn't do the 3.
Click to expand...
Click to collapse
Hmm did you do a clean installation?
And did you grant the installation permissions to magisk?
It worked fined on my devices, also v23.0 with magisk hide still works fine!

html6405 said:
Hmm did you do a clean installation?
And did you grant the installation permissions to magisk?
It worked fined on my devices, also v23.0 with magisk hide still works fine!
Click to expand...
Click to collapse
I did do a clean install and installed magisk through TWRP and it did ask later for permissions in the app itself and allowed via the slider and then updated but never got far with the program update. I've not used the magisk before so probably something I did wrong. Will have another play and video it next time to find where I'm going wrong and couldn't find the Enable Zygisk at all in settings or anywhere

samsum26 said:
I did do a clean install and installed magisk through TWRP and it did ask later for permissions in the app itself and allowed via the slider and then updated but never got far with the program update. I've not used the magisk before so probably something I did wrong. Will have another play and video it next time to find where I'm going wrong and couldn't find the Enable Zygisk at all in settings or anywhere
Click to expand...
Click to collapse
Hey
Do not update Magisk, the new version does not work in our kernel. The Developer is working on a kernel update for our devices so that we can use the latest versions of Magisk. Just wait a little longer, I believe this rom will be one of the best created for our tablets.

Alexfs said:
Hey
Do not update Magisk, the new version does not work in our kernel. The Developer is working on a kernel update for our devices so that we can use the latest versions of Magisk. Just wait a little longer, I believe this rom will be one of the best created for our tablets.
Click to expand...
Click to collapse
Thanks Alexfs will hang on a bit as I tried again earlier with same problems and link for Magisk was down at androidfilehost... much appreciated

samsum26 said:
Thanks Alexfs will hang on a bit as I tried again earlier with same problems and link for Magisk was down at androidfilehost... much appreciated
Click to expand...
Click to collapse
Flash magisk 22.1 and install this module: https://github.com/kdrag0n/safetynet-fix/releases

chhapil said:
everything working fine at my end.
I'm using LOS20 + Magisk+BigGapps Magisk module. the setup quite stable and performance is usable.
Click to expand...
Click to collapse
do you get much lag with animations? I had issues with lineageos 19

Alexfs said:
Hey
Do not update Magisk, the new version does not work in our kernel. The Developer is working on a kernel update for our devices so that we can use the latest versions of Magisk. Just wait a little longer, I believe this rom will be one of the best created for our tablets.
Click to expand...
Click to collapse
I will switch from lineageos 16 to this rom when kernel update is released

Finally fixed the wake up problem in kernel, it took some time to figure out which driver was faulty.
Only for N8000 and N8010 at the moment.
Attention: this is only a test kernel at the moment, if you want to try it, there still could be other issues.

html6405 said:
Finally fixed the wake up problem in kernel, it took some time to figure out which driver was faulty.
Only for N8000 and N8010 at the moment.
Attention: this is only a test kernel at the moment, if you want to try it, there still could be other issues.
Click to expand...
Click to collapse
kernel says it's not compatible with my gt-n8010

w_tapper said:
kernel says it's not compatible with my gt-n8010
Click to expand...
Click to collapse
Give this one another try.

Sooo.. Since installing this rom I have no way to access TWRP. Power+Vol+ ends on "Warning!" screen saying that custom rom can cause problems and choice of two options:
- Vol Up - continue (restarts device and boots the OS),
- Vol Down - Cancel (boots to Download mode).
Rebooting to recovery with advanced reboot ands with above as well...
I reflashed TWRP with ODIN, but that changed nothing.
Any idea?
Ok, after 3 or 4 reflashes recovery works.
Now I have a problem with MAGISK. Manager says MAGISK is available, but doesn't give access to root - it acts as there is no root at all...
So MAGISK is there, but at the same time it isn't (attached image - 001251)... Used zip from OP.
Than after reflash, same zip, MAGISK is not available (000432)... Still boot image is MAGISK patched...

ch3mn3y said:
Sooo.. Since installing this rom I have no way to access TWRP. Power+Vol+ ends on "Warning!" screen saying that custom rom can cause problems and choice of two options:
- Vol Up - continue (restarts device and boots the OS),
- Vol Down - Cancel (boots to Download mode).
Rebooting to recovery with advanced reboot ands with above as well...
I reflashed TWRP with ODIN, but that changed nothing.
Any idea?
Ok, after 3 or 4 reflashes recovery works.
Now I have a problem with MAGISK. Manager says MAGISK is available, but doesn't give access to root - it acts as there is no root at all...
So MAGISK is there, but at the same time it isn't (attached image - 001251)... Used zip from OP.
Than after reflash, same zip, MAGISK is not available (000432)... Still boot image is MAGISK patched...
Click to expand...
Click to collapse
had that same issue with 25.2 on old kernel - flash magisk 24.1

html6405 said:
Give this one another try.
Click to expand...
Click to collapse
The phone works fine till the time it's operating.
Latest magisk 25.2 work fine as well.
But deep sleep issue. after couple of hours, phone has to restarted.
Let me try if I can grab logs

[Recovery][TWRP 3.7.0][Unofficial][Mi 10T/Pro]

Please note that it is not mine if you are here, it means you know what you are doing and are solely responsible for what you are doing.
I see some users can't find twrp for this device and some links are broken. So I share here the last unofficial twrp developed by skkk. All credits and thanks goes to him.
If you have no recovery yet and you are not rooted, you need to use the usual adb commands: fastboot boot <twrp.img>
If you're rooted, you can use the official twrp app[https://play.google.com/store/apps/details?id=me.twrp.twrpapp ] Grant him root rights and flash the twrp image or flash directly from recovery for an update...
Download link
128 MB file on MEGA
mega.nz
or unzip this file to have twrp.img
*update January 15, 2023 (twrp.V-6.8)
*update January 17, 2023 (twrp.V-6.9)
*update January 18, 2023 (twrp.V-7.0)
*update January 30, 2023 (twrp.V-7.1)
*update February 2, 2023 (twrp.V-7.2)
*update april 25 , 2023 (twrp.V-7.7)

Thanks ............​

thanks for sharing and caring for us user of mi 10t/pro

If you have problem with data decryption please use this version twrp (credit to lilydess) and Flash DFE after your ROM.
Although it's version 3.6.2 seems to work better especially on A13 which has even more restrictions than A12.
Note : Unzip this file you will have Twrp.img+DFE.zip
• EROFS Support
• September 8th 2022
• Source Code
Commits · lolipuru/twrp_device_xiaomi_apollo
Contribute to lolipuru/twrp_device_xiaomi_apollo development by creating an account on GitHub.
github.com

Full House said:
If you have problem with data decryption please use this version twrp (credit to lilydess) and Flash DFE after your ROM.
Although it's version 3.6.2 seems to work better especially on A13 which has even more restrictions than A12.
Note : Unzip this file you will have Twrp.img+DFE.zip
Click to expand...
Click to collapse
thanks a lot for this, more powerrr to you sir

abrakadabraham said:
thanks a lot for this, more powerrr to you sir
Click to expand...
Click to collapse
Thank you for being grateful, many here are not grateful more than 100 people have downloaded not even 10 people thanked that's how human ingratitude.

nice work bro keep it up

Full House said:
Please note that it is not mine if you are here, it means you know what you are doing and are solely responsible for what you are doing.
I see some users can't find twrp for this device and some links are broken. So I share here the last unofficial twrp developed by skk. All credits and thanks goes to him.
If you have no recovery yet and you are not rooted, you need to use the usual adb commands: fastboot boot <twrp.img>
If you're rooted, you can use the official twrp app[https://play.google.com/store/apps/details?id=me.twrp.twrpapp ] Grant him root rights and flash the twrp image or flash directly from recovery for an update...
Download link
128 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thanks a lot!!

Thank you so much, thanks for sharing useful TWRP.

Thanks for this amazing recovery

Can it decrypt data on android 12? or even android 13? D:

Yes

plakonn said:
Can it decrypt data on android 12? or even android 13? D:
Click to expand...
Click to collapse
I recommend skk twrp for A12 roms and miui based roms it can decrypt but for A13 lilydess twrp is recommended.

big thanks to you, other recovery thit not stick got twrp bootloop this recovery works super europe xiaomi MI 10 t pro 5G thanks very happy

Full House said:
I recommend skk twrp for A12 roms and miui based roms it can decrypt but for A13 lilydess twrp is recommended.
Click to expand...
Click to collapse
where i can get lilydess twrp? (edit: i mean, from where did you get it?) i cant find it
edit2: it can rly decrypt storage, right? so i can use it without dfe and just write pin into twrp (or remove pin before rebooting to twrp)

plakonn said:
where i can get lilydess twrp? (edit: i mean, from where did you get it?) i cant find it
edit2: it can rly decrypt storage, right? so i can use it without dfe and just write pin into twrp (or remove pin before rebooting to twrp)
Click to expand...
Click to collapse
on telegram.
It depends on the ROM so yes in some cases no need for DFE flash if the ROM does not force encryption.
Yes you can boot to twrp with lock enabled.

Full House said:
on telegram.
It depends on the ROM so yes in some cases no need for DFE flash if the ROM does not force encryption.
Yes you can boot to twrp with lock enabled.
Click to expand...
Click to collapse
so there is no way i can have force encryption and twrp at the same time? (i need encrypted storage but i would like too keep ability to flash zips, ota updates etc. Can pixel experience recovery do it? (with lockscreen pin removed) i mean using pc "adb sideload" command...

plakonn said:
so there is no way i can have force encryption and twrp at the same time? (i need encrypted storage but i would like too keep ability to flash zips, ota updates etc. Can pixel experience recovery do it? (with lockscreen pin removed) i mean using pc "adb sideload" command...
Click to expand...
Click to collapse
I only use twrp ask pixel dev experience.
Anyway some recommend the use of their recovery even if it works with twrp this is due to the fact that there is no official twrp for Apollo.
indeed even if twrp cannot access internal data we can always use adb sideload or usb otg to flash what you want, the only problem in this case will be to access to data/adb/modules in case of bootloop and no twrp backup.

So bootloops caused by magisk module are solved how? By formatting everything?

Full House said:
I only use twrp ask pixel dev experience.
Anyway some recommend the use of their recovery even if it works with twrp this is due to the fact that there is no official twrp for Apollo.
indeed even if twrp cannot access internal data we can always use adb sideload or usb otg to flash what you want, the only problem in this case will be to access to data/adb/modules in case of bootloop and no twrp backup.
Click to expand...
Click to collapse
I dont want to annoy you any more... Is there any guide for this? (how to work with this kind of twrp?). I'm lowkey confused by the fact i can flash from otg but at the same time i can not view storage. ( i managed to destroy system once i tried to flash somethin so i started using DFE.zip but now i need encryption for work app...)
i used to know how it works but i forgot. Thanks for help 🫡