Develop Bugs

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G​Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea)
Disclaimer
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 recovery 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.
Kernel Features:
latest kernel source release
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
spoofed config for firmware checks
Recovery Features:
built in full 64 mode
toybox/busybox support
compatible with Android 10.0 and above
Downloads:
S10e - beyond0lte - G970F/G970N
S10 - beyond1lte - G973F/G973N
S10+ - beyond2lte - G975F/G975N
S10 5G - beyondx- G970F/G977N
avb disabled vbmeta
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download avb disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + bixby + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download avb disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + bixby + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - beyond0lte / beyond1lte / beyond2lte / beyondx
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9820/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
07.03.2022 - TWRP 3.6.1
Security patch: 2022-02-01
Compatibility: only GVA*/GVB* firmwares, OneUI 4.0
Spoiler: Archive
09.01.2022 - android 12 support
Security patch: 2022-01-01
Compatibility: only GUL* firmwares, OneUI 4.0
08.01.2021 - android 11 support
Security patch: 2020-12-01
Compatibility: only ETL* firmwares, OneUI 3.0
27.12.2020 - TWRP 3.5.0 bringup - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
09.12.2020 - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
05.12.2020 - Initial release
Security patch: 2020-11-01
Compatibility: DTJ* firmwares
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Patch TWRP with Magisk
Use recovery to boot up rooted
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version and only if you don't plan to boot rooted with TWRP (some kernels deliver root prebuilt in kernel), or Rollback protection will kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

further reading moved to #2

Thanks for your work, good job

Amazing work as always Corsi, thank you so much!

Thanks Sir I'm fan of your hadesRom and I'll wait your new work//from Thailand

Well done as always

Great work as aways @corsicanu! Keep it up and don't worry about the others, OFFICIAL is yours, haters gonna hate...
Cheers!

Can I just flash this to recovery in ians twrp that I currently have?

Eidluci said:
Can I just flash this to recovery in ians twrp that I currently have?
Click to expand...
Click to collapse
What it says on the box...
If you already have TWRP installed, download .img file according to instructions from step 9 from above, and install from your current TWRP with Install image - browse to image location and select - Recovery

is this better than the ianmcd 3.4.0.3 TWRP?

r3xx3r said:
is this better than the ianmcd 3.4.0.3 TWRP?
Click to expand...
Click to collapse
My thoughts exactly!
For that matter, is it better than Modpunk's 3.4.0-0?
There are various custom ROM Modders stating use this (name) TWRP - all stating different TWRPs.
Presently we have 3 different Mods versions of TWRPs for the S10- family.
I, for one, have difficulty in seeing the difference between the TWRPs???

One is compatibility, two is ian's dropping the support.

Hi! I have problem with latest samsung firmware and twrp. I can get root and i can install twrp from 0. But recovery can't access data folder (sam folders with strange name) and multi disabler put the phone in a "stack at samsung logo" state! Why?

rubino25 said:
Hi! I have problem with latest samsung firmware and twrp. I can get root and i can install twrp from 0. But recovery can't access data folder (sam folders with strange name) and multi disabler put the phone in a "stack at samsung logo" state! Why?
Click to expand...
Click to collapse
You have to format /data to decrypt your device. Be aware that you'll loose all your data. Read FAQ, it includes all the info you need.
Cheers!

AndrzejDwo said:
You have to format /data to decrypt your device. Be aware that you'll loose all your data. Read FAQ, it includes all the info you need.
Cheers!
Click to expand...
Click to collapse
Thanks!

