Database Develop

[RECOVERY][UNOFFICIAL] TWRP 3.1.x

UNOFFICIAL TeamWin Recovery Project
for
Samsung Galaxy Tab 10.1
(p4wifi / GT-P7510)
(p4 / GT-P7500)
(p4tmo / SGH-T859)​
Downloads
Mirror
Changelog:
Code:
3.1.1-20171009_v2
- Fix issue with some updater script functions.
3.1.1-20171009
- Use correct ramconsole address.
3.0.3-20170120
- Compile on android-6.0 base
3.0.3-0 (20161229-p4wifi)
- Update prebuilt kernel
3.0.3-0
- Fix adb sideload
- Enable TRIM
- Reduce GPU carveout size
- Update F2FS
- Compile on Android 7.1.1 base
Donate:
via Paypal​
XDA:DevDB Information
TWRP 3.1.x, Tool/Utility for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
Version Information
Status: Stable
Created 2016-12-19
Last Updated 2019-05-01

'good,i can t wait。

Update from twrp 3.0.2 and after reboot in the new version only perform a cache cleaning and dalvik-cache, it was done indefinitely and after twenty minutes I had to restart by pressing the power button for a few seconds, Reboot so you might have completed the cleanup. How can I get a log of the bug? Maybe help him to correct it.
Sorry for my bad English...

i tried this last night
it installed fine and boots to recovery fine,
but when i tried to install a new rom it freezes and i have to reboot it by holding the power button
the same thing happens if i try to do a wipe

rexxxlo said:
i tried this last night
it installed fine and boots to recovery fine,
but when i tried to install a new rom it freezes and i have to reboot it by holding the power button
the same thing happens if i try to do a wipe
Click to expand...
Click to collapse
Same here on the p4: formatting partitions or installing images never end (and one cannot see any error/warning either). And it the same behaviour when trying to push files via adb while the formatting process or the install of an image hangs --> simply nothing happens (it hangs,too, like if it is blocked).
Fortunately I had an old 2.8.7.0 version on my p4, so this version 3.0.3.0 definately is not working properly on the p4.
Let me know in case I can do some logging or debugging.
Kind regards, mistersixt.

Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg

decatf said:
Build 20170119 is posted. If it still freezes then reboot into recovery again and get the kernel log from /proc/last_kmsg
Click to expand...
Click to collapse
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.

mistersixt said:
Still the same problem with build 20170119, please see last kmesg here (tried to wipe dalvik & cache, it is also waiting forever like when installing zips):
http://144.76.203.117/tmp/last_kmsg_TWRP-3.0.3.0-20170119-P4.txt
Kind regards, mistersixt.
Click to expand...
Click to collapse
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.

decatf said:
Oh, I thought it was locking up. Can you use adb to get the kernel log (dmesg) and and TWRP from /tmp/recovery.log.
Click to expand...
Click to collapse
I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.
Kind regards, mistersixt.

mistersixt said:
I am on the move this weekend, will try to help as much as I can on Monday, however, I do remember that accessing the p4 via adb does no longer work once the TWRP is stuck with wiping cache&dalvik or when trying to install a zip file. And it is indeed not locking up completely, this progress bar simply moves forever, with no error message or warning, and one had to do a reset.
Kind regards, mistersixt.
Click to expand...
Click to collapse
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.

decatf said:
Try the 20170120 build. It is compiled on android 6.0 frameworks instead of 7.1.
Click to expand...
Click to collapse
Bingo, this version seems to be running fine again on the p4!
Thanks a lot,
Kind regards, mistersixt.

getting eror 70 flashing gapps

Recovery unsucessful
I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.

xdatroxx said:
I am on 3.0.3 20170120 build and when performing a recovery TWRP produces an error in the last part of the recovery when recovering System, data and root.
The process extractTarFork ends with error code 225.
Click to expand...
Click to collapse
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.

decatf said:
Go to Advanced.
Tap on Copy Log.
Post the recovery.log that was saved on your device.
Click to expand...
Click to collapse
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)

xdatroxx said:
I found out the problem occurs when restoring the data partition (tried with different back-up sessions)
Click to expand...
Click to collapse
Did you create a file or folder at /data/app/com.android.vending-1.apk ? Perhaps from one of the methods to prevent Play Services from updating? I can reproduce the same issue by doing this.

Thanks for your support and fast response.
Yes, I did!
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?

xdatroxx said:
Thanks for your support and fast response.
Yes, I did!
If Google Play Store updates then I get Error Messages constantly on the screen which basically makes working with the tablet impossible. That is why I created this file which cannot be updated.
What do you suggest?
I assume the data partition is written correctly during back-up, but cannot be restored because of com.android.vending-1.apk?
Click to expand...
Click to collapse
The permissions are too restrictive such that recovery can't overwrite that file.
Remove that file then restore.
Code:
chattr -i /data/app/com.android.vending-1.apk
rm /data/app/com.android.vending-1.apk
You don't need that hack anymore. Install Play Services 10.5.

Thank you very much!!!
Recovery was successful. :good:

Sorry, but I got another error message when trying to flash Viper4Athmos (https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137).
Installation of ZIP file aborts with error code 4. Log is attached.
Thanks for taking a look!

