Database Info

[RECOVERY][UNOFFICIAL] TWRP for Galaxy A11 (Snapdragon)

{
"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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy A11 A115F and A115M.
Download & Guide:
1. Unlock your bootloader.
2. Download Galaxy A11 : a11q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
03.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
17.12.2020 - Update to latest TWRP source
- Fixed fastbootd
- Fixed external_sd and usb-otg mount points.
02.12.2020 - Initial Release.

reserved for fastboot guide

I have a SM-A115M/DS and I tried to flash the multidisabler and get this error!!!
please help me!

JoKeRBrAzZiL said:
I have a SM-A115M/DS and I tried to flash the multidisabler and get this error!!!
please help me!View attachment 5153865
Click to expand...
Click to collapse
Use latest version multidisabler-samsung-2.6c-afaneh92.zip

MY A115F not booting into recovery after flashing .tar file???solution
please help @afaneh92

musamalyk said:
MY A115F not booting into recovery after flashing .tar file???solution
please help @afaneh92
Click to expand...
Click to collapse
You need to boot into twrp immediately, press both volume buttons and connect usb at logo after first reboot.

afaneh92 said:
You need to boot into twrp immediately, press both volume buttons and connect usb at logo after first reboot.
Click to expand...
Click to collapse
it did not work ..please guide more clearly after installing .tar file using odin i m not able to boot into twrp recovery only my samsung keep restating on galaxy a11 ..may be its model difference because i m using Asian model of A11 from Pakistan @afaneh92

musamalyk said:
it did not work ..please guide more clearly after installing .tar file using odin i m not able to boot into twrp recovery only my samsung keep restating on galaxy a11 ..may be its model difference because i m using Asian model of A11 from Pakistan @afaneh92
Click to expand...
Click to collapse
Oh sorry I gave you the wrong instruction.
I have the A115F which is same as your device.
After flashing the tar file, press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo.

hopefully it will work???
have you tried any GSI project treble Rom in your A11
if yes then please tell which one????

i tried it did not work because to stop downlaoding mode need combination of volume down plus power key instead of volume up ..there is not any twrp ....
" press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo" again wrong
please help

musamalyk said:
hopefully it will work???
have you tried any GSI project treble Rom in your A11
if yes then please tell which one????
Click to expand...
Click to collapse
Yes, lineage-18.0-20201120-UNOFFICIAL-treble_a64_bvS installed

musamalyk said:
i tried it did not work because to stop downlaoding mode need combination of volume down plus power key instead of volume up ..there is not any twrp ....
" press power and volume up, then release power at logo and keep vol up pressed until you see twrp logo" again wrong
please help
Click to expand...
Click to collapse
If you disable auto reboot from odin, then you can reboot using vol down and power, after screen goes black press vol up and power until you got to boot logo. then keep vol up.

afaneh92 said:
Yes, lineage-18.0-20201120-UNOFFICIAL-treble_a64_bvS installed
Click to expand...
Click to collapse
please provide link

musamalyk said:
please provide link
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net

New build up.
- Update to latest TWRP source, Fixed fastbootd, Fixed external_sd and usb-otg mount points.

So where is yours build of LOS 18.0? I see there only the LOS 17.1

griha41 said:
So where is yours build of LOS 18.0? I see there only the LOS 17.1
Click to expand...
Click to collapse
Im not building ROMs, those are GSI. Not my own builds.

afaneh92 said:
Im not building ROMs, those are GSI. Not my own builds.
Click to expand...
Click to collapse
Ok. o you pick it from testing branch? And how do you install LOS? I'm tryin' with ADB Sideload but on my SM-A115F it's failed to start (I'm using TWRP that you had placed in this topic.)

griha41 said:
Ok. o you pick it from testing branch? And how do you install LOS? I'm tryin' with ADB Sideload but on my SM-A115F it's failed to start (I'm using TWRP that you had placed in this topic.)
Click to expand...
Click to collapse
Extract to img and flash using fastboot to system, then flash magisk.
Only a64_bvS can work on A11

