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.
Related
Team Win Recovery Project 3.0.2-0
This is for the SM-P580 (gtanotexlwifi) and SM-P585, SM-P585N0, SM-P585M, SM-P585Y (gtanotexllte) Exynos models only! Do not flash on other models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Tab A 10.1 (2016) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
WiFi version: http://teamw.in/devices/samsunggalaxytaba101wifi2016spen.html
LTE version: http://teamw.in/devices/samsunggalaxytaba101lte2016spen.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://build.nethunter.com.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
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.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gtanotexlwifi (WiFi) or gtanotexllte (LTE).
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 and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
--- or (not both) ---
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (WiFi): https://github.com/TeamWin/android_device_samsung_gtanotexlwifi (android-6.0)
Device tree (LTE): https://github.com/TeamWin/android_device_samsung_gtanotexllte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
It's possible to use this metod with T585 ?
Working very well on my tab A 10.1 P585Y.. bug.. cant read internal storage but it can use sd card..
I already root my tab a 10.1 p585y using this twrp.. thanks for making this recovery for our p585y.. now we need custom rom such as resurrection remix..
Worked well
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
Im using p585y version.. same here i didnt find any firmware on internet.. so my solution is using kies.. just install kies and recover it.. work for me.. right now sammobile also doesnt have the firmware yet..
Hope im helping.. press thanks if im help..
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
Will try it bro.. right now im using s7 mod on p585y but doesnt show on settings>storage but it seem working background..
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
cliemonster said:
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Click to expand...
Click to collapse
It is not your system - I had the same issue with the swipe bar. Like you, I tried several times and it finally accepted the swipe (even the pen had a few non-registering swipes).
Hi, can you plz update the links. Cuz idlekernel.com is currently not reachable nor the page of your source code for kernels :-/
And I remain highly unclear if I need a kernel for this dm-verity thing or not. I don't understand the issue reg. system boot partion. What is this? Android is already installed on the TabA - so what should I change there? Or is it for root apps?
If you want to root your tab and install TWRP you need the Kernal to turn off dm-verify and encryption. Do it in the exact order in the OP and don't let your tab try to boot rooted without turning off dm-verify.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
I think you'll find it does. Works on pretty much any Samsung device running Marshmallow.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
focus-pocus said:
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
Click to expand...
Click to collapse
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
BohArie said:
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
Click to expand...
Click to collapse
Restore your stock boot image. Apply the patch. Format your SD card as portable storage, reboot.
Look out in status bar for an SD card notification.
If you don't see it go to settings>storage. Tap the SD card choose format then internal.
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
BohArie said:
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
Click to expand...
Click to collapse
Take that with a pinch of salt. Make sure you migrate your data to the sdcard.
focus-pocus said:
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
Click to expand...
Click to collapse
Could you tell me what your baseband version / build number is? I might try flashing one of the other region's ROMs since there's a few from Hong Kong, Turkey, etc out on Updato
soft bricked device,
i soft bricked my device trying to do the TWRP recovery and it kept saying unable to mount data so i factory reset and it still didnt work so then i wiped a bunch of stuff and now it's soft bricked.
im going to download the Korean Firmware for this device, but is there anyway i can avoid that? any tips?
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.
TWRP RECOVERY
GALAXY GRAND 2
Team Win Recovery Project 3.1.0.x
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.
ScreenShoot:
Bugs:
None
DOWNLOAD Link:
https://mega.nz/#!8EJVAZrA!sr9CuyaoUmPUiavsbIyIIl1MafWO3xi36pf4ffXWtjU
Pls Don't Forget Thanks Button
Thanks works great
skippy_skippy said:
Thanks works great
Click to expand...
Click to collapse
You're Welcome Bro
Now i have TWRP 2.8.7, i just need flash this TWRP.zip in my recovery?
AiWaNczewski said:
Now i have TWRP 2.8.7, i just need flash this TWRP.zip in my recovery?
Click to expand...
Click to collapse
Yes
Awesomely working thnx bro
mani_photoworkz said:
Awesomely working thnx bro
Click to expand...
Click to collapse
You're Welcome Bro
May I flash it on my G7102?
@ndroidvn said:
May I flash it on my G7102?
Click to expand...
Click to collapse
No this is for G7105
There is twrp 3.1.x.x for G7102 you can find in some forums for grand 2. Be sure that it has the same numbers of your phone
Super I am flashing
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?
Samsung Galaxy S8 Active (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.11-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892U (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-CRUISERLTE.apk
androidfilehost
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892A (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTEATT-SS-FF-flashable.zip
LATEST APK: None
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.11-B01 [2019-04-19]
- TWRP updated to 3.3.1.
- Add proper G892A device support.
- Clean up hijack.
- Fix datamedia mount.
- Enhanced Safestrap logo.
- More stuff I forgot, lol
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
- Initial release.
BUGS:
- ROM-slots not working for now.
Great job. I will try to flash stock oreo and this safestrap via this safestrap. So i review to keep it on stock oreo.
After test, it works fine. But I can't keep it with stock oreo.
Can you enable adbd insecure on twrp? Thanks.
quanqw said:
Can you enable adbd insecure on twrp? Thanks.
Click to expand...
Click to collapse
Not sure.
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
That's normal click recovery to go-to safestrap. Bte this is supposed to be for US variants kinda lucky you didn't brick as the model it's for is listed in the title
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
You device is unlocked right? why you need safestrap?
afaneh92 said:
You device is unlocked right? why you need safestrap?
Click to expand...
Click to collapse
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
epiphany74721 said:
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
Click to expand...
Click to collapse
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
afaneh92 said:
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
Click to expand...
Click to collapse
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
epiphany74721 said:
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
Click to expand...
Click to collapse
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
afaneh92 said:
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
Click to expand...
Click to collapse
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
quanqw said:
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
Click to expand...
Click to collapse
You should ask in that thread
4.09-B01 is up
- TWRP updated to 3.3.0.
- Fix reboot function.
- Add reboot to safestrap button in reboot menu.
- Add Edl button in reboot menu.
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
Damn, needs root. I misread the post at first so ignore my previous question.
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
cd109876 said:
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
Click to expand...
Click to collapse
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
afaneh92 said:
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
Click to expand...
Click to collapse
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
cd109876 said:
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
Click to expand...
Click to collapse
Rom slot is broken on arm64 devices.
You can use stock slot only.