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-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
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 ??
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel!
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed. NOTE: This will only flash TWRP to the active slot!
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
N/A
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Frequently Asked Questions (FAQ)
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Common tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
N/A
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse
Frequently Asked Questions (FAQ):
How do I install an OTA while rooted and keep TWRP/root?
Full Firmware zip - in Android
Prerequisites:
Full Firmware zip for new software
TWRP installed to the current slot
Magisk Manager
Steps:
Put Full Firmware zip on root of internal storage
Reboot the device so that the update is detected
Install the update
After install completes BUT BEFORE REBOOTING, install "TWRP A/B Retention Script" module by @osm0sis in Magisk Manager
Install Magisk "to Inactive Slot (After OTA)" in Magisk Manager
Reboot and you're updated with TWRP and root retained
Full Firmware zip - Through TWRP
Prerequisites:
Full Firmware zip for new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Reboot into TWRP
Navigate to Full Firmware zip and install, or sideload zip over adb
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
Incremental OTA package - Through TWRP ONLY
Prerequisites:
Current software stock boot.img
Current software stock recovery.img
Current software stock dtbo.img (only if modified by Magisk or custom ROM)
Incremental OTA zip for current software to new software
TWRP_Flash_tpposite_Slot-CPTBv2.zip
Magisk zip (optional)
Steps:
Ensure you have the latest version of TWRP installed. If you don't, follow the instructions in the OP to flash it.
Boot into TWRP.
Use the "Install Image" feature to flash the stock boot and recovery (and dtbo) images.
Flash the incremental OTA zip.
Flash TWRP_Flash_tpposite_Slot-CPTBv2.zip to retain TWRP.
(Optional) Reboot into TWRP and flash Magisk for root.
The key here is making sure the current slot is fully stock (including boot and recovery images) in order for the incremental OTA zip to install successfully.
What's the deal with these dynamic partitions?
Here's Google's explanation.
Why can't I write to system?
Dynamic partitions (see link above). See @topjohnwu's detailed explanation here.
How do I make modifications to system?
On the stock ROM, you don't. However, you can modify system "systemlessly" with Magisk.
Can I boot the recovery image without flashing it?
No. Fastboot boot isn't possible on this device, but since there's a separate recovery partition (two in fact), and ASUS provides full stock firmware, this isn't a big concern.
What is fastbootd?
Here's Google's explanation.
Can I back up the system/vendor partition separately?
No. Because dynamic partitions. The Super partition is backed up and restored in its entirety. If you need to flash the individual images, use fastbootd.
Why can't I restore X partition (read-only error)?
Some of the partitions that can be backed up in TWRP include sensitive device data which, if corrupted, backed up, and then restored, can irreparably damage the device. Therefore, while these partitions can be backed up in TWRP, only experienced users should restore them, which can be done manually via the dd command.
(I will not provide any additional details on this procedure)
Click to expand...
Click to collapse
Reserved
Big thanks to @Buffydamion for all his tireless testing and log-providing to get this TWRP in fully working order!!
Hopefully there aren't any bugs besides the upstream ones listed in the OP, but if there are, I'll do my best to figure them out.
Since I don't have the device, I'll have to rely on all of you for logs and feedback.
Enjoy!!
--Cap
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Volski_ said:
How did you make it boot on this android 10 device? Official TWRP doesn't support android 10. Dees_Troy is still working on the solution.
Click to expand...
Click to collapse
@Dees_Troy isn't the only person on the TWRP team.
@bigbiff has been working tirelessly to add Android 10 support to TWRP, with help from @mauronofrio, @androiabledroid, myself and others. TWRP is open-source and a team effort. As you'll notice, there are still some upstream bugs that need to be fixed, which is why the official TWRP hasn't been updated yet. But it's working well enough to release it for devices that need it, and when the official TWRP is ready, these devices will have official support.
Works fine for me. Thanks!
The data partition was already partitioned to f2fs.
Flashed magisk and have a rooted phone now. Perfect!
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Captain_Throwback said:
Update - new 20200920 build with stock kernel with f2fs support thanks to a proper fix from @aleasto.
I've also unified the dtb & dtbo with the ROG3 build, so this one needs testing to confirm it's booting for everyone. Please report back here once you have a chance to update.
--Cap
Click to expand...
Click to collapse
So I had to remove the above build as it didn't boot. Building a new one now and hopefully it'll work. I'll keep everyone posted.
New release 20200922-14
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Update prebuilt kernel to source built with @aleasto's patch for f2fs
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
luiscaproducer said:
Hi guys, i tried on mine and worked smoothly...the only thing I still cant do is writing in system folder...I tried multiple app as Root explorer but still can't manage to write anything even with root permission...
Any thoughts?
Click to expand...
Click to collapse
That is normal for dynamic partitions. The full super partition can be written but not the individual block devices.
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
luiscaproducer said:
Thanks Captain! So basically I will have to wait for the official release of the TWRP? Or it will just never happen to have a super partition...Excuse the ignorance
Click to expand...
Click to collapse
That is unrelated to TWRP being official or not, lol.
TWRP upstream will soon be updated to allow read/write of the system partition, but keep in mind that verity will need to be disabled for you to change any of the content, unless you don't want your device to boot .
--Cap
P.S. If you need to make modifications to system, you should use Magisk - it's made for this exact situation.
Captain_Throwback said:
There's a new release available today, which I recommend everyone switch to at their earliest convenience. I've also added a zip attachment to the first post that will allow you to flash a TWRP installed to your current slot to the opposite/inactive slot after an OTA is installed, so that you keep TWRP (otherwise it gets replaced by the OTA/firmware zip). The zip can be flashed either in Magisk Manager after the OTA completes installing (but BEFORE rebooting) or in TWRP after manually flashing a full firmware update zip (but PRIOR to rebooting). The zip simply duplicates the recovery from the existing recovery partition to the opposite slot, so it will only work if TWRP is currently installed to the active slot.
Change Log:
Set data filesystem to f2fs in recovery fstab
Add TWRP flags to disable screen blank to ensure touchscreen gets initialized on boot and screen wake works
Click to expand...
Click to collapse
Works perfect for me. Thank you
Update 20201001-02
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Captain_Throwback said:
Changelog:
- Add support for installing incremental OTAs (requires flashing/restoring stock boot and recovery images while in TWRP)
- Add all relevant partitions to dynamic partition list and improve display of Super partition in Backup screen
- Add asusfw, EFS, Modem, & Persist partitions as backup options (USE WITH CAUTION!!)
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
[email protected] said:
------------------------------------------------------------------------------------------------------------------------
Hi,
I would like to install TWRP. if I understood correctly you have to do this:
1. Unlock Bootloader
2. Install TWRP on both partitions.
3. Install TWRP_Flash_tpposite_Slot-CPTB.zip
4. Install Magisk.
Is it right?
And the correct procedure to update OTA? can you remove magisk and module before?
Thank you for your answers.
Click to expand...
Click to collapse
You don't need #3, as you're flashing TWRP to both slots in #2. That zip is for keeping TWRP after flashing a full firmware zip.
To update with an incremental OTA, you have to have the stock boot and recovery images from the current firmware available to be flashed in TWRP. You have to boot to TWRP and flash both stock boot and recovery, and then you can flash the incremental OTA. Then reboot to bootloader and flash TWRP, then reboot to recovery and flash Magisk for root.
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
[email protected] said:
Great and thanks Captain T.
Just a clarification, if i flash a full OTA (not incremental OTA) i don't need flash the stock boot, right?
Click to expand...
Click to collapse
Correct.
And then you need to flash the zip that flashes TWRP to the opposite slot so you keep TWRP once you reboot. You'll have to reboot back into TWRP and flash Magisk if you want to keep root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03
chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt
I can't install large IMG files to internal memory? For example a gsi?
Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.
Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.
Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.
Updated TWRP Link, previously pointing to dead end.
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.
How to deactive KC Client and
Knox Enrollment Service?
Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.
Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img
klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.