[RECOVERY][R][ONEUI 3] TWRP v3.5.1 For Samsung Galaxy M30s (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"
}
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Downloads
Downloads
vbmeta
Odin tool
MEGA : M30sdd_TWRP_3.5.1_9
First time Installation
Note: custom vbmeta needs to be flashed to disable the verification of custom mods, this is a one time flashing in stock firmware
Backup your data
Unlock the Bootloader, View thread
Reboot to Download mode [Check Key Combos Below]
Disable auto reboot in Odin options, Flash vbmeta.tar in AP slot using Odin tool
Reboot again to Download mode and now Flash twrp-[$version]-m30s.img.tar in AP slot using Odin tool
Boot into TWRP Recovery [Check Key Combos Below]
Decrypt Internal Storage - Flash DM-Verity ForceEncrypt disabler
Wipe -> Format Data
Reboot -> System(without root) | Recovery(with root)
OR
Download Recovery.img file from link and flash it through your current recovery in recovery Partiton
Changelog
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Patching TWRP with Magisk
Download the latest Magisk Manager here & Install
Download/Copy the TWRP image to your device
Press the Install button in the Magisk card
Make sure “Recovery Mode” is checked in options.
In most cases it should already be automatically checked.
Choose “Select and Patch a File” in method, and select the TWRP image
Magisk Manager will patch the image to [Internal Storage]/Download/magisk_patched.img.
Proceed with the above steps to flash Magisk Patched TWRP.
Key Combos
Download Mode - Turn off device, Press and hold [vol + & vol -] connect usb to PC
Recovery Mode - Turn off device, Press and hold [vol + & Power] release power button after screen on, continue pressing [vol +]
Magisk System - Turn off device, Press and hold [vol + & Power] release both keys after screen on
Credits : @santhoosh for his work with M30s DT and thread, @mohitmallick17 for his DT on github, @geiti94 for his work with native A50 device tree.
Support:
Samsung Galaxy M30S | Official™
Official group for the Samsung Galaxy M30S Channel :- @SamsungGalaxyM30sUpdates Photography :- @SamsungGalaxyM30sPhotography Use /rules to see the rules, use /notes to see the notes. @admin or /report can be used to report users.
t.me
PrishSupport : https://t.me/prishsupport
PrishChannel : https://t.me/prishupdates
TWRP : https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Note : Test it and if you found any issue do let me know by PMing me on telegram @neel0210 .

reserved

Thanks for the effort sir
Where is the .tar file for first time installation after flashing vbmeta

Thanks for the effort sir,
Can u add twrp .tar file in the download section.

Development [U1][Recovery][Unofficial][A525X]OrangeFox Recovery 11.1

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"
}
Huge thanks to @geekmaster21 for making this a reality​
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 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.
*/
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A52 OrangeFox Recovery. I will try my best to keep it up to date with @geekmaster21 's work, but can't promise that will remain for ever. If you want the latest OrangeFox Recovery and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. 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 reset in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash OrangeFox and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing OrangeFox Recovery(tar) with Odin:
- Boot to download mode and load VBMeta disabler tar file in AP of Odin
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and VOL - button at the same time to boot to download mode again
- Now, add OrangeFox tar in AP of Odin
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to OrangeFox Recovery
- After booting to recovery successfully, go to WIPE in OrangeFox
- You should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with OrangeFox. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash OrangeFox Recovery (img) or (zip):
- Reboot to recovery
- Select Install
- Select Install Image or zip and search for the OrangeFox Recovery img or zip file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
Android 12 versions
Linked REMOVED (Outdated, use official sources instead)
Android 11 versions
OrangeFox Recovery img by @geekmaster21
OrangeFox Recovery tar by @geekmaster21
OrangeFox Recovery zip by @geekmaster21
Multidisabler zip by Ianmacd
VBMeta disabler for A52
Source Code: https://github.com/geekmaster21/a52q
Source Code: https://gitlab.com/OrangeFox
Credits:
- Samsung for kernel source code
- OrangeFox team for their awesome recovery
- @geekmaster21 for compiling, updating and maintaining OrangeFox for A52

Join our A52 Telegram group​
Code:
Check out the latest projects on our Telegram, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Spanish General Android Telegram group​
Code:
Grupo para los que hablamos español en donde discutimos Android en general /// Group made for Spanish speakers to discuss Android in general
Link: Telegram Group​

Please report any bugs here. As of now, I've only tested with "M" variant (which should really have no difference to "F" variant) and I successfully backed up, wiped, and restored.

-Final Reservation-

Pruh people

Please start custom ROM for this awesome device (Galaxy A52).

