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!
Related
Note: This has been deprecated in favour of LK for Xperia T
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
F.A.Q
Q. The title says TWRP and CWM but when I boot recovery I only see TWRP. How do I get CWM?
A. TWRP is the default recovery, if you want CWM you should download the CWM update.zip in the second post and flash it with twrp.
Technical Info
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.
Updates:
1. Updated image in first post to fix bug where creating a backup would fail and crash twrp.
2. Updated first post to show CWM in title and answer questions about how to get CWM.
Flashable zips:
In the first post it is mentioned about using the FOTAKernel trick by Dees_Troy to offer easy updates. The 2 zips attached to this post are examples of the ease of use.
flashCWM.zip - This will flash CWM to the FOTAKernel and replace TWRP as your recovery.
flashTWRP.zip - This will flash TWRP to the FOTAKernel and replace TWRP that is built into the image that was flashed to your device by fastboot, or to replace CWM with TWRP again if you used the flashCWM.zip
This also makes updates easier as you do not need to replace the kernel image you currently have flashed to your device.
Re: [RECOVERY][TWRP]Stock Kernel on Official Jellybean
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
gregbradley said:
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Click to expand...
Click to collapse
Yes, wifi does work because it is just the stock kernel with TWRP added. I am running it right now with no problems.
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
lilstevie said:
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
Technical Info
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.
Click to expand...
Click to collapse
Such a good news!I will port it to TX JellyBean firmware if you don' mind
gregbradley said:
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
Click to expand...
Click to collapse
only for unlocked bl, correct?
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
hkjr said:
only for unlocked bl, correct?
Click to expand...
Click to collapse
Yes
MysticEnforcer said:
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
Click to expand...
Click to collapse
Same here....seems backup is not working
MysticEnforcer said:
the 'backup' also takes only a few seconds, then the 'backup' is done.
Click to expand...
Click to collapse
Updated first post with a fixed image.
Thank you very much, this is the best message of day.
Just flashed new image
Doing a backup and it seems to work...will update in few minutes when it is finished
EDIT:
It works
Backup complete in 385 seconds
FYI,
both times on rebooting system from recovery I initially got the grey triangle, both times it was only for 10-15 seconds before the phone rebooted...
Testing it now ....
Edit:
[Backup completed in 461 seconds] External SD card with compression on. No Grey triangle for me.
[Restore completed in 192 seconds] Restored backup without any problems. No grey triangle on second reboot either.
Seems to work great for me.
(only clock seems to be incorrect. 7 hours and 16 minutes behind)
Edit 2: thirth boot up seems to get stuck on grey triangle for about 15 seconds
Edit 3: Seems only the first time reboot after using the recovery the grey triangle is there. Rebooted the phone 4 times and only got the triangle 1 time.
Updated first and second post
USB storage does not work at all both on TWRP and CWM
tested 2nd version, works fine for me & no grey triangle :good:
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
Noticed that to
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
lilstevie said:
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
Click to expand...
Click to collapse
Thanks for the reply I guess we just have to wait for the kernel sources to be published
Besides another issue - in CWM wiping dalvik-cache does not work.
romcio47 said:
Besides another issue - in CWM wiping dalvik-cache does not work.
Click to expand...
Click to collapse
I can't reproduce this, if I wipe dalvik-cache in CWM it removes /data/dalvik-cache as it should.
Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10
Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09
Thanks!
OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!
Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.
any chance for g800h support?
sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.
ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.
I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).
ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk
Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...
fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.
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:
*** 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.