Team Win Recovery Project 3.0.2-1
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge+ stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash .
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
[url]http://teamw.in/devices/samsunggalaxys6edgeplus.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_zenlte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S6 edge+, Tool/Utility for the Samsung Galaxy S6 Edge+
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zenlte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-08
Created 2016-04-08
Last Updated 2016-12-18
Builds are coming soon guys, I just made the thread so that we have a reference when updating the site.
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
pmisun said:
Bricked after flash, any suggestion? SM-G928F variant with audax plus 3.0 + audax kernel. Recovery not booting, tried reflash with odin old 3.0.0 recovery but the brick persist...
Click to expand...
Click to collapse
Flash the twrp via Odin provided by the Audax rom, that note 5 recovery
Sent from my Darkside of Edge plus
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
pmisun said:
Solved. Btw there is in repo of twrp dev which is linked by audax also 3.0.1 twrp working version. working as charm.
Click to expand...
Click to collapse
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
jcadduono said:
https://idlekernel.com/twrp/zenlte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
will try this evening.
pmisun said:
will try this evening.
Click to expand...
Click to collapse
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
jcadduono said:
welcome to xda, don't say you'll do things, just do things, it makes people think that they don't have to do it because someone else will do it eventually, slowing things down for everyone.
Click to expand...
Click to collapse
will try and will do..make sense? ok i wont try this.
Why nothing for s6 edge + USC? Everything else except usc version :'(
Tokumei no said:
Why nothing for s6 edge + USC? Everything else except usc version :'(
Click to expand...
Click to collapse
read after first post, builds not up on the site yet, links available
jcadduono said:
read after first post, builds not up on the site yet, links available
Click to expand...
Click to collapse
But there has never been a custom recovery for the s6 edge + USC model. (SM-G928R4 US Cellular) Unless I have missed something then please point me in the right direction for a custom recovery for this specific model.
perfect update TWRP for G928F
https://idlekernel.com/twrp/zenlte/3.0.2-1/twrp-3.0.2-1-zenlte.zip
flash from CWM
It works perfectly fine! The only bug I've found is that vibration doesn't work but that's really not important
Sent from my SM-G928F using XDA-Developers mobile app
Can someone please work on a custom recovery for SM-G928R4? I mean come on now :'(
Works really great on my 928g only vibrations don't work but I don't care thanks a lot.
Guys help
I am using note 5 twrp-3.0.0-0-nobleltezt recovery for my G928C so how to flash this
I have the international SM-G9287 Duo variant on the latest firmware 6.0.1/MMB29K/G9287ZHU2BPC6 (marshmallow) and it's rooted. When I get to the step to press Home+Vol up towards the end of the flash it just reboots normal. Then when I turn of to boot into recovery Home+Vol up+Power I get "RECOVERY IS NOT SEANDROID ENFORCING" in red along the top with the Samsung GS6 logo. I have a tar file with the stock recovery and that boots fine. Any suggestions? Thanks in advance.
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
fisk4rn said:
I can't find the download link to v.3.0.2-1 on the device page. Am I searching in the wrong place? (https://dl.twrp.me/zenlte)
Click to expand...
Click to collapse
Its link is in Post #6.
Powered by Elektrik
Related
Team Win Recovery Project 3.0.2-4
This is for the International SM-G930F/FD/X, Korean SM-G930K/L/S, and Canadian SM-G930W8 Exynos models only! Do not flash on S7 edge or Qualcomm models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/samsung/samsunggalaxys7.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap [Volume Down] to [Volume Up] (continuing to hold [Home] + [Power]) when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
If you only want a bootable system partition:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Note: This does not disable the forced encryption on Bxxx firmware, only Axxx firmware due to a change in vold by Samsung.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-4 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43
v3.0.2-3 - Fix booting on BPH6/APGH bootloaders, rebase on Note 7 sources, enable NTFS-3G formatting
v3.0.2-2 - Fix MTP issue in kernel
v3.0.2-1 - Separation of Korean variants, retrieve actual model from bootloader, drop modem from fstab, remove legacy flags, add bootdevice symlink, last_kmsg support
v3.0.2-0 - See here for the changes.
v3.0.1-0 - Fixed USB OTG storage
v3.0.0-0 (twrp.me) - Disabled backup/restore of modem partition (must be signed and flashed in Odin)
v3.0.0-0 - Initialize new device tree based on Samsung OSRC G930FXXU1APAW kernel.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_herolte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_heroltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7, Tool/Utility for the Samsung Galaxy S7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_herolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-4
Stable Release Date: 2016-10-15
Created 2016-03-11
Last Updated 2019-01-16
If you have a G930P, G930V, G930R, or G930A (aka the US Snapdragon models) your bootloader is locked. I will not be making TWRP for your device - it simply cannot happen. Sorry.
Update: G930T users can expect TWRP for their devices as soon as T-Mobile convinces Samsung to unlock the bootloader - I already have a fully complete working build ready.
You know who you can blame?
THE DONALD!~~~~~~~~~~~~
or Obama, I dunno, blaming Obama is getting kind of old guys, sorry.
jcadduono said:
For those of you with G930FD, G930T, G930W8, G930P....be patient, I'm waiting for Samsung to release the kernel sources. The trees are already ready, just waiting on kernels...
Click to expand...
Click to collapse
Great Work Mate! I just ordered my s7 today but the G930FD is the only one available here in the Philippines. Good thing you're working on multi variants. Thanks.
And root?
Leeum said:
And root?
Click to expand...
Click to collapse
Flash SuperSU 2.68 zip. I have not tried, but I'd imagine it might work. I have a kernel (actually, much more than that) coming up very soon as well.
jcadduono said:
Flash SuperSU 2.68 zip. I have not tried, but I'd imagine it might work. I have a kernel (actually, much more than that) coming up very soon as well.
Click to expand...
Click to collapse
Nice work!
Will your kernel allow system modifications?
NisseGurra said:
Nice work!
Will your kernel allow system modifications?
Click to expand...
Click to collapse
Oh, you don't have the faintest idea...
Let's just leave this image here for clues!
Recovery installed nicely. As 1st post stated, any modifications to system (even mount as RW) gives boot loop.
Is it possible to build the recovery for g935f?
Gesendet von meinem SM-G935F mit Tapatalk
Root confirmed, flash BETA-SuperSU-v2.68-20160228150503 from recovery and it boots up nicely.
hi, sorry for asking but flashing this recovery and then debloater (for example) will cause a bootloop right? because system will get modified. same goes for supersu?
Sent from my SM-G930F using Tapatalk
NisseGurra said:
Root confirmed, flash BETA-SuperSU-v2.68-20160228150503 from recovery and it boots up nicely.
Click to expand...
Click to collapse
Link? https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
innit said:
hi, sorry for asking but flashing this recovery and then debloater (for example) will cause a bootloop right? because system will get modified. same goes for supersu?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
You guys can try installing NetHunter kernel in TWRP.
http://forum.xda-developers.com/galaxy-s7/development/kernel-kali-nethunter-galaxy-s7-t3333839
(grab the kernel-only zip if you only want to try the kernel)
Unfortunately, it doesn't support encryption right now, so you would have to format your data partition in TWRP.
On the bright side, this will allow you to access your internal storage and use MTP from recovery.
jcadduono said:
You guys can try installing NetHunter kernel in TWRP.
http://forum.xda-developers.com/galaxy-s7/development/kernel-kali-nethunter-galaxy-s7-t3333839
(grab the kernel-only zip if you only want to try the kernel)
Unfortunately, it doesn't support encryption right now, so you would have to format your data partition in TWRP.
On the bright side, this will allow you to access your internal storage and use MTP from recovery.
Click to expand...
Click to collapse
thanks, will give it a try. don't really care about encryption or knox (tripped it already few days ago)
Sent from my SM-G930F using Tapatalk
---------- Post added at 10:27 AM ---------- Previous post was at 10:10 AM ----------
jcadduono said:
You guys can try installing NetHunter kernel in TWRP.
http://forum.xda-developers.com/galaxy-s7/development/kernel-kali-nethunter-galaxy-s7-t3333839
(grab the kernel-only zip if you only want to try the kernel)
Unfortunately, it doesn't support encryption right now, so you would have to format your data partition in TWRP.
On the bright side, this will allow you to access your internal storage and use MTP from recovery.
Click to expand...
Click to collapse
i seem not to be able to flash the recovery. it gives me ''fail'' in odin and some txt in download mode ''custom binary (recovery) blocked by FRP lock) or smth. i did remove google account and tried flashing again but the same error
So i don't get my phone delivered until Monday in Australia. If i install TWRP on my device and root using SuperSU 2.68 and delete say for instance a system app and try to reboot i will get a boot loop?
innit said:
thanks, will give it a try. don't really care about encryption or knox (tripped it already few days ago)
Sent from my SM-G930F using Tapatalk
---------- Post added at 10:27 AM ---------- Previous post was at 10:10 AM ----------
i seem not to be able to flash the recovery. it gives me ''fail'' in odin and some txt in download mode ''custom binary (recovery) blocked by FRP lock) or smth. i did remove google account and tried flashing again but the same error
Click to expand...
Click to collapse
Have you tried going into developer options to enable OEM Unlock and USB Debugging? Not sure if that will help or not.
Sent from my SM-G930F using Tapatalk
Leeum said:
So i don't get my phone delivered until Monday in Australia. If i install TWRP on my device and root using SuperSU 2.68 and delete say for instance a system app and try to reboot i will get a boot loop?
Click to expand...
Click to collapse
you don't even need to delete a system app...the moment you MOUNT your system as rw, you break dm-verity
https://idlekernel.com/nethunter/he...r-herolte-marshmallow-3.0.5-20160311-0424.zip
If you flash that in TWRP, it will give you a new kernel and disable forceencrypt and dm-verity, which should allow you to happily modify your system partition.
It also enables f2fs support, so you can back up your system and restore it to f2fs if you really wanted.
You can also wipe your data partition, format it to f2fs, and have unencrypted data and use of TWRP with data and internal storage again.
Or it might not boot at all and things will be broken.
If you've got a factory restore image, give er a shot, eh!
Highspeed123 said:
Have you tried going into developer options to enable OEM Unlock and USB Debugging? Not sure if that will help or not.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
it installed after 5th time but i cannot access the storage, ergo i'm not able to flash the kernel from within the recovery
innit said:
it installed after 5th time but i cannot access the storage, ergo i'm not able to flash the kernel from within the recovery
Click to expand...
Click to collapse
you need to format your data partition first anyway. back up anything you need to while in your rom, then use format data button in twrp.
do not boot back into rom with stock kernel, as it will force re-encrypt your data partition!
this will give you access to internal storage over mtp & more.
also, i suggest micro sd cards!
Knox is getting tripped, right?
Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxyj72016exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/jcadduono/android_device_samsung_j7xelte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
@jcadduono ,
Thanks for official TWRP.
Hello guy !
@jcadduono , thank you very much for great work ! It's fully working for my SM-J710FN
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Not sure if both are related but I had flashed this TWRP 4-5 days back. Last night after reboot (wasn't the 1st one after flashing certainly), phone didn't boot because of custom binary FRP lock. Had to reflash firmware.
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Amit.A said:
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Click to expand...
Click to collapse
jhampzkidoodle said:
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Click to expand...
Click to collapse
Normally on the newer Samsung devices we can flash https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/ and then go to the wipe page and use [Format Data] to turn off encryption.
It seems there is a bug with the Exynos 7870 devices that causes vold to encrypt the device regardless of whether or not boot image fstab actually calls for encryption, and I've tried removing all hints of encryption support from the boot image and yet still the system will start encrypting on the next boot.
TWRP does not support Samsung's closed off encryption as it relies on the Android OS frameworks.
I've tried submitting this issue to Samsung's Mobile Security team but they just shrugged it off and said you can't turn it off on purpose.
So pretty much you're SOL for data partition (internal storage is inside that) reading in TWRP until someone comes along with system modifications to disable encryption or a custom ROM.
Hi bro... @jcadduono
Thanks for making Official TWRP Recovery for our J7 2016. Really its great work Thanks again. :good:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
@jcadduono with the custom kernel http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736 encryption can be turned off.
thewinelover said:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Click to expand...
Click to collapse
I doubt it, it has different exynos processer
artssa said:
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
Click to expand...
Click to collapse
Offtopic post you have. Shouldn't be a problem for flashing a firmware for your device via Odin, whichever ROM you are using.
Join us Samsung Galaxy J7 2016 users Samsung Galaxy J7 ? Official Group in Telegram
Here you can chat with anyone.
Here many xda developers are present.
Here you can share any kind of data and files in any size.
And the biggest thing is that here you will get instant solution to any problem. :good:
Telegram Group Link : https://telegram.me/joinchat/Cmh8LUAs6AFEJUfawPCiWg
Regard by @KeMii :good:
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Installed Xposed... Few Modules and Partition Crushed... It was my Brand NEW Phone :'(
Hello, TWRP backup not properly block set. The size of EFS equal to 4 MB in size, inside the reserve of zeros.
No IMEI as all zeros!
Need to fix, or put my. In my TWRP you can flash system.img from firmware.
Good luck to everyone! TWRP is correctly bekapit EFS.
Extract postcode to flash the IMG.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone. Please forgive me for my English :laugh:
The Lord does not forget to thank! And then I see the downloading is not weak and thanks to zero.
ermakovermakov7878 said:
Hello,your TWRP backup is not correct unit is specified. The efs size is equal to 4MB, inside backup zeros.
I took apart and tell it like it is. That's correct TWRP backup efs + setting backup System.img
Unpack the zip to flash the img.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone.
Please excuse me for my English :laugh:
Click to expand...
Click to collapse
But it is all in russian :/
Will this work with J7-2016 with Snapdragon 617 ?
Skylinestar said:
Will this work with J7-2016 with Snapdragon 617 ?
Click to expand...
Click to collapse
No
will it work on Galaxy J7 prime ? it has same exynos 7870..
jcadduono said:
Team Win Recovery Project 3.0.2-0
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Click to expand...
Click to collapse
i have SM-J710FN. if I only follow below 3 steps, then will i b able to root my device ??
1. allow usb debugging and OEM unlock
2. flash official TWRP via Odin ... then re insert battery & reboot into TWRP
3. wipe data in TWRP and then falsh SuperSU via TWRP
is it enough.. Do I need to flash kernels first ??
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, dm-verity and mount internal storage (/data) :
1. Boot to Twrp
2. Format the Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
TWRP DEVICE Tree: https://github.com/ashyx/TWRP_Samsung_j7maxlte
Kernel source: https://github.com/ashyx/KERNEL_j7maxlte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
NOTE: I built this months ago, but forgot to post it up!
.
Great work @ashyx can you please share device tree
I Tested the recovery on my J7 Max and it's working perfectly after flashing the "Boot image patch : no-verity-no-encrypt_ashyx".
one thing i want to tell that the recovery bootlooped(Rebooting the system or Shutting down and again powering on boots into Twrp) the first time i booted it but after flashing Magisk 14.0 and the "no-verity-no-encrypt" patch it works fine.
I've attached the recovery and kernel logs.
Also add a Warning for users to backup their data as i lost all my data after flashing (
and
Thank you for building a TWRP for my device
If you have free time can you please try to build LineageOS for J7 Max
Can you please share the device tree ?
Rumorbox33 said:
Can you please share the device tree ?
Click to expand...
Click to collapse
Yes when I have the opportunity, but be aware twrp device trees are no good for building LineageOS or other custom OS systems.
Thank you for replying.
i just want to study it, upload whenever you have the time
Samsung j700h
[email protected] said:
Samsung j700h
Click to expand...
Click to collapse
No
ashyx said:
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Please post your source code This have been up for roughly a month And we need em....Thank you good sir for your hard work
Hi since j7 plus has same chipset.. Can we use this also? Thanks
ashyx said:
No
Click to expand...
Click to collapse
@ashyx Please read PMs.
TheMadScientist said:
@ashyx Please read PMs.
Click to expand...
Click to collapse
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
ashyx said:
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
Click to expand...
Click to collapse
Thank you and disregard any PMS and such all have been reversed
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Yuaan rai said:
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Click to expand...
Click to collapse
You can use any file manager with root support to move the apk to /system/app
Rumorbox33 said:
You can use any file manager with root support to move the apk to /system/app
Click to expand...
Click to collapse
Used every app and file manager but to no avail. Finally used twrp itself and boom the problem was solved. Thnks anyway.
Any custom roms for samsung j7 max sm-g615f ??
Plez help
Hey I am using samsumg galaxy j7 2015 model which rooted and have twrp recovery in it so I want to add kernel into it so can you give the file and the method to do so and also the best rom for my device
Hey, i built TWRP 3.2.1-1 for this device including some fixes such as pixel format and many more, will you update the thread if i give you the twrp and device trees or i have to make another thread ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial TWRP 3.3.0 For J7 2017Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Special features:
Code:
- built from Pie kernel source
- built in full 64bit mode
- updated TWRP source to 3.3
- Full F2FS Support
- fully compatible with all Oreo roms
Downloads:
J730x - Latest Release
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
J530x device tree - https://github.com/omnirom/android_bootable_recovery
Credits:
@corsicanu
@Dyneteve
@yshalsager
@TwrpBuilder
XDA:DevDB Information
TWRP_J730, Tool/Utility for the Samsung Galaxy J7 (2017)
Contributors
ananjaser1211, corsicanu
Version Information
Status: Stable
Current Stable Version: 3.3
Stable Release Date: 2019-04-17
Created 2018-08-30
Last Updated 2019-04-18
This TWRP is Android 8.1 Ready, when J7 officially receives Oreo this will be a direct flash either via .tar in odin or just update .img inside twrp itself.
This is also built on updated TWRP trees and all that good stuff. enjoy
sources are here if anyone wants to modify
**F2FS support is not there**
You are the best big thanks ?
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
flarestar123 said:
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
Click to expand...
Click to collapse
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
ananjaser1211 said:
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
Click to expand...
Click to collapse
Haha now even with dolby mod you will live in peace. No loud noise . And btw all those looking for the download link they are posted in github releases under assets
ananjaser1211 said:
[*]Based on Updated TWRP Tree
[*]Build with OMNI_8.1
[*]Support for 7.0/7.1.1/8.0/8.1
[*]ARM64 (2GB+ Zip)
[*]Working MTP (Windows/Linux)
[*]Propper System Mount/unmount
[*]EFS/Radio Backup enabled
[*]Aroma Support
[*]Disabled RED Debug Text
[*]Adjusted Partition Sizes
Click to expand...
Click to collapse
hey,
all is very fine.
NiceWork
plz can u disable Kernel warning line on boot to TWRP
Thanks
Thanks dev :good:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Greight said:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Click to expand...
Click to collapse
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
What is different from Latest releases and Official TWRP Builder?
ananjaser1211 said:
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
Click to expand...
Click to collapse
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
recovery is not seandroid enforcing
Click to expand...
Click to collapse
Any ideas?
quanghuy226 said:
What is different from Latest releases and Official TWRP Builder?
Click to expand...
Click to collapse
Nothing, just wanted to keep twrp builder there as it gets auto updated every month, while mine would only be updated if im experimenting more stuff.right now they are on the same thing
Greight said:
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
Any ideas?
Click to expand...
Click to collapse
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
ananjaser1211 said:
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
Click to expand...
Click to collapse
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Greight said:
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Click to expand...
Click to collapse
ok thanks for clarification, i thought it was stuck, ill add a patch to remove that red logo later.
New TWRP out:
Changes:
switched to TwrpBuilder official builds
included crypto for LineageOS software encrypted data, thanks to @Option58
made preload partition wipeable in recovery
included cpefs and m9kefs partitions in backup for safety reasons
Downloads:
J730x - https://github.com/TwrpBuilder/android_device_samsung_j7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
All the best!
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
EyuphanKundakci said:
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
Click to expand...
Click to collapse
Don't use fake displays. Done
ananjaser1211 said:
Don't use fake displays. Done
Click to expand...
Click to collapse
Other roms work excellent but your roms doesn't work please fix bro.
EyuphanKundakci said:
Other roms work excellent but your roms doesn't work please fix bro.
Click to expand...
Click to collapse
My ROMs work fine. And they are Oreo. Your device probably won't work with stock Oreo as well. Don't go cheap on a screen replacement
Team Win Recovery Project 3.4.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: S20/S20+/S20 Ultra(Exynos variants)
Download
Sources:
Kernel source
TWRP source
Device Tree: Sorry are not under GPL License since are my own so they will not get released
Changelog:
06.12.2020
- Updated TWRP Source
- Adb Push works now without disable MTP in settings
- Fixed the bug where TWRP dont saved settings
- Updated DTB and DTBO for boot on One UI 3.0 (Use Magisk 21.1 for root One UI 3.0)
- Boot only with USB Cable or USB OTG connected (THX samsung for this stupid change in the bootloader)
- Removed decrypter from download folder (use Multidisabler 2.6 instead)
03.09.2020
- Twrp boots now without nulled Vbmeta.img
03.09.2020
- Fixed Optics and Prism Backup and Restore
- Brightness is now no more at max
- CPEFS error is gone
- Sec-EFS added in the FStab
19.08.2020
-Initial Release
Bugs:
-MTP and Encryption (ADB PUSH WORKS when you disable mtp in TWRP mount settings!)
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy S20/S20+/S20 Ultra, Kernel for the Samsung Galaxy S20
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2020-08-19
Created 2020-08-19
Last Updated 2020-12-06
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with vol up+ vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and install multidisabler (you find it here on xda!)
Flash Latest Magisk
press reboot to system in twrp.
Thank you.
Thanks ?
Awesome job bro you rock !!!! ???
You Legend
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Will there be too for Snapdragon Variante of s20?
golfgtiedition30 said:
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Click to expand...
Click to collapse
Yes then you cam flash only twrp. But remember that zips made for lineage recovery dont flashes in twrp since twrp mounts the partitions differently
golfgtiedition30 said:
Thanks a lot great job.
Question:: If I'm already rooted with Linage recovery I can just flash TWRP in Odin skipping all the other steps , correct?
Click to expand...
Click to collapse
Hi all
thanks for the great job
me it's the same, does it work if I just flash the zip?
geiti94 said:
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and disable encryption! (i will post today or tomorrow a encryption remover made for twrp with super.img partition!)
Flash Latest Magisk
press reboot to system in twrp.
Click to expand...
Click to collapse
I am getting this error while formatting the data: failed to mount '/cpefs' (read-only file system)
LENO7 said:
I am getting this error while formatting the data: failed to mount '/cpefs' (read-only file system)
Click to expand...
Click to collapse
its normal since is a read only partition. you can ignore that error
Hi after flashing twrp with odin my galaxy s20 refuses to boot.
I see the warning that I have no offical samsung software and then I boots straigt to the entering fastboot screen.
Any idea how to fix that?
acocalypso said:
Hi after flashing twrp with odin my galaxy s20 refuses to boot.
I see the warning that I have no offical samsung software and then I boots straigt to the entering fastboot screen.
Any idea how to fix that?
Click to expand...
Click to collapse
on newest bootloader when you see s20 splash you need directly to release the buttons or he will boot in fastboot mode
thanks ... can you flash rom gsi?
Legend geiti right way for S20 Series
Jenanga said:
Legend geiti right way for S20 Series
Click to expand...
Click to collapse
this is coming soon too
Jenanga said:
Legend geiti right way for S20 Series
Click to expand...
Click to collapse
where you can search, in google I can't find it
Why am I banned from telegram?
Are we able to do a complete backup/restore? as per previous versions on other models?
Thanks