Norup58 said:
My thoughts exactly!
For that matter, is it better than Modpunk's 3.4.0-0?
There are various custom ROM Modders stating use this (name) TWRP - all stating different TWRPs.
Presently we have 3 different Mods versions of TWRPs for the S10- family.
I, for one, have difficulty in seeing the difference between the TWRPs???
Click to expand...
Click to collapse
If you're not using any modpunk rom (such as his LineageOS) - you'll need to use his twrp - no way around that. - it's really not recommended if you want to run any of the ROMs besides that as it'll likely not work.
Ianmcd twrp is best used on any rom/fw below DTI8 (so anything from DTH7 and below) - This is losing support soon and no longer will be updated.
(tldr: unless you're planning to use my crdroid 7, Ivan's lineage 18 or latest 17.1 - I recommend you keep to this twrp until other roms are updated)
This twrp here (corsicanu) is now the recommended twrp from now on as long as you're on DTI8 or above and flashing DTI8 based roms.

Official builds are up, updated the links and the instructions, read carefully everything before you brick your phone.

Congrats @corsicanu. As always, quality work. Keep it up mate. ??

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 10/+/5G Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 10/+/5G​Only for exynos variants - N970F / N975F / N976B (Europe - Global, Single/Dual-SIM), N971N, N976N (South Korea)
Disclaimer
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 recovery 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.
Kernel Features:
latest kernel source release
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
spoofed config for firmware checks
Recovery Features:
built in full 64 mode
toybox/busybox support
compatible with Android 10.0 and above
Downloads:
Note 10 - d1 - N970F
Note 10 5G - d1x - N971N
Note 10+ - d2s - N975F
Note 10+ 5G - d2x - N976B/N976N
avb disabled vbmeta
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download avb disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download avb disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - d1 / d1x / d2s / d2x
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9820/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
07.03.2022 - TWRP 3.6.1
Security patch: 2022-02-01
Compatibility: only GVA*/GVB* firmwares, OneUI 4.0
Spoiler: Archive
09.01.2022 - android 12 support
Security patch: 2022-01-01
Compatibility: only GUL* firmwares, OneUI 4.0
08.01.2021 - android 11 support
Security patch: 2020-12-01
Compatibility: only ETL* firmwares, OneUI 3.0
27.12.2020 - TWRP 3.5.0 bringup - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
09.12.2020 - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
05.12.2020 - Initial release
Security patch: 2020-11-01
Compatibility: DTJ* firmwares
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Patch TWRP with Magisk
Use recovery to boot up rooted
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version and only if you don't plan to boot rooted with TWRP (some kernels deliver root prebuilt in kernel), or Rollback protection will kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

official builds will be up in few hours

Nice, congrats!

Hi, i'm getting the Note 10 soon & remember when i've tested the S10 months ago that i had trouble with twrp encryption/decryption : can you confirm after wiping data that you can encrypt it (system) and twrp will be able to decrypt it after you enter your pattern..? Thanks.

Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
PS: N971N does not have a build compatible with OneUI 3.0 since no public release of that yet, it will be built once samsung starts pushing the update for that phone.
Regards!

corsicanu said:
Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
PS: N971N does not have a build compatible with OneUI 3.0 since no public release of that yet, it will be built once samsung starts pushing the update for that phone.
Regards!
Click to expand...
Click to collapse
is the latest TWRP 3.5.0_9-4-d1 compatible with the latest Samsung ROM update? Below are the details of the firmware update I'm referring to:
ModelSM-N970FModel nameGalaxy Note 10VersionAndroid 11Changelist21054212Build dateThu, 18 Feb 2021 05:15:51 +0000Security Patch Level2021-03-01Product codeXTCPDAN970FXXU6FUBDCSCN970FOXM6FUBD
Thanks in advance!
Edit: based on this article it's One UI 3.1

Hi,
Is this method works and safe for N971N?
Android 12

nilofino said:
Hi,
Is this method works and safe for N971N?
Android 12
Click to expand...
Click to collapse
Actually I tried and it works

Is it safe after installing TWRP to RE-LOCK the bootloader???

tried using with android 12 trough magisk and i got phone blocked on samsung logo, also i was unable to select storage on wipe menu, any insight?

nilofino said:
Actually I tried and it works
Click to expand...
Click to collapse
HOW?!
I have the same SM-N971N, but I Got the error of showing less storage than it has after flashing. Like, -192GB/60GB and in settings it shows 16GB, Constantly says the TA Downloader has stopped.
So it messed up totally in my case ; and i reverted back
So Help me how did you managed?!

