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. ??

[ROM][12][river] PixelExperience [AOSP]

{
"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"
}
PixelExperience for Moto G7 [river]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 12
Security patch level: January 2022
Build author/Device Maintainer: JarlPenguin
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
​

hello, I have ErrorCode::kInstallDeviceOpenError when sideload the rom with latest river twrp

bitgamer said:
hello, I have ErrorCode::kInstallDeviceOpenError when sideload the rom with latest river twrp
Click to expand...
Click to collapse
Please follow the instructions here. Keep in mind that TWRP isn't supported.

I get the same error as previously posted by bitgamer. I can get PE 11 to work fine. Any help would be appreciated.

I made it!
Follow these steps:
* Reboot into bootloader
*fastboot flash oem
*fastboot flash system
*fastboot flash vendor
*fastboot flash boot
*fastboot flash dtbo
* Reboot into recovery (if not reboot by cmd, reboot manually)
*Apply update by adb
*In CMD window type adb sideload followed by PE12 ROM click enter
* Reboot system

eltuzz said:
I made it!
Follow these steps:
* Reboot into bootloader
*fastboot flash oem
*fastboot flash system
*fastboot flash vendor
*fastboot flash boot
*fastboot flash dtbo
* Reboot into recovery (if not reboot by cmd, reboot manually)
*Apply update by adb
*In CMD window type adb sideload followed by PE12 ROM click enter
* Reboot system
Click to expand...
Click to collapse
can u help me pls? i cant install it

silvatuzkii said:
can u help me pls? i cant install it
Click to expand...
Click to collapse
Download SUPER IMAGES from: https://t.me/ClubJarlPenguin/2420
Download boot.img (recovery) and dtbo.img from: https://t.me/ClubJarlPenguin/2421
Download Pixel Experience ROM from: https://download.pixelexperience.org/river
Download copy-partitions-20210323_1922.zip
Extract super_images.zip in your platform-tools or ADB folder
Copy boot.img and dtbo.img in your platform-tools or ADB folder
Copy the Pixel Experience .zip package in your platform-tools or ADB folder
Copy "copy-partitions-20210323_1922.zip" in your platform-tools or ADB folder
Enable USB debug option in your phone (you need to enable developer options)
Code:
adb devices
adb reboot bootloader
fastboot flash oem super_oem.img
fastboot flash system super_system.img
fastboot flash vendor super_vendor.img
fastboot flash dtbo dtbo.img
fastboot flash boot boot.img
Reboot to recovery mode with volume and power keys. (this recovery looks like the factory recovery)
Sideload the copy-partitions-20210323_1922.zip package by doing the following:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine sideload the package using:
Code:
adb sideload copy-partitions-20210323_1922.zip
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine sideload the package using:
Code:
adb sideload PixelExperience_river-12.0-20220126-1621-OFFICIAL.zip
Tap factory reset
Reboot
Enjoy

Can I dirty flash over last PE Plus 11 (Oct 2021 build)

I can't flash PE recovery at all: "(bootloader) image not signed or corrupt"
Yes I can boot TWRP recovery very easy, but this ROM requires PE recovery for flashing. Is there alternative method to flash or boot PE recovery???

demijan said:
I can't flash PE recovery at all: "(bootloader) image not signed or corrupt"
Yes I can boot TWRP recovery very easy, but this ROM requires PE recovery for flashing. Is there alternative method to flash or boot PE recovery???
Click to expand...
Click to collapse
Download boot.img (recovery) from: https://t.me/ClubJarlPenguin/2421
Code:
fastboot flash boot boot.img
Reboot to recovery mode with volume and power keys.
(this recovery looks like the factory recovery not like the PE, works perfect)

I successfully upgraded from PE 11 to new PixelExperience 12 ROM
Sideload the copy-partitions-20210323_1922.zip is unnecessary in my case.
Thank you so much for your help!

