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.

Made an OB1 Magisk Patched boot.img

7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Don't install TWRP yet. The people who are infinitely smarter than I am will make a TWRP that will work for OB1, and that's way above my pay grade. I hope this helps someone.
[Tutorial] How to flash a new boot.img via Fastboot
Hey Guys, since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode) If you have fastboot already installed on your...
forum.xda-developers.com
Here's how to use it.

getting 'unable to parse kernel log' error

peachypickle said:
getting 'unable to parse kernel log' error
Click to expand...
Click to collapse
it worked fine for me.

How install oxygen os open beta 1 android 11 with keep rooted? Any video tutorial?

it's not too bad...
Install the OTA
Go to magisk manager and pick install.
pick install to inactive slot (after OTA)
make sure you don't have any modules enabled that may be incompatible.
reboot
when the 11 TWRP drops, you can install it as a magisk module to gain custom recovery back

Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.

spheady said:
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
Click to expand...
Click to collapse
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.

spheady said:
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
Click to expand...
Click to collapse
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?

LokifiedMee said:
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
Click to expand...
Click to collapse
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun

Crazyinsanejames said:
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Click to expand...
Click to collapse
Ohh couldn't find Orangefox dual boot's post today so here is the twrp file. It's not really worked on right now and has option to flash magisk on R11 Pass but the copy of magisk is no good on the R11 OS but has magisk. 20.4 option for a Q10 is, when it IDs it. You'll see. The script options. PS orangfox dual booting with three different drives rocks. Also it has a app manager and a magisk mange GUI. Almost forgot beta 10 version 17-19 will not successful y flash this twrp. But any other copy for the phone on xda or OnePlus.com work fine. It's a encryption variety problem. If your password becomes corrupt (only on OS can have password type security on a dual boot setup... I got away with using the same password on both OSs for a minute though. ) in the root partition thiers a directory called Ffiles, with .zip you can flash while TWRped to fix a few things like that. Other than that let me know. Lol I want to mention Evey time you flash an OTA or anything that will alter the work this twrp installs, you need to flash the file afterwards, before rebooting. And reboot after flashing it so everything links up. Of coarse you can select to reboot right back to recovery. Best luck I couldn't find their post on xda so that's why I typed up so much. Lol I'll be funny again I don't know who this stuff on how to downgrade really but thiers a Windows tool that has capibillities err what ever to flash a OTA of 10 in fastboot mode. Anyways no worries. It's called all-in-one flash tool. Works on maney OnePlus phones. Maybe for encrypted data partitions. I run unencrypted stuff I do not like encryption on any electric devices.

aNGERY said:
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Click to expand...
Click to collapse
I just want to say thank you. I tried the new magisk update and it didn't work. I could get to recovery and figured I had PB1 for Andoid11 anffd I would flash to gety baclk to working. Of course I lost root, but was able to get it back with magisk_patched_Ei056.img flashed to boot. It works fine. Can hang with root until TWRP gets updated.
VERY APPRECIATED.

Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!

Crazyinsanejames said:
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Click to expand...
Click to collapse
Well found out thevendor.img didnt work lol. Anyways heres cheap trick i found if your not on an OS with twrp
http://Link removed

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
I'm pretty sure it's insinuated that it's pertaining to OOS11. Don't be willfully obtuse.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
35090 for Android 11 on the OnePlus 7 pro will not work without decrypting it.

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
actually I take that back.
Download TWRP for guacamole
Download TWRP Open Recovery for guacamole
dl.twrp.me
Here you go, 3.5.0_9-0 is the one release on 12/28. Install it and let us know how you like it!

spheady said:
Lol nice it worked. Lol it also
Ty tried for fun. Think thos thread is for ppl trying to boot a .img file of twrp. Can this flash via fastboot. So twrp to twrp I think ill keep my dual boot Twrp its not so basic.ty
Click to expand...
Click to collapse
You can reboot to recovery from the OS with this twrp installed?

Any official or unofficial lineage OS for Samsung galaxy M21

Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!!

Join telegram
they have CrDroid android 11

sinkoo1979 said:
Join telegram
they have CrDroid android 11
Click to expand...
Click to collapse
Thanks so much I'll join the telegram channel.

Before you waste ur time on telegram, the crdroid 11 does not work as of now and the dev isn't prepared to fix it. So wait until it is posted in xda

GuruPrasadAH said:
Before you waste ur time on telegram, the crdroid 11 does not work as of now and the dev isn't prepared to fix it. So wait until it is posted in xda
Click to expand...
Click to collapse
Any GSI you will recommend? (for M215G)

