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?
Related
I do not own the device anymore. So I can't support the thread anymore, if anyone wants to carry on just pm me. But as far as I know there are newer threads about this topic. Thank you
Hey there,
I decided to write a how-to on gaining root for the g531f Galaxy grand prime ve.
This should work for all grand prime devices based on marvel soc.
About this method:
Knox counter was not tripped for my device using this method.
The main steps, flashing latest stock and twrp, are perfomed by Odin. To gain root chainfire's supersu is flashed with twrp. If you are unsure about any step there are enough guides found on xda refering odin, twrp and supersu.
So let's get started.
I`M NOT RESPONSIBLE FOR ANY DAMAGE OR WARANTY LOST ON YOUR PHONE.
1. Make sure your device drivers is installed properly
2. Get Odin v3.09 for example here:
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
3. Get your latest firmware and extract it once
http://www.sammobile.com/firmwares/database/SM-G531F/
4. Get twrp
https://dl.twrp.me/grandprimevelte/twrp-2.8.7.1-grandprimevelte.img.tar.html
5. Get supersu by chainfire
Latest beta
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or confirmed working version 5.52 beta, if the latest doesn't work thanks to @XelSam:
https://download.chainfire.eu/743/Su...erSU-v2.52.zip
6. Backup all things you need and copy supersu to external sd card
7. Boot to stock recovery and perform a factory reset and wipe internal memory.
(power off device and keep holding volume up, home and power button)
8. Reboot to download Mode, then start odin and connect your device
(holding volume down, home and power button to get into download Mode)
9. Flash your firmware with Odin by using the AP button and hit start. Make sure repartition is NOT selected and untick auto reboot. This step takes some time
10. Boot to download Mode again. And flash twrp as mentioned above. Using AP and the same selection.
--if twrp doesn't boot you have to use another firmware (step 9) post #20-- thanks to @bluepower
11. Boot into twrp recovery. Hit install and select the supersu zip file then clean cache and dalvic.
(holding volume up, home and power button)
12. Reboot your phone and see if everything is working.
13. Go to dev settings and tick "manufacturer unlock" to prevent fap lock.
(unlock dev settings: Settings - about phone - tap build number 7 times). If that doesn't work check post #4 and #6 and say thx to @hck5
14. Make a nandroid in twrp recovery to have a clean rooted rom to return to if anything gets messed up with further modding (eg. xposed framework etc.)
10.1 100%Working firmware
If you can't find a version that allows to flash twrp (carrier lock) use this unbranded one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
Check gps. If it doesn't lock install this app and configure your region.
https://play.google.com/store/apps/details?id=by.zatta.agps
CREDITS and CUDOS
chainfire
Twrp team
Odin team
Samsung
If you are interested in xposed check wanams xposed thread.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
The x86 version is working fine for me
For audio enhancement I'm using dolby atmos cause Viper didn't do the trick for me.
http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
So have fun with your unchained device and hit thanks button.
Great job!
Hey there i have the same model and i'm happy that last night i've found your post
i used the pre-rooted firmware and i had the system ui rebooting problem after i uninstalled any of the apps
also i've seen guys who had that security tab problem from settings (didn't happened to me)
I am extracting the stock rom now i prepared everything
i also wanted so badly the viper fx cause the sound is pretty low
i searched for alternative but here you are with dolby atmos
i greatly thank you for the effort for posting this tuto
i will be back after i do the job!
Thanks!!!
---------- Post added at 12:46 PM ---------- Previous post was at 12:25 PM ----------
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
hck5 said:
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
Click to expand...
Click to collapse
Thx for your feedback and confirmation that it is working.
So have fun with your device.
BTW don't forget to make a nandroid backup before you mess around with xposed modules to get back to your rooted rom. I destroyed my system twice with xposed.... And I had to go through this procedure again (thanks touchwiz).
okay
ok. thanks for the advice i was just messing with the modules and i have no backup xD
there is a pic with all i have so far
{
"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"
}
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
and this is the ultimate fix
"i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable" thanks to bhavstech xda member
hck5 said:
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
Click to expand...
Click to collapse
Try to unlock via dev settings. Manufacturer unlock.
http://forum.xda-developers.com/attachment.php?attachmentid=3495074&d=1443947143
If that doesn't work you have to delete your Google account as far as I know.
For me it is working with Google account, but I can't remember if I ticked the dev setting option before or after adding my Google account.
for me has been this one
klausel said:
5. Get supersu by chainfire
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
eau4x6 said:
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
Click to expand...
Click to collapse
I don't know exactly what you mean with sideloading app.
But as far as I know root is needed to install supersu via Google play store. Of course you can sideload the app via adb shell when booted to twrp. But I wanted to keep the tutorial simple without setting up adb etc.
Hope your question is answered.
Thank's for recovery
I thing a new nice rom will coming soon for 531F
klausel said:
Of course you can sideload the app via adb shell when booted to twrp.
Click to expand...
Click to collapse
Transfering APK to internal storage/sd card and installing from there (by opening it in file manager) is what I had in mind.
I don't think is that easy.. You must set system read and write and I guess twrp helps it installing supers in a better way than your file manager does
---------- Post added at 12:49 PM ---------- Previous post was at 12:45 PM ----------
We just need a hell of a rom
finally thank you very much! ?
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
bluepower said:
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
Click to expand...
Click to collapse
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
klausel said:
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
Click to expand...
Click to collapse
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
bluepower said:
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
Click to expand...
Click to collapse
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
bluepower said:
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
Click to expand...
Click to collapse
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
klausel said:
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
Click to expand...
Click to collapse
I'm back. Thanks. I'm going to try now.
Edit: Ok, done.
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
bluepower said:
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
Click to expand...
Click to collapse
Glad to know you got it and thanks for your feedback.
To rule out all misunderstandings and help other people with the same problem.
1. You flashed a rom from another carrier for your region and 2. updated it to the latest version via ota.
3. You installed twrp and 4. supersu
Is that the way you proceeded.?
Did the line for fap lock appear in dl mode?
Thanks in advance
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.
Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: BETA.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source (kernel AQC4)
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
Micro SD card >> Not working.
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
IT'S ADVISABLE TO BACK UP ANY PERSONAL FILES.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
ashyx said:
Unofficial release -TWRP recovery for the Samsung Galaxy J7 Prime SM-G610F/DS - Exynos 7870 Octa. Should also work for the SM-G610M/Y
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: ALPHA(Untested)
I don't own this device so this build is currently untested. It may boot, it may not. If there are issues I would appreciate proper details and if possible the recovery log which can be found under ADVANCED/SAVE LOG.
I always advise having the stock firmware to hand just in case.
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
twrp_3.1.1-1_sm-g610f_5617
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Click to expand...
Click to collapse
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
gean vilharva said:
No meu j7 prime G610F twrp v3.1.1.1 não funcionou travou fiz tudo Serto mas mesmo assim não funcionou
Sent from my SM-G610F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Please don't quote the entire OP.
I don't speask Portuguese, but from what I can make out you are saying TWRP doesn't boot?
Can I ask which firmware build your device is on? You should be on at least AQC4.
Can you try this version?
https://www.androidfilehost.com/?fid=673368273298961224
.
tried this touch is not working
Ephesis said:
tried this touch is not working
Click to expand...
Click to collapse
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Touch is not working
Can you tell me which version is working, the one in the OP or the one above. I will fix the touch.
Click to expand...
Click to collapse
both is working on me but the touch on both is not working.
Ephesis said:
both is working on me but the touch on both is not working.
Click to expand...
Click to collapse
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
ashyx said:
Ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can I ask your firmware version your device is running?
Click to expand...
Click to collapse
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
ah right so the guy in the first post was complaining about touch not that it didn't boot.
Can i ask your firmware version your device is running?
Click to expand...
Click to collapse
j7-g610f
g610fddu1api9
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
The kernel is based on AQC4, so I'm guessing this could be the issue?
Wonder if anyone using AQC4 firmware could confirm?
Ephesis said:
j7-g610f
g610fddu1api9
Click to expand...
Click to collapse
havananyx said:
Google Translate TR> ENG
______________________
Hello there.
The touch does not work when I load TWRP with ODIN. TWRP stays on the first screen.
I can not assign a screen image because the message can not count. I sent the information with a private message that you did not want. I hope it helps.
Good luck with. Good work.
Click to expand...
Click to collapse
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
Touch is working bro thank you. awsome work
ashyx said:
Hopefully this fixes the touch issue: https://www.androidfilehost.com/?fid=961840155545571773
.
Click to expand...
Click to collapse
The Touch issue is fixed but the sd card mount bug is still there ..!
jagopk said:
The Touch issue is fixed but the sd card mount bug is still there ..!
Click to expand...
Click to collapse
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
ashyx said:
I intend to fix that.
Can you do me a favour? Could you install DISKINFO from play store. Open the app then tap SDCARD. Could you post a screen shot making sure I can see PARTITION NAME and DEVICE.
Thanks.
Click to expand...
Click to collapse
Sent from my SM-G610F using XDA Labs
@ashyx Thought I'm not rooted. But I can help u with this kind of things
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
Sent from my SM-G610F using XDA Labs
Click to expand...
Click to collapse
Many thanks for that! Even though you are not using it you're the only one willing to assist.
Anyway based on your post I have made some changes. Could someone test this out and see if it fixes the SDcard mounting issue?
https://www.androidfilehost.com/?fid=961840155545572469
.
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Sent from my SM-G610F using XDA Labs
Elanza_48 said:
@ashyx Do one need to flash SuperSU if he flashes the dm variety and encryption disabled patched kernel ??
Click to expand...
Click to collapse
No need to flash supersu unless you wish to root.
Which kernel are you referring to? There is no need to flash any kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note8 ExynosOnly for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly
{
"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"
}
After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released last May, allowing me to build a custom kernel with many of the problematic Knox security features disabled. What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source (T510XXU5CWA1).
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.tar.md5
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.img
Build archives:
Android File Host
Change Log:
v3.7.0_11-0 (20230330):
Updated to T510XXU5CWA1 OEM stock kernel.
v3.7.0_11-0 (20221102):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
v3.6.2_11-0 (20220905):
Updated to TWRP 3.6.2 release built from AOSP-11 branch.
Updated to T510XXU5CVG2 OEM stock kernel.
v3.6.1_11-1:
Minor update to incorporate fix from TWRP repo.
v3.6.1_11-0:
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T510XXU5CVB1 OEM stock kernel.
v3.6.0_11-2:
Updated to T510XXU5CUL1 posted kernel source.
v3.6.0_11-1:
Updated to T510XXU5CUJ1 posted kernel source.
Updated to TWRP 3.6.0 release built from aosp-11 branch.
v3.5.2_9-0:
Updated to T510XXU5CUF4 posted kernel source.
v3.5.2_9-0:
Updated to TWRP 3.5.2 release built from omni-9.0 branch.
v3.5.1_9-0:
Updated to T510XXU4BUA1 posted kernel source.
Updated to TWRP 3.5.1 release built from omni-9.0 branch.
v3.5.0_9-0:
Updated to T510XXU3BTK1 posted kernel source.
Updated to TWRP 3.5.0 release built from omni-9.0 branch.
v3.4.0-0:
Updated to TWRP v3.4.0 source
Updated to latest custom kernel
v3.3.1-7:
Updated to latest custom kernel
v3.3.1-6:
Switched to .img file for installation from TWRP
v3.3.1-5:
Fixed hang on splash with encrypted user data partition
Added OTA update (.zip) for installation from TWRP
v3.3.1-4:
Fixed MTP support in a way that supports Magisk
v3.3.1-3:
Fixed MTP support
Included boot image with custom kernel
Deprecated separate NoKnox releases
v3.3.1-2:
Changed system partition mount point to /system_root
Fixed screen brightness control
Restored screen timeout
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Donations:
Your support is always appreciated! Just click here.
Good work. Well done.
Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
If this is untrue, please let me know and I'll remove this post asap.
Also let me know if you need any (debug) info.
beta990 said:
Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
Click to expand...
Click to collapse
NoKnox above will patch the T510XXU1ASC7 OEM firmware with the custom kernel and includes the vendor partition fixes in @ianmacd's Multi-disabler. Booting to recovery each time is only required with the Magisk root, which patches itself into recovery (TWRP or stock). More details on @ianmacd's post here.
Thanks for this! I successfully flashed NoKnox, TWRP and Magisk last night and all is working well! @PiCkLeS posted some helpful instructions here for those needing some extra help. Follow the instructions in this thread, but replace the last step with flashing your Magisk-patched TWRP image. No need to mess with running magisk on the stock AP file, you can just modify the TWRP recovery.img.
Magendanz said:
[*]Ensure you're running the T510XXU1ASC7 release
Click to expand...
Click to collapse
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
3c said:
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
Click to expand...
Click to collapse
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
Magendanz said:
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
Click to expand...
Click to collapse
Thanks, downgrading from ASCE worked very well, had to change OEM unlock in dev settings again though (with the date trick).
@Magendanz, l'm willing to test twrp for the 515 model. Dm me ?
I did a backup and did a restore but it kept bootlooping idk if this was because i rooted it first or what..
They released the latest kernel
Awesomeslayerg said:
They released the latest kernel
Click to expand...
Click to collapse
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).
Magendanz said:
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).
Click to expand...
Click to collapse
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
regards
edit: ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
messi2050 said:
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
Click to expand...
Click to collapse
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
messi2050 said:
ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
Click to expand...
Click to collapse
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
Magendanz said:
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
Click to expand...
Click to collapse
Been trying for a week now, still it bootloop at every attempt to enter twrp according to the testers.. not sure what's wrong, I'm building using twrp minimal source also custom kernel works good on stock rom so no idea where is the problem
Are there any release for SM-T515?
b2574028 said:
Are there any release for SM-T515?
Click to expand...
Click to collapse
I have a volunteer to test it, but I was waiting for Samsung to post kernel source for the May 2019 update (T515XXU1ASEH).
'Only official released binaries are allowed to be flashed'
Thank you for this great work. I ended up getting the 'Only official released binaries are allowed to be flashed' at booting after flashing:
- NoKnox-T510XXU1ASEF.tar
- twrp-3.3.1-1-gta3xlwifi.tar
After the flash, the tablet successfully booted into new factory status OS. Once the intial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?
Thank you very much in advance.
redexit said:
After the flash, the tablet successfully booted into new factory status OS. Once the initial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?.
Click to expand...
Click to collapse
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
Thank you!
Magendanz said:
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
Click to expand...
Click to collapse
Whoa, thank you so much for your quick and thorough reply!
I will do what you instructed after another 7 days I guess, (assuming there is no way to get around with this one).
Again I truly appreciate your contribution and hard work.