Database Info

Question Leave data unencrypted

Hello! Is there any possibility now to leave data partition unencrypted?
Tried to install miui.eu with PBRB with dfe toggles enabled - no result.
Tried to install same through TWRP + latest dfe - no result
Tried to install havoc treble + dfe - no result.
Am I missing something?
UPD
I've created DFE patch for 12.0.6.0 xiaomi.eu firmware
Original firmware is hosted here
xiaomi.eu_multi_POCOX3Pro_V12.0.6.0.RJUMIXM_v12-11.zip | by Xiaomi.eu for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Patch is here.
Яндекс
Найдётся всё
disk.yandex.ru
You should replace files in original firmware with files from patch and flash it through recovery
I also flashed latest DFE(may be not beeded)
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
And latest stable magisk(may be also not needed)

If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?

kamild_ said:
If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?
Click to expand...
Click to collapse
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru

Aaaaand I've done it. Works perfectly. Now uploading

What's the pros of leaving data unencrypted?

Do we have to do this unpacking and repacking process for every new version of stock ROM?

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
The only real benefit I know of is being able to switch between different ROMs without having to format data - it would still be recommended to wipe it, but you would be able to preserve your internal storage between ROMs.
Theoretically there's also some performance that you could reclaim by getting rid of encryption, but on such powerful SoC any gains would not be noticable maybe outside of benchmarks.

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
Minor CPU performance and NAND lifetime gain. Also if you somehow clear contents of /metadata partition - you will loose all of your files on /data partition ( and internal sd as /data/media too).
Also several years earlier days I've faced a problem when new firmware can't decrypt data after previous one(it was in lolipop times as I can remember). So, if I can preserve /data unencrypted - I'll try to do so.
qwert8988 said:
Do we have to do this unpacking and repacking process for every new version of stock ROM?
Click to expand...
Click to collapse
Seems yes, at least for now. Not for every rom, just for vendor part.
You can apply this patch to any rom based on 12.0.6.0 vendor. You'll only have to edit original dynamic_partitions_op_list file from rom archive - replace "resize vendor" string with
resize vendor 1563119616

Thanks for the work. Confirmed worked on ArrowOS build 2021.05.04. Flashing dfe and masgisk are not necessary

Thanks !!! It works !!! This is what I have been looking for...
{
"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"
}

vodkinagdan said:
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru
Click to expand...
Click to collapse
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.

Haldi4803 said:
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.
Click to expand...
Click to collapse
If rom is based on OSS vendor - for android 11 this patch working well now. You can try it on A12

[ROM] [OFFICIAL][A13][GApps][GCam] BlissRoms 16.x [guacamole]

{
"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"
}
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customization's across all platforms you run Bliss on.
BlissRoms Download
Code:
[/B][/SIZE][/CENTER]
[SIZE=5][B][CENTER]-Make sure you are on the latest OOS 12
- Dump the BlissROM zipfile through payload_dumper
- flash the partition images with the following commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- Reboot and #StayBlissful
​
Create Bug Report on our Issues Tracker
BlissRoms Github
BlissRoms Gerrit
Kernel Source
| Website | Blog | Facebook | Twitter | Instagram | Telegram Group | Telegram Channel | Docs
If someone wants to donate, please do so via this PayPal link
Thank you for using BlissRoms! And as always: #StayBlissful​

Notes:Oneplus Cam included but video recoerding is not working. GCam GO is also included.

reserved too

I see the installation process is different than the usual factory wipe from recovery, and then flash zip to both sides. Would this process not work?

jp85041 said:
I see the installation process is different than the usual factory wipe from recovery, and then flash zip to both sides. Would this process not work?
Click to expand...
Click to collapse
There are a couple of ways to flash this rom. The important thing is that you are on the latest OOS 11 on the slot you are going to flash the rom on. One way to flash is to follow the install instructions in the first post or what I like to do is flash it through twrp. The problem is decryption doesn't work so you will have to have the rom image on a flash drive. I always recommend formatting data when the android version changes.

Noob question here. Why is it necessary to get the various img files via payload dumper? Why can't they just be assembled in a rar/zip file? Thanks

