[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy On8 SM-J710FN - Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth

Unofficial release -TWRP recovery for the Galaxy On8 - SM-J710FN, Exynos 7580
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Update 1/5/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
ADB backup
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-j710fn_29417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, TeamWin, special thanks to my tester hhaawwkk
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
.

You did good job. If I helped you. hit a thank.
thank you

hhaawwkk said:
You did good job. If I helped you. hit a thank.
thank you
Click to expand...
Click to collapse
Added to credits.

It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk

apna.suresh0305 said:
It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk
Click to expand...
Click to collapse
try a j7 2015 rom and see if it boots

Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
Did anyone tried that..? I can't try without confirmation.
Sent from my Redmi Pro using Tapatalk

great mate.my props here
exynos 7580??typo mate ?

side said:
great mate.my props here
exynos 7580??typo mate ?
Click to expand...
Click to collapse
Typo? No why?

ashyx said:
Typo? No why?
Click to expand...
Click to collapse
isnt j710fn based on 7870 ? is it my fault ?

That's not for j710fn bro.. Maybe you mean j700f? J710fn is SG J7 2016

side said:
isnt j710fn based on 7870 ? is it my fault ?
Click to expand...
Click to collapse
No different device that is the J7. This is ON8.

Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom

hhaawwkk said:
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom
Click to expand...
Click to collapse
Try 1st if not installs then ill make meta folder for u
But 1st try and install

Guys can we keep it on topic and post rom talk below:
https://forum.xda-developers.com/galaxy-j7/help/samsung-galaxy-8-t3499001

@ashyx It will be great if you can also provide link to stock recovery, or any roll back steps to move to stock recovery.
Thanks in advance.

Link to Stock Recovery

Will the device status be official after rooting? I am worried about the updates.

bnayagrawal said:
Will the device status be official after rooting? I am worried about the updates.
Click to expand...
Click to collapse
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?

ashyx said:
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?
Click to expand...
Click to collapse
Well, that says it all. The only reason i wanted to root is substratum. But got to know that it wont work. And after getting nougat, root will not be required for substratum to work.

Do I need to unlock bootloader before flashing twrp or does odin do it itself? If I need to unlock it, how do I do it?

Related

[RECOVERY]TWRP 3.1.1-0 - Galaxy Core Prime VE (SM-G361H )

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
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.
this will VOID YOUR WARRANTY am not responsible for any damage!
Links
beta 5
https://drive.google.com/file/d/1xRiveHDEM5EcwU8tvU5mpHZDeKbPXIVO/view?usp=sharing
BUGS
otg not working
Current status: BETA
HIT THANK BUTTON IF I HELPED
changelog
Beta-1
* Initial release
Beta-2
*Roms installation failed fixed have some problems but still installing n roms
*some bug fixes
Beta3
*system image backup and flash supoort
*bug fixes
*roms installation fixed
*some new features
Beta 4
*recovery backup and flash issue fixed
*some bugs fixes
beta 5
* MTP fixed
* based on latest vegito kernel
* minor bug fixes
Bugs
*otg
Good job, can we get some screenshots?
FardeenTGO said:
Good job, can we get some screenshots?
Click to expand...
Click to collapse
Yes will upload for now am busy
Sent from my SM-G532F using Tapatalk
Screenshots added
new twrp version coming with system image flash and many new features
new twrp version added
HIT THANK BUTTON IF I HELPED
Does the partition sdcard option work?
FardeenTGO said:
Does the partition sdcard option work?
Click to expand...
Click to collapse
Sorry not tested wait while test for now am busy
Sent from my SM-G532F using Tapatalk
odin flash file added
note: this is not a update just a odin flash file
Waiting
For stable version
Radwan Selo said:
For stable version
Click to expand...
Click to collapse
ok any bug you founded
test recovery
usb otg fixed (if you mounted usb and disconnected to use usb again reboot to recovery again)
screenshots not working
some bug fixes
note : this is test recovery mean not stable not beta only for testing
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0 ?
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.?
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
first its beta version not stable
second typing mistake in file name and in thread name
its twrp 3.1.1-0
and if recovery dont flash roms so why twrp:laugh:
my twrp flashing every rom
only two bugs
mtp(use mount usb instead)
otg
Radwan Selo said:
What do u recommend for flashing los14.1 and root addons and gapps aroma "testing or beta" version?
Or back to 3.0.2-0
Is ur recovery 3.1.0-0 or 3.1.1-0?
BTW thank you.
Click to expand...
Click to collapse
well flash stable lineage 14.1 and pico gapps
Beta 4
Recovery flash and backup issue fixed
Some bugs fixes
Improvements
https://drive.google.com/file/d/0B2BVNSuLC6xFVFZoQjZzdWtRaHc/view?usp=drivesdk
Hit thanks button if I helped
beta 5 twrp
MTP fixed (need confirmation )
based on latest vegito kernel
minor bug fixes
PRESS THANKS IF I HELPED
Closed at OP request

[CLOSED][recovery][unofficial] redwolf recovery 23918

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
* We're 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Features:
Code:
- Password protection
- Flashlight ( not working atm )
- MIUI Incremental OTA Support
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflas
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
Information about this recovery
https://redwolfrecovery.github.io/
Bugs:
data decryption does not work
OTA update dont work will look later in it!
Due to many bugs i need to sort it out why encryption isnt working when patern is set, and why ota dont work.
XDA:DevDB Information
Redwolf Recovery , Tool/Utility for the Xiaomi Poco F1
Contributors
bassbounce, dadi11, atg droid
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Beta Release Date: 2018-09-23
Created 2018-09-23
Last Updated 2018-09-23
Reserved
Screenshots Redwolf recovery
https://imgur.com/a/HG5GyaL
Ooh a new recovery First! What are the differences to plain TWRP?
Cool
trax7 said:
Ooh a new recovery First! What are the differences to plain TWRP?
Click to expand...
Click to collapse
More features than TWRP. Most notable feature: Redwolf can decrypt MIUI OTA. This means that you can download OTA as normal through updater and flash through redwolf recovery. No more downloading of full 1.5gb of roms.
Hi!
Thanks for the project.
Did you succeed to fix the /data decryption using FDE (full-disk encryption)?
PerfectSlayer said:
Hi!
Thanks for the project.
Did you succeed to fix the /data decryption using FDE (full-disk encryption)?
Click to expand...
Click to collapse
Sorry, I don't use encryption, so I don't know if it work.
Waiting for ages
Edit : should we flash force encryption disabler after full rom package installation from twrp or is it ok to enable just dm-verity off
jakir69 said:
Waiting for ages
Edit : should we flash force encryption disabler after full rom package installation from twrp or is it ok to enable just dm-verity off
Click to expand...
Click to collapse
I should be automatically flashed by the recovery itself if enable it inside redwolf.
bassbounce said:
I should be automatically flashed by the recovery itself if enable it inside redwolf.
Click to expand...
Click to collapse
You mean no need to install fde? It should be automatically installed by recovery itself?
Puneeth 676797 said:
You mean no need to install fde? It should be automatically installed by recovery itself?
Click to expand...
Click to collapse
At the moment it seems it dont work u need to it with this zip https://androidfilehost.com/?fid=3700668719832238534
bassbounce said:
Yes, Disable DM-Verity & Forced encryption
Automatic deactivation of the Android Verified Boot and Forced encryption directly during the installation of the ROM.
Click to expand...
Click to collapse
That's cool dude
Woaa.. this is the only recovery of choice on my Redmi Note 4 and now it is available for Poco F1. Awesome!
Failed to install ota
Here are ss and logs
Nice to see REDWOLF TWRP in Pocophone
jakir69 said:
Failed to install ota
Here are ss and logs
Click to expand...
Click to collapse
Thanks,
Did u did this before?
After the correct installation reboot your device in to the recovery.
Now click on icon on the top - section with RedWolf specific settings.
Here find and enable this checkbox: "Support OTA Survival trigger package"
Clean flash some full MIUI ROM and flash whatever you want after that.
Reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
bassbounce said:
Thanks,
Did u did this before?
After the correct installation reboot your device in to the recovery.
Now click on icon on the top - section with RedWolf specific settings.
Here find and enable this checkbox: "Support OTA Survival trigger package"
Clean flash some full MIUI ROM and flash whatever you want after that.
Reboot your device in to the system.
When you get some update just download it using updater app and let it automatically reboot in to the RedWolf
Now everything is done! RedWolf will automatically install it and reboot back to the system!
After that you don't have to flash full ROM anymore.. Just always wait for the update from updater app and let it automatically reboot in to the RedWolf.
Click to expand...
Click to collapse
1. Already rebooted into recovery and also took a nandroid backup
2. Already enabled in redwolf specific settings
3. I will try to flash full rom then update the details
Thanks for reply
Can I install this with official twrp android app? As flashing or booting from ADB reverts to the original miui recovery.
bassbounce said:
Yes, Disable DM-Verity & Forced encryption automatic deactivation of the Android Verified Boot and Forced encryption directly during the installation of the ROM.
Click to expand...
Click to collapse
Thats neat. great job :good:
jimdorky said:
Thats neat. great job :good:
Click to expand...
Click to collapse
This is not working as i am testing now i will lock in to it .

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S8 and S8+ Exynos

{
"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 S8/S8+ Exynos​Only for exynos variants - G950F (Europe, Global Single-SIM); G950FD (Global Dual-SIM); G950N (South Korea); G955F (Europe, Global Single-SIM); G955FD (Global Dual-SIM); G955N (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:
S8 - https://twrp.me/samsung/samsunggalaxys8.html
S8+ - https://twrp.me/samsung/samsunggalaxys8plus.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:
S8 Device tree - https://github.com/TeamWin/android_device_samsung_dreamlte
S8+ Device tree - https://github.com/TeamWin/android_device_samsung_dream2lte
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.
Finally no more noobs telling you that quota causes encryption.
I assume that we will going to get 3.2.3.1 soon? No eta just curious ? Twrp on the server is from July...
And finally we get official with proper support??
Big thx
Many thanks
Thanks @corsicanu
Official builds are up!
Regards.
Sent from my SM-N950F using Tapatalk
S8 plus cannot mount usb otg 3.2.3.1 pls help
Iyaadali said:
S8 plus cannot mount usb otg 3.2.3.1 pls help
Click to expand...
Click to collapse
I'm looking into it. Thanks for reporting.
Sent from my SM-N950F using Tapatalk
OTG fix was only required for N8 devices as first time introduced by Tkkg1994, while the official device tree by Jesec had working OTG for dream(2). Moreover the features list says this TWRP is based on latest TWRP source, but the recovery is based on 7.1.2.
Noxxxious said:
OTG fix was only required for N8 devices as first time introduced by Tkkg1994, while the official device tree by Jesec had working OTG for dream(2). Moreover the features list says this TWRP is based on latest TWRP source, but the recovery is based on 7.1.2.
Click to expand...
Click to collapse
My bad that i didn't tested otg on s8 assuming that if it works on note8, it works on s8* too. I submitted a patch in review and will test it myself today as i don't have the otg dongle right now.
As for twrp source, yes it's 7.1, will edit OP if this causes troubles. I don't want to argue with anyone, i only made things official as you know the quota issues, not to mention all the flame from telegram regarding "use official even if it doesn't properly work".
Peace.
Sent from my SM-N950F using Tapatalk
corsicanu said:
My bad that i didn't tested otg on s8 assuming that if it works on note8, it works on s8* too. I submitted a patch in review and will test it myself today as i don't have the otg dongle right now.
As for twrp source, yes it's 7.1, will edit OP if this causes troubles. I don't want to argue with anyone, i only made things official as you know the quota issues, not to mention all the flame from telegram regarding "use official even if it doesn't properly work".
Peace.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
:laugh::good:
Just use the same otg path as from jesecs device tree. I can confirm it works as I am still using his TWRP and tried it yesterday.
Good job bro after testing your last beta file seems that otg its fixed on S8 thanks again brother
Hi, USB OTG option is not working in S8+ SM-G955FD
I flashed latest TWRP 3.2.3.2 but I cant mount /data partition on stock rom:
"Could not mount /data and unable to find crypto header"
Is this fixable - or
Is there a way to access /data without flashing no-dm-verity.zip? (e.g. systemless root or dump userdata img and mount on PC?)
TearsDontFalls said:
I flashed latest TWRP 3.2.3.2 but I cant mount /data partition on stock rom:
"Could not mount /data and unable to find crypto header"
Is this fixable - or
Is there a way to access /data without flashing no-dm-verity.zip? (e.g. systemless root or dump userdata img and mount on PC?)
Click to expand...
Click to collapse
I'm pretty sure you have data encrypted. You can only access it in the running rom. If you can't boot as you are now, flash no-verity-opt-encrypt and you can boot with that, even if encrypted. Boot up stock rom, use titanium or any other solution to backup your data and after that you can format data, boot unencrypted and restore the backups.
As for userdata dump, even if you dump it you can't decrypt it, also systemless root can't decrypt it either.
Sent from my SM-N950F using Tapatalk
corsicanu said:
I'm pretty sure you have data encrypted. You can only access it in the running rom. If you can't boot as you are now, flash no-verity-opt-encrypt and you can boot with that, even if encrypted. Boot up stock rom, use titanium or any other solution to backup your data and after that you can format data, boot unencrypted and restore the backups.
As for userdata dump, even if you dump it you can't decrypt it, also systemless root can't decrypt it either.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Right now I'm on stock(non-rooted, stock kernel) with the default encryption.
So I can just:
1. flash no-verity-opt-encrypt.zip
2. flash Magisk or SuperSU
3. Boot and have root with my encrypted data partition?
Thanks for fast answer btw
Edit; tried that, its booting, but now getting integrity verification failed screen. Even after flashing stock. So I guess I tripped some trusted execution environment and key is gone now.
I have one question to / problem with the encryption:
installed latest TWRP
flashed no-verity-opt-encrypt.zip in order being able to boot
formatted data
Everything works smoothly and as expected. BUT: How do I get the encryption (my company requires that) back now?
Out of the system I can select encrypt data, which is displaying 'Encrypting'. But after the automatic re-boot data is still not encrypted...
Am I missing something?
Phone keeps rebooting into "Galaxy S8" Welcome screen
Hi,
I have followed the process on my G950F but the phone keeps rebooting in a 10 second cycle into the welcome screen. Any ideas?
I am using Odin v3.13.1 and trying to load twrp-3.2.3-2-dreamlte.
I have enabled OEM unlock and it shows OEM LOCK: OFF in Download mode
I can successfully flash TWRP, wipe the DATA partition and transfer and install twrp-3.2.3-2-dreamlte.img. However, once I hit "reboot device" it keeps cycling into this welcome page.
Any ideas? I have tried going back to the official firmware and flashing twrp-3.2.3-1-dreamlte.img but the same happens. Is there anything I am missing?
EDIT: Solved by installing the no-verity-opt-encrypt-6.0.zip with TWRP

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Note: My TWRP builds are free I take no money or selling them, The new builds support US devices unlocked before 9 november or added upon request.
Supported Models:
Galaxy S20 Ultra G9880, G988N, G988U, G988U1 and G988W.
Galaxy S20 plus G9860, G986N, G986U, G986U1 and G986W.
Galaxy S20 G9810, G981N, G981U, G981U1 and G981W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S20: x1q, S20+: y2q or S20 Ultra z3q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@jesec for kernel source and unlock guide
@ianmacd for multidisabler
@sac23 and @elliwigy for testing on S20 Ultra G988U and G986U
Sources:
Kernel tree
Device Tree:
x1q
y2q
z3q
Changelog:
02.06.2022 - Update to Android 12 kernel source
- Fix mount issues
- Update to TWRP 3.6.2
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
03.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
12.12.2020 - Update TWRP to 3.5.0
12.12.2020 - R build: Initial release for android 11.0.
12.12.2020 - Q build: Update to latest TWRP source
- Fix fastbootd.
15.11.2020 - Add TWRP fastbootd support
- Clean up fstab
- Move kernel to gz format.
24.09.2020 - Update prebuilt kernel and dtb's for more dynamic partitions compatibility.
15.09.2020 - Update to latest TWRP source with more dynamic partitions support.
03.09.2020 - Initial Release.
Pardon my ignorance but the g9860 s20+ snapdragon is it supported by this recovery?
fastmix said:
Pardon my ignorance but the g9860 s20+ snapdragon is it supported by this recovery?
Click to expand...
Click to collapse
Sure use y2q build
And if you downloaded multidisabler Im working on updated one
Great to see twrp recovery for snapdragon....hopefully some custom rom development in the future.[emoji106]
Verstuurd vanaf mijn SM-G9860 met Tapatalk
[email protected] said:
Great to see twrp recovery for snapdragon....hopefully some custom rom development in the future.[emoji106]
Verstuurd vanaf mijn SM-G9860 met Tapatalk
Click to expand...
Click to collapse
oh its comming
Finally [emoji7]
Sent from my SM-G9810 using Tapatalk
Do I need to root the device as guided by Jesec in his thread or only unlock the bootloader. Will installing this recovery will auto provide root ?
jsbutran said:
Do I need to root the device as guided by Jesec in his thread or only unlock the bootloader. Will installing this recovery will auto provide root ?
Click to expand...
Click to collapse
The unlock is to allow flashing custom recovery, and no root inside you need to flash magisk to get root.
Works on sm-g9810 s20?
I followed the steps but always get bootup in Android Recovery. Im on g988n snapdragon. Please guide. I have done OEM unlocking. Disabled AVB and flashed recovery. but try to boot in recovery I get into Android recovery. What I'm doing wrong
jucin said:
Works on sm-g9810 s20?
Click to expand...
Click to collapse
you can be the first tester on regular s20.
jsbutran said:
I followed the steps but always get bootup in Android Recovery. Im on g988n snapdragon. Please guide. I have done OEM unlocking. Disabled AVB and flashed recovery. but try to boot in recovery I get into Android recovery. What I'm doing wrong
Click to expand...
Click to collapse
worked fine on G988U, you need to be stock for disabling AVB then wipe and go back to download mode and flash TWRP
I assume this will work on G988U1 too?
ismoore said:
I assume this will work on G988U1 too?
Click to expand...
Click to collapse
If you unlocked your bootloader why not!
afaneh92 said:
If you unlocked your bootloader why not!
Click to expand...
Click to collapse
The bootloader can't be unlocked on the U and U1 models.
afaneh92 said:
Sure use y2q build
And if you downloaded multidisabler Im working on updated one
Click to expand...
Click to collapse
Where is the multidisabler file located? I'm wanting to try this on my US Snapdragon S20+! ?
ismoore said:
The bootloader can't be unlocked on the U and U1 models.
Click to expand...
Click to collapse
Not true pm me for details
ismoore said:
The bootloader can't be unlocked on the U and U1 models.
Click to expand...
Click to collapse
I have unlocked S10 G973U. PM me or join telegram group for more info.
sabrdawg said:
Where is the multidisabler file located? I'm wanting to try this on my US Snapdragon S20+! ?
Click to expand...
Click to collapse
Multidisabler zip cant decrypte for now, super partition vendor are read only and cant modify fstab.qcom, will be fixed later.
The only way is to push edited fstab.qcom to vendor via adb or root manager.
Will add a guide tomorrow.
Theres a file at /system/recovery-from-boot.p or something rather he probably needs to remove else it will overwrite the custom recovery with other one.
afaneh92 said:
you can be the first tester on regular s20.
worked fine on G988U, you need to be stock for disabling AVB then wipe and go back to download mode and flash TWRP
Click to expand...
Click to collapse
jsbutran said:
I followed the steps but always get bootup in Android Recovery. Im on g988n snapdragon. Please guide. I have done OEM unlocking. Disabled AVB and flashed recovery. but try to boot in recovery I get into Android recovery. What I'm doing wrong
Click to expand...
Click to collapse
Same problem here. G9860.

[RECOVERY][SHARED][SURYA/KARNA][R11-0_5] Orange Fox Recovery Project by ManoloRey [UNOFFICIAL]

{
"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"
}
Orange Fox Recovery Project is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Devs are 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 them for messing up your device, they will laugh at you.
*
*/
Features:
Synced with the latest Teamwin changes
Designed with latest Material design 2 guidelines
Implemented support for Flyme and MIUI OTA, and incremental block-based OTA in custom ROMs
Included customization
Inbuilt patches, like Magisk and password reset patch
Password protection
Fully open-source
and more
Bugs:
- files sorting is not remembered between reboots (it seems this depends on the MIUI base used, I just found out that on 12.0.7 this works, but not on 12.0.8)
Screenshots:
Click to expand...
Click to collapse
Changelog - current version:
-----------------------------------
OFOX R11-0_5
md5: 28094aef3c3c8b4ed99810991aecadc6
-----------------------------------
• Sync with latest OrangeFox source
• Added zip encryption-disabler-v1 on modules ofox (Menu/Fox Addons/Other)
• Fixed version number Ofox
• Fixes minor bugs that appear in the previous release
DOWNLOAD - HERE
(also for older versions): BOX
or see attached files
Changelog - older versions:
Spoiler
-----------------------------------
OrangeFox-R11-Unofficial-Beta-surya-10-01
md5: 6e35f2aedc8a11621bd490dec12dc6db
-----------------------------------
• Fix Vibration
• Rework Fastbootd and Adb Sideload code
• Use USB configs from MIUI
• Remove predefined services
-----------------------------------
OrangeFox-R11.0_0_B004-Beta
md5: cb6ffb8710e2a31e68bf8345d1c5d6a9
-----------------------------------
• Fix ADB sideload
• Fix Fastbootd (It's in the reboot menu - "fastboot")
• Decryption works 100% now (Even with PIN or password and Android 11)
How to flash the OFOX:
- via fastboot
Code:
fastboot flash recovery recovery.img
Next reboot in OFOX manually or using a fastboot command.
Code:
fastboot boot recovery.img
REMEMBER: it is important that from fastboot you directly reboot into OFOX recovery or the OFOX will be overwritten.
- via custom recovery:
Code:
flash zip file (see attached file) in recovery
Credits:
- Thanks to TeamWin devs
- Thanks to Orange Fox Recovery Project devs
- Thanks to @MrYacha and @DarthJabba9 - Source Development
- Thanks to @ManoloRey - DONATE
Thanks for the work!
What is the difference with the rest orangefox recoveries?
ManoloRey builds are noticeably faster at startup than Brigudavs, also naming of internal storage is different, also name of backup folder differ. Other needs to be tested, now you can choose between two excellent devs/products and if you feel for it, you can compare which one suits you better...
Thx @jeryll for your help !!! Trying this evening...
Thanks @jeryll for presenting this new variant of OrangeFox.
Is it safe to switch between the different OrangeFox variants?
If you don't use backup restore function, then it is safe to switch between them, otherwise you need move your backups to a proper location so that specific recovery can see them:
ManoloReys OFOX use
/Fox/BACKUPS/insert_your_number_here/folders_with_your_backup(s)
Brigudavs OFOX use
/Fox/BACKUPS/POCO_X3/folders_with_your_backup(s)
Thank you for the swift response! I'm only using TitaniumBackup so I should be safe
Can decrypt after install if coming from a twrp mauronofrio version?
Thanks
jorgeepelos said:
Can decrypt after install if coming from a twrp mauronofrio version?
Thanks
Click to expand...
Click to collapse
probably yes, but I never used mauronofrios TWRP, so IDK
jeryll said:
If you don't use backup restore function, then it is safe to switch between them, [....]
Click to expand...
Click to collapse
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Do you know if there are plans to make OFox for surya an official version?
just Nob said:
I.e. the problem of dynamic position handling is solved and a full system backup/restore is now supported?
Click to expand...
Click to collapse
- AFAIK the problem of dynamic position handling is not solved (yet)
- full system backup/restore is now supported (if certain conditions are met) more about it - HERE
just Nob said:
Do you know if there are plans to make OFox for surya an official version?
Click to expand...
Click to collapse
AFAIK only two people can answer that ManoloRey or brigudav, they are kindly providing OFOX builds for POCO X3
Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?
Master One said:
Damned, totally overlooked that you started a new thread @jeryll
So OrangeFox-R11.0_5-Unofficial-surya is indeed a newer version than @brigudav's OrangeFox-R11.0_1.0-A10-Beta-surya?
With ArrowOS 11 just having moved to OSS vendor, people are reporting problems with decryption in recovery.
Can the current OFOX deal with device decryption on a real A11 base + OSS vendor or does it require an update to OFOX?
Click to expand...
Click to collapse
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.
SkaboXD said:
OFox is indeed older & It won't probably work with A11 OSS encryption, but you can find & try newer TWRP version by brigudav which dates from 3.5.2021. It's on 4pda. I would share download link, but brigudav doesn't allow it.
Click to expand...
Click to collapse
I thought @brigudav is maintaining both OrangeFox and TWRP?
So no new version of OrangeFox that supports A11 OSS decryption yet?
I've just downloaded twrp-3.5.2_10-1-surya.img dated with 20210503, but I already got used to OrangeFox, which just looks nicer, has the proper keyboard for PIN entry and the simplified view for OTA updates.
Can you or someone else confirm that twrp-3.5.2_10-1-surya.img is indeed the correct and newest version supporting A11 OSS decryption?
No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.
syl0n said:
No it doesn't work. There is no recovery available right now that supports OSS vendor rom decryption. Go back to MIUI vendor roms if you need it.
Click to expand...
Click to collapse
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
EDIT : there's a new version by Brigudav... maybe ?!
PYCON said:
Even if with MIUI Vendor there's no way to access to internal storage if it's related to an Android 11 rom. Neither with the latest TWRP release by Brigudav. I see only weird folders / files names.
Click to expand...
Click to collapse
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here
metaxda said:
I, too, saw "weird" folders / filenames,
but eventually I was able to access the internal storage, via TWRP
(ie. read the files unencrypted).
This is not recommended, because it weaken's the phone security,
but you can read some steps --> here
Click to expand...
Click to collapse
I don't understand what some users mean with "no security at all"...
Running Android 10 for example, even if your device is encrypted, if u have a TXT in the internal storage with your bank user / password, it's sufficient to reboot into recovery ( or turn on the device into the recovery pressing VOL + ) and... et voilà. The TXT is here. Encryption of course but perfectly readable.
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents
PYCON said:
So the difference? From that situation to a device with Android 11 and a decrypted internal memory... I can see no differences...
My 2 cents
Click to expand...
Click to collapse
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.
metaxda said:
If phone has Android 11 with OSS Vendor ROMs (or MiUI ROM),
then the TWRP does not show files from internal storage,
ie. all files show like this
Even if encryption is turned off (or no lockscreen/PIN/pattern),
the files/folders cannot be decrypted by TWRP.
Click to expand...
Click to collapse
So basically, it seems that Android 11 is more "secure" than Android 10, speaking only about recovery accessing memory... right ?

Categories

Resources