Develop Bugs

[ROM][SOFIA*/RAV*][10][UNOFFICIAL] OmniROM

{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28

2.3.x Gingerbread?

Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!

googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help

lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F

rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse

stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.

Although not "rooted" you can root after installation just like you would with stock.

Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!

GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!

griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?

.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs

Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs

Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!

My Screen isn't working anymore... using an OTG to move around....
It's the touch screen

Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.

Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?

ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?

gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse

Gotta love how unsupported this ROM is... Or just busy dev...

[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 [ROM] AOSP 12 - SODP [12.0.0_r16]

Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* 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 kernel
* 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?
Android™ SONY Open Source Project (SODP) is AOSP Android as Google publish without any modifications.
*This ROM build is 100% Sony AOSP Code and I planning adding upstream into kernel sony in futures.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough. re-verify you hva respected step flash
----DOWNLOAD SODP ----
GDRIVE
- INSTRUCTIONS FLASH -
1) GO IN FASTBOOTD
On you PC: Enter the following command and wait for the device to reboot into fastbootd : fastboot reboot fastboot or before device start press volume down + power button , in menu select fastbootd
2) DOWNLOAD OEM BINARY & flash it : fastboot flash oem (youroemfile).img
3) UNPACK SODP.ZIP & FLASH these image SODP :
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash product product.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash system_ext system_ext.img
fastboot erase metadata ( if you have error partition no exist like me just ignore )
ignore all other img - I have simply added in zip all img generated after compile
4 ) reboot in recovery - wipe data/factory reset
5) reboot in system ENJOY
Bugtracker:
- I tested and build looks stable for daily use. I have doing basic test and seem all working , I can see btw no night mode enabled by default.
SODP Bugtracker -> If you think the problem is in SODP ( REPORT WITCH PROPER LOG )
XDAevDB Information
AOSP, ROM for the Xperia 10 III
Contributors
Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 12
ROM Kernel: Linux 4.19.x
ROM Firmware Required: Latest Stock Firmware recommended
Based On: AOSP
Version Information
Status: BETA initial release
Current Beta Version: 12
Beta Release Date: 2021-30-12

Is this the same as this?

TrulyPain said:
Is this the same as this?
Click to expand...
Click to collapse
yes its exactly that

ada12 said:
yes its exactly that
Click to expand...
Click to collapse
Okay, thanks for fast answer.

Built it myself in october (AOSP 11), tried to flash it, but got stuck at sony logo and it bootlooped. Will try your tip @ada12 with flashing oem_a and oem_b. Am i right that i have to flash it that way:
fastboot flash oem_a (youroemfile).img
fastboot flash oem_b (youroemfile).img
Do you have any idea how to enable signature spoofing when building the rom? If i succed to do this, i'll build it in the future myself.

Hans Satt said:
Built it myself in october (AOSP 11), tried to flash it, but got stuck at sony logo and it bootlooped. Will try your tip @ada12 with flashing oem_a and oem_b. Am i right that i have to flash it that way:
fastboot flash oem_a (youroemfile).img
fastboot flash oem_b (youroemfile).img
Do you have any idea how to enable signature spoofing when building the rom? If i succed to do this, i'll build it in the future myself.
Click to expand...
Click to collapse
for enable signature spoofing need modify aosp sources ... - you can find patch easy from majority of reposity of custom rom ( pixel experience, ex ... )

I did build and deploy the aosp 11 (not 12) for this phone ok. However did anyone found a way to get the sony camera app on the phone?
The stock app is really basic...
I can also try to deploy the lineageOS version (if one exists) but does anyone know if it has a better camera app?
BTW, I can build aosp 12 but I did not find the sony blob for 12. On their site it is only for 11. Does the OEM 11 works with aosp 12?
Thanks,
M.

