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
Related
Team Win Recovery Project 3.0.2-0
This is for the SM-P580 (gtanotexlwifi) and SM-P585, SM-P585N0, SM-P585M, SM-P585Y (gtanotexllte) Exynos models only! Do not flash on other models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Tab A 10.1 (2016) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
WiFi version: http://teamw.in/devices/samsunggalaxytaba101wifi2016spen.html
LTE version: http://teamw.in/devices/samsunggalaxytaba101lte2016spen.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://build.nethunter.com.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gtanotexlwifi (WiFi) or gtanotexllte (LTE).
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
--- or (not both) ---
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (WiFi): https://github.com/TeamWin/android_device_samsung_gtanotexlwifi (android-6.0)
Device tree (LTE): https://github.com/TeamWin/android_device_samsung_gtanotexllte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
It's possible to use this metod with T585 ?
Working very well on my tab A 10.1 P585Y.. bug.. cant read internal storage but it can use sd card..
I already root my tab a 10.1 p585y using this twrp.. thanks for making this recovery for our p585y.. now we need custom rom such as resurrection remix..
Worked well
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
loraxnope said:
Is there a link to the firmware for the device (SM-P580)? Rooting it and installing TWRP all went well while following the directions, but using App2SD to fix some system apps caused a "Verification Failed" error. Stupid mistake... now I gotta reinstall the ROM, but I can't find it anywhere.
Click to expand...
Click to collapse
Im using p585y version.. same here i didnt find any firmware on internet.. so my solution is using kies.. just install kies and recover it.. work for me.. right now sammobile also doesnt have the firmware yet..
Hope im helping.. press thanks if im help..
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
Will try it bro.. right now im using s7 mod on p585y but doesnt show on settings>storage but it seem working background..
focus-pocus said:
Anyone tried installing "adoptable storage fix" from Tab S2 forum (see link below)?
http://forum.xda-developers.com/tab-s2/general/patch-adoptable-storage-enabler-t3460521/post68658862
Click to expand...
Click to collapse
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
cliemonster said:
Followed the instructions carefully and I'm now rooted! The swipe bar in TWRP seemed to have a little problem. When I first swiped it didn't stick and floated back over to the left side. I tried with my finger several times and then with the spen. It finally registered. It did the same swiping to install SuperSU. Not sure if it just was slow in registering the swipe or something with my system. I was a little nervous when I rebooted but all seems to be well. Thanks for the guide!
Click to expand...
Click to collapse
It is not your system - I had the same issue with the swipe bar. Like you, I tried several times and it finally accepted the swipe (even the pen had a few non-registering swipes).
Hi, can you plz update the links. Cuz idlekernel.com is currently not reachable nor the page of your source code for kernels :-/
And I remain highly unclear if I need a kernel for this dm-verity thing or not. I don't understand the issue reg. system boot partion. What is this? Android is already installed on the TabA - so what should I change there? Or is it for root apps?
If you want to root your tab and install TWRP you need the Kernal to turn off dm-verify and encryption. Do it in the exact order in the OP and don't let your tab try to boot rooted without turning off dm-verify.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
I think you'll find it does. Works on pretty much any Samsung device running Marshmallow.
BohArie said:
So sorry this mod doesnt work for our Tab A series, look like samsung has made weird app to read our storage capacity..
Click to expand...
Click to collapse
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
focus-pocus said:
Yeah, that's what I expected. But this mod also replaces sm binary, so I suspect that this should enable converting to adoptable storage through adb shell (so-called S7 trick). Have you tried that?
Click to expand...
Click to collapse
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
BohArie said:
ive done that.. still not working.. by the way.. i already root my devices when i delete some apps, fb, skypes and any apps that need account force close.. why is that??
Click to expand...
Click to collapse
Restore your stock boot image. Apply the patch. Format your SD card as portable storage, reboot.
Look out in status bar for an SD card notification.
If you don't see it go to settings>storage. Tap the SD card choose format then internal.
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
BohArie said:
thanks.. working well but it say that i already use 91% of my storage.. now i just need to install app.. im using enable adoptable storage zip then i put command using adb..
Click to expand...
Click to collapse
Take that with a pinch of salt. Make sure you migrate your data to the sdcard.
focus-pocus said:
I haven't found a good stock ROM yet (proper US version). No way I'm rooting my tablet before that.
My current tablet is untouched (in terms of custom recovery and ROMs). Is there a way of pulling out a stock ROM from it?
Click to expand...
Click to collapse
Could you tell me what your baseband version / build number is? I might try flashing one of the other region's ROMs since there's a few from Hong Kong, Turkey, etc out on Updato
soft bricked device,
i soft bricked my device trying to do the TWRP recovery and it kept saying unable to mount data so i factory reset and it still didnt work so then i wiped a bunch of stuff and now it's soft bricked.
im going to download the Korean Firmware for this device, but is there anyway i can avoid that? any tips?
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
TWRP-3.1.1-0 for the SM-T285 is now available, you should hop on to this thread for more information.
Update 01/17/2017
==============
TWRP with F2FS support here. Use only if you plan to use the F2FS enabled CM13 builds for the SM-T285.
Update 11/24/2016
==============
* MTP should now be fixed
Installation Instructions
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.0.2-1_SM-T285_20161124.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
enjoy!
jedld said:
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
For the installation instructions, should be the same with the SM-T280 in this thread http://forum.xda-developers.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-a6-sm-t280-t3475381
enjoy!
Click to expand...
Click to collapse
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Thanks
I rooted my device (Glaxy Tab a 7" T285)by your method and files.
Next day i saw my device was off ,i pressed power but it could not boot and show this:
Code:
custom binary blocked by frp lock
Afterward i tried to go recovery by pressing Home+Power+volum up but it could not go recovery and show me:
Code:
custom binary blocked by frp lock
Recovery is not Seandroid Enforcing
Therefor my device had been useless.
so I go to download by odin and install a stock ROM.
I search and saw 2 advises:
1)this problem occur if androd version is 5.1.1
2) this problem occur if in developer menu OEM Unlock Option is disabled.
IS THIS ADVISES TRUE? OR THAT PROBLEM HAS OTHER REASON?
I went dev menu and enabled OEM and afterward i did ROOT again.
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
2) How do i unroot my device?
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
Click to expand...
Click to collapse
If you install a new rom, then yes you have to factory reset. If it is just to install TWRP I don't think you need to do that.
2) How do i unroot my device?
Click to expand...
Click to collapse
Easiest way is to just flash stock again
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
acornkenya said:
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Click to expand...
Click to collapse
MTP should now be fixed with the latest release.
jedld said:
MTP should now be fixed with the latest release.
Click to expand...
Click to collapse
MTP is now working like a charm; thank you
Adam Hui said:
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
Click to expand...
Click to collapse
Pls help subinary files not installed superSU v2.78.SR1
siukbah112 said:
Pls help subinary files not installed superSU v2.78.SR1
Click to expand...
Click to collapse
Just download & flash latest SR5 superSU.zip
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Shook1 said:
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Click to expand...
Click to collapse
ok, I've updated the instructions.
finally, I've managed to flash the recovery img to my Stock 285. I have compiled the heimdall from source (github), using Debian 8 Jessie. I also managed to download the stock firmware from sammobile using wget + cookies trick so it can be resumed without requiring a premium account. Thanks for the TWRP
BTW, after installing the SuperSU the SELinux is gone? do I need to flash your custom kernel too?
What do you mean? Was SELinux set to permissive? From what I know the stock kernel has SELinux configured to always enforce and can't be disabled that easily.
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
{
"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"
}
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
gian20 said:
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
Click to expand...
Click to collapse
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
jedld said:
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
Click to expand...
Click to collapse
I don't know if that issue (missing keyboard) was patched with the new stock firmware update on Dec 13, 2016 or if it may block installation of custom firmwares... I ended up not using a password on the lock screen, I deleted the passowrd.key and modified the android settings database to disable password lock, but seperating the necrpytion password using an app.
Unroot without rebloating?
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
DJThunderGod said:
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
Click to expand...
Click to collapse
If you have removed the bloatware it should stay like that unless you reflash the stock rom.
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
kannaiah said:
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
Click to expand...
Click to collapse
It's possible the stock rom overwrites the recovery since you rebooted straight to stock after flashing. Try to flash again but this time when the device reboots, try to press and hold power + home + vol up immediately to attempt to load TWRP recovery.
No More FRP Lock Problem While Installing Xposed.
Note: Before you start reading this thread. I am not responsible for any damage caused to your device do it at your own risk but this method is 100% working so be confident and if u got any errors while doing this process comment on the thread or pm me. This method is only tested with samsung smg531f stock rom (means original rom by samsung). Try this on other custom roms like CM,AOSP,MIUI etc. at your own risk.
Hi XDA today I am here to help people who are unable to install xposed framework in their Grand Prime SM-G531F their are not any threads of installing xposed so I thought of creating one and If you have a problem in installing xposed and getting errors then you are at the right place. If you occured frp lock problem while installing xposed then you are at the right place.
Also try:-
[MASTER THREAD]Samsung Galaxy Grand Prime SM-G531F
S6 S Voice For Grand Prime All Models 5.1.1 Only
Google PIXEL bootanimation For Samsung Galaxy Grand All Models 5.0+
Android Nougat bootanimation for Samsung Galaxy Grand Prime All Models 5.0+
[PORT]S6 Wallpaper Picker for Grand Prime All Models 5.0+
J5 Prime Keyboard + Android N Emojis for Grand Prime All Models 5.0+
Requirements:
1. A Brain.
2. Rooted device.
3. TWRP Recovery.
4. Root Explorer.
5. A Normal PC.
6. Samsung USB Drivers. ( Download them from Samsung official Website ) or If you have Samsung Kies then you have drivers already Installed.
7. Download all files in attachment.
Procedure: No 1.
Steps to Install TWRP and Root SM-G531F:.
1. First You need to install TWRP Recovery. So you can easily be able to root your device downloadtwrp-2.8.7.1-grandprimevelte.img.tar or twrp3latest.tar from attachment.
2. Now You have to go to settings>aboutphone> and then hit build number 7 times now you have developers option. go and check usb debugging and OEM Unlock.
{
"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"
}
3. After that remove your google account by going into settings>accounts.
4. Now shutdown your device and put it in download mode by holding Volume down+Home+Power button together to boot in download mode.
5. Connect your device with PC and open odin (make sure you have installed samsung drivers). after connecting in odin there will be a box that will become yellow. Now click PDA and select TWRP Recovery now hit start after this twrp will be installed.
6. Now put the downloaded BETA-SuperSU-v2.52.zip file in you sdcard and then reboot in recovery mode by pressing Volume UP+Home+Power Key together now you will get boot in TWRP recovery.
7. Now go click install and select the BETA-SuperSU-v2.52.zip file you downloaded and flash it.
8. Now do wipe dalvik cache.
9. Dont add google account because first u need to flash xposed module. I will tell u when to add google account.
OR
You can download the Pre-rooted system so you dont have to do the above steps:
https://www.androidfilehost.com/?fid=24665542585484026
Note:- You need to factory reset your device after you install pre-rooted system. ( I will suggest you to follow the twrp root method instead of prerooted system. )
Procedure: No. 2
Steps to Install Xposed Frimware:.
1. Download the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip and Xposed apk from attachment.
2. Now go into recovery mode by pressing Volume UP+Home+Powerkey together.
3. After you get into recovery click install and then select xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip file flash it and reboot.
4. Now the xposed firmware has installed now install xposed apk file and grant the file root access.
5. Now the final and last step download Stock original recovery and reboot in download mode by pressing Volume down+Home+Power key together.
6. Now open odin and click pda and select stock original recovery file and click start now twrp recovery will be replaced with stock recovery now you will not get frp lock error. Now you can easily add your google account and there will be no frp lock and you can easily use xposed now.
For latest Update of Xposed Framework for grand prime visit:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Congrats You have successfully Installed Xposed.
Thanks @waleeds1 for reminding me to add this.
If you got Bootlooped while installing xposed:
Then Simply download xposed uninstaller zip from attachment and put it in your sd card and flash it.
Special Thanks: @wanam
If you like my work hit thanks.
Nice tutorial. What about backup, do I need to back up system when I experimenting with xposed. And are there good modules for G531f?
mita99796 said:
Nice tutorial. What about backup, do I need to back up system when I experimenting with xposed. And are there good modules for G531f?
Click to expand...
Click to collapse
Thanks bro
Yes Its upto u to make a backup of system but I have backup of system everytime. There are so much modules for g531f available. But now I am waiting for the google assistant I hope it will come on lollipop also.
P.s: can u tell me are u able to see the images on the thread?
Owen007 said:
Thanks bro
Yes Its upto u to make a backup of system but I have backup of system everytime. There are so much modules for g531f available. But now I am waiting for the google assistant I hope it will come on lollipop also.
P.s: can u tell me are u able to see the images on the thread?
Click to expand...
Click to collapse
Yes, all images are fine. ☺
mita99796 said:
Yes, all images are fine. ☺
Click to expand...
Click to collapse
Oh ok thanks for the info man
Owen007 said:
No More FRP Lock Problem While Installing Xposed.
Hi XDA today I am here to help people who are unable to install xposed framework in their Grand Prime SM-G531F their are not any threads of installing xposed so I thought of creating one and If you have a problem in installing xposed and getting errors then you are at the right place. If you occured frp lock problem while installing xposed then you are at the right place.
Requirements:
1. Rooted device.
2. TWRP Recovery.
3. Root Explorer.
4. A Normal PC.
4. Download all files in attachment.
Procedure: No 1.
Steps to Install TWRP and Root SM-G531F:.
1. First You need to install TWRP Recovery So you can easily be able to root your device download twrp-2.8.7.1-grandprimevelte.img.tar from attachment.
2. Now You have to go to settings>aboutphone> and then hit build number 7 times now you have developers option. go and check usb debugging and OEM Unlock.
3. After that remove your google account by going into settings>accounts.
4. Now shutdown your device and put it in download mode by holding Volume down+Home+Power button together to boot in download mode.
5. Connect your device with PC and open odin (make sure you have installed samsung drivers). after connecting in odin there will be a box that will become yellow. Now click PDA and select TWRP Recovery now hit start after this twrp will be installed.
6. Now put the downloaded BETA-SuperSU-v2.52.zip file in you sdcard and then reboot in recovery mode by pressing Volume UP+Home+Power Key together now you will get boot in TWRP recovery.
7. Now go click install and select the BETA-SuperSU-v2.52.zip file you downloaded and flash it.
8. Now do wipe dalvik cache.
9. Dont add google account because first u need to flash xposed module. I will tell u when to add google account.
OR
You can download the Pre-rooted system so you dont have to do the above steps:
https://www.androidfilehost.com/?fid=24665542585484026
Procedure: No. 2
Steps to Install Xposed Frimware:.
1. Download the xposed-v86.0-sdk22-arm-custom-build-by-wanam-20160709.zip and Xposed apk from attachment.
2. Now go into recovery mode by pressing Volume UP+Home+Powerkey together.
3. After you get into recovery click install and then select xposed-v86.0-sdk22-arm-custom-build-by-wanam-20160709.zip file flash it and reboot.
4. Now the xposed firmware has installed now install xposed apk file and grant the file root access.
5. Now the final and last step download Stock original recovery and reboot in download mode by pressing Volume down+Home+Power key together.
6. Now open odin and click pda and select stock original recovery file and click start now twrp recovery will be replaced with stock recovery now you will not get frp lock error. Now you can easily add your google account and there will be no frp lock and you can easily use xposed now.
Congrats You have successfully Installed Xposed.
If you like my work hit thanks.
Click to expand...
Click to collapse
How to get this...in setting menu shows information storage, language, android version, clock and charging information
Sahin551 said:
How to get this...in setting menu shows information storage, language, android version, clock and charging information
Click to expand...
Click to collapse
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Owen007 said:
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Click to expand...
Click to collapse
I already have xposed framework
Owen007 said:
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Click to expand...
Click to collapse
Thanks bro))
Your device is looking cool now @Sahin551
Thread Updated with lastest twrp recovery.
Plz make a custom ROM for sm-531f
Sushant515 said:
Plz make a custom ROM for sm-531f
Click to expand...
Click to collapse
I am trying to make one custom rom be patience. I will release it soon.
Owen007 said:
I am trying to make one custom rom be patience. I will release it soon.
Click to expand...
Click to collapse
Thanks a lot
Hey guys. I tried this yesterday, and got to the end but something went wrong, and there was no superSu in my phone. Last night i installed original firmware and did factory reset to phone, and when i tried this today, i kept stuck on part where you install twrp via odin. In odin it says PASS, and looks like everything is cool, but then i pull out USB from phone, go into recovery mode with VOL UP+HOME+POWER and it starts original recovery mod, not twrp recovery mode. But yesterday it started twrp recovery mode instantly. Can anyone help me?
DzonTravolta said:
Hey guys. I tried this yesterday, and got to the end but something went wrong, and there was no superSu in my phone. Last night i installed original firmware and did factory reset to phone, and when i tried this today, i kept stuck on part where you install twrp via odin. In odin it says PASS, and looks like everything is cool, but then i pull out USB from phone, go into recovery mode with VOL UP+HOME+POWER and it starts original recovery mod, not twrp recovery mode. But yesterday it started twrp recovery mode instantly. Can anyone help me?
Click to expand...
Click to collapse
Tell me if u r still getting this error? U flashed twrp3 or twrp2?
Owen007 said:
Tell me if u r still getting this error? U flashed twrp3 or twrp2?
Click to expand...
Click to collapse
I just needed to unchek a. reboot in odin and it worked perfeclty fine! No more error. I used both of them when that happend
DzonTravolta said:
I just needed to unchek a. reboot in odin and it worked perfeclty fine! No more error. I used both of them when that happend
Click to expand...
Click to collapse
Oh ok If u got anymore problem ask me via pm and good luck with your android
Have anyone ever tried Linux deploy if yes please help me I am having great trouble using it
Sent from my SM-G531F using Tapatalk
Hack House said:
Have anyone ever tried Linux deploy if yes please help me I am having great trouble using it
Sent from my SM-G531F using Tapatalk
Click to expand...
Click to collapse
Linux deploy what it does? I want to know
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
{
"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"
}
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
can you make an English video please thx!
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Not happening.
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
the_bulk said:
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
Click to expand...
Click to collapse
Theres no official TWRP for Speadtrum based 2016 J3s. There are newer versions for the J30F/FN i think, but atm i don't care/need it.
Since we don't have an Exynos or Qualcomm SoC, the custom rom scene doesn't look so good. Pretty much you have Lineage (MM & N), RR (N) and more recently DotOS (N), but they all suffer from pretty much the same problems give or take, in top of that most of the other roms are dead since the devs moved on to other phones, the ones I mentioned before don't really receive updates oftem. Right now im using stock with root and Xposed, is working fine, however im thinking about giving a second chance this rom: https://forum.xda-developers.com/galaxy-j3-2016/development/j2-pro-port-markus-rooted-t3657383 is stock MM, a port from the j210F wich i think is newer and somewhat better than this other j2 port: https://forum.xda-developers.com/galaxy-j3-2016/development/marshmallow-rom-j320f-t3623551
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Odin Faild
Hi Guys!
I tried to flash the TWRP recovery on my J3 (2016) , but odin saids its faild could you help me with it please?
milewap said:
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Click to expand...
Click to collapse
I flashed latest Magisk v18,with TWRP and yes TWRP vorks great tnx dev...for all :good:
Here's another one TWRP custom recovery,this one he has a bekap EFS....downloaded from 4pda ru site.All credits goes to them
SM-J320F-TWRP-F2FS.tar.md5
And here SM-J320FN-TWRP-F2FS.tar.md5 for FN but it does,on J320F i flashed today and works without problems.
Here it is PIT J320F if someone needs it...
Need help
mauriciognr said:
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Click to expand...
Click to collapse
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
AminNadery said:
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
Click to expand...
Click to collapse
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Sorry for bothering again.
mauriciognr said:
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Click to expand...
Click to collapse
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
AminNadery said:
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
Click to expand...
Click to collapse
First, perform a factory reset and flash your stock ROM (with odin), afterwards twrp and then magisk. Whatever problem you might have it will go away after a clean install of your rom. Use latest magisk.
Odin
Can I do this without computer???
How to Root Samsung S23 (SM-S91*B/N/0)
WARNING!
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but some ROMs are patched for all these mentioned features, you can use custom ROM or patch it yourself for stock ROM. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
How to Unlock Bootloader
Follow below four steps to ulock the bootloader
1.Enable Developer Option
Open the Settings app on your Galaxy device.
Choose About > Software Information.
Now tap on Build Number 7 times to enable the developer option.
You’ll get a message “You’re now a developer.”
Now Developer option has been enabled.
2: Enable OEM Unlock
Go to the Settings app again on your device.
Navigate to the Developer option.
Enable the toggle next to OEM Unlocking.
Tap YES to turn on the confirmation dialog box.
3: Boot Your device to Download Mode
While device is booted → Connect device to PC → Select to Restart → As soon as device screen turns off, Press and hold Volume Up + Volume Down simultaneously OR In case device is powered off Press and hold Volume Up + Volume Down simultaneously and connect your device to the PC via a USB Cable.
You can see the warning message on your device and release the pressed keys.
Finally, press the Volume Up key once, and you will be booted into Download Mode.
4: Unlock Bootloader
Once device booted into Download Mode, you will see option to long press Volume up to unlock bootloader,Now, press and hold the Volume Up key for a few seconds., Here, you’ll get a confirmation whether you are sure to proceed.
Use the Volume Up button to reply to the confirmation.
This will erase all the data on your device and unlock the bootloader.
Once completed, your device will automatically boot up to the OS.
Now you have successfully unlocked the bootloader
How to root S23
Instructions for stock non rooted ROM
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Download and Install latest Magisk apk (Get Latest Magisk apk from here)
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
When done, copy patched file to PC
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
Install the Magisk app you’ve already downloaded above and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
Upgrading the OSOnce you have rooted your Samsung device, you can no longer upgrade your Android OS through OTA. To upgrade your device’s OS, you have to manually download the new firmware zip file and go through the same AP patching process written in the previous section. The only difference here is in the Odin flashing step: do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Important Notes
Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
PS : It is strongly recommended to make EFS backup once you root device and save to safer place like on cloud or PC
For TWRP : Read here
Credit : topjohnwu Guide part taken from Origin guide here
{
"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"
}
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
zzattack said:
Will try this now. Should the other slots BL/CP/CSC be filled with the firmware files when flashing this AP?
Click to expand...
Click to collapse
No needs, Flash requied file with AP slot onl
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
zzattack said:
I flashed the AP file. I could not enter recovery mode to do factory reset. Device went into boot-loop mode, but after some failed attempts launched recovery by itself. Then I was able to do factory reset, and device boots properly.
Magisk (25.2 from apk in your zip file) still indicates: not installed. Ramdisk yes. Zygisk no (obviously).
Click to expand...
Click to collapse
You flashed AP file I have provide or one with patched with magisk yourself?
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
zzattack said:
Earlier today I used Magisk alpha to patch the AP from WA6 firmware.
Some minutes ago I flashed AP file from you on top. It only wrote boot and vbmeta.
Any debug info/logging I can provide?
Click to expand...
Click to collapse
Odin was passed successful?
Kernel I have provided is surely Patched., May be needs to contact Jhon with log. Kindly post in Magisk thread
Yes, no problems from ODIN. I will try to find the magisk thread and useful logging infos.
Magisk log added
zzattack said:
Magisk log added
Click to expand...
Click to collapse
If you can save log from Magisk App - Logs - Save and attach here
Also show me screenshtot of magisk app
Nice!!!
zzattack said:
Magisk log added
Click to expand...
Click to collapse
I have updated link (with debug version), Can you flash again and Install included Magisk? After this take log so I can send to Jhon with debug version. Also take screenshot of magisk app
Logs + magisk screenshot attached with debug image and apk.
zzattack said:
Logs + magisk screenshot attached with debug image and apk.
Click to expand...
Click to collapse
Do you have telegram? If yes inbox me. We can do some test with easy communication
@zzattack or any other user
I have updated link(v3), If anyone available to test new version.
.
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
Great,
That's awesome news!
Thank you very much for testing.
Any other user available to test then let me know, Next test will be for Root with Magisk Stable (25.2)
Debug version already reported working (reported by @zzattack )
.
I'm waiting for my s23 ultra next week and then I'll be able to test.
I'm aware I'll lost Samsung Pay and pass. I really don't care... Don't use it... But, will I have troubles with Google pay and secure folder if rooted?
zzattack said:
This one gave me the "Magisk needs additional setup" prompt. After accepting + reboot, Manager detects magisk correctly and root is functional. Great work!
Would you be able to upload a release kernel too? Thanks so much!
Click to expand...
Click to collapse
does zygisk work?