I love the ROM, haven't ran Bliss since the OnePlus One iirc, not bad at all. Visible works too so that's a plus. Thank you! Aside from going with something like substratum, is there a way to change accent color? I looked in Themes under Blissify settings but can't find where to change it. The only bugs I have had was the screen not coming back up until clicking power but it was literally one time and only waited 5 seconds to resolve.

Does it have built-in phone recorder

Not by default as far as I have seen, not something I looked into that closely. Fun note, my phone is also a bit glitchy compared to others, so don't take my weird issues as representative of the entire ROM, but if I watch videos that have too loud of a noise and I have my volume turned all the way up, my phone powers down. Happened on the daily dose of internet video where they show a slow motion bolt being cut.

Bliss is one of the best custom roms I have experienced, thanks for beating this titan work to support oneplus 7 pro

New build v16.2
Many new features
Built on OOS 12 firmware
GCam
Download: https://downloads.blissroms.org/media/guacamole/Bliss-v16.2-guacamole-OFFICIAL-gapps-20221226.zip
Rom Changelog: https://blog.blissroms.org/2022-12-06-typhoon-16.2-updates-dec-2022/
Enjoy!

srgrusso said:
There are a couple of ways to flash this rom. The important thing is that you are on the latest OOS 11 on the slot you are going to flash the rom on. One way to flash is to follow the install instructions in the first post or what I like to do is flash it through twrp. The problem is decryption doesn't work so you will have to have the rom image on a flash drive. I always recommend formatting data when the android version changes.
Click to expand...
Click to collapse
Are you sure we need to be on oos11 firmware? Most other A13 roms require A12 firmware

bobbylo said:
Are you sure we need to be on oos11 firmware? Most other A13 roms require A12 firmware
Click to expand...
Click to collapse
A12 Firmware. I flashed a couple days back. Running great.

sfacimma said:
A12 Firmware. I flashed a couple days back. Running great.
Click to expand...
Click to collapse
ok,thanks

bobbylo said:
ok,thanks
Click to expand...
Click to collapse
hey,one more question,How did you flash this,just from the bootloader?Or from the recovery fastboot mode? Thanks

what may be the problem when I use bliss 16.2 in oneplus 7 pro the phone heats up quite a bit and discharges quickly while with other roms everything is normal

