Develop Bugs

[ROM][angler][10.0.0_r40] AOSP 10.0 [2020/07/05]

{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps.
What's Working:
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
Important Info:
To flash this rom you need TWRP 3.3.1.0 or newer.
Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
vendor, radio, bootloader img's: https://androidfilehost.com/?w=files&flid=286833
The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.
Instructions:
If updating from a previous AOSP-10 build, follow the steps below:
If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above.
Boot into TWRP.
Flash the ROM zip.
Reboot & enjoy.
Note: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
If coming from a different ROM:
If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above. also make sure you have the newest twrp, linked above.
Boot into TWRP.
Wipe system & data & cache partitions.
Format data.
Flash rom & GApps & su zips (GApps & su zips are optional).
Reboot & enjoy.
Note:
If your phone suffers from the bootloop issue, download the BLOD patch and install it via TWRP (4 Core) after flashing the ROM .
Downloads:
Recovery:
TWRP-3.3.1.0
TWRP-3.3.1.0 (4 Core)
BLOD Patch (4 Core)
Builds:
AndroidFileHost
Google Drive
GApps:
Open GApps
XDA:DevDB Information
AOSP 10.0.0, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
Source Code: https://android.googlesource.com/
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Testing
Created 2020-04-15
Last Updated 2020-07-19

Install Instructions
Grab our recovery from the OP Post section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.

Changelog
AOSP-10.0 2020705
July Security Patch

Omg .. Pixelboot is amazong ???

Both build folders seems empty right now...

daigoro64 said:
Both build folders seems empty right now...
Click to expand...
Click to collapse
Check again. They should be back.

PixelBoot said:
Check again. They should be back.
Click to expand...
Click to collapse
Google Drive is fine. Thanks!

Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!
Click to expand...
Click to collapse
It will not cause any issues

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
Click to expand...
Click to collapse
Bootloader and radio are installed for sure by default. You can check their versions starting the device to bootloader.
If there is a Vendor mismatch is show to you as soon as you enter the home.

if I am doing a clean install is it necessary to flash Gapps ?

nueloc said:
if I am doing a clean install is it necessary to flash Gapps ?
Click to expand...
Click to collapse
No. You can either flash or not flash GApps.

I just wanted to chime in and Say thank you @PixelBoot! Also does anyone have a recommended stock like Gaaps that replaces all default apps with their Google counterpart?

I hope there's anybody can help me. I wiped system & data & cache, then flashed the rom. As TWRP said - successfully. While trying to boot the system I saw the message that there is "no OS installed". I tried to boot it anyway and it worked. System booted normally, but it's looking very old fashioned. According to system information in the menu it is android 10 aosp. I realized there is no gapps so I wanted to install them. And here my problem starts - while trying to open TWRP from bootloader by choosing 'Recovery mode' it every time boots the system instead TWRP.

1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.

yourrealking said:
1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.
Click to expand...
Click to collapse
Here is my takes on these "issues":
1. I have linked the recovery which works in the OP thread both for 4 core and 8 core users. Don't see the reason of flashing the recovery from the TWRP website.
2. Yes. I have noticed this. It is an inconvenient bug, but since recovery isn't used too much, we'll have to deal with this minor issue.
3. Logcat would be appreciated if sent while listening to the music.
4. I'm not sure if you are aware that the reason behind this ROM is for the simplicity and stock AOSP. This is not about being feature packed, but is supposed to simulate a newer version for the Nexus 6P's previous firmwares.
5. This setting is set to the default one of AOSP. No modifications were set unlike that of LineageOS.
6. This should be more or less the same as the experience found on LineageOS as the device tree is very similar.

1. I just happened to already have the official 3.1.1.0 installed before installing this ROM. I read the description and thought that since my version was already 3.1.1.0, I did not have to install a new TWRP. This caused me a lot of problems (wasted time waiting it for to boot, lost all files on the Data, because I had to re-flash the stock ROM). I wrote this to help other users so that the may not experience the same thing I had.
3. I have tried Google Music and another third-party music player and the symptom was the same, so I thought it was a known issue. Anyway, this is not really a big issue, just a small stuttering, and I have disabled screen rotation. I just wrote that to help others to know about it before they decide to move to this ROM.
4. Yeah, I know. I did not write that to complain, or force you to implement those, but as other things, I wrote that to help others to decide before installing. Because changing ROM is a big and time-consuming thing, so it is good to know what it can do and what it cannot do before doing it.
5. I see. I could find a workaround, like creating an app that can modify the dimming degree, or disable auto-brightness.
6. This is strange. I can definitely feel big difference. I had been using LineageOS, and most of the time, I used the fingerprint sensor to turn on the phone instead of pressing the power button. Well, this is not a deal-breaker. I just have to put my finger one or two more times or wait one more second till it gets unlocked.
Thanks for the ROM. So far, for me, the feature I can get from Android 10 outweighs the downsides above. I had been stuck at Android 8 for over two years, and it was boring.

Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here

zzitam said:
Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here
Click to expand...
Click to collapse
Yup, completely normal.

Can’t modify the system in any way e.g copying Pixel Launcher to system
Is this because of data encryption?

[UNOFFICAL][TWRP][Recovery] TWRP 3.5.2_9-2 [ysl][UNIFIED]

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Always updated with latest twrp changes
- Decryption Works "Official miui, custom roms"
- Works with any 32bit and 64bit roms
- Treble enabled
- F2FS support
- FDE/FBE & SAR/NON-SAR Unified support
Notes:
- It works only with pie fw
Install guide: "You must have the Bootloader unlocked"
- Install ADB & Fastboot tools on your pc
- Go on fastboot mode
- Run "fastboot flash recovery yourrecoveryimage.img"
- Reboot and enjoy
Bugs:
- Maybe something i didn't saw during my usage, in case send logs if you encounter in a bug
Download:
Here
Support Group:
Here
Source code:
TWRP
Device tree
Kernel
Credits:
@Dees_Troy
@krasCGQ
@mahajant99
@Lostark13
@m_vaisakh
ROM OS Version: Android 9
ROM Kernel: Linux 4.x
ROM Firmware Required: pie
Based On: OMNI
Version Information
Status: Stable
Current Stable Version: 20210130
Stable Release Date: 2021-01-30
Created 2021-01-30
Last Updated 2021-01-30

11/08/2021 Build
HTML:
Source Changelog:
- Synced with latest twrp.me changes
- Merge aosp/pie-gsi changes
- Update f2fs-tools to v1.14.0
- Update nano to v5.2
- Squeeze performance while flashing a zip
- Start progress bar thread only when is required
- General fixes
Device Changelog:
- Build toybox
- Build userspace ExFAT driver
- Fixup encryption issues
- General fixes
Old Builds:
Spoiler
01/03/2021 Build
HTML:
Device changelog:
- Synced with latest twrp changes
- Readd /cust on partitions list
- Backup /persist as image
- Rename /sdcard1 to /external_sd
- General bug fixes

New update is out https://androidfilehost.com/?fid=17248734326145746072
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617

twrp release: 3.5.1_9 · TeamWin/[email protected]
Change-Id: I13dfadea507d7050cec35d00d5cfabdf25462b15
github.com
everything is setted up for the first unofficial 3.5.1 release
waiting for seeing whole changelog on twrp.me ...

interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?

gherv1 said:
interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?
Click to expand...
Click to collapse
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one

Its_Vixano said:
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one
Click to expand...
Click to collapse
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.

gherv1 said:
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.
Click to expand...
Click to collapse
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"

Its_Vixano said:
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"
Click to expand...
Click to collapse
Ok, i tried right now, flashed it, and now rebooted to the system, i see miui logo, and is not moving from there ) and i've the latest stock update, i guess is similar to global ver

removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem

gherv1 said:
removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem
Click to expand...
Click to collapse
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences

Its_Vixano said:
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences
Click to expand...
Click to collapse
There is something else wrong, i just downloaded this one https://xiaomifirmwareupdater.com/miui/ysl/stable/V12.0.2.0.PEFMIXM/
flashed the boot img, and it's still stuck at miui logo, i mean, i have some experience with dead phones, but this one is very strange, oopa, worked now, so it was just the cn boot img, and needed a little bit of time to boot with his normal one
ill try to mod with magisk and flash again, i keep you in touch
I also flashed cache.img, i don't know if helped, but just in case if someone else have same problem

O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay

gherv1 said:
O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay
Click to expand...
Click to collapse
You are welcome

New update is out https://androidfilehost.com/?fid=7161016148664784278
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617

Greetings to the creators of twrp recovery and to the moderators of this thread
I wonder if anyone knows if there are themes to customize this version of recovery 3.5.2 9 0?
Thanks

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.

Development [RECOVERY][OFFICIAL] TWRP 3.7.0-3 for Galaxy A52s 5G

Team Win Recovery Project
Code:
#include <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.
*/
{
"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"
}
Disclaimer:
I am not responsible about any damage of any kind that this custom binary may cause.
Please pay attention to this post & related ones before proceeding and follow the guide correctly. I will not offer support for any issues that have been already stated.
Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox features. It can't be resetted in any way, so think twice before flashing this.
Bugs can be reported here in XDA or via the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
What's TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
Spoiler: Unlock the bootloader
Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
Decryption will only work if no password/PIN/pattern is set in Android (One UI).
Download:
Galaxy A52s 5G (a52sxq):
twrp.me
Bootloader/Modem collection:
GitHub
Sources:
Kernel source code: https://github.com/BlackMesa123/android_kernel_samsung_sm7325/tree/sep-14.1/twrp-12.1
Device tree: https://github.com/TeamWin/android_device_samsung_a52sxq
Changelog:
Check Post #2.
A52s 5G Community Telegram Groups:
General
Development
Credits:
Samsung for the kernel source code
TeamWin for their awesome recovery
@Captain_Throwback for his help and troubleshooting
@ShaDisNX255 & @ronardnx for testing out the recovery