Rafin Rahman said:
HOW?!
I have the same SM-N971N, but I Got the error of showing less storage than it has after flashing. Like, -192GB/60GB and in settings it shows 16GB, Constantly says the TA Downloader has stopped.
So it messed up totally in my case ; and i reverted back
So Help me how did you managed?!
Click to expand...
Click to collapse
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions

nilofino said:
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions
Click to expand...
Click to collapse
No to be honest, i never messed with that part lol
But if it really is how you say, then let me try this pain once again :")

nilofino said:
Just follow the instructions!
It seems that you have selected "repartition" option (in odin options),
You can find the solution easly. Maybe installing the stock Rom helps, but plz search for the solution before doing any further actions
Click to expand...
Click to collapse
can you help me finding the twrp flashable zip for N9710N?

I used the original one from official website
Rafin Rahman said:
can you help me finding the twrp flashable zip for N9710N?
Click to expand...
Click to collapse

nilofino said:
I used the original one from official website
Click to expand...
Click to collapse
OK I DID IT! But man, twrp got installed, but no magisk, nothing is installing/flashing via TWRP, idk whyy!! :")
Maybe its android 12 thats causing problem
It did successfully installed TWRP as Custom Recovery, but as for superuser, Im handcuffed now , Sed Lyf:")

Intento instalar Twrp junto con Vbmate en mi N971N y me tira este error y si solo instalo Twrp no pasa del logo de Samsung

Thank you for your hardwork!

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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 Recovery
* 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.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

[ROM][UNOFFICIAL][UNIFIED] VoltageOS v2.2 [Android 13][January 23th, 2023]

{
"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"
}
VoltageOS 13.0 | Tiramisu for Mi A2 Lite (daisy)​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
More info: HERE
Telegram Voltage: Group
If you like our work you can buy us a cup of coffee
*TogoFire Maintainer Daisy
*PIX: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOAD:
VoltageOS 2.2 230123: CLICK HERE
SHA256: 3c21e3f7c2b8c6f90f8c7388e0a481c6e842f313d2dfd04c5f6c6e5fcda18385
Gapps $hit Package (Recommended): LiteGapps | Microg | MindTheGapps
Recovery: HERE
If you use instagram or any $hit like facebook, use this: LINK
Installation Guide​Clean Flash
1) If you are coming from any MiuiROM, GSI, or any other PortROM, edl miflash from firmware 10.0.18.0 or 11.x.x is mandatory.
2) Edl firmware 11.x.xx or 10.x.xx (install firmware via miflash if needed)
3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs).
4) Reboot to recovery
5) Boot to Recoovery
6) Format Data--Yes
7) Reboot to recovery
8) Wipe data, system, dalvik cache, internal storage.
9) Install ROM
10) Install TWRP
12) Reboot to recovery
13) Install LiteGapps (optional)
16) Install Magisk (optional)
17) Reboot to system
Dirty Flash
1) Backup Everything (Most Important)
2) Download ROM
3) Boot to TWRP (Power and vol+; or Advanced Restart > Recovery)
4) Backup Data partition (optional)
5) Install the 'update' ROM
6) Install TWRP ZIP (optional)
7) Then reboot to recovery. (Note: in current recovery the slot changes by itself, no longer need to change manually)
8) Install GApps that you've used to installed, and Magisk.
9) Wipe dalvik and reboot
10) Reboot to system
GUIDE FULL
Link​
ROM Source: https://github.com/VoltageOS
Source: Kernel & Device & Vendor
Support Links:​TogoFireWork Channel
TogoFireWork Group
McQuaidLab
XDA:DevDB Information
ROM OS Version: Android 13.0 | Tiramisu
ROM Kernel: Linux 4.9.X
ROM Firmware Required: 10.0.18, 11.0.04, 11.0.16 or greater
Based On: AOSP

reserved!

reserved...!!!

@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovery with format data system etc.? Thanks.