I can't seem to sideload the copy-partitions file. It always gives the error message "failed to find META-INF/com/android/metadata, failed to parse metadata in the zip file. Installation from ADB completed with status 2. Installation aborted"" I downloaded the copy-partions file several times in case of a bad download. Any suggestions to get this to work. Also could i continue to sideload the PE rom after this error? Thanks

My problem in this PE 12 ROM is that the wifi connection is generally poor and not always constant. Yes, and one more thing, the antutu benchmark result in this ROM is about 50% lower than in the PE 11 ROM!

dwilbur said:
I can't seem to sideload the copy-partitions file. It always gives the error message "failed to find META-INF/com/android/metadata, failed to parse metadata in the zip file. Installation from ADB completed with status 2. Installation aborted"" I downloaded the copy-partions file several times in case of a bad download. Any suggestions to get this to work. Also could i continue to sideload the PE rom after this error? Thanks
Click to expand...
Click to collapse
I too am having this issue. Opening the file with 7zip shows there is no "/android/metadata" subfolder. Looked for an older version of the file and it's almost the same. ie instead of "/android/metadata" there is "/google/andriod" with the following files
update-script
update-binary
I can get to fastboot mode and into recovery mode but that's about it. Any help to either complete the PE install or revert to stock would be appreciated.

Restoring to the original android 10 ROM is very easy, just download the appropriate stock ROM from this site: https://motostockrom.com/motorola-moto-g7-xt1962-5
and flash it according to simple instructions. The procedure is completely safe and painless

JarlPenguin said:
Please follow the instructions here. Keep in mind that TWRP isn't supported.
Click to expand...
Click to collapse
Please!!!!....when will we have an update?

Seriously, to install this rom is it necessary to install an image first? LOL

I hope that in an eventual update (if there is one) it will be an installation with fewer steps, as usual.

JarlPenguin said:
PixelExperience for Moto G7 [river]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
​
Android OS version: 12
Security patch level: January 2022
Build author/Device Maintainer: JarlPenguin
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
I​
Click to expand...
Click to collapse
It doesn't work Very well on mine, it constantly Closes my keyboard makeing it so I can't have my keyboard open for More than a second. And my mobile data flickers on and off (I'm on TMobile)

This is very strange behavior, did you try factory reset maybe?

[ROM][Android 13][UNOFFICIAL][OTA] LineageOS 20.0 for Xiaomi Mi A2 Lite [daisy]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
- Selinux is enforcing
- FBE build, don't use twrp for these builds
- Custom kernels are NOT supported
- Read the instructions carefully
Downloads
- Here
Flashing instructions
- Here (Suggestions for improving the guide are welcome)
Sources:
- LineageOS
- Kernel Tree
Happy modding!

Reserved

Good news

Great!

Okay but does it run Crysis?

Stonks

I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot

a1291762 said:
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
Click to expand...
Click to collapse
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
for now you can use some old build i made https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220319-UNOFFICIAL-daisy.zip
i should upload a new one as soon as possible (maybe tomorrow/today)

Its_Vixano said:
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
Click to expand...
Click to collapse
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
My recovery process:
* Boot into TWRP
* Flash Lineage 18.1
* Boot into (Lineage 18.1) recovery
* Install Lineage 19.1
* Boot into (Lineage 19.1) recovery
* Flash Gapps and Magisk
* Boot into system

a1291762 said:
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
Click to expand...
Click to collapse
Avoid using the 'fastboot boot' command, somehow it doesn't works
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery

Its_Vixano said:
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Click to expand...
Click to collapse
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.

a1291762 said:
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
Click to expand...
Click to collapse
It should work, but sometimes it takes a couple of tries with reboots in between. I did not find a pattern yet, but in general flashing boot and doing the power vol+ combo should be fine. Maybe it's a timing thing, not sure. Try to switch which button you press first maybe, or try to press them at the exact same time. A bit weird, yeah
UPDATE: pressing the + button just a bit earlier seems to be doing the trick for me!

just done a test build for fixing the privapp permission issues (random bootloops caused by some normal reboots), seems fine here but i don't really trust my self
https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220329-UNOFFICIAL-daisy.zip
report if something will be wrong with it
edit: Apparently it's fine so
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting

Its_Vixano said:
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Click to expand...
Click to collapse
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed

a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Yep, that's the right way to update the rom

I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer

nabav said:
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
Click to expand...
Click to collapse
- Just follow the instructions, everything is written here
- Should be stable enough for daily driving it, sadly i don't use daisy anymore as a 'primary' device
- I also use fdroid and adaway and they don't require root

a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Hi a1291762,
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used? If it is an upgrade procedure rather than an update procedure (are those to be expected at all?) can you give a more detailed explanation? I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?). Does your procedure work with fastboot or adb? Whatsoever, though it is not my daily driver I am very happy with my Mi A2 Lite with TWRP and Magisk but I also like playing... (with 75 years).
Thanks for all of your efforts!
grufty47