Hey, this worked however
I tried this myself and noticed I seem to head into a boot loop after rebooting some 5 times. I don't know what causes this, but I noticed it after trying to get gapps to work via magisk and randomly hit into a "Your device is corrupt" sony boot loop.
I tried without magisk/root, and noticed I hit the same issue after rebooting 5 times (just to see if it was rebooting in general causing this).
It fixes itself with data intact once I reflash the boot once again.
I'm stumped as to what causes this. Is it because I rebooted multiple times within half an hour? Is there something that can trigger the phone to think boot partition is corrupt?
Edit: It was one of the files I flashed from the Op's post, after I flashed everything to stock 167 EU firmware and only updated system.img with a bunch of GSI's (as I learnt they are a thing and damn perfect), I got it working. Guess something was incompatible between my device and the files attached.

Will you be keeping this up to date? How does it compare to GSI? I just want completely barebones degoogled rom.

Good on Sony for offering this up, that's amazing. And thank you OP for building it!
Anyone who is running it - does it have OTA updates? Or do you need to build and flash each time?

WaterMan! said:
Good on Sony for offering this up, that's amazing. And thank you OP for building it!
Anyone who is running it - does it have OTA updates? Or do you need to build and flash each time?
Click to expand...
Click to collapse
I will need rebuild in every update and user will need reflash all img ... december build have selinux permissive its worried me for security I will need modify sony sources for fix it

My phone just got bricked, lol. For the third time. By rebooting my phone. This piece of software has some bugs left. Also pro-tip for the future: Userdebug builds are often more buggy as they are not meant for production use.

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 [UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)

OrangeFox Recovery Project​
{
"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"
}
Downloads OrangeFox-R12.1​
Installation (for Stable roms )
Code:
fastboot boot OrangeFox-12.1-lisa.img
After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot.
​
Installation method 2 (If you firmware based on weekly China Beta (xiaomi.eu and other)
[UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)
OrangeFox Recovery Project Downloads OrangeFox-R12.1 Installation (for Stable roms ) fastboot boot OrangeFox-12.1-lisa.img After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot. Installation method 2 (If you...
forum.xda-developers.com
NEW: OrangeFox Recovery | Build in Cloud
Version Information
Status: Beta ( Unofficial )
Current Beta ( Unofficial ) Version: R12.1
Release Date: 10-June-2022
Spoiler: for Donate:
BTC Wallet :
bc1qepm8lmd6228dhdpn9e0rjkplpq7yftdhkxywcp
​

is it gonna work with Android 12?

neoxcool said:
is it gonna work with Android 12?
Click to expand...
Click to collapse
yes, this recovery is built to work with a12+ (a11 is compatible)
(some little things need to be completed, but this will be later)

I have actually a Xiaomi 11lite 5G NE with Xiaomi.eu rom (a11: version 12.5.9, rooted with magisk 15.1) and twrp-3.6.0_11-0-lisa. I am very happy with them but I would like to try this recovery. Can I install it over TWRP using "ramdisk install"?
Must I reinstall from Platform tool?
I appreciate very much that you are working on a android 12 compatible version!

Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....

neoxcool said:
+++ Installation method 2
Click to expand...
Click to collapse

quasyl said:
Installation method 2
Click to expand...
Click to collapse

I did it with 1st method but will try 2nd later ...

Even after following method 2 commands, it still gives a slight vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all... I am on MIUI 13 by Papp54 (22.7.7 Beta) (https://forum.xda-developers.com/t/xiaomi-11-lite-5g-ne-by-papp54-r.4449665/)

neoxcool said:
Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....
Click to expand...
Click to collapse
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta

Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!

Eliliyah said:
Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!
Click to expand...
Click to collapse
You tested on MIUI 13/A12 or MIUI 12.5/A11?

If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
plz check
fastboot boot recovery.img
Click to expand...
Click to collapse
Hi, Yes. This recovery.img worked. I flashed the ofox recovery now. I'm on papp54 22.1.13 rom. Thank you

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Thanks, it works now. Please update the instructions and download links in your main post.

zgfg said:
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta
Click to expand...
Click to collapse
Dkpost3 will answer your query, mate ...​

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Works on Xiaomi.eu 22.7.13. Thanks mate!

Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!

MAT.PH said:
Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!
Click to expand...
Click to collapse
Newest PixelOS build?

[email protected] said:
Newest PixelOS build?
Click to expand...
Click to collapse
Yes
PixelOS_lisa-12.1-20220712-0056