Related
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
AndreSkywalker said:
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
Click to expand...
Click to collapse
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
nazagato said:
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
Click to expand...
Click to collapse
So a more modern android version won't work? That's a huge bummer to be honest.
Maybe try to get Dirac like in HavocOS cause it seems realy good
Triparadox said:
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
Click to expand...
Click to collapse
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
AndreSkywalker said:
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
Click to expand...
Click to collapse
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Triparadox said:
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Click to expand...
Click to collapse
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Triparadox said:
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Click to expand...
Click to collapse
Happened same to me yesterday.I tried dolby and it crashed.So now I'm using Viper4Android, it works great.I can send you settings for headset:
Headset
Master Power: ON
PlaybackAGC: ON
Effect Strength: Moderate
Firequalizer: ON
Preset: R&B
Headphone Surround: ON
Effect Level: 2
Viper Bass: ON
Bass Boost: 3.5dB
Viper Clarity: ON
Clarity: 3.5dB
Cure Tech+: ON
Binaural Level: Extreme
Cheers
AndreSkywalker said:
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Click to expand...
Click to collapse
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Triparadox said:
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Click to expand...
Click to collapse
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
AndreSkywalker said:
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
Click to expand...
Click to collapse
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Triparadox said:
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Click to expand...
Click to collapse
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
AndreSkywalker said:
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
Click to expand...
Click to collapse
i don't see any module.
Triparadox said:
i don't see any module.
Click to expand...
Click to collapse
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
AndreSkywalker said:
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Click to expand...
Click to collapse
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Triparadox said:
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Click to expand...
Click to collapse
I use dolby atmos with viper4android. Dolby atmos is effective with the headset, without the headset it doesn't work very loudly, while viper4android works both ways.
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
szmoki42 said:
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
Click to expand...
Click to collapse
Hi,
Unfortunately, it doesn't work for me either and there is currently no solution to the problem
Man that just s#cks.
If anyone knows something, please don't hold it
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 gpad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
polygaryd said:
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 glad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
Click to expand...
Click to collapse
Oh and there is no twrp version for this device for me to try to install the rootless driver which I did download to try to install manually.
Anyone with knowledge about this out there that can help?
I too have the same issue so can we put our heads together and fix it? Im using mtk 6753t octa core agptek t06s mp4 player I patched my recovery.img with universal mtk twrp patcher but no dice booting to recovery. By the way I'm rooted and tried everything.
I'm reading this... https://www.apkmirror.com/apk/team-dewitt/viper4android-fx/viper4android-fx-2-7-2-1-release/