OldNoobOne said:
Any GSI you will recommend? (for M215G)
Click to expand...
Click to collapse
Any will work. I personally use crdroid since it is lightweight, has good performance, and has a lot of customizations. Use soulr344's twrp and use the built in super cmd to flash. Then flash Multidisabler, null vbmeta and magisk.
Use this build: https://github.com/eremitein/treble-patches/wiki/crDRom11-Project
Also don't plug in charger while power off, it will become stuck on boot screen. Use vol down+ power to reboot if that happens. Also DONT install hktweaks and overclock/underclock, it will cause random reboot
Chill
GuruPrasadAH

GuruPrasadAH said:
Any will work. I personally use crdroid since it is lightweight, has good performance, and has a lot of customizations. Use soulr344's twrp and use the built in super cmd to flash. Then flash Multidisabler, null vbmeta and magisk.
Use this build: https://github.com/eremitein/treble-patches/wiki/crDRom11-Project
Also don't plug in charger while power off, it will become stuck on boot screen. Use vol down+ power to reboot if that happens. Also DONT install hktweaks and overclock/underclock, it will cause random reboot
Chill
GuruPrasadAH
Click to expand...
Click to collapse
thanks bro ,
I dont have null vbmeta though, can you post link for null vbmeta if possible and the sequence of flashing the files as per your opinion.
I am downloading ( crdrom-v313-210921-arm64-BvZ-lite.img.xz ) for M215G (Galaxy M21 2021 Edition)
#Note -
I tried to flash another lineage GSI for android 11-> LirRMod ( lir-v313-210915-arm64-bvZ-lite.img) but failed so. Thanks in advance bro

OldNoobOne said:
thanks bro ,
I dont have null vbmeta though, can you post link for null vbmeta if possible and the sequence of flashing the files as per your opinion.
I am downloading ( crdrom-v313-210921-arm64-BvZ-lite.img.xz ) for M215G (Galaxy M21 2021 Edition)
#Note -
I tried to flash another lineage GSI for android 11-> LirRMod ( lir-v313-210915-arm64-bvZ-lite.img) but failed so. Thanks in advance bro
Click to expand...
Click to collapse
Yes... I failed many times, but it is all about the null vbmeta. That only disables dm-verity. I made this vbmeta flasher myself, bc no other existed.
Order-
1. WIpe data and reboot to recovery
2. Plugin to pc and transfer gsi image, vbmeta zip, multidisabler, and magisk(optional) to documents folder.
3. Go to terminal
4. Type the following cmds one by one
cd sdcard
cd documents
super mount system
super flash system [Name-of-the-image].img
5. Flash vbmeta
6. Flash multidisabler
7. Flash magisk(again, optional)
8. Flash custom kernel if u want( I recommend PrishKernel)
9. Reboot to system and enjoy.

Bro thanks so much, I will try your steps and tell you what happens ok

GuruPrasadAH said:
Yes... I failed many times, but it is all about the null vbmeta. That only disables dm-verity. I made this vbmeta flasher myself, bc no other existed.
Order-
1. WIpe data and reboot to recovery
2. Plugin to pc and transfer gsi image, vbmeta zip, multidisabler, and magisk(optional) to documents folder.
3. Go to terminal
4. Type the following cmds one by one
cd sdcard
cd documents
super mount system
super flash system [Name-of-the-image].img
5. Flash vbmeta
6. Flash multidisabler
7. Flash magisk(again, optional)
8. Flash custom kernel if u want( I recommend PrishKernel)
9. Reboot to system and enjoy.
Click to expand...
Click to collapse
Hi bro, I followed the steps above till step 5:
1. cd sdcard (worked)
2. cd documents (worked)
3. super mount system (worked)
4. super flash system crdrom-v313-210921-arm64-bvZ-lite.img (flashed but in 1s time)
so , I think gsi did not flash properly. any idea why?

OldNoobOne said:
Hi bro, I followed the steps above till step 5:
1. cd sdcard (worked)
2. cd documents (worked)
3. super mount system (worked)
4. super flash system crdrom-v313-210921-arm64-bvZ-lite.img (flashed but in 1s time)
so , I think gsi did not flash properly. any idea why?
Click to expand...
Click to collapse
Actually, raw images flash like this only. Carry on doing all the steps bro(did u try flashing every thing else and try booting?). Anyway, hope this helps you

GuruPrasadAH said:
Actually, raw images flash like this only. Carry on doing all the steps bro(did u try flashing every thing else and try booting?). Anyway, hope this helps you
Click to expand...
Click to collapse
Thanks bro, finally CRD managed to boot , I flashed stock rom then after that I followed your steps and it booted! . You saved my life bro coz GSI flashing guide on xda looked very complicated to me.
You said you made the vbmeta file on your own so you should be senior member in xda not new member XD . If you have donate button then pls post coz you & CrD deserve some donations. Thanks a lot
Can you also make vbmeta for Redmi Note 10 Mojito? Pls Pls

