Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996
{
"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.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Update 18/5/2018
TWRP 3.2.1-1 build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support
IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.
WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. 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.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot
NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:
UPDATE: 18/5/2018 TWRP 3.2.1-1
twrp_3.2.1-1_T820_28518
twrp_3.2.1-1_T825_29518
UPDATE: 8/5/2017 TWRP 3.1.0-1
twrp_3.1.0-1_sm-t820_AQD6
twrp_3.1.0-1_sm-t825_AQD6
Previous builds:
SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426
SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then Magisk needs flashing below to disable dm-verity.
Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):
MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
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 Magisk
5. Reboot
OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to TWRP
2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler
3. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
4. Install Magisk
5. Reboot and check DATA is mountable
Done.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
RESERVED
Delete
Deleted.
ashyx said:
How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?
Click to expand...
Click to collapse
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
suzook said:
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
Click to expand...
Click to collapse
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
ashyx said:
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
Click to expand...
Click to collapse
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
suzook said:
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
Click to expand...
Click to collapse
Its in the first post.
ashyx said:
Its in the first post.
Click to expand...
Click to collapse
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
suzook said:
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
Click to expand...
Click to collapse
I need the recovery log after installing supersu and boot.img patcher.
ashyx said:
I need the recovery log after installing supersu and boot.img patcher.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
Click to expand...
Click to collapse
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
Click to expand...
Click to collapse
Yes apply the patch after supersu to be on the safe side.
Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M
ashyx said:
Yes apply the patch after supersu to be on the safe side.
Click to expand...
Click to collapse
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
Click to expand...
Click to collapse
Yep. Just extract it from the tar archive and then select install in twrp.
ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.
Click to expand...
Click to collapse
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
Click to expand...
Click to collapse
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
Click to expand...
Click to collapse
Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.
Related
{
"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 custom recovery for the Tab A SM-T280/T285. Latest build is 3.2.1-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, 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.
UPDATE 08/01/2018 - TWRP updated to version 3.2.1-1
UPDATE 21/11/2017 - Magisk updated to v14
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says 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 the other buttons.
You should now see TWRP recovery.
DOWNLOAD:
TWRP_3.0.2-1_SM-T280_261016
twrp_3.2.1-1_sm-t280_080118
twrp_3.2.1-1_sm-t285_080118
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this. (FIXED)
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
This step only required for the SM-T280
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v14:
1. Download Magisk v14 to your device
Magisk v14
2. Install the Magisk v14 zip with TWRP
This step only required for the T280
3. Flash the patched boot image below with TWRP.
magiskv14_boot_aqd1
4. Reboot
5. Install Magisk manager
Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Help me root my phone
Sent from my SM-G903W using XDA Free mobile app
ashyx said:
GUI lag fix - Lag in the GUI should now be fixed
MTP fix
Click to expand...
Click to collapse
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
jedld said:
interesting, what caused the lag to happen? I initially suspected it to be gpu clock throttling but didn't have time to figure it out
Click to expand...
Click to collapse
Hi Jed, after trying various different configs in twrp and even modifying the graphics source code it made no difference.
Using the the touch debugger in twrp it was apparent that the touch was responding fine.
So I turned my attention to the kernel.
After several builds of modifying the cpu config making no difference, it turns out TWRP only supports double buffering, but the kernel was forcing triple buffering.
It seems this was causing an extra frame to be displayed causing what seemed like lag and explains why when pressing the screen a second time would cause the frame to update.
The page that was in ram had changed when tapping a button, but the wrong frame in the buffer was displayed until the next touch which then updated the display.
Disabling triple buffering in the kernel fixed the issue.
jaritico said:
PRE-ROOTED boot image can be used on 285? (needed for Systemless Root ) same at magisk patched boot
Click to expand...
Click to collapse
You don't need it for the T285.
Worked perfectly, first time.
Installed supersu via trwp and then img via boot in twrp also.
Thank you for the clear tutorial.
Excellent
just about to root mine now are there any custom roms that can go on it?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, 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.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says 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 the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
I don't know how this is working for others, but installing SuperSu uninstalled android.
Ethan-56 said:
I don't know how this is working for others, but installing SuperSu uninstalled android.
Click to expand...
Click to collapse
It does what? [emoji55]
Also please don't quote the entire OP.
ashyx said:
It does what? [emoji55]
Also please don't quote the entire OP.
Click to expand...
Click to collapse
OK, I'm new to XDA. I installed TWRP and supersu, but when switching to Odin to install that other supersu thing, It wouldn't boot properly I tried deleting supersu, but I uninstalled android entirely. I got the splash screen, but TWRP warned that there was no OS installed. Does XDA Developers have a tutorial on reinstalling Android? I also can't locate the stock firmware and I forgot to back up my system.
Download the stock firmware from sammobile or UPDATO and flash with odin.
T280 comes in on Tuesday, will try this method and report back. Seems fairly easy, thanks for allowing us to have TWRP and root, it will help in debloating this 8gb version i picked up.
Any suggestion how to install Magisk v9?
Root done in five minutes, I can't believe!
Thanks ashyx!
What Gives???
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
gello924 said:
magiskv7_boot_sm-t280 in first post Failed to download, registered in Microsoft Security as a Trojan! Also download page in Android file host has the developer name as "ashyt6" and not "ashyx."
Anyone else noticed this, or did I miss something???
Click to expand...
Click to collapse
Ffs have you never heard of false positives? [emoji55] What do you expect you're installing files that compromise an operating system.
Also what relevance is it that my AFH user name is different?
ashyx said:
TWRP custom recovery for the Tab A SM-T280. Latest build is 3.0.2-1
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
NOTE: BEFORE MAKING MODIFICATIONS, 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.
UPDATE 26/10/2016: GUI lag fix - Lag in the GUI should now be fixed
MTP fix - MTP should now be working
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says 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 the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
NOTE: at the moment there seems to be a bug which causes the GUI to get a little laggy. If things stop responding just be patient and wait for the GUI to respond. I'm looking into this.
For Systemless Root with SuperSu.
1. Install Supersu via TWRP
SR1-SuperSU-v2.78-SR1-20160915123031
2 . Flash the PRE-ROOTED boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file). Current version is [SR1-SuperSU-v2.78-SR1-20160915123031].
supersu_2.78_SR1_systemless_boot_t280
3. Reboot
4. Check you have root
To install Magisk v7:
1. Download Magisk v7 to your device
Magisk v7
2. Install the Magisk v7 zip with TWRP
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file)
magiskv7_boot_sm-t280
4. Reboot
To Install Magisk v7 with SuperSu:
1. Follow the instructions above to install SuperSu
2. Reboot to TWRP and install the Magisk v7 zip below:
Magisk v7
3. Flash the patched boot image below with ODIN(AP slot) or TWRP(extract boot.img first from tar file):
magiskv7_boot_sm-t280
4. Reboot
5. Install Magisk Manager
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
followed your instruction & it works, many thanks..much appreciated:good::good::good:
Hi ashyx
To start sorry for my English, I am French and a bad student.
I want to thank you for this guide and all of your contribution on the Android scene :good:
I followed your instructions successfully but I have some questions
Can I install Busybox? If so, is it useful? If yes, how?
I have to do update Magisk v7 to v9?
To finish what is the best solution to extend the internal memory? Actually I used Link2Sd but I'm not satisfied
Thanks again for your work, a little boy will be in the angels when he will receive his gift of Christmas
Error - Security check (boot)
While odin is telling me everything it's correct and shows PASS message on my tablet Sm-t280 shows Security check fail - (boot) and when i restart i can't see any changes,
Oem unlocked and usb debug activated i tried flash with twrp image file and with supersu img file.
I hope your help thanks
Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
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.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: BETA.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source (kernel AQC4)
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
Micro SD card >> Not working.
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
IT'S ADVISABLE TO BACK UP ANY PERSONAL FILES.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
ashyx said:
Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
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.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: ALPHA(Untested)
I don't own this device so this build is currently untested. It may boot, it may not. If there are issues I would appreciate proper details and if possible the recovery log which can be found under ADVANCED/SAVE LOG.
I always advise having the stock firmware to hand just in case.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Click to expand...
Click to collapse
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
gean vilharva said:
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Please don't quote the entire OP.
I don't speask Portuguese, but from what I can make out you are saying TWRP doesn't boot?
Can I ask which firmware build your device is on? You should be on at least AQC4.
Can you try this version?
https://www.androidfilehost.com/?fid=673368273298961224
.
tried this touch is not working
Ephesis said:
tried this touch is not working
Click to expand...
Click to collapse
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Touch is not working
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Click to expand...
Click to collapse
both is working on me but the touch on both is not working.
Ephesis said:
both is working on me but the touch on both is not working.
Click to expand...
Click to collapse
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
ashyx said:
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
Click to expand...
Click to collapse
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can i ask your firmware version your device is running?
Click to expand...
Click to collapse
j7-g610f
g610fddu1api9
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
The kernel is based on AQC4, so I'm guessing this could be the issue?
Wonder if anyone using AQC4 firmware could confirm?
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
havananyx said:
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
Click to expand...
Click to collapse
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
Touch is working bro thank you. awsome work
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
The Touch issue is fixed but the sd card mount bug is still there ..!
jagopk said:
The Touch issue is fixed but the sd card mount bug is still there ..!
Click to expand...
Click to collapse
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
ashyx said:
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
Click to expand...
Click to collapse
Sent from my SM-G610F using XDA Labs
@ashyx Thought I'm not rooted. But I can help u with this kind of things
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
Sent from my SM-G610F using XDA Labs
Click to expand...
Click to collapse
Many thanks for that! Even though you are not using it you're the only one willing to assist.
Anyway based on your post I have made some changes. Could someone test this out and see if it fixes the SDcard mounting issue?
https://www.androidfilehost.com/?fid=961840155545572469
.
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Click to expand...
Click to collapse
No need to flash supersu unless you wish to root.
Which kernel are you referring to? There is no need to flash any kernel.
{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note8 ExynosOnly for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly
Unofficial release -TWRP recovery for the Galaxy A6 plus 2018 - SM-A605 MSM8953
{
"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.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 18/11/2018
Beta build released.
Current status - Beta (tested working)
Treble supported
Update 14/12/18 - OTG support added.
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.
NOTE: ON ANDROID 5.1.1> 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.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot and hit start.
twrp_3.2.3-1_sm-a605_141218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
6. Move on to root instructions below. This is a requirement to get the device to boot.
*****OREO ROOT INSTRUCTIONS:*****
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
A605_oreo_forced_encryption_disabler
2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @nebkas for initial testing, @BlackMesa123 for RMM bypass zip.
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
Hi, I also collected my twrp for sm-a605fn but I have a memory card and it mounts all partitions at once, can I help you? You can write in a telegram to me
kes228 said:
Hi, I also collected my twrp for sm-a605fn but I have a memory card and it mounts all partitions at once, can I help you? You can write in a telegram to me
Click to expand...
Click to collapse
Not sure what you mean by it mounts all partitions at once?
ashyx said:
Not sure what you mean by it mounts all partitions at once?
Click to expand...
Click to collapse
I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job
---------- Post added at 02:08 PM ---------- Previous post was at 02:00 PM ----------
kes228 said:
I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job
Click to expand...
Click to collapse
you can follow the link https://t.me/joinchat/AAAAAElB-MiezOR9qbn4MQ
For communication
post was obsoleted
U writes that your recovery virus is detected, hmm weird
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
you are great ashyx. does this boot.img work with all the different regions firmware?
nebkas said:
Thanks a lot @ashyx
I will try it out in the evening. 15:00 we have here now in Romania, I will be arround in 7 hours.
I recommend all testers, to patch the boot.img with magisk from their own localized firmware. Download your firmware from samsungbay.
1. Flash the whole firmware, all included 5 files with odin.
2. extract from the AP_ file the boot.img.lz4 .
3. unpack the boot.img.lz4 with a command line tool. I ran into problems and not patchable boot.img with extracting with 7zip.
4. Install magisk manager app and go to install. Choose the before extracted boot.img from the original firmware. Magiskt will now patch the boot img and you will be able to flash it via odin.
------------------------------------------------------
5. after all that worked fine, flash the recovery with odin.
Now you should have a twrp recovery and boot into it. Format the data etc. at mentioned in the inital post.
Click to expand...
Click to collapse
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.
ariber14 said:
you are great ashyx. does this boot.img work with all the different regions firmware?
Click to expand...
Click to collapse
There's a good chance as the sources are the same for all models.
In my experience with other devices it will work without issue.
It's not strictly necessary to flash the patched boot image as Magisk may be able to patch the boot image. However not always which is why I provided it pre-patched.
balanadi said:
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
Click to expand...
Click to collapse
At least this indeed confirms this device supports RMM.
In that case I should provide a link to the RMM patch here.
hi . when i wanna flash the pached boot in download mode it says only offical binaries are allowed to be flash
what should i do?
ashyx said:
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.
Click to expand...
Click to collapse
I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM
---------- Post added at 18:16 ---------- Previous post was at 18:12 ----------
erfanhsz said:
hi . when i wanna flash the pached boot in download mode it says only offical binaries are allowed to be flash
what should i do?
Click to expand...
Click to collapse
Delete the google account, and restart your phone to disable FRP LOCK. Also check in developer options, that you check OEM UNLOCK ENABLE
nebkas said:
I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM
Click to expand...
Click to collapse
What you're suggesting is no different to flashing the Magisk zip with TWRP. Except using Magisk manager just makes it a more long winded process, as there are extra steps involved.
As long as Magisk and RMM patch are flashed before booting to system there shouldn't be an issue.
ashyx said:
At least this indeed confirms this device supports RMM.
In that case I should provide a link to the RMM patch here.
Click to expand...
Click to collapse
great news!! finally we have decent twrp and root thanks to ashyx keep up the good job bro
ariber14 said:
great news!! finally we have decent twrp and root thanks to ashyx keep up the good job bro
Click to expand...
Click to collapse
Any chance you could do me a favour and post me the recovery.log with an SD CARD installed?
ashyx said:
Any chance you could do me a favour and post me the recovery.log with an SD CARD installed?
Click to expand...
Click to collapse
I haven't flashed twrp yet. Propably tonight will be done. Of course i will send you the recovery log
to disable rmm prenormal from twrp
https://drive.google.com/file/d/1mm86XUJOji0fZRhd4WqwSZmNN272X1Y-/view?usp=sharing
Wow you did amazing thing! but there is a small problem. I cannot change brightess in recovery.
Hello ashyx again how can I contact you?
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
dario-20 said:
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
Click to expand...
Click to collapse
Always wipe dalvic cache data storage and format data before you flash any rom
It
akoaypinoy said:
Always wipe dalvic cache data storage and format data before you flash any rom
Click to expand...
Click to collapse
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
dario-20 said:
It
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
Click to expand...
Click to collapse
How you flash havoc? Vanilla or Gapps version?
akoaypinoy said:
How you flash havoc? Vanilla or Gapps version?
Click to expand...
Click to collapse
Gapps
If you installed a new rom, clear the data and delvik cache at the end.
StaryMuz said:
If you installed a new rom, clear the data and delvik cache at the end.
Click to expand...
Click to collapse
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
dario-20 said:
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
Click to expand...
Click to collapse
That's weird, havoc is not kind of caf rom , hnnn
akoaypinoy said:
That's weird, havoc is not kind of caf rom , hnnn
Click to expand...
Click to collapse
After this installation I cannot boot into recovery! Probably I installed twrp in wrong way for the very first time. But still don't know how to make it right. It means when I install twrp in the wright way I cannot install Havoc... Maybe tommorow I will try to come back to twrp...
The correct way to install TWRP is to run it without installing it first and then install it to the ramdisk. If you do it any other way, you will delete the boot and replace it only with the recovery one. Then the phone can't go anywhere but recovery.
only boot from twrp. dont flash it
inn0ichi said:
only boot from twrp. dont flash it
Click to expand...
Click to collapse
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
dario-20 said:
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
Click to expand...
Click to collapse
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
akoaypinoy said:
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
Click to expand...
Click to collapse
Thanks but: Now I am on OrangeFox recovery (which I cannot boot - it was the last flashed recovery). Typing fastboot boot twrp.img gives back: not found
What do you suggest in this situation?
StaryMuz said:
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
Click to expand...
Click to collapse
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
StaryMuz said:
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
Click to expand...
Click to collapse
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
{
"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"
}
Reboot to recovery → I return to the same recovery as above.
dario-20 said:
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Click to expand...
Click to collapse
orangefox is that your recovery now. Orangefox and twrp are recovery both. The difference is that orangefox can no flash the kernel unlike twrp. Please be specific what you are doing,
Orangefox and twrp are recovery
HavocOS is a rom
Before you do make specific, or else you get messed.
dario-20 said:
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
View attachment 5449627View attachment 5449629
Reboot to recovery → I return to the same recovery as above.
Click to expand...
Click to collapse
Everytime you install a new make it read . Because other rom have own recovery. (Ex. Pixelplus) once you install that automatically you have a pe recovery once it reboot , so the proper way to maintain twrp is "flash current twrp" which you can find in advance in twrp recovery. Remember once you flash a new rom don't reboot and go to advance then flash the current twrp. After that reboot.