Unofficial TWRP for sagit [F2FS+EXT4][Unofficial]

Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM

Thank you for your great work . keep it up

Thanks,I'm following the topic

Sorry for my ignorance....but can somebody tell me the difference between these two?

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/

DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward

fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course

New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?

Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0

Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?

perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1

I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...

Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?

Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )

This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444

New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.

Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!

I assume this twrp version use for flashing gsi. Am I correct?

[RECOVERY][OneUI-2.5][UNOFFICIAL] TWRP 3.4.0_10.0 For Samsung M51 - Final

*** WARNING ***​This version of TWRP is not compatible with Samsung android 11 (OneUI 3.1) release and it won't work if you have updated your phone to that android version
If you need more detailed steps of what do then wait for my complete guide
I'M NOT RESPONSIBLE IF YOU BRICKED YOUR DEVICE BECAUSE YOU ARE STILL NEWBIE
This is recovery won't get further updates or support​
Bugs
-Userdata decryption is not working so you should use an external SD or USB OTG for putting ZIPs and IMGs on it in order to flash them
How to Install
1. Unlock your bootloader
2. Boot to Odin mode
3. Check AP box and select TWRP tar file
3. Hit start
4. Have fun
Download
TWRP 3.4.0_10 - Stable 1
Sources
TWRP device tree: https://github.com/Lehkeda/android_device_samsung_m51_pbrp/tree/android-10_pbrp/
Kernel source: https://github.com/Lehkeda/android_kernel_samsung_m51/tree/ten

Change Log:
Stable 1 - 19th of December 2020
- Fix MTP
- Fix data partition mounting
- Fix system image flashing
Beta 2 - 16th of December 2020
- Fix ADB
- Fix mounting partitions (Except userdata)
- Fix navigation bar
- Fix CPU temperature
- Add reboot to download mode
Beta 1 - 12th of December 2020
- Initial Release

F.A.Q
How to mount system root to flash ZIPs and other stuff?
-Go to Advanced > terminal
-Type "mkdir /system_root"
-Type "mount /dev/block/mapper/system /system_root"
How to mount data partition?
-Go to Advanced > terminal
-Type "mount /dev/block/by-name/userdata /data"

Thanks man. I ll try to fix mtp , storage and scaling.

bekirakil said:
Thanks man. I ll try to fix mtp , storage and scaling.
Click to expand...
Click to collapse
Storage is partially fixed now.
For MTP, I compiled the kernel without Samsung MTP and it's Kinda working... adb can detect it now, but it still now showing on my computer
I need to add a proper init stuff for it

i was able to fix mount sdcard but i couldn't fix data im working on it

The encryption is really annoying

That was the best i could do. Data mounting is not working because of encryption. I couldn't find the key directory of the encryption. But you can flash from external sd.

Hello. Backup, Restore, running smoothly? Can I back up without problems? Thank you very much, thank you.

onurmemo77 said:
Hello. Backup, Restore, running smoothly? Can I back up without problems? Thank you very much, thank you.
Click to expand...
Click to collapse
It would be nice if you can test that for me as I'm not able to test right now!

LahKeda said:
It would be nice if you can test that for me as I'm not able to test right now!
Click to expand...
Click to collapse
Sure, I'll help.
But I couldn't download the new version of the twrp. Would you please upload to sites like media fire gdrive? Thank you very much, thank you.

onurmemo77 said:
Sure, I'll help.
But I couldn't download the new version of the twrp. Would you please upload to sites like media fire gdrive? Thank you very much, thank you.
Click to expand...
Click to collapse
Download it from a pc or activate desktop site option before downloading it or click on download it anyway link

