Develop Bugs

[RECOVERY][ROOT]TWRP 3.1.1-1 Samsung Galaxy J7 MAX 2017 SM-G615F

Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
{
"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 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, dm-verity and mount internal storage (/data) :
1. Boot to Twrp
2. Format the Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
TWRP DEVICE Tree: https://github.com/ashyx/TWRP_Samsung_j7maxlte
Kernel source: https://github.com/ashyx/KERNEL_j7maxlte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE: I built this months ago, but forgot to post it up!
.

Great work @ashyx can you please share device tree

I Tested the recovery on my J7 Max and it's working perfectly after flashing the "Boot image patch : no-verity-no-encrypt_ashyx".
one thing i want to tell that the recovery bootlooped(Rebooting the system or Shutting down and again powering on boots into Twrp) the first time i booted it but after flashing Magisk 14.0 and the "no-verity-no-encrypt" patch it works fine.
I've attached the recovery and kernel logs.
Also add a Warning for users to backup their data as i lost all my data after flashing (
and
Thank you for building a TWRP for my device
If you have free time can you please try to build LineageOS for J7 Max

Can you please share the device tree ?

Rumorbox33 said:
Can you please share the device tree ?
Click to expand...
Click to collapse
Yes when I have the opportunity, but be aware twrp device trees are no good for building LineageOS or other custom OS systems.

Thank you for replying.
i just want to study it, upload whenever you have the time

Samsung j700h

[email protected] said:
Samsung j700h
Click to expand...
Click to collapse
No

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Please post your source code This have been up for roughly a month And we need em....Thank you good sir for your hard work

Hi since j7 plus has same chipset.. Can we use this also? Thanks

ashyx said:
No
Click to expand...
Click to collapse
@ashyx Please read PMs.

TheMadScientist said:
@ashyx Please read PMs.
Click to expand...
Click to collapse
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.

ashyx said:
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
Click to expand...
Click to collapse
Thank you and disregard any PMS and such all have been reversed

https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?

Yuaan rai said:
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Click to expand...
Click to collapse
You can use any file manager with root support to move the apk to /system/app

Rumorbox33 said:
You can use any file manager with root support to move the apk to /system/app
Click to expand...
Click to collapse
Used every app and file manager but to no avail. Finally used twrp itself and boom the problem was solved. Thnks anyway.

Any custom roms for samsung j7 max sm-g615f ??
Plez help

Hey I am using samsumg galaxy j7 2015 model which rooted and have twrp recovery in it so I want to add kernel into it so can you give the file and the method to do so and also the best rom for my device

Hey, i built TWRP 3.2.1-1 for this device including some fixes such as pixel format and many more, will you update the thread if i give you the twrp and device trees or i have to make another thread ?

[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2

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.
{
"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"
}
CHANGELOG for 3.2.1-0:
- 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD LINKS:
Current and past versions of TWRP can be found at one of the mirrors below:
- Primary (Recommended)
- Primary (Backup)
INSTALL INSTRUCTIONS:
TWRP install (requires TWRP 2.8.4 or higher already installed):
1) Download the latest version of TWRP appropriate for your device/firmware
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find other alternative installation methods on our website (direct link to your device)!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2, Tool/Utility for the Xiaomi Mi Note 2
Contributors
joe2k01
Version Information
Status: Stable
Created 2018-04-06
Last Updated 2018-04-06

I really want twrp 3.2.1-1. Miui firmware not Packed in new.dat are not installed on Android 8.

Thank you very much! Very nice to see the official one!

Sorry about the noob question but I'm not sure. Is possible updating with this version without getting the official recovery? Any explanation helps, thank you!

Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Sent from my Nokia 7 plus using Tapatalk

Stransky said:
Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Click to expand...
Click to collapse
I had the same problem a few days ago trying to recover root after updating to MIUI 9.5.4 and sadly have no idea whats going on.
I fixed it downloading the MIUI firmware to my PC (fastboot option) and used Mi Flash Tool to flash it above the existing one (no wipe) and it booted again normally.
I recently updated to 9.5.5 but I haven't tested yet if now it works. So far I have no clue what I'm doing wrong.
Sorry if my english it's not perfect, hope it helps.

Good morning friends!
I installed Rom Beta MIUI 10 Global 8.7.5 in TWRP 3.2.2
However, the system does not boot even though I'm formatting with TWRP.
Would there be some other method for ROM to reboot?
Can anyone help me with this question?
I install MIUI 10, do the procedure by installing TWRP, restart Smatphone via TWRP, install SuperSU, format the System. But when I restart my Smartphone, it does not leave the startup screen

Thanks a lot man. I've got a minor issue. Mouse cursor in the center for all time.

hi is there any way install twrp in mi note 2 with support of ota update

kmanilpillai said:
hi is there any way install twrp in mi note 2 with support of ota update
Click to expand...
Click to collapse
Always need to flash the full rom instead of ota after installing twrp. Why?

kmanilpillai said:
Always need to flash the full rom instead of ota after installing twrp. Why?
Click to expand...
Click to collapse
If you are referring to MIUI OTAs, those are differently sorted inside(folder wise) the archive... So TWRP will not find the files he needs to read...
Full ROMs are normally arranged inside (folder wise) and that's why you can flash them...

New version available 3.3.0-0 as of 20190412.
No changelog for scorpio, but article on XDA here about changes.
https://www.xda-developers.com/twrp-3-3-0-release/
Maybe useful if you need encryption, or edl?
Been using previous version for Xiaomi.eu with no problems.
Scorpio is actually a really good phone, very dependable, as long as you don't overheat it.

latest version of miui (miui11)
did it the latest twrp 3.3.1.0 work/run/installed fine on latest miui (miui 11.0.2.0) please help me
thanks in advance

I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)

Shok II said:
I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)
Click to expand...
Click to collapse
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.