ShaDisNX255 said:
Please report any bugs here. As of now, I've only tested with "M" variant (which should really have no difference to "F" variant) and I successfully backed up, wiped, and restored.
Click to expand...
Click to collapse
I have tested first released and it booted to system ( stock rom + GSI ). Kakarot kernel by @neel0210 make it stabled in GSIs. But MTP does not work, It will be better if you can fix MTP for first released. Rooted stock rom + fix safetynet API net error + bypass safetynet.

A custom recovery so fast? WOW! Thanks, great job!

Silly question: Are OTA-updates (in stock rom) still possible after unlocking the bootloader ?

2faraway2 said:
Silly question: Are OTA-updates (in stock rom) still possible after unlocking the bootloader ?
Click to expand...
Click to collapse
After just unlocking it, yes. After tripping Knox, by flashing anything unofficial, no.

VonSparq said:
After just unlocking it, yes. After tripping Knox, by flashing anything unofficial, no.
Click to expand...
Click to collapse
So after flashing OF no more OTA updates, right ? Thanks

I updated the links for newer versions. They load faster and MTP is fixed.

2faraway2 said:
Y.ou still can do OTA updates.
Click to expand...
Click to collapse

not working for A12

Ray putting in some massive efforts! Thanks for porting this over!

not working for A12

tridi001 said:
not working for A12
Click to expand...
Click to collapse
This isn't for the A12 but for the A52?

ashraftheboss said:
This isn't for the A12 but for the A52?
Click to expand...
Click to collapse
i know that is for A52
but i mean A12= Android 12

tridi001 said:
i know that is for A52
but i mean A12= Android 12
Click to expand...
Click to collapse
Oh man my bad, I apologize!

I've tried many of times to install this recovery in my A52 running latest VB3 and every time its stuck in a loop at splash screen.
While TWRP is working fine, but TWRP does not support OTA updates.
Any solution????

Development [RECOVERY][OFFICIAL] TWRP 3.7 for Galaxy A52 4G and A72 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"
}
Official TWRP 3.7 For Galaxy A52 4G and A72 4G
Disclaimer
Code:
*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.
Features:
Android 11, 12 and 13 support
Encryption support (AOSP and OneUI)
Bugs:
Encryption only works on OneUI if no screen lock is set
Downloads:
A52 4G: TWRP.me
A72 4G: TWRP.me
How to install
Open Settings -> About Phone -> Software and tap "Build Number" 7 times until it says "developer mode enabled".
Go back to Settings -> Developer Options -> Enable "OEM unlocking"
Enter Download Mode by powering off your phone, then hold down both volume keys and connect your phone to a Computer.
Release all keys, then hold down Volume Up to get into "Device unlock mode" and confirm that you want to unlock the bootloader. This will wipe all data from the phone.
The phone will automatically reboot. Now go through the initial setup and connect your phone to the internet (either using Wifi oder Mobile data).
Go back to Developer Options and check that OEM Unlocking is there and grayed out. Your bootloader is now unlocked.
Download and install Samsung Drivers on your Computer.
Download the latest *.tar from the TWRP website for your phone.
Download Odin, from example from https://downloads.corsicanu.ro/samsung/.
Turn off your phone and reboot to download mode by holding down Volume up and Volume down and then connect your phone to a PC. Then press Volume Up once to get into Download mode.
Open Odin and check if your device is detected.
Put the TWRP tar file you downloaded into the AP tab and put disabled VBMeta in the USERDATA slot.
Click start and wait for the installation to finish, Odin will show PASS.
Immediately after the screen goes black hold down Volume up and Power button at the same time until you enter TWRP (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning).
If you properly followed all the steps you should now see the TWRP menu.
Once TWRP has booted you need to format your data again to be able to boot into system.
Donations
This is not essential, but if you like TWRP and my work feel free to send me or TWRP a donation.
Sources:
A52 4G: https://github.com/TeamWin/android_device_samsung_a52q
A72 4G: https://github.com/TeamWin/android_device_samsung_a72q
Kernel: https://github.com/Simon1511/android_kernel_samsung_sm7125
Credits:
TeamWin
@Velosh for the original TWRP trees
@corsicanu for updating multidisabler for A12 and providing download links for Odin, USB drivers, etc
@redymedan for the video guide
Testers on Telegram
Everyone else involved

Reserved.

Nice job, congrats! Glad to see another Samsung being alive in terms of custom deving.

Amazing! thanks for the work Devs!