Can you give me your email please? I need your help at my project. Maybe you can help. (Sorry for my bad english i'm german )

bekirakil said:
Can you give me your email please? I need your help at my project. Maybe you can help. (Sorry for my bad english i'm german )
Click to expand...
Click to collapse
DM me at telegram @lehkeda

The userdata decryption bug, does that mean it can't access the phone's storage in TWRP?

Camack said:
The userdata decryption bug, does that mean it can't access the phone's storage in TWRP?
Click to expand...
Click to collapse
Yes, but you can still access the data on USB device or external sdcard

@LahKeda After installing TWRP and flashing Magisk, do I need to press power and volume up button every time I restart the phone to have Magisk root or can I boot it normally without pressing anything?

swiftez said:
@LahKeda After installing TWRP and flashing Magisk, do I need to press power and volume up button every time I restart the phone to have Magisk root or can I boot it normally without pressing anything?
Click to expand...
Click to collapse
+1 would like to know too as the current root method patching boot.img with Magisk, you have to press power and volume up every time you restart the phone to keep root.

Thanks for the recovery. I have a question. Can I simply flash this via odin (no stock firmware download required) and it will work? I'm asking because in the other twrp thread there is a requirement of downloading and flashing stock firmware. The firmware for my region hasn't released yet.

Affangta said:
Thanks for the recovery. I have a question. Can I simply flash this via odin (no stock firmware download required) and it will work? I'm asking because in the other twrp thread there is a requirement of downloading and flashing stock firmware. The firmware for my region hasn't released yet.
Click to expand...
Click to collapse
Yes, no need to flash stock firmware at all.

[RECOVERY][UNOFFICIAL][OneUI3.1] TWRP 3.5.1_10.0 For Samsung M51

I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES, DATA LOSS, OR THE WORLD WAR III...
FLASH THIS AT YOUR OWN RISK
ALWAYS READ THE INSTRUCTIONS BEFORE INSTALLING ANYTHING CAREFULLY.
IF YOU ARE NOT SURE, ASK IN THE COMMENTS BELOW OR IN THE TELEGRAM GROUP FOR HELP. OTHERWISE, DON'T BLAME ANYONE OTHER THAN YOURSELF
Bugs
-Userdata decryption is not working. You can flash multi disabler (check this before flashing) to disable encryption or use an external SD or USB OTG for putting ZIPs and IMGs on it in order to flash them
- Data backup is not working due to device encryption
How to Install
0. READ F.A.Q section first here
1. Unlock your bootloader
2. Boot to Odin mode
3. Check AP box and select TWRP tar file
4. Hit start
5. Reboot to TWRP and flash multi disabler if you want (check this before flashing it)
6. Have fun
Download
TWRP 3.5.1_10 - Beta 2
Multi Disabler
Sources
TWRP device tree
Kernel source

Change Log:
Beta 2 - 24th of March 2021
- Update to latest kernel 4.14.190
- Fix MTP on the latest kernel
- Clean up dynamic partitions
- Released kernel 4.14.190 source
Beta 1 - 20th of March 2021
- Initial Release

F.A.Q:
What is data encryption and why doesn't it work on TWRP?
Samsung M51 uses file-based encryption that encrypts the user data partition.
By default, TWRP can't decrypt user data partition, which makes it impossible for us to access the internal device storage from TWRP or recovery MTP, which means you can't put ROM files on your internal phone storage and flash them from there.
What is Multi disabler and how does it affect your phone?
- Multi disabler disables and removes the encryption on the data partition, which makes it possible for you to access your internal storage from TWRP or recovery MTP. thus, making it possible for you to flash files from internal storage.
- Removing the encryption on your device's internal storage makes it possible for you to access your files from recovery directly, which makes it possible for anyone to access your private files without your permission from recovery.
- All of the above means that your device will be less secure. So if you care about device encryption then don't flash the multi disabler and use a USB OTG or a sdcard to flash ROMs, which I recommend. Otherwise, flash the multi disabler at your own risk!!!
- FLASHINF MULTI DISABLER REQUIRES PERFORMING A FULL DATA WIPE WHICH MEANS YOU WILL LOSE YOUR DATA. SO BACKUP YOUR DATA BEFORE FLASHING IT.
My device keeps rebooting to recovery after flashing TWRP, why?
Most probably you will need to wipe your data partition and flash multidisabler
Data backup is not working even after flashing multidisabller, why?
Current multidisabler still can't fully disable FBE encryption, which means that TWRP can't read data partition at all, hence creating backups will always fail.

Reserved just in case

Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.

onurmemo77 said:
Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.
Click to expand...
Click to collapse
Currently I have no working ROM so I can't test back and restore functionality. But backing data should be working.. don't take that for granted tho..
It would be great if you can test that and report if it's working or not, or wait until I or someone else test that.

thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!

ilya33 said:
thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!
Click to expand...
Click to collapse
What error do you get? Can send me the recovery log?

LahKeda said:
What error do you get? Can send me the recovery log?
Click to expand...
Click to collapse
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:

ilya33 said:
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:
Click to expand...
Click to collapse
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.

LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com

LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks

ilya33 said:
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com
Click to expand...
Click to collapse
prerooting won't solve encryption issues. Maybe when TWRP can be build using android 11, we can fix encryption issues or at least partially fix it.

ilya33 said:
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks
Click to expand...
Click to collapse
Then go ahead and test this one. plus lineage 18.1 will drop here soon!

Backup failed
Error code: 255

saleem137 said:
Backup failed
Error code: 255
Click to expand...
Click to collapse
Did you even read the FAQ section?
anyways, backups will fail because of data encryption

Does this TWRP require to format data after installing without Multi disabler?

smallKING81 said:
Does this TWRP require to format data after installing without Multi disabler?
Click to expand...
Click to collapse
Nope, but you may need to install multidisabler to prevent the phone from reverting back to stock recovery. Don't formate the data after flashing Multidisabler and see if the phone boots or not

LahKeda said:
Then go ahead and test this one. plus lineage 18.1 will drop here soon!
Click to expand...
Click to collapse
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?

ilya33 said:
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?
Click to expand...
Click to collapse
Data backup doesn't work because of data encryption.
Yes! it's working without any problems with lineage 18

how downgrade sm-a605fn from android 10 to 9

Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you

1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.

nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.

I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks

Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.

I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
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
exactly which file do I have to download among ASSETS of any release?
Thank you very much

Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com

Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.

Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com

Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again

It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.

Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...

Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article

nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again

Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.

The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.

Maybe I have to try with sideload ?

Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?

nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?

Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.