dr.bahaeddin said:
@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovert with format data system etc.? Thanks.
Click to expand...
Click to collapse
Being firmware greater than or equal to 10.0.18, it's fine. If it's coming from a Lupe rom, then just go straight to install the rom

Is this pre-overclocked? What are the clocks?

ortizjammet said:
Is this pre-overclocked? What are the clocks?
Click to expand...
Click to collapse
McQuaid Lab
McQuaid Lab Kernel: https://t.me/McQuaidKernel Download & Changelog: LINK Kernel Source If you like our work you can buy us a cup of coffee *TogoFire Maintainer *PIX: [email protected] Orangefox old OrangeFox Recovery Project...
forum.xda-developers.com

It will be helpful is guys share your experience about this rom...

New update!
Small important fixes made.
Changelog of the last commits: IMG | DT
Enjoy!

@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.

dr.bahaeddin said:
@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.
Click to expand...
Click to collapse
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.

TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this
Click to expand...
Click to collapse
TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.
Click to expand...
Click to collapse
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?

cappuccini said:
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?
Click to expand...
Click to collapse
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.

TogoFire said:
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.
Click to expand...
Click to collapse
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!

cappuccini said:
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!
Click to expand...
Click to collapse
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.

TogoFire said:
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.
Click to expand...
Click to collapse
...the requirements of the individual ROMs seem to differ a lot, with LOS for example they are supposed to be significantly higher.
what about the XDA rules? These also have to be complied with in an official ROM. what about banking apps and other security-critical apps in case of damage? Metadata is stored with every login. Even the proprietary messenger WhatsApp registers a custom ROM and refuses support.
In a Samsung thread a maintainer wrote that the unofficial ROM is only for testing.... A very difficult topic for me, ultimately everyone must decide for themselves who they trust.
Thanks for the insight into the world of developers and best regards

Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
...this installation guide has been very helpful to me:
[DEPRECATED] Detailed Installation Guide for Custom Roms (Mi A2 Lite - Daisy)
Heya, This is a guide aimed on helping you to switch to a custom rom from the stock firmware. For any questions, feel free to join our Telegram groups. PREREQUISITES 1) Stock rom recommended by the maintainer of the rom that you want to flash...
forum.xda-developers.com
P.S. I am currently testing MSM Xtended v4 with LiteGapps core, there were no problems during installation.

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
Can it be that you have installed GApps for Android 12? This ROM is Android 13...

SOLVED! YEAH! Took me hours but finally got it!
So either the new stock rom (daisy_global_images_V11.0.21.0.QDLMIXM_10.0) did it or it is related to the installation with adb sideload or from SD card which caused my issue (I finally simply copy the installation zip files through USB while TWRP is active on the phone and gives access to the memory from computer, and installed them using the dedicated button (no adb sideload)).
Time to test now
@cappuccini : yeah I read this guide and had the android 13 gapps version (but you are right, it took me a while to understand it was the folder 33 on sourceforge...).

