Develop Bugs

[RECOVERY][arm64]TWRP Recovery [3.2.2-r1] [10 July 18]

{
"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.
This is my own unofficial customized build of 64 bit twrp for athene. It can be used on both Nougat and Oreo (32 bit and 64 bit ROMs) without any problem.
Known Bugs:
Encryption will not work. (Will be hopefully fixed in future builds) Not tested yet.
Changelog:
~~ -r2
* Overhaul twrp tree and add arm64 support
~~ -r1
* Based on AOSP/OmniROM 8.0.0_r32 release
* Fix stuck on 'black' screen entering recovery
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
How to flash:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly. Check this thread if you haven't done it already.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To temporarily boot twrp:
Code:
fastboot boot <filename.img>
To flash it to the recovery partition:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
*Now manually reboot to the recovery mode using the volume down keys. The current ROM will patch the recovery partition to its earlier state if this step isn't performed and you directly reboot to the system.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
~From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
Downloads:
Latest build: Direct Link
Older Builds: [url]https://sourceforge.net/projects/twrp-athene/files/[/URL]
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: [url]https://github.com/omnirom/android_bootable_recovery[/URL]
[url]https://github.com/rajatgupta1998/android_kernel_motorola_msm8952[/URL]
Version Information
Status: Beta
Created 2017-12-20
Last Updated 2017-12-20

is it compatible with shreps twrp backup?

Ayan Uchiha Choudhury said:
is it compatible with shreps twrp backup?
Click to expand...
Click to collapse
Yes, should work :good:

thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem

arun4777 said:
thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem
Click to expand...
Click to collapse
That's not related to twrp. Restoring the whole data partition from one rom to another causes problems for sure. Better to use titanium backup and backup/restore user apps with it.

This should work with the G4 (Regular non Plus model) Right?

Vaizen said:
This should work with the G4 (Regular non Plus model) Right?
Click to expand...
Click to collapse
Yes [emoji106]
Sent from my Moto G4 Plus using Tapatalk

tywinlannister7 said:
Yes [emoji106]
Click to expand...
Click to collapse
Actually it didn't let me flash latest RR. Had to flash official version for it to flash correctly.

Update: 30 Dec 2017
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download

tywinlannister7 said:
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download
Click to expand...
Click to collapse
Will i able to flash 32 bit also and does backup restores?

Can I Flash 32 bit ROM and 64 with this recovery?

Luis Infante said:
Can I Flash 32 bit ROM and 64 with this recovery?
Click to expand...
Click to collapse
Yes u can

StevenFernandes said:
Yes u can
Click to expand...
Click to collapse
Thanks

i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev????

arun4777 said:
i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev
Click to expand...
Click to collapse
It's a bug found on many twrp builds. I don't know if it's device specific.

I notice they Ghost touch with they USB cable and PC connected for ADB Sideload (and this affect to the ROMs)
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
I forgot to say that in this recovery for arm64 3.2.1.0 I don't have the arrow of the mouse appearing sometimes in the center of the screen (always on recovery, and sometimes on the system)

When i flash via fastboot the reovery, fastboot send me this error?
target reported max download size of 536870912 bytes
sending 'recovey' (14840 KB)...
OKAY [ 0.589s]
writing 'recovey'...
(bootloader) Invalid partition name recovey
FAILED (remote failure)
finished. total time: 0.597s
Click to expand...
Click to collapse

striplex said:
When i flash via fastboot the reovery, fastboot send me this error?
Click to expand...
Click to collapse
Yeah, see what you type: "recovey" but the partitions name is recovery

work roms 32 and 64 bits?

biel.paes said:
work roms 32 and 64 bits?
Click to expand...
Click to collapse
If you looked a few posts before you would clearly know that, yes, this build of twrp supports both 32 and 64 bit roms. Please use the search function before posting!

[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][10.0][AOSP+GAPPS][04/08/20]

Code:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
{
"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"
}
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 10.0
Notes:
1. If you want to root then copy the stock boot from the latest stock rom into internal and use magisk to patch it, then flash the patched boot in bootloader (fastboot flash boot patched_boot.img)
2. I will try to provide monthly patch updates and fixes as needed, don't ask for ETAs... I usually aim for the 5th of each month or whenever Google releases their patches
Bugs:
* voLTE not enabled by default, you can try this app and see if it works. some users report network drops or sms causing crashes.
You tell me? I worked hard to get everything working, I don't see any other issues, please report real issues, not feature requests from MIUI or other roms.
Getting fastbootd drivers working on windows:
1. Download these drivers and unzip
2. follow the instructions here to install the unsigned drivers
3. select the windows inf
Steps:
Please follow these steps closely!
For new installs:
1. Unlock bootloader
2. Download vbmeta from here and flash it in fastboot like this:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_note9s.img (IF YOU DONT DO THIS STEP, VOLTE AND OK GOOGLE WONT WORK!)
3. In bootloader enter: 'fastboot reboot fastboot'
4. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
5. enter 'fastboot reboot recovery'
6. select format userdata
7. then select reboot to system
To upgrade from previous versions:
1. Reboot to fastbootd (adb reboot fastboot from inside android or fastboot reboot fastboot from bootloader)
2. After we reboot you will see 'fastbootd', enter 'fastboot flash system system.img' (extract the system.img and put it in the folder you're in
3. Reboot
Downloads:
Latest ROM
For those who want stock camera with 48mp support on back and 16 on front
1. Download ANX camera from here along with the 48mp addon
2. flash in magisk both modules
3. Reboot
4. Give ANX camera all the permissions in app info
5. First time might crash then re-open
6. To fix portrait in front camera, download anx camera config from play store and search for portrait, enable all settings except for 'portrait night front'
7. restart app
@phhusson for his work on GSI (donate to this man, he works on dozens of devices), he worked closely with me to get everything working!
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that!
Source: https://github.com/aosp-tissot
Phh source:Link
XDA:DevDB Information
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][10.0][AOSP+GAPPS][04/08/20], ROM for the Redmi Note 9 Pro
Contributors
sooti, phhusson
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2020-07-23
Created 2020-05-26
Last Updated 2020-08-18​

Changelog:
04/08/20:
* Added option to close annoying suggestions in settings (like we could in pie)
* August security patch
23/07/20:
* Fixed camera crashing in apps that dont support aux (bigo live, zoom, etc)
08/07/20:
* Fixed voLTE, no more crashes from SMS
* Fixed overlay for joyeuse & Excalibur (should fix brightness and other small issues)
07/07/20:
* Latest July security patch
* Cleaned up overlay and removed useless junk
* Fixed auto-brightness bouncing every second and made it smooth and with a longer delay (match all other OEMs)
* Fixed minimum auto-brightness being 9, now 0 works fine
28/06/20:
* Removed voLTE being installed by default (ims), those coming from old version who still have problems, search for 'ims' under apps and uninstall app.
Those who voLTE was working fine with SMS and no crashes can download the apk from here and install link
24/06/20:
* Did a proper fix for google voice, should have better hw support (clear play store, play services and google app to fix any netflix issues)
* Made the voLTE app install only once per system install, just uninstall ims apk if you dont want voLTE or are having issues with it
* Added support for excalibur (Redmi Note 9S Pro Max)
21/06/20:
* Added voLTE support for all qcom devices
18/06/20:
* Google voice enrollment fixed (Clear google play services and google app to avoid any issues on upgrade)
* Added zygote preforking to improve app performance on launch
04/06/20:
* Fixed setting the audio props at boot, some users were changing setting and it wouldnt reset at boot, should fix audio for users who changed settings
02/06/20:
* mic was too loud, lowered a bit and seperated it so call mic is stock volume and camcorder is a bit louder.
* Louder headphone volume and speaker
* Fixed Phh settings overriding our needed defaults at boot
* Removed 96kbps aac limit and raised it to 320kbps (should increase audio recording quality)
* June security patch
31/05/20:
* Fixed auto-brightness max value (linear setting)
* Added 'redmi note 9 pro global version (joyeuse)' (untested but should work)
28/05/20:
* Fixed DRM not being L1
* Fixed Netflix missing prop (netflix will play in HD now)
* Increased volumes of headphones, cam/voice mic and speaker
28/05/20:
* Some more brightness fixes
* Fixed bt not playing media
27/05/20:
* Fixed bt not working on boot
* Changed auto-brightness values to stock values
* small gapps fixes
26/05/20:
* Initial commit

reserved

So... Its just flashing via fastboot? No custom recovery needed?

omararce said:
So... Its just flashing via fastboot? No custom recovery needed?
Click to expand...
Click to collapse
Yup, just fastboot flashing, dont forget to wipe from stock recovery

sooti said:
Yup, just fastboot flashing, dont forget to wipe from stock recovery
Click to expand...
Click to collapse
All right! Thanks i´ll flash it in a bit and try to give some positive feedback
Cheers

Just to add normal fastboot command i am pretty sure has problems, usually this is advised to be used "fastboot flash super "system.img"

Welcome. :laugh::laugh::laugh:

QuantumShqipe said:
Just to add normal fastboot command i am pretty sure has problems, usually this is advised to be used "fastboot flash super "system.img"
Click to expand...
Click to collapse
No don't flash that, it needs to be flashed from fastbootd, super is a partition that holds vendor and system

I stuck at fastbootd. Command Prompt says: “waiting for any device”. Really need asssistance

kinhrau said:
I stuck at fastbootd. Command Prompt says: “waiting for any device”. Really need asssistance
Click to expand...
Click to collapse
Are you on windows? I think you'll need a driver... Otherwise it works fine on Linux

sooti said:
No don't flash that, it needs to be flashed from fastbootd, super is a partition that holds vendor and system
Click to expand...
Click to collapse
Mmm alright then fair enough, I know what the dynamic super partition table is about but haven't messed with gsis so I would not know and maybe users don't know what they are doing since they failed to install this

QuantumShqipe said:
Mmm alright then fair enough, I know what the dynamic super partition table is about but haven't messed with gsis so I would not know and maybe users don't know what they are doing since they failed to install this
Click to expand...
Click to collapse
once i found the fastboot drivers ill check it out

Good work man,
Fastbootd is the only way to go... Had this issue yesterday when I tested phh and then havoc... had to download and extract these drivers to a folder. ... Which were linked directly from the android OEM drivers page
Then you have to hold shift and restart windows and choose the advanced restart to disable driver verification.
Then plug the phone in whilst in fastbootd mode.... Find the device in device manager ... Update drivers and point to the the xiamio driver.rar which you extracted earlier ... It should find the device .. install and viola.
But yes....worked instantly on MX Linux ?
Good news - the fastbootd included in lineage recovery also works the same. Tried and tested... Will give your gsi a try tomorrow

Well. Just installed the drivers and everything is detected by PC. Flashing through commandline the result is "remote: 'Partition not found') fastboot: error: Command failed"
Any ideas?

omararce said:
Well. Just installed the drivers and everything is detected by PC. Flashing through commandline the result is "system partition not found".. any ideas?
Click to expand...
Click to collapse
You didnt boot to fastbootd
First boot to bootloader then:
Code:
fastboot reboot fastboot

CFKod said:
You didnt boot to fastbootd
First boot to bootloader then:
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
I was on fastbootd, somehow the partition its not recognized by fastboot, tried with fastboot and with Xiaomi Flasher Jar tool that is around ...
---------- Post added at 02:34 PM ---------- Previous post was at 02:11 PM ----------
can i use fastboot erase system?
And then fastboot -u flash system name_of_system.img?

Does this have working BT Audio? Like media audio?

doctahjeph said:
Does this have working BT Audio? Like media audio?
Click to expand...
Click to collapse
Yup, everything works

I tried bt audio and can't put on

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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:
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:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 (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 S22 S901B
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22: AFH: r0s twrp and kernel / Drive: r0s 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 group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

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, thank you for twrp. Can this make system R/W ? I need to modify some files in system image. Thanks

NaiimAb10 said:
Hi, thank you for twrp. Can this make system R/W ? I need to modify some files in system image. Thanks
Click to expand...
Click to collapse
Not yet, still need a lot of work

Can S22 with 8GEN1 use this TWRP ？

sinaamos said:
Can S22 with 8GEN1 use this TWRP ？
Click to expand...
Click to collapse
Check OP there is supported list, also you know 8gen1 is snapdragon and the title says exynos and you still asking if it works?
Check the othe snapdragon thread.

Step 4 fails for me because of Knox Guard. Custom binaries blocked.
There is no way around this right?

Hi, noob question here...
Can I update firmware and retain root and TWRP without losing data? If yes - how to do it?

Worked perfectly with given guide!
1. TWRP recovery running
2. Could flash custom kernel from afaneh92
3. Also I downloaded Kernel tree and used build_menu to compile the same kernel with arch/arm64/configs/afaneh_r0s_defconfig
4. Could flash custom kernel self compiled as mentioned from (3.)
Next step was to adjust the defconfig from afaneh92 with some other features, but everytime I stuck in bootloop if I try. My approach was the following:
1. Load env variables from build_menu
2. make menuconfig load afaneh_r0s_defconfig
3. activate features from =n to =y (i.e. CONFIG_IP_VS=y)
4. copy newly created .config settings into afaneh_r0s_defconfig
5. start build_menu -> build kernel -> r0s
6. make flashable zip
7. boot into TWRP recovery and install custom kernel
8. Result: stuck in bootloop
my config still has CONFIG_SECURITY_ALWAYS_PERMISSIVE=y
Is this the right approach to add features to my kernel, or I am totally wrong with this? Here are some features I need for my kernel:
BLK_CGROUPDUMMYBLK_DEV_THROTTLINGEXT3_FS_POSIX_ACLBRIDGEIP_VSBRIDGE_NETFILTERIP_VS_NFCTVLAN_8021QIP_VS_PROTO_TCPBRIDGE_VLAN_FILTERINGIP_VS_PROTO_UDPBTRFS_FSIP_VS_RRBTRFS_FS_POSIX_ACLIPC_NSCFQ_GROUP_IOSCHEDNET_L3_MASTER_DEVHUGETLBFSIPVLANCGROUP_HUGETLBMACVLANCGROUP_NET_PRIONETFILTER_XT_MATCH_ADDRTYPECGROUP_PERFNETFILTER_XT_MATCH_IPVSDM_THIN_PROVISIONINGSECURITY_APPARMORVXLANUSER_NS

lowowly said:
Worked perfectly with given guide!
1. TWRP recovery running
2. Could flash custom kernel from afaneh92
3. Also I downloaded Kernel tree and used build_menu to compile the same kernel with arch/arm64/configs/afaneh_r0s_defconfig
4. Could flash custom kernel self compiled as mentioned from (3.)
Next step was to adjust the defconfig from afaneh92 with some other features, but everytime I stuck in bootloop if I try. My approach was the following:
1. Load env variables from build_menu
2. make menuconfig load afaneh_r0s_defconfig
3. activate features from =n to =y (i.e. CONFIG_IP_VS=y)
4. copy newly created .config settings into afaneh_r0s_defconfig
5. start build_menu -> build kernel -> r0s
6. make flashable zip
7. boot into TWRP recovery and install custom kernel
8. Result: stuck in bootloop
my config still has CONFIG_SECURITY_ALWAYS_PERMISSIVE=y
Is this the right approach to add features to my kernel, or I am totally wrong with this? Here are some features I need for my kernel:
BLK_CGROUPDUMMYBLK_DEV_THROTTLINGEXT3_FS_POSIX_ACLBRIDGEIP_VSBRIDGE_NETFILTERIP_VS_NFCTVLAN_8021QIP_VS_PROTO_TCPBRIDGE_VLAN_FILTERINGIP_VS_PROTO_UDPBTRFS_FSIP_VS_RRBTRFS_FS_POSIX_ACLIPC_NSCFQ_GROUP_IOSCHEDNET_L3_MASTER_DEVHUGETLBFSIPVLANCGROUP_HUGETLBMACVLANCGROUP_NET_PRIONETFILTER_XT_MATCH_ADDRTYPECGROUP_PERFNETFILTER_XT_MATCH_IPVSDM_THIN_PROVISIONINGSECURITY_APPARMORVXLANUSER_NS
Click to expand...
Click to collapse
you can simply edit afaneh_r0s_defconfig

I did. I.e. I changed
# CONFIG_IP_VS is not set
to
CONFIG_IP_VS=y
then compiled, flashed and tried to boot into system but stuck in bootloop.
I started to create the config with menuconfig because sometimes activating some of the CONFIG_ features additionally dependencies come in place or are not even available to activate.
Like activating CONFIG_IP_VS with menuconfig result in following:
CONFIG_IP_VS=y
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
Or if you want to use CONFIG_BRIDGE_VLAN_FILTERING you first need to activate CONFIG_VLAN_8021Q because of the dependencie.
So I thought doing with menuconfig is the "saver" solution. But anyway, got the same problem.

lowowly said:
I did. I.e. I changed
# CONFIG_IP_VS is not set
to
CONFIG_IP_VS=y
then compiled, flashed and tried to boot into system but stuck in bootloop.
I started to create the config with menuconfig because sometimes activating some of the CONFIG_ features additionally dependencies come in place or are not even available to activate.
Like activating CONFIG_IP_VS with menuconfig result in following:
CONFIG_IP_VS=y
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
Or if you want to use CONFIG_BRIDGE_VLAN_FILTERING you first need to activate CONFIG_VLAN_8021Q because of the dependencie.
So I thought doing with menuconfig is the "saver" solution. But anyway, got the same problem.
Click to expand...
Click to collapse
Anyway this is twrp thread, and I don't support kernel edit, mine is stock permissive

Thank you so far. Then I need some help in kernel edit. I start a new topic in questions section.

I'm getting bootloops on Android 13 BWA2, ADB doesn't work either. There's no possibility to install ROMs since the data partition is wiped when you flash TWRP and you can't copy files from windows to the device because it's not recognized.

neo2k12 said:
I'm getting bootloops on Android 13 BWA2, ADB doesn't work either. There's no possibility to install ROMs since the data partition is wiped when you flash TWRP and you can't copy files from windows to the device because it's not recognized.
Click to expand...
Click to collapse
You flashed the kernel!

afaneh92 said:
You flashed the kernel!
Click to expand...
Click to collapse
How am I supposed to flash the kernel if I can't get the zip file on my phone? Can you provide a tar file to be flashable in Download mode?

Will your TWRP be compatible with the new S23 series?

Well done. Flashed this image on four S22 phones, no problem. Fifth, my own - well, as mentioned on Telegram channel, I forgot to flash multidisabler. Wouldn't be a problem, but as I already setup the phone and moved over 180GB in it, I would like to query wheter it would be possible to support Samsung encryption. I am not demanding, so please don't be mad - just asking for possibility. Would be nice to have feature. While I can backup my data using migrate, I still prefer NAND backups.

neo2k12 said:
How am I supposed to flash the kernel if I can't get the zip file on my phone? Can you provide a tar file to be flashable in Download mode?
Click to expand...
Click to collapse
plugin flash drive. Mount as OTG. Problem solved

Development [ROM] [13.0] [alioth/aliothin] ArrowOS 13.1 [MiPa] [OTA]

{
"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.
MiPa Edition my personal fork. More clean and some features for myself.
Website: https://arrowos.net
Telegram MiPa Lab (maintainer chat): Chat
Github ArrowOS: https://github.com/ArrowOS
Github ArrowOS-MiPa-Edition: https://github.com/ArrowOS-MiPa-Edition
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Tip: Choose date and build type: "GAPPS" or "VANILLA" to download.
Read our blog article/post about:
* GAPPS and VANILLA variants
GPL compliance:
ROM Source - https://github.com/ArrowOS-MiPa-Edition/
Kernel Source- https://github.com/ArrowOS-MiPa-Edition/android_kernel_xiaomi_alioth
ROM OS Version: Android 13
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI S
Based On: AOSP

INSTALLATION PROCEDURE:
__________________________________________________
First installation (Clean flash):
You need PC with adb/fastboot tools.
Download boot, vendor_boot and rom zip:
https://sourceforge.net/projects/mi...arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mi...3.0/alioth/Additions/vendor_boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-fork/arrow-13.0/alioth/
Reboot in fastboot. Flash arrowos recovery (boot.img and vendor_boot.img):
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Reboot in ArrowOS Recovery:
fastboot reboot recovery
Make format data (Factory reset -> Format data).
Flash ROM (Apply update -> Apply from ADB):
adb sideload name.zip
Follow what show on device, should be ... Step 1/2 -> 2/2, then flashing ended, can reboot device in system. (In cmdline: If the process succeeds the output will stop at 47% and report `adb: failed to read command: Success`. In some cases it will report `adb: failed to read command: No error` which is also fine!")
If you want install separate gapps on vanilla buildtype, after flash ROM:
Advanced -> Reboot to recovery
Flash gapps (Apply update -> Apply from ADB):
adb sideload name.zip
__________________________________________________
Install updates via Updater:
Go in Settings -> System -> Updater
Downlad new build -> Install -> Reboot
Device will automatically download, install a new build and reboot.
Installation can take up to 1 hour, on 50% will stuck, it normal, just waiting (Why? - Don't forget, you now have a/b devices, a new update is installed in the background in an inactive slot, without recovery. That's why it's taking so long. Don't like? Flash manually via recovery.)
___________________________________________________
Install updates via recovery (dirty flash):
You need PC with adb/fastboot tools.
1) Download new build and reboot into Recovery
2) Flash ROM (Apply update -> Apply from ADB):
adb sideload name.zip
3) Reboot into System
__________________________________________________
How update only fw part MIUI:
You need PC with adb/fastboot tools.
Download fw part MIUI, which you need from: https://xiaomifirmwareupdater.com/archive/firmware/alioth/
1) Reboot into Recovery
2) Flash fw part MIUI (Apply update -> Apply from ADB):
adb sideload name.zip
Look on device:
WIll show "Signature verification error" -> Tap "Install anyway" -> Waiting installation end.
3) Reboot into System, if you installed it after new ROM build, or Reboot into Recovery, if you want flash new ROM build.
__________________________________________________
Also you can use TWRP/OFR/ETC for install or update this ROM. Instructions you can find in twrp topics or telegram groups.
__________________________________________________
My official telegram group: CLICK HERE