Changelog:
Please note that this only includes device-specific changes. For global TWRP changes, go to twrp.me.
20230104 (3.7.0_12-3)
- Fix /vendor backup restoring
20221224 (3.7.0_12-2)
- Updated kernel to DVK5
- Support Android 13 decrypt with no password
- Fix /efs, /sec_efs backup
20221208 (3.7.0_12-1)
- Fix fastbootd
- Disable stock recovery patching in /vendor
20221012 (3.7.0_12-0)
- First release

It's been a while since I released something here in XDA. I'm happy to join the modding train again with this custom recovery, hoping to see more cool stuff come out for this device soon

Amazing work, always happy to test. Great step towards more development.

Nice job plus Nice instructions. Thanks a lot

Most peru dev

Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?

Brilliant!! Thankz for this. Now bring on custom stuff lol.

Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?

Finally!!

Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
BlueChris said:
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?
Click to expand...
Click to collapse
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps

New minor build released to mitigate the /data and /efs backup errors. If you're still having issues, try to delete the /sdcard/TWRP folder and reboot again to recovery.

New version works perfect. Thanks!!

BlackMesa123 said:
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps
Click to expand...
Click to collapse
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...

BlueChris said:
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...
Click to expand...
Click to collapse
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this

BlackMesa123 said:
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this
Click to expand...
Click to collapse
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?

Yeap i changed to none and is working now.... i will do a full backup now and then i will put the security on again.
Thx anyway.. a full phone backup was what i was needing.

BlueChris said:
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?
Click to expand...
Click to collapse
Unfortunately with the current build you'll have to choose between disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly

BlackMesa123 said:
Unfortunately with the current you'll have to choose betweeb disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly
Click to expand...
Click to collapse
No worries m8, take your time and again thank you for this.

BlueChris said:
No worries m8, take your time and again thank you for this.
Click to expand...
Click to collapse
I have some bad news: unfortunately decrypt with password/PIN set in lockscreen is not supported in the TWRP itself, so posting a new build with fixed gatekeeper would be useless anyway. As soon as the android-12.1 TWRP branch fixes this issue I'll be posting a new build for the recovery, hoping this issue will be addressed asap

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