bobbylo said:
hey,one more question,How did you flash this,just from the bootloader?Or from the recovery fastboot mode? Thanks
Click to expand...
Click to collapse
Sorry. Didn't see this earlier. Here's what I did......
Extract the boot.img from the payload.bin
From cmd prompt:
adb reboot bootloader
Once in bootloader, and from cmd prompt:
fastboot flash boot boot.img
Reboot to Recovery
--wipe/format (you'll lose all data/pics/files)
--Install via ADB option (I forget the actual option name)
Then, from cmd prompt on PC:
adb sideload Rom_Name.zip
When completed (after sitting at 47% for a while):
--Reboot to System option

Thanks for this Bliss, nice work !

sfacimma said:
A12 Firmware. I flashed a couple days back. Running great.
Click to expand...
Click to collapse
Can you guide me how I should flash oos 12 on both slots? since MSM tool only flashes to one slot

Obnomus said:
how I should flash oos 12 on both slots?
Click to expand...
Click to collapse
Go to crDroid 13 thread, it says in red text where to get the tool for flashing 12 firmware in both slots.

Development [TB-J716F] TWRP for Android 12 / ZUI 14

Hi, people!
Spoiler: Old message:
Porting our TWRP for A12 (ZUI 14.0.127).
Now it's fully working, exept touchscreen. But with mouse connected via OTG you can to do all neeeded operations.
IMPORTANT! The method of decrypting /userdata is not implemented there (different from A11), so you need to install the DFE-NEO patch to make it work properly with your data.
EDITED: New version v5
Added ability adb/MTP on encrypted /data.
MTP works on demand, pressing Disable MTP-Enable MTP, displays SD card only.
UPDATED Febr. 08:
Built a new full-featured version with data decryption from source. For Android 12 - ZUI 14
Decrypts data by default, if the tablet is not protected.
If it's protected by pin/password, it asks for it and decrypts internal storage.
I haven't tried the pattern, see here: https://twrp.me/faq/openrecoveryscript.html (Specific pattern decrypt note), try it yourself.
Device tree lies here: https://github.com/F1tm0t/twrp_device_lenovo_J716F
Many thanks to:
Yahoo Mike - for useful tips on decryption implementation and general support.​LSS4181 - for Q706F device tree, I used it as a basis for mine.​Ungeskriptet - for his J716F device tree for A11, it was useful for me.​TWRP_J716F_A12_DD. img DD means Data Decryption.
Working: Everything, excluding vibration.
MEGA

PS.
Welcome to collaboration.
I have another variant of TWRP with a malfunctioning touch. The pressure points do not correspond to the position of the buttons. It need to add some calibration files or the right firmware or the right driver for the screentouch. This is too complicated for me I'm just advanced user, no guru.
Please, write me in PM if you can help with this issue.

Nice to see some development for the TB-J716 tablet XD since the developer don't want to release the kernel source/ open source to the public.

Die you add the firmware for touch to TWRP? I have it like this in my TWRP port: https://gitlab.com/ungeskriptet/and...tree/android-11/recovery/root/vendor/firmware
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.

Ungeskriptet said:
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.
Click to expand...
Click to collapse
Yes, I was trying this.
Thanks for the tip. I have a couple of questions. I'll write you in PM, if you don't mind.

Version with working touch is here:
Файл из Облака Mail.ru
Вам открыли доступ к файлу. Отправлено с помощью Облако Mail.ru.
cloud.mail.ru
and here:
100 MB file on MEGA
mega.nz
Remember, you can't to backup data before using DFE-NEO patch.
Many thanks to Ungeskriptet for helping.
To be continued (I hope)

New version for ZUI 14 with new features:
* added many partitions for backup/restore
* added some partitions for flashing via Install IMG
* A set of partitions is enough to backup/restore an entire OS
Placed here. To see how it works, click here:
Spoiler: Youtube
FFBM mode is my mistake, wrong button pressed, no need

Hello @f1tm0t
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Could you help to edit that value? I tried many tool to rebuild TWP with new prop but no luck, device bootloop
Thanks

phamthanh said:
Hello @f1tm0t
Click to expand...
Click to collapse
Hello, friend.
My TWRP works with adb/MTP quite excellent.
The following is needed:
decrypt /data
permission in the system to debug from this computer
Spoiler
{
"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"
}

Thanks for your help, I will redownload and double-check again.

Hi @f1tm0t
I re-download and flashed v3 but the same result
Could you help me to check it
Thanks

phamthanh said:
I re-download and flashed v3
Click to expand...
Click to collapse
I offer version 4: https://mega.nz/file/g4VBnIpC#_4_x0b3V-Z6oSoXDA2xbHSN7hBKXRgjnwfFMLfPcYXA
My version cannot decrypt /data, so you have to install the DFE-NEO patch from TWRP.
After rebooting to OS you must to enable USB debugging, it create adb.key in /data.
And after rebooting to TWRP you can use adb/MTP, because TWRP sees adb.key in not-encrypted /data.

phamthanh said:
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Click to expand...
Click to collapse
Made new version (in the title), adb works by default. Enjoy!

f1tm0t said:
Made new version (in the title), adb works by default. Enjoy!
Click to expand...
Click to collapse
Many thanks

Updated.
New TWRP with working data decryption, see update in topic.

CrDroid-v9.0 Pixel 4 XL

crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
official builds can be found here = https://sourceforge.net/projects/crdroid/files/coral/9.x
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCES
Kernel: https://github.com/putzwon/android_kernel_google_msm-4.14
Device tree: https://github.com/putzwon/android_device_google_coral
Vendor: https://github.com/putzwon/proprietary_vendor_google_coral
ElmyraService: https://github.com/putzwon/android_packages_apps_ElmyraService

putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
what about flame? is it updated build?

cRdroid rocks the PX4!!! Thank you putzwon!!!

what the different with this version..?
link

Thank you so much sir
putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
thaaaaaaaaaaaaaaaaaaaaaanks

can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?

very good
{
"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"
}

anonras said:
what the different with this version..?
link
Click to expand...
Click to collapse
This is the latest Android 13 (crDroid-v9.0 android 13.0), your link is the older 12.1 Android

vlbr said:
can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?
Click to expand...
Click to collapse
It might work, but stick with OP steps, those 110% WORK, but up to you. I gave up on TWRP when A/B partitions came out and chose to just stick with and use stock ROM recovery. That will always work, TWRP, maybe not so much, IDK, it might, but you wont get the same type of help if you choose your own path (TWRP).
Also, just an FYI on nomenclature, this isn't firmware, but ROM, firmware contains all partitions, drivers, ETC., this is just the OS (ROM).

Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time

tonyhieu said:
Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time
Click to expand...
Click to collapse
huh?

GROOVYJOSHCLARK said:
huh?
Click to expand...
Click to collapse
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.

tonyhieu said:
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.
Click to expand...
Click to collapse
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.

@putzwon, I have used this OS (ROM) since Friday, and thoroughly testing EVERYTHING! WOW, I am literally floored at how well EVERYTHING works!!
I have NO ISSUES, NO BUGS, NO SHOWSTOPPERS, nada. Even Now Playing works, I am floored by all of this! It is amazing, and I rarely say that about a ROM (with no bugs also being reported - at the same time), and as I noted earlier, in the past, cRdroid wasn't great for me (random bugs, and/or missing features I rely on). NOT this version, this version IS GREAT FOR ME, I have EVERY SINGLE possible tweak I want/need/use, PLUS functional services / RIL (Radio Interface Layer) I.E. CALLs/TXT/MMS, PLUS no bugs, or FCs, or anything that would keep me away!
Normally, I use LOS, and LOS only (while testing all other ROMs for users and myself), but always landing back with LOS, not this time! I am STICKING WITH cRdroid for the foreseeable future, it is my DailyDriver and will remain so until something changes (but doubtful at this point)!! I have everything I need, baked right into the ROM, so I don't even need my LSPosed modules (other than SafetyNetFix once ROOT'ng)!
EXTREMELY WELL DONE and THANK YOU FOR THIS ROM!!!! For the rest of XDA users, this ROM WORKS! It works EXTREMELY WELL, is bug-free (from my extensive testing and standpoint). I haven't found any bugs yet (not a single one)!