grufty47 said:
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used?
Click to expand...
Click to collapse
The OP guide seems to be written for people coming from something other than Lineage. The first part of it sets up the Lineage recovery and formats user data.
Since I was coming from Lineage and already had the recovery, I figured I could skip those steps. The OP guide says you can skip formatting data if you're coming from Lineage and I figured the recovery can't have changed too much.
I don't know how much testing was done for a Lineage 18 -> 19 upgrade. It worked for me but I barely had anything installed when I did it. Make backups in case of data loss and all that.
Something I don't understand in the OP guide is the suggestion to use the copy_partitions script. It only seems useful if your phone is somehow in an odd situation where miscellaneous A and B partitions don't match? It can't hurt to run it I guess.
grufty47 said:
can you give a more detailed explanation?
Click to expand...
Click to collapse
My 18->19 upgrade process matches the 19 "OTA" process. Refer to the OP guide for screenshots and details.
1. Boot to recovery
2. Sideload the lineage zip
3. Reboot to recovery (changes the active slot)
4. Sideload gapps
5. Sideload Magisk
The lineage zip is like a "full OTA" for the stock ROM. Flashing it overwrites system, boot and vendor, hence the need to flash gapps and magisk again. But the recovery only supports flashing to the current slot, hence the reboot in the middle.
grufty47 said:
I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?).
Click to expand...
Click to collapse
FBE has to do with encryption. I found this that might help explain it.
https://www.reddit.com/r/LineageOS/comments/hd534a
Booting TWRP 3.5.2_9.2 (fastboot boot twrp.img) shows only garbage names under /sdcard plus a bunch of other places (but not all of /data). So I guess TWRP doesn't support FBE encryption? I'm not sure why that matters for flashing system partitions, but if any of lineage, gapps or magisk expects to write to places covered by FBE then clearly that's not going to work properly under TWRP.
Since you have installed TWRP over the Lineage recovery, you'll have to get a Lineage recovery back on your phone before you can upgrade. Using the provided recovery should work I guess? If not, you could use TWRP to flash the most recent Lineage 18 zip, which will also replace TWRP with Lineage recovery. Part of the reason I attempted the 18->19 upgrade in the first place is because I couldn't get the provided recovery to boot on my phone.
I hope that helps.
Lincoln

[ROM][13.0][OnePlus 7T Pro][OFFICIAL] crDroid v9.5 [20230620]