cobben said:
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.
Click to expand...
Click to collapse
Ah so that's why.
Flashed Lineage 17, and now TWRP is persistent, thank you!
Oh right, I noticed that the display brightness is not working (default is too bright btw), as I slide to the right or left, there is no brightness change, TWRP 3.4.0. Haven't tried the older versions tho. Display brightness settings in Lineage works fine.

Development [RECOVERY] [UNOFFICIAL] TWRP-3.5.1 [20210702]

{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
FEATURES AND FIXES:
No need to reboot TWRP after flashing ROM, to flash gapps or any other zips. All zips you flash after a ROM will automatically go to the new slot.​
No need to flash TWRP everytime after flashing a ROM. TWRP automatically flashes itself after a zip (Controllable via a toggle)​
Supports Hentai OS encrypted devices​
Supports flashing MIUI zips​
Supports Vibration​
Supports wiping data without wrecking encryption. ​
BUGS:
On encrypted devices, if u unmount and remount /data, it will show garbage files in storage. This is because of metadata encryption and to fix it, reboot recovery.
SUPPORTS AND TESTED ON:
Mi11x (aliothin)
UNSUPPORTED (BUT MAY WORK):
Poco F3, Redmi K40 (alioth)
FLASHING INSTRUCTIONS:
Boot into attached boot.img using the following command:
Code:
fastboot boot twrp-aliothin.img
Once booted, go to Advanced -> Press "Flash current booted TWRP"
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
CREDITS:
@Nebrassy for original TWRP and device tree. I also repurposed some of his commits from gerrit.
SOURCE CODE:
Kernel (Prebuilt): https://github.com/ArrowOS-Devices/android_kernel_xiaomi_alioth
DOWNLOADS:
https://drive.google.com/file/d/1oY5WxfXYPRLumCcaPPFGuq9OhtB3CM_X/view?usp=sharing
MD5:- 0909f61c83ce9876843dabba5bf1247e
TELEGRAM GROUP LINKS:
https://t.me/PocoF3GlobalOfficial
https://t.me/pocoF3GlobalUpdates

Reserved

Reserved

ayy pro <3

Yay Yahoo

Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."

I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...

vasishath said:
Great work.
Click to expand...
Click to collapse

blinoff82 said:
Thx for your work, dev.
Quick question. Why is it not recommended to install magisk via TWRP now?
UPD: Flashed Magisk successfully with unchecked "inject twrp..."
Click to expand...
Click to collapse
Twrp reflashes itself after every zip flash, hence it removes magisk, you can uncheck inject twrp option to flash tho.

@vasishath
Hello,
First of all thank you for developing a version of TWRP.
I have a little problem with this one: failed to mount: system_root, vendor, odm
Unable to find partition for path storage
I can't install TWRP ...
I'm on the weekly xiaomi.eu
Here are the issues I'm currently having with your version of TWRP.

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot

Shadowk1ller said:
I have the same question, how should we flash magisk now? I'm old school so for me it was allways the best and fastest way...
Click to expand...
Click to collapse
John Wu recommands direct install from magisk app

vasishath said:
John Wu recommands direct install from magisk app
Click to expand...
Click to collapse
TWRP not installed after installing custom ROM. Please check.

deif102 said:
Patch the boot.img using the Magisk App and then flash the patched boot.img via fastboot
Click to expand...
Click to collapse
To much work, when i can simply flash it in twrp after i flash the rom, it was that easy in past times...
But can i uncheck inject before flashing and then check it again and flash current booted TWRP as in the beggining?

Which rom did u flash ?
blinoff82 said:
TWRP not installed after installing custom ROM. Please check
Click to expand...
Click to collapse

vasishath said:
Which rom did u flash ?
Click to expand...
Click to collapse
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..

NE0HP said:
He is referring to use controllable toggle so I assume you should have enabled it before flashing rom. I still didn't tried this twrp so dunno where actually this toggle is..
Click to expand...
Click to collapse
Of course this toggle was turned on before flashing (by default).

blinoff82 said:
My own ROM - Syberia OS (AOSP).
(Maybe after flashing ROM I can install twrp.img in recovery ramdisk?)
Click to expand...
Click to collapse
It appears to me that the ramdisk-files.sha256sum file was removed after u flashed the ROM. That caused the TWRP flashing to fail. Does your ROM's zip modify the current running ramdisk in anyway ?

Will future Miui builds now be using this version of twrp? if this is the case i wont need to flash it right now.

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

Development [RECOVERY][3.7.0_12-8][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support

This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too.
As always I'm not responsible for any bricked device or data loss resulting from the use of this TWRP builds. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Permanent installation is not possible with TMO stock ROM installed.
Installation overwrites all boot partition changes done previously (e.g. by Magisk or custom kernel). So you have to reflash all zips that change the boot partition after TWRP is installed.
For permanent installation, you have three options depending on your current system.
1. Option for rooted devices:
Download the twrp-installer zip
Flash it with Magisk manager or some other kernel flash utility
Reflash your custom kernel and Magisk.apk if previously installed (see example of how to install with Magisk manager below). Or alternatively flash zips in TWRP.
Don't reboot
Rename downloaded Magisk.apk to Magisk.zip
Open Magisk app
Select Modules tab
Click "Install from storage"
Select Magisk.zip
2. Option for users with other custom recoveries but without root:
Download the twrp-installer zip
Reboot to recovery
Flash it with "adb sideload twrp-installer*.zip"
Reboot to recovery
Reflash your custom kernel and Magisk.apk if previously installed
3. Option is universal:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Go to Advanced > Flash Current TWRP
Reflash your custom kernel and Magisk.apk if previously installed
Try without installation:
Download boot.img
Reboot to bootloader
Run "fastboot boot boot.img" with the TWRP boot image on your PC
Uninstall:
Just flash the boot partition with your current ROMs boot image with the following steps.
Replace "YOUR ROM BOOTIMAGE" with the filename of the extracted boot image of your current ROM.
Reboot to bootloader
Run "fastboot flash boot_a YOUR ROM BOOTIMAGE"
Run "fastboot flash boot_b YOUR ROM BOOTIMAGE"
Alternatively you can flash your currently installed OTA zip, which overwrites boot on the unused slot, but not on the currently used one.
TWRP Updates:
Download and flash the twrp-installer zip
After that reflash your custom kernel and Magisk if previously installed
ROM Updates:
Please follow the official update instructions for your ROM!
If they give an option to update via recovery you have to substitute adb sideload commands with zip installations. Also use the "Automatically reflash TWRP after flashing a ROM" option, if you are going to install a ROM zip to preserve TWRP installation.
In case your ROM does not provide a recovery update instruction you can try to update via recovery but you are on the safe side if you follow the official instructions. They always have a reason for their particular update instructions!
Instructions that work for me (on LOS based ROMs):
Flash ROM zip with "Automatically reflash TWRP after flashing a ROM" checked
Flash your previously installed zips (custom kernel, Gapps, Magisk, etc)
Reboot to system
If Gapps packages keep crashing:
Reboot to TWRP
Flash Gapps again
Reboot to system
For OOS updates should work out of the box, but if you have issues you can follow these steps (I haven't tested them):
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
About backups/restore:
Restore data only WITHOUT pin/pattern set.
If you restore a backup made from another ROM, then the currently installed, you may have to format data. So please manually copy all contents from /sdcard to a PC or flash drive.
Backups can be made with or without pin/pattern set. It is always good practice to copy your backups to your PC or an USB drive. Also after you restored your data partition you have to reboot to system and do a second reboot to get a working system.
To make first boot faster and eliminate the need to reboot again, additionally use the step mandatory for OOS users.
If you want to copy your backup to PC, but it doesn't show up, flash change_backup_selinux_context.zip, which is available in download folder.
For OOS users:
When data is restored, you have to delete "/data/system/users/0/package-restrictions.xml" before rebooting to system.
In case you restore a backup with pin/pattern set or have some other issues I have a guide that works for me:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
How to use MTP, adb and fastbootD:
Windows:
Install official Google USB drivers and select the right USB drivers. For MTP and adb, the WinUSB driver is sufficient on Windows 11. For fastbootD, Google drivers (Android Bootloader interface) has to be chosen.
You may have to select WinMTP for MTP and Google USB drivers for adb, if you run Windows 10.
To use adb on Windows, MTP has to be disabled with "Mount->Disable MTP" in TWRP.
Steps for choosing a specific driver (no the exact wording):
Connect phone in specific mode
Open device manager
Right click on phone either under "Android device" or "USB device", depending on mode
Select "update driver"
Select 2. option "browse my computer"
Select "pick from available drivers"
Pick driver according to above description
Linux:
Intall the fastboot and adb packages for your distribution
Set udev rules. There might be a package for your distro or use this gh repo: https://github.com/M0Rf30/android-udev-rules
Add user to the group used in udev rules. Most common are "plugdev" and "adbusers"
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/nilz3000/kernel_oneplus_sm8350-twrp
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/nilz3000/android_hardware_oplus
Bugs:
Permanent installation alongside TMO stock isn't possible
Error message regarding vendor_dlkm in fastbootD for OOS users (just cosmetic and not problematic)
In case you notice anything else please let me know.
If you encounter any bug, please give me description with logcat.txt and recovery.log output attached. You can copy those to your data folder in TWRP, if you go to Advanced->Copy Logs.
Thanks to:
@Nebrassy for the original device tree
@osm0sis for the zip installer
TWRP team
LineageOS

Thank you for this! Will try tomorrow.

Ah man this is dope. Thank you bud!!!

It seems to boot and decrypt very well, but backup always fails with error createtarfork 255

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.

Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...

vipinpvarghese said:
Hi Guys,
Can the latest TWRP be used to flash A13 ROMs like we used to do with older devices? I am fed up with wiping the entire storage for every ROM installation using sideloading...
Click to expand...
Click to collapse
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.

der_akinator said:
Updating A13 ROMs, in my case crdroid 13, works fine. I have not tested clean installation of a different ROM after factory reset with user data preservation.
Click to expand...
Click to collapse
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?

vipinpvarghese said:
You meant to say you just wiped data, cache and dalvik and flashed the ROM zip via TWRP ? Or without data wipe?
Click to expand...
Click to collapse
Yes, but it was the same ROM I reinstalled after wipe.

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse

der_akinator said:
Can you send me the logcat and recovery.log output of the failing backup? You find that option in Advanced -> Copy Log -> Include Logcat. I will look into it.
Click to expand...
Click to collapse
Sorry i forgot about recovery log

EugenStanis said:
Sorry i forgot about recovery log
Click to expand...
Click to collapse
recovery.log
Zippyshare.com - Free File Hosting
www1.zippyshare.com

Anyone tested it with stock OOS13?

der_akinator said:
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by most Android 12 and 13 ROMs.
As always I'm not responsible any bricked device or data loss resulting from the use of this TWRP version. You use this at your own risk.
For ROMs using FBEv1 encryption aka A11 encryption, please use the official builds by @Nebrassy from:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Download:
twrp-3.7.0-12.1 - Google Drive
drive.google.com
Installation:
Get your rom's vendor_boot image. For most ROMs this can usually be downloaded. For OOS based ROMs you can get it for example by extracting it from the official payload.bin with payload-dumper-go. A third universal option, if you have root, is to use the command "dd if=/dev/block/by-name/vendor_boot_SLOT of=/sdcard/vendor_boot.img" on your device. This writes the vendor_boot image to your sdcard folder, but you have to substitute SLOT with either a or b, depending on your currently active slot.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the TWRP vendor_boot image.
Run "fastboot boot boot.img" with the TWRP boot image.
Go to Advanced > Flash Current TWRP.
After that is done, if you were using a custom kernel, reflash it now.
If you were using magisk, reflash it now.
Reboot to bootloader.
Run "fastboot flash vendor_boot vendor_boot.img" with the ROM vendor_boot image from step one.
In the case you just want to test TWRP without installation, please skip steps 5-7.
Permanent installation works fine for me with crdroid 13 and magisk installed. I have not tested any other ROMs or custom kernels. After permanent installation you can at any time reboot to recovery without reflashing vendor_boot. During a ROM update use the "Automatically reflash TWRP after flashing a ROM" option in the install zip menu to preserve TWRP.
Source Code:
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8350
Device Tree:
https://github.com/nilz3000/device_oneplus_sm8350-common-TWRP
https://github.com/nilz3000/device_oneplus_lemonadep-TWRP
https://github.com/LineageOS/android_hardware_oplus
Bugs:
Please let me know. I have not encountered anything major yet.
Thanks to:
Nebrassy
TWRP team
LineageOS
Click to expand...
Click to collapse

For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.

Update
Hi everyone,
I just uploaded a new build. It fixes some missing firmware files and kernel module loading.
USB OTG, vibration and battery status is now working.
Download:
29.11.22 - Google Drive
drive.google.com

EugenStanis said:
It seems to boot and decrypt very well, but backup always fails with error createtarfork 255
Click to expand...
Click to collapse
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Here is a link to the github issue, maybe it helps you solving the problem.
createTarFork() process ended with ERROR: 255 when trying to back up data with multiple users · Issue #1373 · TeamWin/Team-Win-Recovery-Project
Yes, I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ (Oneplus 6) Yes, I am running the latest version of TWRP (3.2.3-1) Yes, I have read the FAQ (https://twrp.me/FA...
github.com

tnchng said:
For the cRDroid 13, which OOS Base are you using? I used C66, with own rec fine, if use your TWRP 3.7.0, can't boot.
Click to expand...
Click to collapse
I use C.63 and have not tested with other firmware versions.

der_akinator said:
Your problem seems to be a general TWRP problem, that oftentimes happens in multiuser system. And I couldn't access your recovery.log. In this file you find conflicting files, that are the reason for the error.
Click to expand...
Click to collapse
Strange, i have never ever in my life used multiuser