*** 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.
Related
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!
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?
That's great and fast, I'm thinking tab 3 plus is getting hot now.
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.
wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA
wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?
matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA
matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...
Updated TWRP for the Z5 Compact
REQUIRES:
- Unlocked bootloader
- Have Fastboot drivers installed on the PC you use for flashing
FEATURES:
- MTP support
- ADB root
- Reboot to Bootloader
- SD Card access
Not working (for now):
- Decryption <- working on it when I have time
Changelog:
23.02.2018
- Backup/Restore fix for USB OTG
- small fstab tuning (thanks @GreyLeshy)
- DL link updated - Now you will have access to all builds inside GDrive folder
22.02.2018 - 2
- Fix SD Card (again) on latest build
22.02.2018
- USB OTG fixed
15.02.2018
- Possibly fixed decryption, need feedback
13.02.2018
- Fixed SD card
7.02.2018
- First build
DOWNLOAD LINK
Google Drive
Instructions:
- Connect phone to PC in Fastboot mode
- Open Command Prompt and type
Code:
fastboot flash recovery recovery-name.img
- Take off the cable and boot into recovery by holding Power + Vol Down until you feel a vibration
Disclaimer: I am merely distributing the ready image. I will do my best to keep this thread up-to-date with the latest TWRP releases and provide fixed images in case there is a bug, I can help you to solve some problems but do not expect any timeframe.
I am not responsible for any bricked phones, missed alarms or thunderstorms. What you do with your phone is your own choice. Happy flashing!
Credits:
@TwrpBuilder for making this, all credits go to them
and all other maintainers and contributors to the code
trax7 said:
Needs testing:
- Decryption
Click to expand...
Click to collapse
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Don't need decryption and everything else works fine!! Strange how md5 checksum is now Digest!! Must be an Oreo thing
Sent from my Sony Xperia Z5 Compact using XDA Labs
@trax7
I own a Zuk Z2, on it the decryption problem was caused by unaligned/updated vendor blobs. I hope this can give you an hint on how to fix decryption.
Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.
trax7 said:
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.
Click to expand...
Click to collapse
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.
Thank you!
Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
Not working (for now):
- Decryption
- You tell me
Click to expand...
Click to collapse
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!
rm43115 said:
Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!
Click to expand...
Click to collapse
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?
What about encrypted data partition. Is it possible to fix decrypting?
jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
At the moment no, but you can try and test whether it picks it up after a factory reset... Backup ur data tho.
trax7 said:
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?
Click to expand...
Click to collapse
Ha, last night I found the problem for the strange error messages during the backup (it's not a problem of your TWRP-version):
In the .TWRPS file these partitions (persist, persistent, misc, firmware, ta) are still registered for backup from the old TWRP-version I used before.
I just had deleted the .TWRPS file and have created it again ... AND ... ERROR GONE!
I use E5823, but I would not call the problems with the violet lamp and the double-touch-unlock-screen an error ... rather a nice-to-have feature.
I mean, do not waste time with these banalities, if you do not know the solution.
USB OTG storage support
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?
rm43115 said:
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda
Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
Doe.it said:
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.
Click to expand...
Click to collapse
jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
Decryption can't be achieved by only password. It requires a factory reset (not wipe data!). This is a security measure and each Android device creates their own password for encrypted data partition. So any other passwords such as lock screen security pin won't work. All ways go to performing a factory reset. In addition, in order not to have encrypted data partition again, fstab inside boot image must be modified.
rm43115 said:
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
Yes, it is possible. Your device support OTG on it's stock fstab. After we get our works done, we will look onto this too!
Stay tuned!
berkanktz
GreyLeshy said:
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda
Click to expand...
Click to collapse
@GreyLeshy: Can I add it manually?
rm43115 said:
Can I add it manually?
Click to expand...
Click to collapse
Yes, You can with Android Image Kitchen
New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.
trax7 said:
New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.
Click to expand...
Click to collapse
THANK YOU!!!!
Now I can test the decryption this weekend ... if my children let me.
trax7 said:
Changelog:
22.02.2017
-USB OTG fixed
15.02.2017
-Possibly fixed decryption, need feedback
13.02.2017
- Fixed SD card
7.02.2017
- First build
Click to expand...
Click to collapse
You mean 2018 and not 2017.
In the latest two builds SD card access is broken again (or at least I can't access it). Reverting to recovery_suzuran-130218.img SD card access works again.
Unofficial TWRP Upstream for hero2lte
- TWRP 3.3.0-0
- Built on top of latest kernel source and upstreamed to 3.18.138
- Support for Samsung ROMs and can mount data after using them
- Code was cleaned up a lot and it should be more stable.
Credits to Ivan Meler for kernel and device sources and exynos-linux-stable for the upstreaming of linux kernel for our devices.
Instructions:
How to install TWRP recovery.img
1. Boot into an existing TWRP build
2. Download recovery image.
3. Copy TWRP image to your device
3. Click the 'Install' button
4. Click the 'Install Image' button
5. Navigate to where you downloaded the image and click on it
6. Select 'Recovery' partition option from the list, and swipe to confirm flash
7. Reboot back into recovery and you'll be in the updated recovery.
--
How to install Odin recovery.tar
1. Download Odin3 v3.13.1
2. Download Odin flashable
4. Restart your device in to Download mode (by holding Vol- & Home & Power)
5. Connect your device to your computer
6. Click 'AP' and select the .tar image you downloaded
7. Click the 'Start' button to flash the recovery
8. Reboot into recovery (by holding Vol+ & Home & Power) after successful flash.
Downloads:
16-04-19
————-
TWRP recovery.img
Odin recovery.tar
Sources: https://gitlab.com/developerlukeroms/twrp-hero
Thank you! I'm already using Tkkg1994's moded version but I guess you made some updates and improvments on it.
gonna flash it later.
edit: No freezing while changing time zone and language. Working really smooth. I think it's also faster while getting back-up and creating diggest.
Adding it to my signature since many people asking about mount data problems on custom rom threads. Once again thank you for the great work.
is there quota support like tkkg1994-version?
I flashed this version and everything went ok but i only noticed that battery level is always lower in twrp but not a big deal,thanks.
dangerhouse said:
is there quota support like tkkg1994-version?
Click to expand...
Click to collapse
Yep
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
I'm using it on pie port, working great. you can take it as Android 8.1+
Champ16 said:
Can I use it while having an android pie rom?(confused after reading the title that says android 8.1)
Click to expand...
Click to collapse
Yes, android 8.1 means the twrp base, not what rom it works for. it works perfectly on pie roms
huge thank you dude!!
turbolukex5 said:
Unofficial TWRP Upstream for hero2lte
Click to expand...
Click to collapse
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.
The settings for twrp saved in internal sdcard... Don't delete the TWRP folder
wurstherpes said:
The settings for twrp saved in internal sdcard... Don't delete the TWRP folder
Click to expand...
Click to collapse
That really helped Thank you!
rroyy said:
Is there a way to make TWRP settings permanent? It reset to default after some time. (It's like that with official one too) also anychance to have it without Official TWRP app? I uninstall it but after 1st recovery boot it comes back again. Have to keep it disabled.
Click to expand...
Click to collapse
You can't if you wipe internal storage, plus theres an option to uncheck installing twrp app in the recovery.
Is it possible to add f2fs data and cache
Good working ty so much
Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu
gupt07ash said:
Nice work
But can it keep data decrypted after I install magisk?
Currently using root with supersu
Click to expand...
Click to collapse
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted
turbolukex5 said:
As long as dm-verity is disabled, it will keep decrypted, without this twrp it wouldnt mount to twrp although being decrypted
Click to expand...
Click to collapse
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.
gupt07ash said:
This worked like a charm. I can read internal partition over magisk now. But I'm getting an error while making a backup. the recovery says "E: recv error on uevent". this error does not interrupt the backup progress and the backup can still be completed but its an error I keep getting.
Click to expand...
Click to collapse
E: recv error on uevent is harmless message, no need to worry about it.
turbolukex5 said:
E: recv error on uevent is harmless message, no need to worry about it.
Click to expand...
Click to collapse
Bruh if you made this, you're a legend!
I can finally use root hide and make full backups
Thanks :good:
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