[ROM] [13] [taimen] crDroid 9.5 [OFFICIAL] [18.04.2023]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
Gapps (for vanilla variant) (Download from here)
Magisk Delta 25.0 or newer for root (after first boot) - (Download from here)
Pixel 2 XL Product partition extender zip (repartition): Instructions here
First time installation:
Wipe all partitions. Boot into fastboot and execute:
fastboot erase system_a
fastboot erase system_b
fastboot erase product_a
fastboot erase product_b
fastboot erase vendor_a
fastboot erase vendor_b
After that, follow instructions:
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Flash pixel 2xl extender zip: adb sideload <zip_name>.zip
After finished, reboot into fastboot
Activate opposite slot you want to flash: fastboot --set-active=b to flash in slot A and vice versa
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <rom_name.zip>
Wait to get finished.
Go to Reboot and reboot to bootloader
Set active slot where you installed ROM (ex. A): fastboot --set-active=a
Wipe data with fastboot -w
Boot into system. Enjoy
Note:
For Vanilla build, extra steps are:
Do steps from 1 to 13 also. After that:
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <gapps_name.zip>
Reboot to bootloader
Wipe data with fastboot -w
Boot into system. Enjoy
Update installation:
Option 1:
Use seamless OTA.
Option 2 (Recommended):
Boot into fastboot mode
Set opposite active slot (ex. if you installed ROM in slot A, change to B): fastboot —set-active=b
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Dirty flash ROM with command and wait to finish: adb sideload <rom_name.zip>
After it's finished, go to Reboot and select slot where you installed ROM
Reboot to system and enjoy
Note:
For Vanilla, do steps from 1 to 7 but skip point 8 and do this:
Reboot to bootloader
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <gapps_name.zip>
Reboot to bootloader
Wipe data with fastboot -w
Boot into system. Enjoy
If you installed Magisk, do steps from 1 to 7 but skip point 8 and do this:
For Vanilla do steps from note before Magisk!
Reboot to bootloader
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Flash Magisk zip: adb sideload <magisk_name.zip>
Wait to finish
Reboot to system and good to go
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_wahoo
Download:
ROM
Vanilla: https://crdroid.net/taimen
Gapps (unofficial): Download
Changelog: https://crdroid.net/taimen/9#changelog
Known issues:
None, please report if you find any into
Visit official website @ crDroid.net
crDroid Device Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Update 18.05.2023
Changelog:
* Android May 2023 Security
* Switch completely to AOSP Monet implementation
* Use Google Lens as QR code scanner when google search is installed
* Fix crash in rare instance while opening notification panel
* Added new QS header images
* Fixed systemui crash on QS panel pull down in rare instances
* Fixed few overlapping lockscreen fonts
* Various fixes and trivial optimizations
Download:
Vanilla
Gapps (unofficial)
Update 17.04.2023
Changelog:
Device changes:
* Enable Smart Charging
* Removed some unnecessary packages and blobs as included in March Security updates
Rom changes:
* Initial crDroid 9.4 release
* Updated to April 2023 security patches (android-13.0.0_r41)
* Allow toggling VoWiFi while roaming by default
* InternetDialog: Require unlocking to turn on hotspot
* Added back support for unlinked ringer streams
* Fixed Eleven options such as "use as ringtone" and "delete" media due to missing MANAGE_EXTERNAL_STORAGE permission
* Update Chromium Webview to 112.0.5615.101
* Updated translations
* Bug fixes
Download:
Vanilla
Gapps (unofficial)
Update 01.04.2023
Changelog:
Device changes:
* Enable Smart Pixels
* Enable FPS Info
* Fixed some sepolicy issues
Rom changes:
* March Security 2023 Update
Download:
Vanilla
Gapps (unofficial)
Update 01.03.2023
Changelog:
Device changes:
* Fix rounded corner rendering issues
* Enable app suggestions
* Use AiAi for app predictions
Rom changes:
* Introduce App Lock
Download:
Vanilla
Gapps (unofficial)
===========================
Update 25.02.2023
Changelog:
Vanilla:
* Android February 2023 Security update
* Updated and fixed Safety Net checks without root by default
* Various under the hood optimizations for performance
Gapps:
* Same as Vanilla
Download:
Vanilla
Gapps (unofficial)
Check flashing instructions for steps!
Also this ROM needs repartition. For more info, check flashing instructions.
Report bugs: Telegram group

Awesome...cant wait to boot this bad boy! Mahalo!

We became official! xD

So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.

ieatabiscuit said:
So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.
Click to expand...
Click to collapse
can you attach logs? also do you have Telegram? please join group and report there if you have. Thanks.

Hello,
Is this offer unlimited google photo backup in original quality?

Rajaasim1980 said:
Hello,
Is this offer unlimited google photo backup in original quality?
Click to expand...
Click to collapse
Hello. Yes, it does

IonutGherman said:
Hello. Yes, it does
Click to expand...
Click to collapse
Great mate i will try this thanks

Is current build enforcing or permissive? Google Pay with Magisk probably works, right? Thank you, great job, @IonutGherman.