OldNoobOne said:
Thanks bro, finally CRD managed to boot , I flashed stock rom then after that I followed your steps and it booted! . You saved my life bro coz GSI flashing guide on xda looked very complicated to me.
You said you made the vbmeta file on your own so you should be senior member in xda not new member XD . If you have donate button then pls post coz you & CrD deserve some donations. Thanks a lot
Can you also make vbmeta for Redmi Note 10 Mojito? Pls Pls
Click to expand...
Click to collapse
Just a few clarifications:
1. I only made the flasher zip for the vbmeta. The image itself - was provided by google.
2. This zip should and will probably work on all phones, except maybe a few with weird vbmeta partition name( samsung vbmeta partition name is actually vbmeta_samsung instead of vbmeta only, and I think LG does the same too).
If it does not work( shows failed msg ) then send me the link of that device's twrp. I will maybe make an update if i find time.
Chill
GuruPrasadAH

Also, I'm just 13 yo as of now, so no donation for me. However, if u want to donate to crd, follow these two links:
https://www.paypal.com/paypalme/crdroidandroid -For crDroid themselves
For the guy who built the GSI, there seems to be no donate button.
Also, I saw ur post asking question about how M215G is different. Actually it is same, and remember - fastboot can never be installed on samsung. Also, turn off auto reboot when flashing twrp with odin, then hold down vol down+power for 7 secs until it reboots, then immediately press vol up+power. After this, wipe data and flash ROM.
If u reboot back to system without flashing multidisabler/rom, twrp will automatically be replaced with stock recovery. Hope this helps.
Chill
GuruPrasadAH

GuruPrasadAH said:
Also, I'm just 13 yo as of now, so no donation for me. However, if u want to donate to crd, follow these two links:
https://www.paypal.com/paypalme/crdroidandroid -For crDroid themselves
For the guy who built the GSI, there seems to be no donate button.
Also, I saw ur post asking question about how M215G is different. Actually it is same, and remember - fastboot can never be installed on samsung. Also, turn off auto reboot when flashing twrp with odin, then hold down vol down+power for 7 secs until it reboots, then immediately press vol up+power. After this, wipe data and flash ROM.
If u reboot back to system without flashing multidisabler/rom, twrp will automatically be replaced with stock recovery. Hope this helps.
Chill
GuruPrasadAH
Click to expand...
Click to collapse
Thanks bro, I am surprised how all the developers I came across are 13 year old
Wish you luck bro
CrDroid is good but I think ROMs are better than GSIs, for example -
1. CrDroid GSI has issue with MTP, device not getting recognized by PC! but inside TWRP I can transfer files from pc to Internal Storage
2. Also 3-button NavBar background is opaque not transparent so NavBar takes up 10% of the screen, gesture is fine but navbar is very handy.
I did not find any CrDroid vanilla version

