Related
This is the EASIEST way to root Xperia V. This will work on most other xperia devices. Also will work on most other devices like Samsung, LG etc.
I AM NOT RESPONSIBLE FOR ANY DAMAGE/DAMAGES CAUSED BY ROOTING YOUR DEVICE. USE ROOT AT YOUR OWN RISK
Guide
1. Download "Towelroot" apk. ~click~
2.Go to "Settings > Security" and enable "Unknown Sources"
3.Install Towelroot apk.
4.Open the app Towelroot.
5.Click "Make it rain"
Thats all. Now you have root access. Now you can uninstall Towelroot app.
Go to the Play store and install "SuperSU" by Chainfire.
Your phone may give you a warning "Towelroot app is harmful". Just ignore it.
This will ONLY work if a) the kernel date is older than June 2014 b) the device has a qualcomm processor
This is the easyest way to root xperia V,T,TX. But there is already a thread - http://forum.xda-developers.com/showthread.php?t=2798411
krasimiretov said:
This is the easyest way to root xperia V,T,TX. But there is already a thread - http://forum.xda-developers.com/showthread.php?t=2798411
Click to expand...
Click to collapse
Yeah there is a thread already. Thanks for the info. Someone ask a forum moderator to delete this thread.
or just use KINGROOT. google it. Super simple as well.
Easy to root
:good:
I am having a strange issue.
Actually, I have Gionee M2 indian version with kitkat installed.
I rooted it using Kingroot app and everything worked fine and root sucessfull.
After that I installed Xposed installer App, 2.6.1,
and then installed the framework using installer,
reboot was asked and rebooted.
But it was showing, Xposed not installed, install and reboot, but in framework, it shows both active.
Unfortunately, xposed was not working with these active.
Then I saw a video on youtube in which he solved this problem, procedure was, : --- >
1. go to es explorer
2. then Device - > System - > etc -> theme - >
3. rename map.properties file to amap.properties
after this reboot,
I followed the same procedure, and now after rebooting,
I am not able to open anything, it is showing Application error, unfortunately, launcher has stopped, and it is not letting me get in any option or even go to setting,
whenever i try to go to setting using notification menu, error shows setting has stopped and again laucher has stopeed,
I am not able to do anything.
Please HELP ME ASAP,
and help to get xposed installed in it
Hii do you joined any whatsapp grup for gionee m2 if you joined pls send me grup invitation link
Do you tyu to hard reset to your phone ???
Reply as soon as possible
Thanks
ravibhardwaj2305 said:
I am having a strange issue.
Actually, I have Gionee M2 indian version with kitkat installed.
I rooted it using Kingroot app and everything worked fine and root sucessfull.
After that I installed Xposed installer App, 2.6.1,
and then installed the framework using installer,
reboot was asked and rebooted.
But it was showing, Xposed not installed, install and reboot, but in framework, it shows both active.
Unfortunately, xposed was not working with these active.
Then I saw a video on youtube in which he solved this problem, procedure was, : --- >
1. go to es explorer
2. then Device - > System - > etc -> theme - >
3. rename map.properties file to amap.properties
after this reboot,
I followed the same procedure, and now after rebooting,
I am not able to open anything, it is showing Application error, unfortunately, launcher has stopped, and it is not letting me get in any option or even go to setting,
whenever i try to go to setting using notification menu, error shows setting has stopped and again laucher has stopeed,
I am not able to do anything.
Please HELP ME ASAP,
and help to get xposed installed in it
Click to expand...
Click to collapse
I have a WALTON Primo_HM and I also rooted once with Kingo ROOT or KingRoot . This app does root your phone safely but not greatly.I also installed Xposed installer in the phone but it says it was active and others said it wasn't active.The main issue is with the root.Try giving your phone a hard reset. I will not be responsible for the damage occurrence.
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Hgt45 said:
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Click to expand...
Click to collapse
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Rom said:
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Click to expand...
Click to collapse
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Hgt45 said:
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Click to expand...
Click to collapse
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Rom said:
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Click to expand...
Click to collapse
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Hgt45 said:
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Click to expand...
Click to collapse
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Rom said:
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Click to expand...
Click to collapse
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Hgt45 said:
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Click to expand...
Click to collapse
Hello,, any sugestion. ?
Have a great day.
H.
: (
Sent from my SM-N910P using Xposed Modules
Hgt45 said:
: (
Sent from my SM-N910P using Xposed Modules
Click to expand...
Click to collapse
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
samep said:
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hello Samep, I'm impressed and thankful on how you describe everything, I know its takes lon time and dedication to write,, THANKS A LOT, I know these will be the most comprehensive for many many users... I will try to do what you explained. ..
Also thanks to Rom and others for your suggestions and help.
Have a great weekend.. all the best wishes for all.
Regards
Herm.
slm note 4
note 4 I am using n910c 6.0.1. I have installed the device rooted twrp but I do not know which xposed i will install. I write armv7l in the kernel.
I do not know how many sdk I have to help you rejoice
Hello everyone,
I am facing an issue and will be eternally grateful if someone helped me with it. I recently lost some very important audio recordings from my phone. These are very important and I want to run a data recovery tool to help retrieve them but all such tools require root access. I then rooted my phone using magisk and checked the status via those root check apps and they show the status as rooted. However, the problem is that none of the data recovery tools recognize the root and hence cannot run a scan. Perhaps I am overlooking something here. Model of my phone is SM-N920I. I flashed the magisk via twrp and have also installed the Magisk manager. Everything is up to date. Again, when I check the root status of my phone via the app "Root checker basic" it says "Root access is properly installed". Also, when I am using the data recovery tool i.e. Fonelab my phone does not prompt me for root access. Nothing is shown on the screen.
I am sorry if this thread is in the wrong section. Mods can feel free to move it or notify me. Thanks
If other root apps are functioning properly it's an issue with the app you're trying to use. You should contact the developers of the apps in question...
See post #3 for in depth guide !
->insert usual general disclaimer of liability
Required:
Odin3_v3.14.1 flash tool
Samsung USB Driver installed
Frija or something else, to download stock files
7zip or similar
1: Unlock bootloader (will wipe your precious data, void warranty, break Knox e-fuse and who knows what else !)
-unlock dev option (just harass your Build number in settings)
-be connected to the internet (WiFi or 5g)
-allow USB debugging
-OEM unlock
-be warned that this might cause WWIII
-Power off your device. Press Volume Up + Volume Down THEN plug your Tablet lnto a PC to boot into download mode.
-Release buttons immediately when the blue screen shows itself.
-Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
-Go through the initial setup.
-Skip through all the steps except wifi or 5g
-sign into your Google or Samsung account
-Enable Developer options & USB debugging
-reboot
-You have an unlock bootloader and have control over your device, (it is unfair that this voids your warranty as you should be able to use your hardware as you please).
2: Root install:
-Install Magisk
-use frija or something else to get the latest file according to your device and your CSC :
-patch the whole AP file with magisk (transfer of big files can be tricky, using SD card to transfer file from computer to tablet and vice versa seems like one if the easiest way)
-use odin to flash AP (the patched one), CP, BL and CSC (will wipe once again and reboot)
-Open magisk to finish install (reboot)
-You have root
3: Root update:
-use Frija or something else to get the latest file according to your device and your CSC :
-patch the whole AP file with magisk
-use Odin to flash AP (the patched one), CP, BL and Home_CSC (using CSC will wipe)
-Press and hold Vol-down and Power let go of all buttons once the screen turn on.
-You have root, data kept and update
Please let me know if something should be added or edited.
Hi @Vinsang! Thanks for the nice post. I'd like to suggest you edit the type of thread this is and make it a "How To Guide" instead of "Question" thread. That will help it stand out, especially if anyone uses the Quick Filters at the top of the list of threads in this section.
Edit: Thanks for changing it. Cheers!
How to Root (or update an already-rooted device)Prereqs
Install the USB driver from https://developer.samsung.com/android-usb-driver
Get the latest Odin from https://odindownloader.com/category/download and unzip it
Get the latest Frija from https://github.com/SlackingVeteran/frija/releases and unzip it
Start Frija and begin downloading the latest firmware for your Model and CSC:
{
"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"
}
Model Numbers
S8 Ultra 5G: SM-X906
S8 Ultra Wifi: SM-X900
S8+ 5G: SM-X806
S8+ Wifi: SM-X800
S8 5G: SM-X706
S8 Wifi: SM-X700
CSC: Settings > About Tablet > Software Information > Service provider software version
Step 1 - Prepare your Tablet (only necessary for first install on unrooted device)
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Turn on OEM unlocking
NOTE: If the OEM Unlocking option doesn't appear, connect the device to the internet, wait a few minutes, then try again
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Step 2 - Patch the stock firmware to make it rooted
Frija should have finished downloading by now, unzip the file (remember where you unzipped it to)
Plug your tablet in to your computer via USB and click Allow if it prompts to allow data access
If this is your first install / you're rooting the tablet for the first time:
Download Magisk-vXX.XX.apk from the topmost release at https://github.com/topjohnwu/Magisk/releases
Copy the Magisk-vXX.XX.apk and the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open the My Files app on the tablet and browse to Downloads
Click the Magisk-vXX.XX.apk and it will prompt you to click Settings
In Settings, turn on My Files, then it will give you a prompt to Install
When Magisk is done installing, click Open
If your tablet was already rooted, and you're just updating:
Copy the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
After the file is done copying, unplug your tablet from USB
In Magisk, click Install in the top Magisk area, then the option for Select and Patch a file
Click My Files > Downloads, select the AP_XXX_XXX.tar.md5 file and click Done at the bottom
Click Lets Go -> After a few moments, it should display this (ignore 'Installation failed' at the top, it always does that):
Step 3 - Apply the rooted firmware
Plug your tablet back in to USB, then on your PC, go back to This PC > Galaxy Tab S8 Ultra > Internal Storage > Download and copy the magisk_patched-xxx.tar file back to the folder where you unzipped the zip file from Frija
After the copy is finished, unplug your tablet from your PC and completely power off your tablet
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Click volume up (the side of volume nearest the power) briefly (don't hold it) to go into download mode
Start Odin and accept the disclaimer prompt
Click BL and select the BL_XXX_XXX.tar.md5 file where you unzipped the zip file from Frija
Click AP and select the magisk_patched-XXX.tar file
If this is your first install / you're rooting the tablet for the first time (this WILL wipe your data):
Click CSC and select the CSC_XXX_XXX.tar.md5
If your tablet was already rooted, and you're just updating (this WILL NOT wipe your data):
Click CSC and select the HOME_CSC_XXX_XXX.tar.md5
Odin should now look like this:
Click Start. When it's finished, Odin will display "PASS!" and the tablet will automatically reboot.
Step 4 - Verify and finalize
Go through the normal setup, signing in to your Google and Samsung accounts this time
Click on Magisk that is now pre-installed, and go through the Settings step to allow it to install again
It should prompt you that your device needs additional setup and one more reboot, click OK
After rebooting, your device should be fully rooted. Use a root checker app if you want to verify.
Step 5 (optional) - Get Netflix (and banking apps etc) working with root
Install https://github.com/Fox2Code/FoxMagiskModuleManager/releases and run it
Search for Universal Safetynet Fix by kdrag0n and install it
In Magisk settings click Systemless hosts, turn on Zygisk, turn on Enforce Denylist
Click Configure Denylist, then the 3 dot menu and Show System Apps
Search for Google Play Store, click it, check the check and turn on all options underneath
Search for Google Play Services, click it, turn on .gms and .gms.unstable ONLY
Search for Netflix, click it, check the check and turn on all options underneath
(optional) Add your bank / pay app, etc here if you'd like
In Settings > Apps, search for Google Play Services and Google Play Store and clear all data (not just cache) for each
Reboot
NOTE - This is currently only passing Widevine level 3, so Netflix is limited to SD. I'm still trying to figure out how to get L1 / full HD.
Is there currently any way to make nandroid backups without TWRP since there isn't a build of it for the Tab S8 line yet?
SavXL said:
Is there currently any way to make nandroid backups without TWRP since there isn't a build of it for the Tab S8 line yet?
Click to expand...
Click to collapse
Not you can't make a full nandroid back up without TWRP for the moment. You can use Swift backup or something similar to backup some things in particular, Google backup is also pretty convenient.
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Dunno about Netflix, but this worked for banking apps:
Add this module : https://github.com/kdrag0n/safetynet-fix
Zigisk and enforced denylist on and add Netflix (or other) in the deny list. Reboot and tryout.
It seemed that the download section isn't there anymore on the latest magisk, same on other devices. You gotta download them separately.
skrowl said:
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Click to expand...
Click to collapse
Not sure when, but somewhere in an update, the ability to download modules from magisk directly was removed. You can download them using an app called Fox's Magisk Module Manager. You can search for modules just like you could on Magisk, and they'll be added once you install them and reboot. Also, for the netflix thing, your device may not be passing safetynet. Checking this was also remove in an update, but you can check it with YASNAC.
Edit: I just did this with my rooted Tab S7+, but it should work with the S8+ and S8U as well. Doing this should let you pass safetynet and be able to use Netflix.
1. Enable Zygisk in Magisk settings, then reboot.
2. Enable Enforce DenyList in Magisk settings, then go to Configure DenyList.
3. Enable show system apps with the menu on the top-right, then search "google play services".
4. Enable DenyList for com.google.android.gms & com.google.android.gms.unstable, then reboot.
5. Open YASNAC to run safetynet attestation, you should be passing basic integrity but failing cts profile match.
6. Download and install the latest version of the safetynet fix for zygisk module, then reboot.
7. Check YASNAC again, you should now be passing basic integrity and cts profile match.
8. Go to settings > apps, find google play service & google play store, clear data for both of them, reboot.
9. Go to the play store > settings, play protect certification should now say "device is certified".
10. Open Magisk > Configure DenyList, search for Netflix (enable show system apps if you need to), enable DenyList for everything, reboot.
11. Update Netflix if it's not up to date. If the play store is allowing you to update Netflix at all, then you're good to go.
Now you have Netflix running on your rooted tab!
Edit 2: Accidentally saved my first edit before I finished the instructions, my bad.
skrowl said:
Prereqs
Install the USB driver from https://developer.samsung.com/android-usb-driver
Get the latest Odin from https://odindownloader.com/category/download and unzip it
Get the latest Frija from https://github.com/SlackingVeteran/frija/releases and unzip it
Start Frija and begin downloading the latest firmware for your Model and CSC:View attachment 5574197
Model Numbers
S8 Ultra 5G: SM-X906
S8 Ultra Wifi: SM-X900
S8+ 5G: SM-X806
S8+ Wifi: SM-X800
S8 5G: SM-X706
S8 Wifi: SM-X700
CSC: Settings > About Tablet > Software Information > Service provider software version
Step 1 - Prepare your Tablet
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on OEM unlocking
Turn on USB Debugging
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Step 2 - Patch the stock firmware to make it rooted
Frija should have finished downloading by now, unzip the file (remember where you unzipped it to)
Plug your tablet in to your computer via USB and click Allow if it prompts to allow data access
If this is your first install / you're rooting the tablet for the first time:
Download Magisk-vXX.XX.apk from the topmost release at https://github.com/topjohnwu/Magisk/releases
Copy the Magisk-vXX.XX.apk and the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open the My Files app on the tablet and browse to Downloads
Click the Magisk-vXX.XX.apk and it will prompt you to click Settings
In Settings, turn on My Files, then it will give you a prompt to Install
When Magisk is done installing, click Open
If your tablet was already rooted, and you're just updating:
Copy the AP_xxx_xxx_tar.md5 from the zip file Frija downloaded to:
This PC > Galaxy Tab S8 Ultra > Internal Storage > Download
Open Magisk
In Magisk, click Install in the top Magisk area, then the option for Select and Patch a file
Click My Files > Downloads, select the AP_XXX_XXX.tar.md5 file and click Done at the bottom
Click Lets Go ->. After a few moments and it should give you a screen like this:View attachment 5574199
Step 3 - Apply the rooted firmware
On your PC, go back to This PC > Galaxy Tab S8 Ultra > Internal Storage > Download and copy the magisk_patched-xxx.tar file back to the folder where you unzipped the zip file from Frija
After the copy is finished, unplug your tablet from your PC and turn the tablet off
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Click volume up briefly (don't hold it) to go into download mode
Start Odin and accept the disclaimer prompt.
Click BL and select the BL_XXX_XXX.tar.md5 file where you unzipped the zip file from Frija
Click AP and select the magisk_patched-XXX.tar file
If this is your first install / you're rooting the tablet for the first time:
Click CSC and select the CSC_XXX_XXX.tar.md5
If your tablet was already rooted, and you're just updating:
Click CSC and select the HOME_CSC_XXX_XXX.tar.md5
Odin should now look like this:View attachment 5574201
Click Start. When it's finished, Odin will display "PASS!" and the tablet will automatically reboot.
Step 4 - Verify and finalize
Go through the normal setup, signing in to your Google and Samsung accounts this time
Click on Magisk that is now pre-installed, and go through the Settings step to allow it to install again
It should prompt you that your device needs additional setup and one more reboot, click OK
After rebooting, your device should be fully rooted. Use a root checker app if you want to verify.
Edit - Thanks OP, but I don't think of this as a better guide. I just took really careful notes of what I was doing, so that I'd be able to reproduce it in 6 months when my brain had completely forgotten all the buttons!
Click to expand...
Click to collapse
Excellent guide. I just had my OOBI this morning & I forgot about having to change the date to an earlier one, check for a software update, etc before being able to see OEM unlock in developer settings. But that's a one & done.
skrowl said:
Anyone work out how to get Netflix working with root yet? Also, is Magisk manager showing any modules to download in the Magisk app for you guys? I can install from file, but the downloading functionality doesn't seem to be working.
Click to expand...
Click to collapse
To download magisk modules use this app; https://github.com/Fox2Code/FoxMagiskModuleManager
To hide root you can try this:
1. Magisk -> Settings -> Hide the Magisk app (It will get a new random package name so other apps won't see that it's actually Magisk and additionally you can choose a new name for the app as well.)
2. Open the newly created magisk app, install extra files when prompted and tab will reboot automatically.
3. Flash MagiskHide Props Config https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases
4. Reboot
5. Flash Universal Safetynet Fix https://github.com/kdrag0n/safetynet-fix/releases
6. Reboot
7. Add any app you want to hide root from to DenyList: Google Play Store, Google Play Services, Google Services Framework, Netflix, banking apps etc.
8. Enforce DenyList MUST stay turned off!
9. Flash Shamiko module to hide root properly.
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
10. Reboot
After checking Frija, found that an update was available fro my SM-X906B EUX, Just updated to X906BXXU1AVCD/X906BOXM1AVCD/X906BXXU1AVCD using step 3 of the guide without issue (root and data kept).
Is there a way to be notify when an update is out ? Or do i have to manually check every month?
Do we have changelog or something similar?
Vinsang said:
After checking Frija, found that an update was available fro my SM-X906B EUX, Just updated to X906BXXU1AVCD/X906BOXM1AVCD/X906BXXU1AVCD using step 3 of the guide without issue (root and data kept).
Is there a way to be notify when an update is out ? Or do i have to manually check every month?
Do we have changelog or something similar?
Click to expand...
Click to collapse
Someone else had given the link to this site (for your model) https://samfw.com/firmware/SM-X906B.
No automatic notifications, but I use a Windows program that checks sites for updates (https://samfw.com/firmware/SM-X900 for my model, which won't arrive for another 12 days).
Might also be able to use https://www.sammobile.com/firmwares/
Somewhere on this site might occasionally be generic changelogs https://www.sammobile.com/news/galaxy-tab-s8-ultra-february-2022-security-update-released/#
Samsung Galaxy Tab S8 Ultra
Introduction Samsung is making no secret of the fact that it wants to offer the best Android tablet on the market. ...
www.sammobile.com
Samsung Galaxy Tab S8+
Introduction Prior to the Galaxy Tab S8 series, the
www.sammobile.com
Samsung Galaxy Tab S8
Introduction Samsung's flagship tablet lineup was due for a major refresh and the company came through with the Galaxy Tab S8 ...
www.sammobile.com
Quick question. If another software update were to come out, could I update it and still have magisk and root access afterwards? My Tab S8+ says its device status is official, and it doesn't tell me that my device is rooted when I connect to the server to check for updates. So, if I updated this way, would that remove the whole patching the AP file with magisk and flashing it with Odin thing? It'd be awesome to have the latest updates and such while maintaining root access.
To keep root and your data while updating, follow the step 3 of the guide in post #1( it requires that you look manually for updates).
I wouldn't advise to update via OTA while rooted. I don't even think you'll get the prompts.
Vinsang said:
To keep root and your data while updating, follow the step 3 of the guide in post #1( it requires that you look manually for updates).
I wouldn't advise to update via OTA while rooted. I don't even think you'll get the prompts.
Click to expand...
Click to collapse
That's odd because I got the prompt to update on my rooted Tab S7+ (it also says the device status is official) when the OneUI 4.1 update came out for it. I haven't tested to see if that would change anything, but since the S7+ has TWRP, I can just restore a backup Incase something doesn't turn out well.
Hi all. I purchased a SM-X900 from the Samsung website(UK). I am having a serious problem with getting the OEM unlocking option to display in the developer options menu. I have tried the known workarounds (change date/disable automatic updates, etc) but had no success. Does anyone have any other methods/ideas? I previously had the tab s7+ and had no problems with this.
Any tips would be much appreciated!
brunosilvauk said:
Hi all. I purchased a SM-X900 from the Samsung website(UK). I am having a serious problem with getting the OEM unlocking option to display in the developer options menu. I have tried the known workarounds (change date/disable automatic updates, etc) but had no success. Does anyone have any other methods/ideas? I previously had the tab s7+ and had no problems with this.
Any tips would be much appreciated!
Click to expand...
Click to collapse
I've had some issues where after enabling OEM Unlocking and going through the process, after Unlocking and resetting, the option disappears, but OEM is still unlocked. Not sure what causes this, but after rebooting for some root-required things and checking again, the option was there and changeable. I actually went throught the normal initialization process on my Tab S7+ and Tab S8+ (wifi, clock, samsung account, etc) and never had any issues. Maybe try either factory resetting again or flashing latest stock firmware (you can flash official firmware even if oem is locked). YMMV though. This specific issue of the option not showing up at all never happened for me, so I'm not sure how much help my suggestions will be.
SavXL said:
I've had some issues where after enabling OEM Unlocking and going through the process, after Unlocking and resetting, the option disappears, but OEM is still unlocked. Not sure what causes this, but after rebooting for some root-required things and checking again, the option was there and changeable. I actually went throught the normal initialization process on my Tab S7+ and Tab S8+ (wifi, clock, samsung account, etc) and never had any issues. Maybe try either factory resetting again or flashing latest stock firmware (you can flash official firmware even if oem is locked). YMMV though. This specific issue of the option not showing up at all never happened for me, so I'm not sure how much help my suggestions will be.
Click to expand...
Click to collapse
Thanks, in my case, I have not seen this OEM option at all, since I received the device. I have not been able to root it.
brunosilvauk said:
Thanks, in my case, I have not seen this OEM option at all, since I received the device. I have not been able to root it.
Click to expand...
Click to collapse
Well, something I can recommend is downloading the latest firmware update for your specific device (use either frija or samfw), going into download mode by holding vol+ and vol- while connecting the device to a PC, and flashing it with Odin, or you can update officially since your device hasn't been rooted yet. Maybe the current version you're on is affecting it somehow? No clue man. This issue is brand new to me.
SavXL said:
Well, something I can recommend is downloading the latest firmware update for your specific device (use either frija or samfw), going into download mode by holding vol+ and vol- while connecting the device to a PC, and flashing it with Odin, or you can update officially since your device hasn't been rooted yet. Maybe the current version you're on is affecting it somehow? No clue man. This issue is brand new to me.
Click to expand...
Click to collapse
No joy, have no idea how to fix this. Thank you for your input anyway! Maybe someone else has any other ideas?