Hello Simon1511,
Please, to not make mistakes, the first time when I enter the TWRP, I must in the right order :
- 1 Format Data
- 2 Flash Multi-Disabler
- 3 Flash Disable DM Verity
- 4 Reboot on recovery or system to access the phone
In addition for Android 12, I have to root the phone first ?
Because I want to have on this phone also ROOT + TWRP.
I come from an s10 Android 10 and the way to install TWRP seems different...
Thank you in advance.

The restoration is not working for vbmeta and super partition

Elvaa said:
The restoration is not working for vbmeta and super partition
Click to expand...
Click to collapse
Restoring the super partition works fine.
However, restoring vbmeta is generally not possible because only Odin can flash stuff to it.

TWRP has been updated to version 3.7!
Changelog
Code:
-Encryption/Decryption support for AOSP 12 and 13 ROMs
-Updated kernel to latest
-Fixed USB OTG and enabled NTFS support
-Switched to using FFS for MTP
-Added busybox bins
-Fixed ADB sideload

Hope this works for Android 13 on "A525FXXS4CVK4".

MobAndro said:
Hello Simon1511,
Please, to not make mistakes, the first time when I enter the TWRP, I must in the right order :
- 1 Format Data
- 2 Flash Multi-Disabler
- 3 Flash Disable DM Verity
- 4 Reboot on recovery or system to access the phone
In addition for Android 12, I have to root the phone first ?
Because I want to have on this phone also ROOT + TWRP.
I come from an s10 Android 10 and the way to install TWRP seems different...
Thank you in advance.
Click to expand...
Click to collapse
I hope the "DM Verity Disabler (Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip)" works for One UI 5.0 also...

SRooks1976 said:
I hope the "DM Verity Disabler (Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip)" works for One UI 5.0 also...
Click to expand...
Click to collapse
You don't need to flash that.
As you can see in the guide you only have to flash Multidisabler.

Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.

SRooks1976 said:
Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.
Click to expand...
Click to collapse
Well, this happens because the multidisabler zip disables most of Samsung's security mechanisms which (for somehow) make the phone think that a Service Provider Update is needed.
This should go away once you confirm it and/or reboot.

Can I root & install twrp with A13?

Simon1511 said:
Well, this happens because the multidisabler zip disables most of Samsung's security mechanisms which (for somehow) make the phone think that a Service Provider Update is needed.
This should go away once you confirm it and/or reboot.
Click to expand...
Click to collapse
Nope, even after rebooting many of times, the s**t happens.......
Reverting to Magisk Method without TWRP.

SRooks1976 said:
Why this keeps popping up after I installed this TWRP recovery, whilst earlier I patched the original AP file with Magisk and installed the firmware with that AP file, rooted my A52 (A525F), it was not there.
But when I installed TWRP, format Data, installed multi-disabler zip file, this keeps popping up.
Click to expand...
Click to collapse
This happens because you install a CSC that's not your original and it can't find the configuration for your SIM. Deleting system/priv-app/CIDManager should fix it.

Hello!
ShaDisNX255 said:
This happens because you install a CSC that's not your original and it can't find the configuration for your SIM. Deleting system/priv-app/CIDManager should fix it.
Click to expand...
Click to collapse
Hello! Is the latest one must be selected to backup system/vendor partition and restore it correctly later? If so, why its size is not counted?

can i flash this twrp on my a52f, which is still on stock rom binary 2

Linlova said:
can i flash this twrp on my a52f, which is still on stock rom binary 2
Click to expand...
Click to collapse
#1 says:

Simon1511 said:
#1 says:
View attachment 5794007
Click to expand...
Click to collapse
I already knew that before hehe, but just to make sure

Development [ROM][13][UNOFFICIAL] ArrowOS 13 for Realme GT Neo2 5G