GROOVYJOSHCLARK said:
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.
Click to expand...
Click to collapse
Yes, this is a type of 4XL, it's cheaper to 20% .

Installed it yesterday and almost everything is working perfectly. The only feature that seems to be missing Soli which is a shame since it's a fun novelty.

best rom ever love you

thaaanks

Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks

ojessie said:
Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks
Click to expand...
Click to collapse
it is easy
i do it everytime I flash a custom rom
you need to root your phone using magisk
then instal
Migrate - ROM backup 5.0.1​from play store
open it and take a full backup of your installed apps
copie this backup to your laptop
and after flashing this perfect rom
copie the backup from the laptop to the phone
and root the phone again
and instal
Migrate flasher​from play store
open it
and flash the file you backed up
this way you will have allll your apps including your banking apps with all your data
you will not have to instal anything twise...
good luck
it is easy
don't worry..

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery​View attachment Samsung-Logo-MSP.webp​
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers
Note :-​
Samsung binery is impossible to downagrade. ​This method will do install old stock as a custom rom (signature removed stock rom). So this method only can downgarde android version. ​This method cannot downgrade modem or radio or bootlooder such as (aboot,lk,non-holes) like critical images. if you try that it will dead your device​
Click to expand...
Click to collapse
Not Tested in All Devices. So I Don't know this method is working for all samsung devices. Proofs are at the end. You Have to try and tell
What you need​
Latest binery of stock rom that you need to downgrade​
Bootloader Unlocked Device​
Lz4 Unpacker​
Simg2img.exe​
Hxd​
Android Image kitchen​
Odin​
7zip​
Windows Computer
​If you have super.img device shipped with Android 10 or Android 10+​You must have unlocked bootloader​If your device cannot use magisk this method will not work for you. (A20s user cannot do this) ​
1. Unlock your device bootloader​2. Download the Latest binery of stock rom that you need to downgrade (samfw)​3. Extract the whole Ap.....tar.md5​Get all boot.img.lz4 recovery.img.lz4 super.img .lz4(vendor.img.ext4.lz4 and system.img.ext4.lz4)​
{
"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"
}
4. Convert .lz4 to img​Grag and drop lz4 file to lz4.exe​​5. Then Patched the boot.img with magisk and unpack and repack recovery.img using android image kitchen (aik)​6. Then paste simg2img.exe to where converted super.img located.​
7. Then open cmd from there and type simg2img super.img super.raw​then you will get a super.raw​
8. Open HXD and grag and drop super.raw to hxd​​9. Then CTRL+F and search all the U number of the firmware you downloded​According to me it is U4​
9. Then Find a phases like this and fill all phases with zero bytes (there should be more than one)​
10. Then Save it and remove the super.raw.bak​11. Then Rename the super.raw to super.img and make tar with 7zip including patched boot.img recovery.img and super.img​12. Flash it and Format data​
Patched vbmeta is not essential due to magisk patched boot.img​
If you Have System.img and Vendor.img Device Shipped with Android 7 8 9​​1.Do all the steps untill number 6​2.Then convert system.img.ext4 and vendor.img.ext4 to raw by open cmd then, simg2img.exe system.ext4.img.raw and same to vendor​3.Open both System.ext4.img.raw form Hxd and Countinue with step 9​4.Then save Both vendor and system and delete the .bak files​5.Then rename system.img.ext4.raw to system.img.exe4 and vendor.img.ext4.raw to vendor.img.ext4​6.Then Convert to Lz4 by open cmd and lz4 -1 system.img.ext4​7.Then Make tar using Magisk patched boot.img and repacked recovery.img and system.img.ext4.lz4 and vendor.img.ext4.lz4​8. Flash and wipe Data​
Patched vbmeta is not essential due to magisk patched boot.img​​Proof Tested Devices,​
Samsung Galaxy M01 (Qualcomm)
Downgrade Android 12 to android 10 (u4 to u3)
Samsung Galaxy A71 Qualcomm
Android 13 to Android 10 (U8 to U3)
Updates​
Some users said they cannot flash super.img in a51 and s20 exyons version. May be this method will not work for exyons. I dont know that need to test more
Downgrade success for s20 fe 5g qcom using this method
Still not tested on MTK
Video Tutorial​
Remove Signature from Super or System/Vendor​
Downloads​Hxd
This method also can use for update android version without upgrading binery version.​