Device changelog arrow-13.1: Click here
Device changelog arrow-13.0: Click here
Note​
- arrow-13.1 recommend use with fw part MIUI 14:
EEU: V14.0.7.0.TKHEUXM or any other.
- arrow-13.0 recommend use with fw part MIUI 13:
Global: V13.0.5.0.SKHMIXM, V13.0.6.0.SKHMIXM
EU: V13.0.9.0.SKHEUXM
IN: V13.0.9.0.SKHINXM
CN: V13.0.9.0.SKHCNXM
- If LDAC codec's dont work with your headphones, need disable BT A2DP Offload:
Settings -> Developer settings -> Disable Bluetooth A2DP hardware offload (-> reboot)
- If you have visual bug's into launcher, need rm package_cache (can just use fastboot boot twrp by skkk -> file manager; or if have root, rm via file manager with root-access):
delete folder into /data/system/package_cache/

when Arrow os 13 official come ? i am waiting for that .
i am the big fan of Arrow OS .

Akash420 said:
when Arrow os 13 official come ? i am waiting for that .
i am the big fan of Arrow OS .
Click to expand...
Click to collapse
Never

I love you Palaych best ROM ever. Very stable, battery-efficient, smooth ROM.
Yes guys, it's unofficial and a personal fork, however this doesn't mean anything - the ROM is great and gets nice updates! If any of you need support, TG group is "mipa_lab". Sometimes I help out there.