{
"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"
}
ArrowOS​
Code:
/*
* 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.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
PayPal: Donate to me
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me (need to be reproducable + include logs)
Be sure to include a log : check how to
HOW TO FLASH
* Reboot to TWRP
* Flash ArrowOS zip with adb sideload or USB OTG
* Flash magisk (optional)
* Format data
* Reboot to system
Tip: Be sure to be on RealmeUI 3 C.09, GDPR C.08 or CN C.10 before flashing this ROM.
DOWNLOADS
Click here to Download
Tip: Use the latest TWRP build for flashing this ROM.
Read our blog article/post about:
* HOW-TO report a bug
GPL compliance:
ROM Source- https://github.com/ArrowOS
Device Source- https://github.com/realme-sm8250-devs
Kernel Source- https://github.com/realme-sm8250-devs/android_kernel_realme_sm8250

Wow

Downloading

will there be a vanilla build?

Awesome

Pro af

Finally

my touch screen doesnt work anymore, please help
edit: nvm i fixed it

Deleted

Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?

andrew202 said:
Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?
Click to expand...
Click to collapse
You need to format data partition, so that it will be fix that problem.

Extra instructions.
1. Running RMX3370 Global RUI c.04
2. Unlock bootloader, using deeptest app method
3. Make sure you have adb/fastboot platform tools and driver on your computer
4. To use TWRP, get latest found on XDA in RM GT Neo 2 forum, extract the zip since they didn't upload as an img for simplicity and place the img file in the same directory as your adb files
5. Use - adb boot recovery.img
6. Once TWRP is loaded on your phone go to ADB Sideload and slide to activate
7. On computer, make sure to check adb is active using - adb devices
8. If your device lists on command prompt, then go ahead and flash the rom using - adb sideload rom.zip
9. After this you can flash magisk zip (this is optional, I personally didn't)
10. Once this is done, go to Wipe, and Click on Format Data button, type yes and enter it - data will format
11. Then reboot to system
Note, flashing twrp with - adb flash recovery command - does not work from c.04 --- this is why adb boot is used instead.

Nurujjamanpollob said:
You need to format data partition, so that it will be fix that problem.
Click to expand...
Click to collapse
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.

andrew202 said:
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.
Click to expand...
Click to collapse
You may need to try:
Format data partition, right after that, go to twrp menu and choose reboot to recovery option.
If still you see 0 mb, it's due to kernel or rom problem I think.

andrew202 said:
Im having a strange issue, I have the newest twrp build. everything went well flashed c_04. Flashed arrow os after everything boots runs good. I want to root so i download magisk transfer over my boot image patch it. Reboot back into twrp recovery and file system says 0mb I am unable to mount it. Not sure if I maybe missed a step. After seeing a unmountable filesystem in twrp i can just reboot back into the system fine. I have tried with screenlock password and without, I have also tried to enter my screenlock password into the decrypt data under mount. I used fastboot to flash the boot file and it worked. Still confused a bug maybe?
Click to expand...
Click to collapse
That is TWRP bug , officially TWRP still does not supports Android 12 decryption , you wont have this problem if a) ROM is force encryption disabled or b) ROM is below Android 12 like Android 11
In my opinion becuase of lack of kernel source for ANDroid12 for our device by Realme
We should try to use Android 11 ROMS , since everything works in it

andrew202 said:
I did that right away after flashing firmware, I can get the data partition to show up if I change the data partition file system and change it back. But soon as I do a reboot it's back to 0mb.
Click to expand...
Click to collapse
If you are coming from an A12 ROM,
after flashing the new ROM, go to fastboot and do "fastboot -w" to format data.
your newly flashed ROM will boot.
The genius Neo2 devs forgot the crucial detail that people could be coming from A12 and TWRP cant mount partitions to even format data

EisregenHaha said:
my touch screen doesnt work anymore, please help
edit: nvm i fixed it
Click to expand...
Click to collapse
How did you fix it? I'm having the same problem

omgitsvoltpunk said:
How did you fix it? I'm having the same problem
Click to expand...
Click to collapse
Flash newest rui before flashing arrow.

A new ArrowOS update is available to download !
ROM changelog:
• Sync arrow's 12/06/2022 source
Device changelog:
• Build nqnfcinfo
• Import default_volume_tables.xml from my_product
• Label some logging properties on sepolicy
• Move a vendor acdbdata leftover to odm
• Reduce headset volume
• Reset dimlayer HBM + fp press state on error
• Stop building tinymix
• Switch to Oplus libperfmgr and drop QTI perfd
• Switch to Oplus light service

A new ArrowOS update is available to download !
ROM changelog:
• Sync arrow's 16/07/2022 source
Device changelog:
• Add TICK effect in oplus vibrator service
• Build audio amplifier for top speaker
• Cleanup properties
• Drop a few useless Oplus camera services
• Enable properly QTI media c2 service
• Fix 1080p60fps and Netflix crash
• Fix OTP SMS
• Switch to Oplus QTI sepolicy repo
• Track some audio configs from QCOM audio hardware
• Update prebuilt kernel and blobs to RMX3370_11.C.07
• Update touchpanel firmware from odm if newer
• Update wifi tether overlays for hostpot