OldNoobOne said:
Thanks bro, I am surprised how all the developers I came across are 13 year old
Wish you luck bro
CrDroid is good but I think ROMs are better than GSIs, for example -
1. CrDroid GSI has issue with MTP, device not getting recognized by PC! but inside TWRP I can transfer files from pc to Internal Storage
2. Also 3-button NavBar background is opaque not transparent so NavBar takes up 10% of the screen, gesture is fine but navbar is very handy.
I did not find any CrDroid vanilla version
Click to expand...
Click to collapse
Actually, one guy Daniel on telegram built a crdroid 11 rom(not gsi) for m21, however last I checked, it did not boot and booted into fastboot(pls don't ban me lol).
The dev said it was a DT(device tree) bug and that the fix wud take time.
And since there was more trolling than development happening in that group, I exited it.
Once it boots, it wud probably be posted under roms, so no need to join that toxic group as of now

GuruPrasadAH said:
Actually, one guy Daniel on telegram built a crdroid 11 rom(not gsi) for m21, however last I checked, it did not boot and booted into fastboot(pls don't ban me lol).
The dev said it was a DT(device tree) bug and that the fix wud take time.
And since there was more trolling than development happening in that group, I exited it.
Once it boots, it wud probably be posted under roms, so no need to join that toxic group as of now
Click to expand...
Click to collapse
Thanks bro, t.me is crazy with bots monitoring everything. Its not very secure as per me coz it downloads unwanted things to our device. It feels like as if soviet kgb is watching every group we join LOL.

I just wanted to say that if you're in android 11, you can flash the GSI image directly to system. Use TWRP 3.5.1 v3
Wipe data ( If you want to decrypt internal storage, flash multi disabler and format data )
Flash GSI
Flash dmverity disabler or magisk

Fredin_ said:
I just wanted to say that if you're in android 11, you can flash the GSI image directly to system. Use TWRP 3.5.1 v3
Wipe data ( If you want to decrypt internal storage, flash multi disabler and format data )
Flash GSI
Flash dmverity disabler or magisk
Click to expand...
Click to collapse
Hi Fredin bro, long time ..how you been? Youre the most helpful nice guy in t.me
My Redmi Note 10 came with MiUi 12.5.1 Android 11 out of the box, in these two months that ive been using Nebrassy2-Twrp and its different than Soulr344-Twrp, (Soulr344-Twrp 'super ' command = Nebrassy2-Twrp '#su' command), I couldnt flash GSIs using ( TWRP-3.5.2-mojito-Nebrassy-2.img ) so far.
Ive requested Soulr344 dev to make Soulr344-Twrp for RN10 Mojito/Sunny. If he ever drops by XDA perhaps he might notice.

Question How to flash a Android 12 ROM without decryption problem?

I've been struggling to flash Android 12 without my internal storage to be unaccessible by TWRP... I simply can't decrypt my data and the only way to fix it is to format data and revert back to a Android 11 ROM.
Did anyone manage to flash Android 12 successfully? How?

Well I gotta tell you sadly, decryption does not work for any Android 12 system currently. So you gotta have to live with it, until we get decryption support.
And don't try to fiddle with disabling encryption, I did it and I quickly regretted it.
Also, you always have to format data after flashing a ROM to remove encryption, except if you update your current ROM.

ADB Sideload is the answer.
If you have TWRP installed already then as you know when you go into recovery you cant see any data. User ADB Sideload instead and it will flash it the same way

KashMiester said:
ADB Sideload is the answer.
If you have TWRP installed already then as you know when you go into recovery you cant see any data. User ADB Sideload instead and it will flash it the same way
Click to expand...
Click to collapse
ADB sideload isn't the answer, because that's already what I use to flash a Android 12 based ROM. Doesn't change that TWRP can't decrypt data

meirioon said:
ADB sideload isn't the answer, because that's already what I use to flash a Android 12 based ROM. Doesn't change that TWRP can't decrypt data
Click to expand...
Click to collapse
That is because their no recovery that will decrypt A12, just not possible yet. Sideload is the way for now, it works fine. Decryption isn't available yet and hopefully someone cracks it soon

Not towards achieving decryption, however after flashing A12 ROM, and clicking on format data, I get numerous errors with TWRP. Any solution? Is it related to recovery or some issue with data partition? Thanks!

Many people have issues with TWRP. Flash Orangefox recovery in TWRP, boot into it and try.
sujju said:
Not towards achieving decryption, however after flashing A12 ROM, and clicking on format data, I get numerous errors with TWRP. Any solution? Is it related to recovery or some issue with data partition? Thanks!
Click to expand...
Click to collapse

I'm having the same issue but how can I revert back to a Android 11 ROM if my internal storage is inaccessible?

I did it just by flashing Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip after flashing the rom.
You can search for this file in the web.

bizzaro87 said:
I did it just by flashing Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip after flashing the rom.
You can search for this file in the web.
Click to expand...
Click to collapse
Does NOT work at all on Android 12 roms having just tried it

try these scripts

Anybody try these scripts ^? Just sideload them?

I used disable dm verity force encrypt and a12 worked without a problem, I can access image and more! My recovery is orangefox. It worked really great with a12. No problem until now!

patricktech said:
I used disable dm verity force encrypt and a12 worked without a problem, I can access image and more! My recovery is orangefox. It worked really great with a12. No problem until now!
Click to expand...
Click to collapse
@meirioon
+1
For OSS attached

I used disable dm verity force encrypt
Click to expand...
Click to collapse
At which installation stage did you flash it under OrangeFox? Before or after A12 installation?

akapune said:
At which installation stage did you flash it under OrangeFox? Before or after A12 installation?
Click to expand...
Click to collapse
After A12 and magisk.
Directly after DfE don't forget to format data.

Laptapper said:
After A12 and magisk.
Directly after DfE don't forget to format data.
Click to expand...
Click to collapse
that means, that you don't update your rom to a new version without loosing data.
you are always doing a clean install.
or am I wrong?

gorillaz_gr said:
that means, that you don't update your rom to a new version without loosing data.
you are always doing a clean install.
or am I wrong?
Click to expand...
Click to collapse
No, if you're decrypted with DFE once and formated with yes, you can flash new ROM and DFE without formating. Means dirty install without loosing internal data. Or you make clean by only wiping data and in this case also your internal SD stay as before without loosing your personal files.

Laptapper said:
No, if you're decrypted with DFE once and formated with yes, you can flash new ROM and DFE without formating.
Click to expand...
Click to collapse
Do I have to flash DFE again after each OTA update?

akapune said:
Do I have to flash DFE again after each OTA update?
Click to expand...
Click to collapse
Yes but don't format