Thanks for the new build, although for some reason the download was super slow i managed to get the GAPPs file and hash matches. I'm on the November GAPPs build - A12.1 and wanted to know if I can dirty flash/sideload the new build. Also do I need to flash the new boot and vendor boot files?
Thank you for your hard work.

after 47% error for me:
please help me
adb sideload Arrow-v13.0-alioth-MiPa-20230104-GAPPS.zip serving: 'Arrow-v13.0-alioth-MiPa-20230104-GAPPS.zip' (~47%) * failed to read command: No error

medela said:
Thanks for the new build, although for some reason the download was super slow i managed to get the GAPPs file and hash matches. I'm on the November GAPPs build - A12.1 and wanted to know if I can dirty flash/sideload the new build. Also do I need to flash the new boot and vendor boot files?
Thank you for your hard work.
Click to expand...
Click to collapse
Yes you can update to it.
You don't have to flash the boot and vendorboot from my experience... I just flashed the ZIP..

cyanGalaxy said:
Yes you can update to it.
You don't have to flash the boot and vendorboot from my experience... I just flashed the ZIP..
Click to expand...
Click to collapse
Will give it a try and report back.

wizzvpn said:
after 47% error for me:
please help me
adb sideload Arrow-v13.0-alioth-MiPa-20230104-GAPPS.zip serving: 'Arrow-v13.0-alioth-MiPa-20230104-GAPPS.zip' (~47%) * failed to read command: No error
Click to expand...
Click to collapse
It succeeded. ADB is just reporting incorrectly. It's a common bug with ADB.