Interesting.. I'll try it when I get back my pc

tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding

oznear said:
tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding
Click to expand...
Click to collapse
Try with replace vendor/firmware from u4 stock (dosent depend on android version)

Hi, If I flashed it through Odin, do I still need to supply the BL, CP, CSC? Thanks in advance.

A10 -> A9 9 on SD S10: the flashing itself works but device's now stuck on booting - cannot get to A9 recovery

jq555888 said:
Android 10 -> Android 9 on snapdragon S10: the flashing itself appeared to work but device's now stuck on booting - cannot get to Android 9's recovery for some reason which I suspect is due to a different partition layout (device's shipped with Android 9); tried to erase userdata with Android 10's recovery but still can't get it to finish booting. Any ideas?
Click to expand...
Click to collapse
You used latest version of android 9?

smiley9000 said:
You used latest version of android 9?
Click to expand...
Click to collapse
Yeah - this was last version of A10 - A9

jq555888 said:
Yeah - this was going from G9700ZHU4DTL2 (last version of Android 10) to G9700ZCS2ASJU (last version of Android 9)
Click to expand...
Click to collapse
stuck in android boot animation?

smiley9000 said:
stuck in android boot animation?
Click to expand...
Click to collapse
yes! it's like the startup screen

jq555888 said:
yes! it's like the startup screen where it usually says the phone's model (with the text "this phone is not running official software"). it's the one after pressing the side button, but not the "SAMSUNG" screen.
Click to expand...
Click to collapse
enable usb debugging and try to get logs

smiley9000 said:
enable usb debugging and try to get logs
Click to expand...
Click to collapse
thank you! any way to achieve this by modifying the official A9 rom?

jq555888 said:
thank you! any way to achieve this by modifying the official A9 rom?
booting to twrp for A9 also fails not sure if it's a parition problem but A10 twrp works
Click to expand...
Click to collapse
maybe due to kernel

hello ! i have a problem with Android image kitchen , when i click repackimg.bat he say me
Fichier introuvable
Paramètre incorrect.
Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers
Packing ramdisk (as root) . . .
Windows sudo required but not found.
*** Reinstall Android Image Kitchen, then add ***
*** sudo.exe to your antivirus exceptions! ***
Error!
how can i fix this pls?

Thanks for taking the trouble to make this thread @smiley9000
Anyone tried this on s10e exynos variant with android 12 - downgrade to android 10 ?