{
"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
Installation/Update Instructions:
From official ROM Android 12 to crDroid 9
From official ROM Android 11 to crDroid 9
From crDroid 8 (or other custom ROM) to crDroid 9
Installing crDroid 9 updates
Sources:​ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Common Device tree: https://github.com/crdroidandroid/android_device_oneplus_sm8150-common
Device tree: https://github.com/crdroidandroid/android_device_oneplus_hotdog
Vendor Common Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_sm8150-common
Vendor Device tree: https://github.com/crdroidandroid/proprietary_vendor_oneplus_hotdog
Download:​crDroid ROM
Recovery Image
OnePlus 7T Pro firmware
GAPPS: Already Included
Known issues:​Tell me
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
crDroid OnePlus 7T Pro (hotdog) Telegram group

From official ROM Android 12 to crDroid 9
Spoiler: Click to expand...
Pre-installation:
Download latest recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Unlock the bootloader (Instruction)
3) Enter to fastboot mode (With the device powered off, hold Volume Up + Volume Down + Power).
4) Flash our recovery in both slot:
Code:
fastboot flash recovery_a <recovery_filename>.img
fastboot flash recovery_b <recovery_filename>.img
5) Reboot to installed recovery
Code:
fastboot reboot recovery
6) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
7) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
8) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

From official ROM Android 11 to crDroid 9
Spoiler: Click to expand...
Pre-installation:
Download latest vendor firmware, recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Unlock the bootloader (Instruction)
3) Enter to fastboot mode (With the device powered off, hold Volume Up + Volume Down + Power).
4) Unpack vendor firmware zip file. We go into the unpacked folder and run the Update-firmware.sh file (if you have Linux installed) or Update-firmware.bat (if you have Windows) from the Administrator account. We follow the instructions of the installer step by step and make sure that everything is done without errors. At the end of the script program, the phone will reboot into recovery mode.
After the first start of recovery, the screen will not perceive pressing the screen. To navigate through the menu, use the volume buttons and the Power button to confirm the selection.
5) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
6) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
7) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

From crDroid 8 (or other custom ROM) to crDroid 9
Warning:
People ask the question: "Is it possible to update crDroid 8 firmware to crDroid 9 while keeping the data"? Yes it is possible. But, after the update, there may be problems with some programs or the system. Therefore, I highly recommend doing a "clean" install.
Spoiler: Click to expand...
Pre-installation:
Download latest vendor firmware, recovery image and latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Enter to fastboot mode (From system: Restart... -> Bootloader. Or with the device powered off, hold Volume Up + Volume Down + Power).
3) Unpack vendor firmware zip file. We go into the unpacked folder and run the Update-firmware.sh file (if you have Linux installed) or Update-firmware.bat (if you have Windows) from the Administrator account. We follow the instructions of the installer step by step and make sure that everything is done without errors. At the end of the script program, the phone will reboot into recovery mode.
After the first start of recovery, the screen will not perceive pressing the screen. To navigate through the menu, use the volume buttons and the Power button to confirm the selection.
4) (You can skip this step if you decide to save the data) Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
5) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
6) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

Installing crDroid 9 updates
If for some reason OTA update is not possible. The data will be saved.
Spoiler: Click to expand...
Pre-installation:
Download latest crDroid 9 firmware (Download)
Installation:
1) Backup your data to PC, OTG flash drive...
2) Reboot system into Recovery mode (From system: Restart... -> Recovery. Or with the device powered off, hold Volume Down + Power.).
3) On recovery main page tap Apply update -> Apply from ADB
Now sideload <rom_filename>.zip using command:
Code:
adb sideload <rom_filename>.zip
If getting message Signature verification failed click Yes. You'll see process stuck on 47%, Don't worry you'll get Success message just wait.
6) Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.

Reserved5

in the next update, if possible, would love to see dolby/opcam
eagerly waiting to install . thanks a lot for andoid 13 <3

On android 12 when i unlock i am losing widevine L1.
ON android 11 when i unlock it is retained.
Damn the new vendor blobs.
i just flashed back to oos11 and unlocked while retaining widevine L1.
Would it be possible to retain L1 and flash Crdroid 9 when on android 11 without the new vendor blobs?
Is anybody else facing this issue?
iv'e tried 2 upgrade paths. from oos11 and oos12.
Only when unlocking on oos11 i can retain L1.
alternatively is there a way to unlcok bootloader on A12 and retain widevine L1?
thanks so much for your work... been excitedly waiting for crdroid 9.

Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?