No
After reboot
"miui" starts

cyanGalaxy said:
It succeeded. ADB is just reporting incorrectly. It's a common bug with ADB.
Click to expand...
Click to collapse
No
After reboot
"miui" starts

wizzvpn said:
No
After reboot
"miui" starts
Click to expand...
Click to collapse
For big ROMs afaik ADB splits the ROM. You should see details on the phone screen too. What do you see on the phone? Also, make sure you use a good type c cable and the phone shows up correctly in the device manager. Good luck!

wizzvpn said:
No
After reboot
"miui" starts
Click to expand...
Click to collapse
Your Terminal-output indicates that the flash succeeded.
You need to format data afterwards, when coming from a different ROM. Otherwise the bootloader can't boot to the ArrowOS boot-slot, and it'll auto-switch to the other boot-slot (with MIUI on it).
This may have been what happened.

medela said:
For big ROMs afaik ADB splits the ROM. You should see details on the phone screen too. What do you see on the phone? Also, make sure you use a good type c cable and the phone shows up correctly in the device manager. Good luck!
Click to expand...
Click to collapse
tnx my freand
......
.........
step 1/2
Error applying update: 7 (errorCode: :kInstallDeviceOpenError)
E:Error in /sideload/pakage.zip (status 1)

medela said:
Will give it a try and report back.
Click to expand...
Click to collapse
All good, just flashed and only good things to report: the ROM is lovely

wizzvpn said:
tnx my freand
......
.........
step 1/2
Error applying update: 7 (errorCode: :kInstallDeviceOpenError)
E:Error in /sideload/pakage.zip (status 1)
Click to expand...
Click to collapse
please make sure you read and follow the installation instructions in the OP:
Reboot in fastboot. Flash arrowos recovery (boot.img and vendor_boot.img):
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
Reboot in ArrowOS Recovery:
fastboot reboot recovery
Make format data (Factory reset -> Format data).
lastly: Flash ROM (Apply update -> Apply from ADB):
adb sideload name.zip
Good luck!

Oh, final Andirod 13 came! thank you so much, waiting for some time from Arrow 12.1

Dos this rom support call recording?