Yahoo1 said:
Is current build enforcing or permissive? Google Pay with Magisk probably works, right? Thank you, great job, @IonutGherman.
Click to expand...
Click to collapse
Enforced. Yes, works if you know how to hide it properly.

hello when i try to flash rom in twrp then it gives this error
failed to mount /vendor(device or resource busy)
flashing from stock android 11 with unlocked bootloader
any solution would be appreciated ?

ieatabiscuit said:
So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.
Click to expand...
Click to collapse
Just flashed this again. Full data format/wipe. Have data on Verizon no prob. Text sending doesn't work for me either. BUT... I can send gifs, emojis, pics, AND recorded voice msgs. With mic button on text line,, not mic button that's on tool line that writes out text. It's VERY strange. Still haven't received a response from anyone I sent logs to.

I realized that I was getting error because of not doing re-partition before flashing the ROM as was on stock android 11. I actually wasted so many hours in failed attempt of flashing so many ROMS and has to flash stock factory image many times ..don't know why no flashing instructions in here mention this important part of doing re-partition

Rajaasim1980 said:
I realized that I was getting error because of not doing re-partition before flashing the ROM as was on stock android 11. I actually wasted so many hours in failed attempt of flashing so many ROMS and has to flash stock factory image many times ..don't know why no flashing instructions in here mention this important part of doing re-partition
Click to expand...
Click to collapse
Forgot to mention that, will update main thread in the next couple of days. I am busy now with studying.

KC69 said:
Just flashed this again. Full data format/wipe. Have data on Verizon no prob. Text sending doesn't work for me either. BUT... I can send gifs, emojis, pics, AND recorded voice msgs. With mic button on text line,, not mic button that's on tool line that writes out text. It's VERY strange. Still haven't received a response from anyone I sent logs to.
Click to expand...
Click to collapse
Where did you sent logs? To who?

Sorry guys, I builded in a hurry and made this topic kinda in a hurry too, next weekend will be free and will put everything to have a smooth installation and good experience. Also will bring new update. Thank you.

IonutGherman said:
Where did you sent logs? To who?
Click to expand...
Click to collapse
To los team. I don't know how to send a log here. Tell me how on xda and I'll send you one.

KC69 said:
To los team. I don't know how to send a log here. Tell me how on xda and I'll send you one.
Click to expand...
Click to collapse
LOS Team doesn't have anything to do with crDroid. If you have Telegram, join this group: https://t.me/ionutbuilds
or when you reply, you have a button to attach files. from Matlog app, go to 3 dots - Save zip and upload that zip here or in the Telegram group.

IonutGherman said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
Gapps (Download from here)
Magisk Delta 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1: Boot into TWRP
step 2: Format Data, Wipe other. Reboot to another slot and repeat.
step 3: Flash crDroid zip
step 4: Reboot to Bootloader, boot to TWRP
step 5: Flash Gapps - (optional and only for Vanilla)
Update installation:
Option 1 (Preferred):
Use seamless OTA.
Option 2 (Preferred):
step 1: Reboot to inbuilt recovery (From Either Advance restart - after holding the power button, when phone is on OR Press Volume up and power from power off state.)
step 2: Navigate to "Apply Update" -> "From ADB"
step 3: From your computer issue command "adb sideload <FILENAME>
step 4: Flash Gapps using sideload - (optional and only for Vanilla).
step 5: Reboot
Option 3:
step 1: Boot into TWRP
step 2: Flash crDroid
step 3: Reboot to Bootloader, boot to TWRP
step 4: Flash Gapps - (optional and only for Vanilla).
step 5: Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_wahoo
Download:
ROM
Vanilla: https://crdroid.net/taimen
Gapps (unofficial): Download
Changelog: https://crdroid.net/taimen/9#changelog
Known issues:
None, please report if you find any into
Visit official website @ crDroid.net
crDroid Device Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Click to expand...
Click to collapse
Will there be an official build for the regular Pixel 2 sometime in the future?