vsm778 said:
Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?
Click to expand...
Click to collapse
I had the same problem on some rom need to modify point access and change some parameters like delete user/pass, proxy etc..

Thetimelost said:
I had the same problem on some rom need to modify point access and change some parameters like delete user/pass, proxy etc..
Click to expand...
Click to collapse
ill just stay on crdroid 8 for a bit longer, im rooted and have all my favourite magisk modules. Plus i'm waiting for some crdroid 8 features to get transferred to crdoird 9 (like OOS Camera, dolby atmos, etc.).

Anyone with auto brightness problem? Mine is going crazy sometimes. Everything is normal and suddenly "boom" - screen is going brighter and I must manually dimm it.

vsm778 said:
Had latest Android 11.
Followed instruction `from Android 11 to crDroid 9`.
Everything went fine except mobile data. Couldn't connect. Wifi only.
I guess there's a problem in a modem.
Any thoughts?
Click to expand...
Click to collapse
just goto sim settings and reset access points and mobile data will start working. i was going crazy for 2 days thinking something is wrong with ROM.

===== 20221107 =====
* Added: Allow disabling clipboard overlay
* Added: Hidden network support for hotspot
* Added: Connected devices manager for hotspot
* Added: More DNS providers to private DNS
* Added: Long press to copy wifi password
* Added: Show more APK details on App info screen
* Launcher: some more small changes here and there as well as fixes
* Enable split notification shade in landscape
* Some more improvements to hotspot
* Fixed possible SIM issues with non-dual sim variants
* Removed notification clear all icon/bg styles (useless)
* Added wireguard support
* Reworked bootanimation
* Rebased Updater
* Updater: corrected changelog URL
* Updated Aperture (Camera)
* Updated libcore
* Updated translations
* Many Fixes and Improvements
>> Download link <<
or OTA update
================
Donate for my work

When I install this my touchscreen stops working. How do I fix this?
Crdroid 8 was working perfectly.

FalKoopa said:
When I install this my touchscreen stops working. How do I fix this?
Crdroid 8 was working perfectly.
Click to expand...
Click to collapse
You missed the "Firmware" step

chuckiler said:
On android 12 when i unlock i am losing widevine L1.
ON android 11 when i unlock it is retained.
Damn the new vendor blobs.
i just flashed back to oos11 and unlocked while retaining widevine L1.
Would it be possible to retain L1 and flash Crdroid 9 when on android 11 without the new vendor blobs?
Is anybody else facing this issue?
iv'e tried 2 upgrade paths. from oos11 and oos12.
Only when unlocking on oos11 i can retain L1.
alternatively is there a way to unlcok bootloader on A12 and retain widevine L1?
thanks so much for your work... been excitedly waiting for crdroid 9.
Click to expand...
Click to collapse
is there any way to get widevine L1 working with the A12 vendor blobs?
has anyone suceesfully retained L1 while updating A12 vendor blobs?

chuckiler said:
is there any way to get widevine L1 working with the A12 vendor blobs?
has anyone suceesfully retained L1 while updating A12 vendor blobs?
Click to expand...
Click to collapse
It's since the oos12 and cos12 CBT came out that I unlock both and I still have widevine L1.
And so are 99% of users.
You are doing something wrong

Can anyone please tell me if this ROM passes safetynet and banking apps can be used as well?

After trying all available A13 ROMs for my 7T pro ..... I must say this is the most stable, most fluid ROM with best battery backup.
But PE excels in particular 2 fields i.e. audio(you can easily distinguish between each instrument playing in background) output quality and display calibration(if you have the eyes to see the difference of finer tuning of each spectrum). Though the difference is really negligible.
I think in overall score this ROM beats PE. Soooo fluid I can't believe it !!!
Thanks dev for this awesome stable ROM.
I'll again come back to this ROM in future builds to see if these two fields are also set above par.
Again I can't thank enough for this awesome ROM.

