TWRP 3.2.0.0 Moto Z2 force [Nash] - Moto Z2 Force ROMs, Kernels, Recoveries, & Other

TWRP 3.2.0.0 Moto Z2 force [Nash] - Moto Z2 Force ROMs, Kernels, Recoveries, & Other

{
"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"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly

Related

Unofficial TWRP Mako 3.0.2.0 EXT4/F2FS/NTFS

Unofficial TWRP Touch Recovery for Google Nexus 4 codename MAKO with ext4 f2fs and NTFS support
{
"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 is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:
Flashing Instructions:
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go in fastboot mode (hold down Power + Vol down for a ew seconds.
2. Open terminal window/command prompt to execute following commands
Code:
fastboot flash recovery TWRP_Mako-3.0.0-ext4-f2fs.img
3. With volume up and down select recovery mode e click power
4. Enjoy you reboot in TWRP 3.0.0
Download Links:
TWRP-3.0.2.0
XDA:DevDB Information
Unofficial TWRP Mako 3.0.2.0 EXT4/F2FS/NTFS, Tool/Utility for the Google Nexus 4
Contributors
vocoderism, Dees_Troy
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2016-04-08
Created 2016-02-06
Last Updated 2016-04-08

Thank you!

great job!
usb otg with "magic" zip works nice

It'd be nice to have native USB-OTG support without replacing the kernel. While mounting, backup to, restore from and install from all work as expected, I'm unsure of how installing ROM's (LP and MM ROM's specifically) using this method might be affected.

[/COLOR]
dimaka1256 said:
great job!
usb otg with "magic" zip works nice
Click to expand...
Click to collapse
What is the "magic" zip? A kernel to support usb OTG? Does it still need a external power source?

I'm assuming he's referring to the zip file contained in the following thread...
http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689
And yes, it needs to be a powered OTG cable, either a premade y-cable or as I did, bought a cheap normal OTG cable and splice an old 5v charger into it.

bfoos said:
I'm assuming he's referring to the zip file contained in the following thread...
http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689
And yes, it needs to be a powered OTG cable, either a premade y-cable or as I did, bought a cheap normal OTG cable and splice an old 5v charger into it.
Click to expand...
Click to collapse
yes, you're right in both cases
backupping and restoring to usb work ok, both with twrp2831 and this one and kernel replacing
installing 5.1.1 rom works ok with 2831 and kernel replacing
seems like M should also have no problems
external power will be needed until some crazy man dismantles the board and solders 5v bus power
ps congrats on becoming senior!

well, i've got a first problem
"magic" zip contains franco's 191 kernel which doesn't support f2fs so f2fs partitions are unaccessible by a recovery modded this way
i've tried to find the solution by exxtracting boot.img from quanta kernel but (my bad) i don't remember how to compile boot.img from zImage or extract it froom working device
upd: will try flashify or some other app to backup a boot.img from working device

i've done it!
concluding previous post
I tried to convert my /data and /cache to f2fs and keep usb-otg functionality in recovery
i applied the zip from here http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689 and lost my f2fs partitions (the kernel contained there is franco's r191 and doesn't support f2fs
as a daily driver for my phone i use quanta #10 kernel http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561 that works with stickmount nicely
So my job was:
-extracting boot.img from alive system with quanta kernel (done with flashify)
-replace boot.img in "magic" zip with acquired in previous step
so i got usbotg-replace-recovery-kernel-q10.zip
additionally, quanta kernel does not allow USB OTG by default - we should enable it in companion app or by terminal command
Code:
echo "1" > /sys/module/msm_otg/parameters/otg_hack_enable
So i created another zip that does one job - makes it
so, howto:
1. flash twrp recovery provided in OP post
2. flash usbotg-replace-recovery-kernel-q10.zip once
3. flash usbotg-q10_enable.zip EVERY TIME you boot the recovery to use USB OTG in it
disclaimer:
i'm not responsable for any consequences with your devices, at least I've flashed factory image for several times until i realised the problem - it helps
maybe i've violated some copyrights sorry and feel free to contact me
the job done is quick and dirty - i'll be glad to see, if someone makes my ideas better
yes, and it works for me
Credits:
@zaclimon for creating marvellous kernel
@zman0900 for most of work on "magic" zip
@ziddey for messing with USB OTG stuff
@vocoderism for messing with this recovery
upd: installing MM omniROM 6.0.1 20160207 succeeded with all this stuff

For info only.
My Nexus 4 running Chroma ROM February revision (based on 6.0.1 MMB29Q) appeared to work ok with TWRP 3.0, but refused to back up because it saw zero space available. It also didn't keep settings between boots. I restored 2.8.7.0 and this works fine - it sees over 10GB free, performs the backup, and retains settings.
Occasional random reboots make me think that perhaps I have a hardware problem, so maybe it's just my N4?

dimaka1256 said:
i've done it!
concluding previous post
I tried to convert my /data and /cache to f2fs and keep usb-otg functionality in recovery
i applied the zip from here http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689 and lost my f2fs partitions (the kernel contained there is franco's r191 and doesn't support f2fs
as a daily driver for my phone i use quanta #10 kernel http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561 that works with stickmount nicely
So my job was:
-extracting boot.img from alive system with quanta kernel (done with flashify)
-replace boot.img in "magic" zip with acquired in previous step
so i got usbotg-replace-recovery-kernel-q10.zip
additionally, quanta kernel does not allow USB OTG by default - we should enable it in companion app or by terminal command
Code:
echo "1" > /sys/module/msm_otg/parameters/otg_hack_enable
So i created another zip that does one job - makes it
so, howto:
1. flash twrp recovery provided in OP post
2. flash usbotg-replace-recovery-kernel-q10.zip once
3. flash usbotg-q10_enable.zip EVERY TIME you boot the recovery to use USB OTG in it
disclaimer:
i'm not responsable for any consequences with your devices, at least I've flashed factory image for several times until i realised the problem - it helps
maybe i've violated some copyrights sorry and feel free to contact me
the job done is quick and dirty - i'll be glad to see, if someone makes my ideas better
yes, and it works for me
Credits:
@zaclimon for creating marvellous kernel
@zman0900 for most of work on "magic" zip
@ziddey for messing with USB OTG stuff
@vocoderism for messing with this recovery
upd: installing MM omniROM 6.0.1 20160207 succeeded with all this stuff
Click to expand...
Click to collapse
Awesome! I was doing this exact thing last night but had to go to bed. All I was missing was the terminal command. Here's a little tip though, use Android Image Kitchen to unpack and repack your boot.img. This will gzip the image and vastly reduce its size. And yup installing MM roms works just fine.

Awesome work! Thanks

Since TWRP will obviously happily boot and function to varying degrees with just about any old kernel, I think this merits more testing. Since Quanta is an AnyKernel, it just modifies the RAM Disk of whatever base kernel you install it on. Perhaps there exists a full kernel that has OTG hard coded and enabled, thus negating the need for using a script to enable it every time. F2FS isn't really that important to me, but it is obviously for others. I think I'm going to play around with some LP/MM kernels and see what I can come up with. I'll happily share my findings with you fine folks.

bfoos said:
Since TWRP will obviously happily boot and function to varying degrees with just about any old kernel, I think this merits more testing. Since Quanta is an AnyKernel, it just modifies the RAM Disk of whatever base kernel you install it on. Perhaps there exists a full kernel that has OTG hard coded and enabled, thus negating the need for using a script to enable it every time. F2FS isn't really that important to me, but it is obviously for others. I think I'm going to play around with some LP/MM kernels and see what I can come up with. I'll happily share my findings with you fine folks.
Click to expand...
Click to collapse
Why don't you guys simply don't change TWRP's init script to add an entry to enable the OTG switch at boot? I'm pretty sure it can be done without any additional external script because it was self-compiled beforehand.

Hah, I was just about to unpack the 3.0.0-0 image and poke around.

bfoos said:
Hah, I was just about to unpack the 3.0.0-0 image and poke around.
Click to expand...
Click to collapse
Lool true there is still this option. You could do something like:
write /sys/module/msm_otg/parameters/otg_hack_enable 1
inside the init.rc of the recovery.

Yeah, I was gonna go that route, but instead I just copied the enable.sh script from @dimaka1256's zip file, dumped it in sbin and called it as a service from within init.rc. Repacked the image and flashed it... SUCCESS!!! USB-OTG enabled on boot!
***EDIT***
Here's some technical information (including the steps used to create it) about the attached zip file.
I first flashed the boot.img contained in the latest PureNexus release, then Quanta v10. Rebooted into system and used flashify to do a kernel backup. I then replaced the ziddey-boot.img image in the "magic" zip file referenced earlier in this thread, rebooted into recovery and flashed it. Rebooted recovery and flashed @dimaka1256's usbotg-q10_enable.zip and tested to see if OTG and F2FS were working... SUCCESS!!! I then rebooted back into system and used flashify to do a recovery backup. I unpacked the image with Android Image Kitchen, took the enable.sh from usbotg-q10_enable.zip and dumped it into the ramdisk's sbin directory and edited the init.rc file to call the enable script as a service. Repacked the image and flashed it, tested OTG and F2FS once more and it passed. Zipped the image as it was just over the 8MB attachment limit for .img files here. So, extract and flash away and enjoy something we should have natively... OTG!!!

bfoos said:
Yeah, I was gonna go that route, but instead I just copied the enable.sh script from @dimaka1256's zip file, dumped it in sbin and called it as a service from within init.rc. Repacked the image and flashed it... SUCCESS!!! USB-OTG enabled on boot!
Click to expand...
Click to collapse
seriously you can remove most of lines of the script that are related to checking board name (no need to it, since recovery is ok and launched) and leave just setting permissions and echo'ing the parameter
nice work!

Yup, a little teamwork by some like-minded individuals and we now have in my opinion, the best of everything TWRP has to offer our beloved N4's. 3.0.0-0, OTG, F2FS, etc.

Amazing, big up for the port. I was thinking that we will have official support, but as this thread has shown up, I realised that we'll not.
A dumb question: is this recovery capable of restoring backups made by twrp-2.8.7.0 ?

[Recovery] Official TWRP for Galaxy S6 edge (3.0.2-0)

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 (6.0+) 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 no-verity-opt-encrypt.zip.
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/samsunggalaxys6edge.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.10.7.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] + [Power] 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] + [Power] 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-0 (twrp.me) - same as v3.0.2-1
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_zerolte (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_zerolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-27
Created 2016-04-08
Last Updated 2016-10-02

Builds are coming soon, just putting a thread up for a reference on the device page!

jcadduono said:
Builds are coming soon, just putting a thread up for a reference on the device page!
Click to expand...
Click to collapse
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app

christopherrrg said:
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte 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

I have successfully flashed the latest twrp. Though I had issues with the older one in backup restore area. Does the new do up backup and restore without error?

Nothing for SM-G925I ? zeroltedv

Ognjen123 said:
Nothing for SM-G925I ? zeroltedv
Click to expand...
Click to collapse
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.

jcadduono said:
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte 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
G925W8 PC5 sources are up. Nothing for the 920W8 yet.

violin.siva said:
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
Click to expand...
Click to collapse
Can you please pm the link ?
---------- Post added at 11:16 PM ---------- Previous post was at 11:06 PM ----------
Can the twrp-3.0.2-1-zerolte.tar.md5 be flashed on the g925i ?

Why aren't the link working?

G925f link?
Inviato dal mio SM-G925F utilizzando Tapatalk

Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?

Ognjen123 said:
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Click to expand...
Click to collapse
Twrp 3.0.2 with arter97 kernel. Working flawlessly in my g925i.

This is making me crazy , is there any suport here ? Links not working , where from to dl the 3.0.2-1 ver for g925i ?

OEM Unlock ??
I can't find it in my Developper Menu. I have 6.0.1 !
Help please...

Anyone found a working link for the recovery file?

Questions about TWRP versions found over some threads
I would like to know some things. Firstly say there's still nothing when you open http://teamw.in/devices/samsunggalaxys6edge.html
so, i looked up the link you gave
https://idlekernel.com/twrp/zerolte
but if I don't remember wrong, zerolte is S6 flat.
Does that kernel work anyway?
If that's so, does that mean official http://teamw.in/devices/samsunggalaxys6.html or TWRP S6 Edge Europe Version would also work?
Why wouldn't they?
Also, what's the difference with the twrp from @arter97 found Here
with yours?
Thanks!!
I hope someone could shed some light over those questions.
Sorry for my bad english!

Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .

Ognjen123 said:
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Click to expand...
Click to collapse
See my above post.

Alright, this is what I did for my S6 Edge 925F which works fine so I thought I would share it with you guys:
I flashed the latest TWRP using ODIN from this link:
http://www.arter97.com/browse/S6/ke...r97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
which is the same link given at the bottom of this post along with the instructions as well:
http://forum.xda-developers.com/showpost.php?p=60390986&postcount=5
After rebooting the phone (which looped a couple of times), I flashed the latest SuperSU 2.71 (Beta) from ChainFire in the newly flashed TWRP which is given here:
http://forum.xda-developers.com/showthread.php?t=1538053
And now I have TWRP with SuperSU. I need to mention that I rooted my phone with CF-Auto root previously so it was already rooted, but I just wanted to have custom recovery for flashing other .zip files.
I also tried the latest stable version of SuperSU first, but it had problems finding and installing binaries. But there are no problems with the latest Beta (2.71) so far.

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy A7 SM-A720F/DS

Unofficial release -TWRP recovery for the Galaxy A7 - SM-A720F/DS, Exynos 7880
{
"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.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 12/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
NOTE: THIS IS CURRENTLY IN THE TESTING STAGE, THERE MAYBE BUGS, IT MAY NOT BOOT AT ALL. I DON'T OWN THIS DEVICE. I CAN'T FIX ISSUES IF PEOPLE DON'T POST RECOVERY LOGS OR PROPERLY DESCRIBE THE ISSUE. STOCK RECOVERY IS PROVIDED BELOW IF NEEDED.
Features:
MTP working > to be confirmed
ADB working > to be confirmed
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 images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
Issues:
Current versions of SuperSU seem to be incompatible.
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.10.7.
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: ON SOME ANDROID 5.1.1/6.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: twrp_3.1.0-1_sm-a720f_12417
Stock recovery: A720FXXU1AQC5_stock_recovery
To Root:
PHH SUPERUSER
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
or MAGISK
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
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 root (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, my tester moistcity
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
. .

thanks

Hello, when I'm flashing SuperSU the phone reboots at extracting files.

Cannot flash supersu
Sorry, I'm a new member. Had inadvertently edited

@aindra.ap29
Why did you post that?! Please remove your unnecessary post.

moistcity said:
Hello, when I'm flashing SuperSU the phone reboots at extracting files.
Click to expand...
Click to collapse
Any chance you can you test the patched version of SuperSU below?
Please save the recovery log file afterwards.
SR3-SuperSU-v2.79-SR3-20170114223742-ashyx
.

thanks bro.. :highfive:
can i try with firmware A720FXXU1AQC6?
and how about knox?

ashyx said:
Any chance you can you test the patched version of SuperSU below?
Please save the recovery log file afterwards.
SR3-SuperSU-v2.79-SR3-20170114223742-ashyx
.
Click to expand...
Click to collapse
Fancy meeting you here
I've got magisk already but I'll try to flash this and report back with the recovery log.
Off topic question though,
Has there been any successful attempt at removing the knox counter on new samsung phones (S7, A2017, C2017 etc..)?

moistcity said:
Fancy meeting you here
I've got magisk already but I'll try to flash this and report back with the recovery log.
Off topic question though,
Has there been any successful attempt at removing the knox counter on new samsung phones (S7, A2017, C2017 etc..)?
Click to expand...
Click to collapse
No, it can't be done. This is one thing that Samsung make sure of. I've seen certain websites and procedures claiming they can, but I know of no recent Samsung device that can be reset.

@ashyx will you make a version for the A5?

@ashyx
Ok, I've been reading and watching videos on Magisk, which I have never heard of before, so now I have a more informed opinion of it. It's interesting, but there definitely are some red flags, particularly with version 12 (as per reviewers). I might give it a shot, even though I still think SuperSU is more reliable and stable.
As for the patched SuperSU, was it patched by Chainfire or by you?

stephymv said:
@ashyx
Ok, I've been reading and watching videos on Magisk, which I have never heard of before, so now I have a more informed opinion of it. It's interesting, but there definitely are some red flags, particularly with version 12 (as per reviewers). I might give it a shot, even though I still think SuperSU is more reliable and stable.
As for the patched SuperSU, was it patched by Chainfire or by you?
Click to expand...
Click to collapse
Blimey you don't trust anyone! It was patched by me, honestly I won't steal your bank account details.

ashyx said:
Blimey you don't trust anyone! It was patched by me, honestly I won't steal your bank account details.
Click to expand...
Click to collapse
Lol. It's not about that, I just like to be well informed. Among other things, now I know, for example, that when Chainfire updates its app (say, to 2.80), the ZIP might still be unflashable, due to the patched version being yours, not theirs, thus, rendering their official download page pretty much useless to A7 users.
I don't have a Windows device, so I'll update you when I can.
Thanks.

stephymv said:
Lol. It's not about that, I just like to be well informed. Among other things, now I know, for example, that when Chainfire updates its app (say, to 2.80), the ZIP might still be unflashable, due to the patched version being yours, not theirs, thus, rendering their official download page pretty much useless to A7 users.
I don't have a Windows device, so I'll update you when I can.
Thanks.
Click to expand...
Click to collapse
Why do you need Windows?

ashyx said:
Why do you need Windows?
Click to expand...
Click to collapse
To flash TWRP with Odin.

stephymv said:
To flash TWRP with Odin.
Click to expand...
Click to collapse
I'd assumed you'd already flashed it. No PC at all?

ashyx said:
I'd assumed you'd already flashed it. No PC at all?
Click to expand...
Click to collapse
Yeah, none at all. I always have to go to a lanhouse, or ask someone to use theirs.
Unfortunately, we still need Windows for a lot of things, even when we don't want/have it anymore. Hopefully someday you guys will create methods where neither root nor Odin are needed to flash custom recoveries.
Oh, and I reinstalled the stock ROM when SU failed, so that's why.
See you soon.

@ashyx
Hmm.. I tried flashing the patched SuperSU but the same thing happens. It automatically reboots at "extracting files". Guess I can't provide a useful recovery.log
I restored back to my old root and I just recently discovered that magisk has some downloadable modules. Some worked but the xposed sdk23 87.1 says its been installed but doesn't appear on the modules and rebooting doesn't do a thing. I guess, help?

@moistcity
Because you're already rooted, you can probably install the Xposed sdk (if you have a Samsung, get the patched sdk, by Wanam, to avoid bootloops) directly (via TWRP) and then the Xposed installer (manager) on Android.
As for making it work within Magisk, @ashyx might know, I can't help you there as I am yet to try and know Magisk firsthand. I don't know if Magisk (modules segment) and Xposed installer can coexist, but you never know ('til you know).
Try installing the Xposed installer and see if the module you installed from Magisk shows up on the former.
Assuming they can coexist (and flashing the sdk via TWRP on a device with Magisk won't trigger bootloops), you can just install Xposed the traditional way then, unless you absolutely want the Magisk module to work. Before doing the traditional method, look up for information on coexistence, before risking it.

Will it work for A7 - SMA700FD ??

[Android 10][Recovery][A715F]TWRP 3.5.0 [ianmacd]

{
"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:
/*
* Your warranty is now void.
*
* 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 doing this to your device
* 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.
*/
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, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.0_10-4.img by ianmacd
twrp-a71-3.5.0_10-4.tar by ianmacd
Multidisabler zip by Ianmacd
VBMeta disabler
Previous Versions:
TWRP 3.5.0 10-2
TWRP 3.5.0_10-2.tar by Ianmacd
TWRP 3.5.0_10-2.img by Ianmacd
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
TWRP 3.5.0_10-4
This minor release accommodates the new (currently canary only) packaging of Magisk.
Future versions will no longer come as a separate .zip file, but will have the Magisk payload embedded inside the Magisk Manager .apk file.
To this end, TWRP will now also list any files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files.
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71

Join Ian's TWRP Telegram group
Code:
Check out the latest TWRP releases and notes on Ian's Telegram group
For anything already released, please ask here in XDA
Link: Telegram Group
Join our A71 Telegram group
Code:
Check out the latest projects on our Telegram, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Spanish General Android Telegram group
Code:
Grupo para los que hablamos español en donde discutimos Android en general /// Group made for Spanish speakers to discuss Android in general
Link: Telegram Group

How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.

so this will NOT work on an unlocked A71 A716U?

sixisixsix said:
so this will NOT work on an unlocked A71 A716U?
Click to expand...
Click to collapse
I don't think so, not sure. I don't have that device.

ShaDisNX255 said:
I don't think so, not sure. I don't have that device.
Click to expand...
Click to collapse
thank you for the response! So this model will work A71 SM-A715F/DS (amazon link)

Well it works on SM-A715F, I think the DS just stands for Dual SIM.

ShaDisNX255 said:
Well it works on SM-A715F, I think the DS just stands for Dual SIM.
Click to expand...
Click to collapse
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally

sixisixsix said:
ahh ok thank you. Samsung has an asinine amount of sku's/model which makes it extremely confusing especially in the US where you have to seek out global versions and cannot buy locally
Click to expand...
Click to collapse
Thats the truth. I've been a Samsung user for years and I still get confused with all their variants

Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse

taha2626 said:
Hi, thank you for your work.
I am getting "Invalid Zip Format" and "directory) Error opening" errors with this method at TWRP. I followed the steps, put the image into gsi folder and renamed it to system.img. Any help?
Click to expand...
Click to collapse
Probably was zipped incorrectly. Not sure.

Yeah you're right. Should've known better to zip 3 folders together instead of the parent one. It's working now and I'm testing Havoc-OS. Great, thanks.
ShaDisNX255 said:
Probably was zipped incorrectly. Not sure.
Click to expand...
Click to collapse

New TWRP is up! 3.5.0_10-4
Check out the changelog and the new download links in the OP

ShaDisNX255 said:
How to install GSI with TWRP:
The A71 (and almost all 2020 devices I believe) doesn't use the traditional partitioning system, they now include the super partition. This is called a dynamic partition. Basically, it contains system, vendor, odm and product images inside. TWRP can't install system.img directly to system partition for now, so you will have to follow a workaround.
You can follow the guide here: https://forum.xda-developers.com/t/...ung-galaxy-a51-super-partition-image.4216083/
This guide was made for the A51, but has been also confirmed working for the A71 since they both use this dynamic partition
Feel free to ask questions here or in that thread, we can try to help out.
Click to expand...
Click to collapse
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?

karan5chaos said:
@ShaDisNX255 apologies for going a bit off topic.. But could you tell if any GSI rom is stable for our device?
Click to expand...
Click to collapse
I'm sorry but I don't use GSI. I'm quite contempt with Samsung software lol.

Will this work with A71 5G? I have SM-A716U

cyclesrxnder said:
Will this work with A71 5G? I have SM-A716U
Click to expand...
Click to collapse
No, it won't.

Thanks!

A7160可以用吗
Translation: Can A7160 be used

Is it possible to add password on TWRP?

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]

Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.

Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??

works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.

Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.

I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol

Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.

Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.

Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.

zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.

Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?

As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.

I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?

Not unless you can recieve ota while rooted.

New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.

Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?

Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.

Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?

Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.

Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com

Database Develop

welcome