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

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

{
"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

Related

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 FE 5G (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 S20 FE 5G G7810, G781B, G781N, G781U, G781U1, G981W and G780G (4G).
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S20 FE 5G: r8q.
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 group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ooobs007 for testing on S20 FE 5G G781B
ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
02.06.2022 - Update to Android 12 kernel source
- Fix mount issues
- Update to TWRP 3.6.2
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
23.05.2021 - Update to latest TWRP source, update kernel to G781BXXU3CUD6.
03.03.2021 - Update to latest TWRP source, Add terminal multidisabler script. fstab cleanup.
22.01.2020 - Fix USB-OTG for Q & R builds.
15.01.2020 - Initial build for Android 11
31.12.2020 - Update TWRP to 3.5.0
15.11.2020 - Add TWRP fastbootd support, Move kernel to gz format.
11.11.2020 - Initial Release.

Hello,
Thank you very much my friend .

my phone Unlock bootloader ok
install Magisk Manager ok
-----------------------------
just ı want twrp
please exynos s20 fe

arlequin2k3 said:
Hello,
Thank you very much my friend .
Click to expand...
Click to collapse
Welcome, Enjoy.
bylumax said:
my phone Unlock bootloader ok
install Magisk Manager ok
-----------------------------
just ı want twrp
please exynos s20 fe
Click to expand...
Click to collapse
Exynos not supported. maybe in future.

afaneh92 said:
Supported Models:
Galaxy S20 G7810, G781N, G781U, G781U1 and G981W.
Click to expand...
Click to collapse
So it doesn't work with the G781B version, right?

ilMerovingio said:
So it doesn't work with the G781B version, right?
Click to expand...
Click to collapse
Should work with any Snapdragon version with an unlockable bootloader, therefore any non US Fe version.

ilMerovingio said:
So it doesn't work with the G781B version, right?
Click to expand...
Click to collapse
Oh, sorry forgot to add it.
It was tested on G781B.

Hello ,
Okay I just tried to install twrp. So the installation went well but the concern is that it does not recognize my sd card and therefore cannot access the multidisabler and magik files to continue ....
I also tested by putting everything on a usb key and the same problem .....

arlequin2k3 said:
Hello ,
Okay I just tried to install twrp. So the installation went well but the concern is that it does not recognize my sd card and therefore cannot access the multidisabler and magik files to continue ....
I also tested by putting everything on a usb key and the same problem .....
Click to expand...
Click to collapse
You can push them through adb to any place like root / or /data
Also you can use external sd!
Try to copy files to sdcard while you booted to system!
USB OTG will be fixed next build.

afaneh92 said:
You can push them through adb to any place like root / or /data
Also you can use external sd!
Try to copy files to sdcard while you booted to system!
USB OTG will be fixed next build.
Click to expand...
Click to collapse
Your idea to connect the pc to the phone to seem to work. Twrp recognized the twrp file on my disk and I introduced the 2 files. And there it worked .... Thank you very much for the idea.

Silly question but can I still install OTA updates if I unlock bootloader/flash custom recovery or root the phone? And will stock recovery flash every time I install OTA update?
Thanks in advance

Is there magisk that we can root? Any guides on it please.

Huberttus said:
Silly question but can I still install OTA updates if I unlock bootloader/flash custom recovery or root the phone? And will stock recovery flash every time I install OTA update?
Thanks in advance
Click to expand...
Click to collapse
Flashing multidsabler make some changes to system and vendor. So no OTA, Flash full firmware instead.
Nchls said:
Is there magisk that we can root? Any guides on it please.
Click to expand...
Click to collapse
Flash magisk zip in TWRP or patch boot.img using magisk manager and flash via odin.

New build up!
15.11.2020 - Add TWRP fastbootd support, Move kernel to gz format.

After installing this will i use knox stuff like secure folder?

tabish84 said:
After installing this will i use knox stuff like secure folder?
Click to expand...
Click to collapse
No, you need to fix them to work again.

Hello ,
This update can be installed directly or must first be installed the 1st version. I ask this question given the size difference between the 2. Thank you for your answer .

arlequin2k3 said:
Hello ,
This update can be installed directly or must first be installed the 1st version. I ask this question given the size difference between the 2. Thank you for your answer .
Click to expand...
Click to collapse
Yes can be flashed directly, You can see in changelog that we moved to gzip format, that explain the size difference.

afaneh92 said:
No, you need to fix them to work again.
Click to expand...
Click to collapse
Where is the fix?

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 (Exynos)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.

Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg

DeblaGaming said:
Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg
Click to expand...
Click to collapse
My bad I missed that but you can know from G991B its regular not Ultra.

@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?

I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.

Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same

DJBhardwaj said:
@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?
Click to expand...
Click to collapse
You can flash apk
orkavaneger said:
I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.
Click to expand...
Click to collapse
Vibration not working in twrp only, read more.
bigpotato107 said:
Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same
Click to expand...
Click to collapse
Yes need to redo every step.

i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?

Emrah132 said:
i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?
Click to expand...
Click to collapse
Follow instructions.

i didnt need vibration its great job thank you afaneh92

can i flash twrp without lost magisk root?

What about encryption issue.. is there any clue on next release. I don't think I found a problem except for the two things that were mentioned above bugs

Hi,
I was able to install magisk. In the end, I want to install exposed framework. In the TWRP mode, whenever I try to install, I get an error.
-Mounting /system and /vendor read-write mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted
In the end, it says "Updating partition details" .. done. Can you please help me in resolving this error.

Thanks for your efforts, dev! Everything working as expected.

Hello, is there any way to re-enable encryption after TWRP installation? No matter, FBE or FDE. It says "not fully working" and I see only not working at all, maybe I am doing something wrong?

A note on firmware updates:
It is possible to follow all the instructions from the original post but SKIP the step of wiping your data from within TWRP when updating your firmware. You need to run the multidisabler though. This works if you had already installed this TWRP version with encryption disabled, including a data wipe, but now want to update your firmware. So wiping data is only needed for the first time.
In fact, if you had installed this TWRP version and do a firmware update via odin but do not flash this TWRP version with vbbeta disabled, your phone simply won't start anymore. It will ask you to factory reset.
So once you go TWRP, you have to reinstall it for future updates.
@afaneh92 do you want to add this as a hint in your OP?

Thank you for your great work and the fast twrp publishing! I was able to install and boot a GSI.
Now I would like to flash microg/gapps to system, but the system partition does not have any free space left. In the twrp wipe menu I cannot find the system partition to increase size. Would it be possibe to add this feature or are other steps mandatory to increase system partition in size?
Again, thanks a lot for your efforts!

Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.

WiS3 said:
Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.
Click to expand...
Click to collapse
In your place I would just try. Take a backup and try the installation, skipping ONLY the data wipe. If this fails, either use your backup or include the wipe.
Though, I HIGHLY assume you need to wipe for the first install of TWRP to remove the encryption initially. In future TWRP updates, you can skip wiping.

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S21+ (Exynos)

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Fix haptic feedback
- Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.

Nice to hear, now I am a bit more tempted to get an S21+
I hope roms will follow

I have error trying do backup. Folder optics make crash and reboot to twrp again. My first backup was fully all folders but now every crash on optics. Still great work

Ziomus said:
I have error trying do backup. Folder optics make crash and reboot to twrp again. My first backup was fully all folders but now every crash on optics. Still great work
Click to expand...
Click to collapse
have you disabled encryption? and logs?

afaneh92 said:
have you disabled encryption? and logs?
Click to expand...
Click to collapse
Yes multi 2x times wipe data Yes reboot. Ive acces to whole data. How to make log for you that will help you? And like i was saying first backup super partition for me was succesful. Then i delete it and trying make new backup, and starts in middle of work. I Discovery that is "optics" folder So now i make backups without it (4Mb data inside optics"

internal memory is corrupted after FactoryReset !!!
any fix

czar22 said:
internal memory is corrupted after FactoryReset !!!
any fix
Click to expand...
Click to collapse
Format data and type yes.

still no FIX
I rewrote the firmware and took it from 0

czar22 said:
still no FIX
I rewrote the firmware and took it from 0
Click to expand...
Click to collapse
Then you are doing something wrong

czar22 said:
still no FIX
I rewrote the firmware and took it from 0
Click to expand...
Click to collapse
We're you on the newest update before unlocking bootloader and installing twrp

is there a TWRP [AUF6] version ????

czar22 said:
is there a TWRP [AUF6] version ????
Click to expand...
Click to collapse
my twrp can work on v3 bootloader, the twrp in the link taken without authorship.

afaneh92 said:
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 S21+ G996B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21+: t2s.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
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.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Click to expand...
Click to collapse
hello, will this work on my device that has SM-G996B/DS as an model number? thanks!

Redisity said:
hello, will this work on my device that has SM-G996B/DS as an model number? thanks!
Click to expand...
Click to collapse
Yes check supported devices in OP

Hi, i just updated my S21+ Exynos to android 12. It's rooted with magisk and just installed the last TWRP.
But I'm gettin 255 error when trying to backup data. I've been told that TWRP can't backup android 12 data, is that true? There is any workaround? And any hope for this to be fixed?

ffp. said:
Hi, i just updated my S21+ Exynos to android 12. It's rooted with magisk and just installed the last TWRP.
But I'm gettin 255 error when trying to backup data. I've been told that TWRP can't backup android 12 data, is that true? There is any workaround? And any hope for this to be fixed?
Click to expand...
Click to collapse
Try to check recovery log and delete the folders causing the error

afaneh92 said:
Try to check recovery log and delete the folders causing the error
Click to expand...
Click to collapse
I did that, it was a dalvick-cache folder. I moved it. But then the backup failed again because another completely different folder...

ffp. said:
I did that, it was a dalvick-cache folder. I moved it. But then the backup failed again because another completely different folder...
Click to expand...
Click to collapse
Yes need to remove it as well

afaneh92 said:
Yes need to remove it as well
Click to expand...
Click to collapse
How can i know they aren't important? Is this Twrp unable to decrypt android 12 encryption true? And what if I get another error with another folder?

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 [RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 A53 5G A536B, A536E, A536N & A5360
Download & Guide:
1. Unlock your bootloader.
2. Downloads for A53 5G: a53x twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
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.- Go back to Wipe > Format Data > type yes.- Reboot to recovery.7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
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
@MaloyZV on telegram for testing
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
12.07.2022 - Initial Release.

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.

Hi, I am currently testing this. So far, I have only flashed the TWRP via ODIN (already have a custom ROM running).
I want to backup my data first before messing around. When I try to mount internal storage, it says 0MB.
So do I need to flash the custom kernel before I can access the data partition or internal sdcard?
Or is data access/backup not supported?

aximut said:
Hi, I am currently testing this. So far, I have only flashed the TWRP via ODIN (already have a custom ROM running).
I want to backup my data first before messing around. When I try to mount internal storage, it says 0MB.
So do I need to flash the custom kernel before I can access the data partition or internal sdcard?
Or is data access/backup not supported?
Click to expand...
Click to collapse
You cant access the data as mentioned in bug list we dont have encryption support.

afaneh92 said:
You cant access the data as mentioned in bug list we dont have encryption support.
Click to expand...
Click to collapse
I am running LineageOS (based on PHH GSI) which is not encrypted.
This is what the log says.

aximut said:
I am running LineageOS (based on PHH GSI) which is not encrypted.
This is what the log says.
View attachment 5661271
Click to expand...
Click to collapse
And what does GSI that installed to system has to do with data encryption?
If you are worried about your data just move them to pc
And if you are worried about encryption simply dont use twrp.

afaneh92 said:
And what does GSI that installed to system has to do with data encryption?
If you are worried about your data just move them to pc
And if you are worried about encryption simply dont use twrp.
Click to expand...
Click to collapse
The GSI has no support for userdata encryption, which means that the internal data can't be encrypted (and should be unencrypted in /data). Otherwise I would not be able to boot into the ROM. But maybe I am wrong on this.
So if I reformat my data and run the multidisabler, does that mean I can access data in TWRP even having a custom ROM?

aximut said:
The GSI has no support for userdata encryption, which means that the internal data can't be encrypted (and should be unencrypted in /data). Otherwise I would not be able to boot into the ROM. But maybe I am wrong on this.
So if I reformat my data and run the multidisabler, does that mean I can access data in TWRP even having a custom ROM?
Click to expand...
Click to collapse
Yes after running multidisabler and formatting data. You might able to boot GSI without custom kernel but not stock

afaneh92 said:
Yes after running multidisabler and formatting data. You might able to boot GSI without custom kernel but not stock
Click to expand...
Click to collapse
OK thanks. What partition does the multidisabler actually patch to disable encryption? System? Or boot?

aximut said:
OK thanks. What partition does the multidisabler actually patch to disable encryption? System? Or boot?
Click to expand...
Click to collapse
Vendor is ro, it convert it to rw then patch vendor/etc/fstab.exynos****

TWRP and your kernel work in A536N, But root and /system are still ro
I installed stock May 24 firmware with magisk patched before installing TWRP
P.S ) I have to clear dalvik & cache every reboot

gckim250 said:
TWRP and your kernel work in A536N, But root and /system are still ro
I installed stock May 24 firmware with magisk patched before installing TWRP
P.S ) I have to clear dalvik & cache every reboot
Click to expand...
Click to collapse
Yes as I said earlier only vendor is rw to disable encryption. We cant do the same for system as the size doesn't fit.

Ah, Biometrics lockscreen from stock ROM conflicts with SafetyNet Fix module...
That's why I have to clear that every reboot...

Are there any roms available for the A53? Because I was looking for twrp .zip files for this phone, and couldn't find anything for this model.

Lowkeys said:
Are there any roms available for the A53? Because I was looking for twrp .zip files for this phone, and couldn't find anything for this model.
Click to expand...
Click to collapse
phh's AOSP, LineageOS GSI, Pixel Experience GSI are only available for A53 at this time
vndklite version of these can be installed via fastboot mode!
If you want zip-flashing rom, waiting is the only soulution unfortunately
Pixel GSI : https://github.com/ponces/treble_build_pe/releases/download/
phh's AOSP : https://github.com/phhusson/treble_experimentations/releases
Lineage GSI : https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/

gckim250 said:
phh's AOSP, LineageOS GSI, Pixel Experience GSI are only available for A53 at this time
vndklite version of these can be installed via fastboot mode!
If you want zip-flashing rom, waiting is the only soulution unfortunately
Pixel GSI : https://github.com/ponces/treble_build_pe/releases/download/
phh's AOSP : https://github.com/phhusson/treble_experimentations/releases
Lineage GSI : https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/
Click to expand...
Click to collapse
If I were to download phh's AOSP extended for the Samsung galaxy A53 would I have to get the vanilla version? Also when downloading due I have to extract the img.xz file to just get the .img file, and then using an sd card put the file on the phone to flash?
Note my phone model is SM-A536E/DS.

Lowkeys said:
If I were to download phh's AOSP extended for the Samsung galaxy A53 would I have to get the vanilla version? Also when downloading due I have to extract the img.xz file to just get the .img file, and then using an sd card put the file on the phone to flash?
Note my phone model is SM-A536E/DS.
Click to expand...
Click to collapse
gapps = google apps (e.g play store)
vanilla = no google apps
You should install that via TWRP fastboot mode! (or fastbootd)
In fastboot, you may need USB 2.0 port
P.S) my phone is A536N + stock ROM
Treble Info : https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

Will this work on my sm-a536w?

redliner79 said:
Will this work on my sm-a536w?
Click to expand...
Click to collapse
Your bootloader cant be unlocked currently

Database Info

welcome