Development [Recovery] [a32] OrangeFox Recovery Project [Stable-ish, Unofficial]

{
"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
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this 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.
*/
Introduction
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox version: R11.1
For device: a32
Maintainer: Ahnet ( @Captain_cookie_200 )
OrangeFox source:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Device tree:
GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6.
Device tree for building OrangeFox Recovery for Samsung Galaxy A32 4G (MTK), based on A325FXXU2BVD6. - GitHub - Epico-Bot/ofox_device_samsung_a32: Device tree for building OrangeFox Recovery for Sa...
github.com
Kernel Source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features:
Code:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included assorted customizations
Inbuilt patches, like Magisk and password reset patch
Several addons
Password protection
Fully open-source
Frequently updated
Status
Stable-ish
Tested on:
SM-A325F (by me)
SM-A325M (by @filipedonato)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings is fixed but for fixing settings such as theming resetting on reboot is by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.​
Installation
Code:
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:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. 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).
5. Your device will boot into download mode with a warning. Accept it.
6. 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.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
 
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename OrangeFox recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. 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:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: OrangeFox TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. 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 OrangeFox up and running now.  
 
Post-Installation:
MUST: Trigger Multi-disabler.
1. In OrangeFox, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
1. In OrangeFox, go to Backup
2. 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, PBRP and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to OrangeFox (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. 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.
Credits:
To the OrangeFox and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.

reserved

reserved

I have tried to talk to various developers about the settings not saving issue. They have no idea. I have myself tried playing around with the tree but nope. So unless someone has a fix for this i have no idea

New Build!
Whats new?
Fixed the settings such as theming resetting on reboot by editing the bootable/recovery/twrp.cc and at line 396 (as of now) changing the bool to true. This makes the recovery load the themes twice. This should only be for encrypted devices but since it has fixed our issue we'll use this workaround until a proper solution has been found.
If you see the recovery trying to decrypt storage dont worry about it. its just because of this. It does nothing.

It's stable? I mean, i can install gsi's and zips?

ApiYoshi said:
It's stable? I mean, i can install gsi's and zips?
Click to expand...
Click to collapse
yes i use orangefox. flashing gsi works fine. same goes with zips

Captain_cookie_200 said:
yes i use orangefox. flashing gsi works fine. same goes with zips
Click to expand...
Click to collapse
Ok, i flashed it and is awesome!! Thanks for great work brother!

ApiYoshi said:
Ok, i flashed it and is awesome!! Thanks for great work brother!
Click to expand...
Click to collapse
You should make a telegram group

ApiYoshi said:
You should make a telegram group
Click to expand...
Click to collapse
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates

Works in A32 A325M Brazil variant.

really nice you are keeping the a32 alive!

applesucksLmao said:
really nice you are keeping the a32 alive!
Click to expand...
Click to collapse
i did nothing tbh. all the credit goes to the people who put effort in making twrp work i just copied and built it. all the credit goes to them

Captain_cookie_200 said:
i dont really know on how to maintain one. me and someone else made it but its sitting dead i'll see later on. and i'll post a thread abt it if there are any updates
Click to expand...
Click to collapse
Ooh, i undertand

One question, you will update the recovery when an update came out?

ApiYoshi said:
One question, you will update the recovery when an update came out?
Click to expand...
Click to collapse
yes i will try

Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it

Seth Ofc said:
Where do I get the orange fox TAR, I see it in the steps but I don't see it to download it
Click to expand...
Click to collapse
sorry i didnt include it. but i think i specified. rename OrangeFox recovery img file to recovery.img
then use 7zip or winrar or any other archiver and then add to archive. There select tar and compress. I'll include tar files in next builds by default

Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it

Seth Ofc said:
Thanks I already compressed the recovery.img to recovery.tar, do you know of any aosp rom for the a325m I was looking for but I can't find it
Click to expand...
Click to collapse
use a generic system image.
if you want heres a list: here