[F31xx][GUIDE] How to install working Viper4Android on rooted XA - Sony Xperia XA Guides, News, & Discussion

Hi all,
I make this small guide to explain and provide working packages for having V4A working on XA, I will not explain what is Viper4Android or how it works but you can have your answers here: http://www.xda-developers.com/tweak-your-mobile-audio-with-viper4android-audio-effects/
When tested I can't having it working with app form official thread, I attached a zip package with the version I use and a fix for Marshmallow.
First of all you must have a rooted device and custom recovery.
1) Download attached zip and extract it
2) Copy 2 files on your phone
3) Install Viper4Android apk, don't launch it
4) Reboot phone in recovery, flash su-policy zip and WIPE DALVIK CACHE
5) Reboot phone to Android, launch app, allow root permissions, V4A will ask for install drivers, allow and reboot.
6) Open stock music app and play music, open V4A app again, enable tabs you want, verify driver is working in "Driver Status" menu (you must have same infos like attached screenshot) and enjoy
7) (Optional) In V4A menu ( 3 dots) go to "lock effect mode" and select Headset, now display Headset tab, go in menu again and select "switch to drawer view". Now "Headset" is your master for settings, you have more settings to play and they are applied to all other profiles.
Don't forget to disable ALL audio enchancement in phone settings and in your music app !!
For now V4A is not fully stable on XA probably because of the apk version I use, I you have time to find a more stable apk please feedback
Personnal feedback:
Use "Normal" FX Compatible mode for settings and switch to "Compatible" after. (reboot)
You can enable "Force Enable V4A" if it doesn't work in your music app like Poweramp, it will enable V4A for ALL sounds in ALL apps but drain a little more the battery.
When setting if it stop to work you have to reboot the phone.

Related

Bluetooth Headset make louder

Hello,
My Moto G4 currently has root. Unfortunately, the voice of the caller via the Bluetooth headset is very quiet, is there a possibility to boost the volume?
On the phone and headset stands maximum
Ay-Bee said:
Hello,
My Moto G4 currently has root. Unfortunately, the voice of the caller via the Bluetooth headset is very quiet, is there a possibility to boost the volume?
On the phone and headset stands maximum
Click to expand...
Click to collapse
I have installed SwanSong and the sound is amazing. SwanSong have an aroma interface and it will be easy for you to install it with all the guides inside the installer. Here are the steps I have done to install it (Same as provided by @tywinlannister).
1. Install the BusyBox app and also install BusyBox inside it.
2. Set SELinux to be permissive. (This is important, but you can do it during the installation of SwanSong).
3. Flash Arise Sound Systems zip from the link https://www.androidfilehost.com/?w=files&flid=151719
(Click Aroma & look for ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip)
4. Reboot to system.
5. Configure the mods.
6. Reboot again.
This is the recommended setup from the developer itself while flashing SwanSong in Aroma. (Thanks to guitardedhero)
I would recommend Core (mandatory, if not already installed), ViPER4Arise™ 2.5.0.5, Profiles, Arkamys™, ICEsound™, Skip Config and Preset, MusicFX (unless you know it's already installed, this script will leave an existing MusicFX installation intact and end, just in case), permissive (do not, if Enforcing Mode is preferred), Repair SD Card Permissions (allow up to 3-5 minutes of additional time for this script).
Once booted:
Android Settings > Apps > Menu > Show System > Arkamys > Enable Phone Permissions
Android Settings > Apps > Menu > Show System > ViPER4Arise > Enable Storage Permissions
Open ViPER4Arise™ and select Audiophile™ X profile from the Load Effect Profile option in Menu.
On displayed output tab:
Master Power > Off
Master Power > On
Menu > Device Status
Should show Enabled, Normal, and Processing: Yes (at least during audio playback for some scenarios)
If you want to select ViPER4Arise™ through a media player's Equalizer option (not necessary, recommended for users that prefer to get to ViPER4Arise™ through a media player rather than launch the app from Recents or App Drawer):
Android Settings > Apps > Menu > Show System > MusicFX > Disable
Reboot for good measure.
Hope it will help for you. If anything bad happens, just dirty flash your rom (only wipe cache and dalvik) and everything will be good. :good:
NB: There will be a lot of modules during the aroma installation which you can skip (Toolkit, Dolby Plus, Dolby Atmos etc) if it is not mentioned in the recommended setup. Its your choice. Enjoy a crystal clear sound from the great developers.
Thanks to @nazim7
Thread located https://forum.xda-developers.com/moto-g4-plus/themes/request-please-help-viper-fx-moto-g4-t3567120

Viper4Android Pixel 2 XL stereo speaker optimization profile (Android Q working)

Updated: OP contains instructions for Android Pie and below, post #5 has current instructions for Android Q.
Saw a couple Viper4Android threads, did not see much in terms of profiles for the 2 XL specifically. Just got the 2 XL coming from a 6P and there was a great profile to optimize it's internal speakers so decided to try out the mod for the 2 XL's speakers. Working very nicely.
Not sure if this will work with every ROM but works nice on Bootleggers (should work on any Pie ROM including stock) and thought I would share so more people could enjoy much improved sound quality. Makes rooting the phone well worth it.
Instructions:
After installing Magisk 18.1
Install BusyBox and run the set-up
Download the Viper4Android V4.1 (used Material theme) via Magisk manager
run the install process, select 2.5.0.4 material theme, install as system app, grand root access then reboot
Load the DorianX profile taken from the 6P. Just unzip then look over the extracted files.
Edited to explain further: You will probably need to individually place the "SRS Audio HD" IRS file in the Viper4Android Kernel folder and put the Profile folder in the Viper4Android Profile folder (using a file explorer to copy/paste the files). Once that's done, in the Viper4Android app under "Convolver", tap it and choose "impulse response file", You should see the "SRS Audio HD" IRS file that you placed in the Kernel folder, select it, tick the box next to Convolver to enable it. Under the main app settings you should be able to select and load the profile. If you did it correctly the DorianX profile folder should be visible to select it. It depends which version of Viper4Android you install. If you do materialized (2.5.0.4) the above should work. Let me know if any problems
Play some music. Toggle Viper4Android master power on and off under the phone speaker tab within the app then back to on once to enable it. Usually you have to do this to "officially" enable Viper4Android. If it's working you will hear the difference. Under the app settings you can verify that the app is processing as well under "driver status". Working with the latest Poweramp, Youtube, etc.
Credit to DorianX who made the profile. There are 4 profiles included to optimize specific bluetooth devices, headphones,etc but just using the internal speaker one (for now). Unable to locate the past post in the 6P forum containing the profile and which other devices were optimized to link to it.
Works very well and thought it was worth posting and making a small contribution so for now enjoy! Profile attached.
Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
powerserge1 said:
Have Viper4Android working nicely on Android Q Beta 4.
Those that downloaded this profile if you don't mind posting the Dorian profile speaker settings (all of them for each tab and whether enabled or disabled) would appreciate it. Profiles no longer can be loaded in this version of Viper.
Looking at the speaker xml file can see some of the settings but probably not all.
Magisk 19.3, Adaway works, viper now works all on today's beta 4. Tried all versions and combos. Getting the driver to install and stick was a big pain.Can post some instructions if anyone is interested. I'm sure plenty of people would like to get viper working.
Now if only Google apps like Gmail and Google play would be themed. Can see the force dark toggle is broken in this beta. Not sure if the Google apps were theming in Beta 3 or not.
Click to expand...
Click to collapse
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
libracez said:
a lot interesting of this, this is a reason why I am rollback to custom on pie while like q beta
Click to expand...
Click to collapse
See below
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
libracez said:
succesfuly, ty
for my 2xl It was
1. installation from xda lab - reboot
2. install audio modification library - reboot
3. open viper (still asking to install driver - just close app, don't choose nothing)
4. go to Magisk switch off audio modification library - reboot
5. viper successfully load, status normal and working (media) with just my favorite profile no custom settings
Click to expand...
Click to collapse
Our 2 XL's can be temperamental, lol.
Glad you got it working. Not sure how the driver installed and the viper app fixed itself with the audio modifications module switched off. It's like you didn't need that module at all. Whatever works.
Just happy we have viper for Q. Played games, music, youtube and running stable here.
powerserge1 said:
Ok I got it. No need to PM me the profile. Took most of the night but done now.
Would be unable to stay on Q without Viper4Android as well...
Make sure to uninstall all previous versions of Magisk and modules to start fresh.
Install Magisk 19.3 via twrp, install latest Magisk manager and then Busybox (make sure to set up busybox). Some are having problems with this Beta and Magisk so YMMV. Working well for me and no app lag.
On Pie in Magisk you should see Viper4Android 2.7.1 module as available
On Q it's not listed (for me at least) so get it from XDA labs.
Install Viper4Android:
https://labs.xda-developers.com/store/app/download/com.pittvandewitt.viperfx (link to direct download, must be signed in)
Or use this link: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
The installer will install it as a magisk module. Grant supersu permissions, install driver, phone will reboot.
Install the magisk audio modifications library module. Reboot. After rebooting disable this module (do not uninstall). Reboot again.
Open up Viper4Android. If it asks you to install driver again do so and phone will automatically reboot. Repeat if needed. If driver install remains unsuccessful try enabling and disabling the audio modifications module then try again. What worked for some worked the opposite for others in past threads on previous Android versions and various devices. Here is the thread for reference: https://forum.xda-developers.com/pixel-2/help/viper4android-driver-installation-fails-t3766362
Once driver is installed the app will load properly and under driver status it will probably say "unsupported" and "abnormal". Close the app
Go back into Magisk manager. Now toggle to re enable the audio modifications module. Reboot. (This is the module that allows Viper4Android to process and can help to install the driver)
Upon reboot, Viper4Android should work. Play some music, check the driver status to verify, you may need to toggle off/on master limiter to finally enable it.
For this profile, put the SRS file in OP above in the Viper4Android Kernel folder. Under the apps speaker tab manually input these settings:
Master limiter: On
Playback gain: moderate or 2, max gain 4x, output threshold -1.9db
FIR Equalizer: On. EQ is flat
Convolver: On. Tap convolver then select the SRS inpulse file you placed in the Kernel folder. Cross channel set to 0
Profit.
You can set or disable the viper4android notification icon in the statusbar within the app's settings.
Let me know how the 2 XL's speakers sound Post updated, instructions should be clear enough. Some having problems will need to wait for the updated Magisk. Moving forward, we do have viper4android working on Q. Fully tested on my 2xl and stable with beta 4.
Thanks to @Team_DeWitt
And Dorianx for his profile originally created for the 6p
Click to expand...
Click to collapse
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated
Mr. Blanco said:
Please forgive me for sounding like a complete tool ..lol but i cant seem to find viper4android app on my phone in the file explore to be able to put the srs file from the dorian zip to the folder in my phone , any help would be greatly appreciated
Click to expand...
Click to collapse
No problem. You are looking for the viper4android folder not the app. See attached screen
powerserge1 said:
No problem. You are looking for the viper4android folder not the app. See attached screen
Click to expand...
Click to collapse
I figured that and searched and searched through internal storage and root directory and i cannot find that app anywhere in my file explorer ..lol this is crazy im using Mixplorer and have attached pics , not sure if i should erase everything and start from scratch again ..lol
Edit: Okay after multiple reboots it magically showed up and was able to put file in correct place but now Driver Status Enabled = no (message) strange ....gonna start over and see if i can get everything working ..lol Thank you for your help @ powerserge1
Edit: Everything up and running and working ... Profit
Mr. Blanco said:
Edit: Everything up and running and working ... Profit
Click to expand...
Click to collapse
Good stuff. To anyone else installing viper just to note if you click on driver and see it as processing = no this does not mean you did anything or the install went wrong. Play a video or music, driver should show as processing yes. When nothing is playing then processing will be no.
Does this enable dual speaker for calls/message alerts?
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
joedajoester said:
How did you guys get magisk working on Q beta 4? For me it makes systemui not start on boot and it skips the lock screen entirely. And if it does boot normally, apps take over 10 seconds to launch. I have tried to wipe system data cache and then ran the flash-all bat and still have the issue. A lot of others have the issue on the magisk canary thread. Some don't have it. Someone suggested after a full wipe with -w it fixed it.
Click to expand...
Click to collapse
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477
powerserge1 said:
Looks like I found a solution that is working for several members (and it was purely by accident because installing Magisk threw an error). Uninstall Magisk in TWRP first then:
https://forum.xda-developers.com/showpost.php?p=79682444&postcount=477
Click to expand...
Click to collapse
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
joedajoester said:
It's not working for me. I had to reboot about 4 times because systemui wasn't starting up and I was getting a black wallpaper with no status or nav bar. Finally rebooted normally and at times apps refuse to open but it's slightly better than it was. This is just so weird. Do I really need to wipe my phone or is it magisks fault?
Click to expand...
Click to collapse
Someone in the Android Q discussion thread might be able to help better. Google pulled the beta so it's tough to say whether in your case it's a magisk or android issue. Or both.
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me
zxspectrun said:
I love this post for real, I have a Pixel 3 with Android P, viper v2.7.1.
I had to port the userprofile to the new version, if someone want it, PM me
Click to expand...
Click to collapse
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
powerserge1 said:
Feel free to post it as well. Curious how you were able to port the profile. Looked everywhere but couldn't find any info to convert the old profile to the new preset format.
Click to expand...
Click to collapse
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0
zxspectrun said:
I just installed the viper4android mod showed on the screenshot and it ported all my old profiles
attached dorian ported to v2.7.1.0
Click to expand...
Click to collapse
Yes it did the same for me. The first time, almost forgot. I did not find the sound to be the same, not even close. Ultimately I still had my Nexus 6p and was able to retrieve the settings and input them manually. Then the sound was as it should be.
Do you find the sound identical with the ported profiles? It might be hit and miss.

V4A OOS10

Anyone having trouble with getting V4A to work on OOS10? Everytime I open it up after a reboot, it keeps asking to re-install drivers. Any solutions?
This steps works for me
Uninstall ViPER4Android and Audio Modification Library if you have them installed in Magisk. Reboot after uninstalling.
Download the latest ViPER4Android FX apk from XDA Labs.
Install the downloaded APK.
Open the ViPER4Android application but do not install the driver yet. Click on cancel when prompted.
Close the application and then open Magisk Manager.
Install Audio Modification Library from the downloads section and do not reboot once the installation is complete.
Go back to ViPER4Android and now install the driver. The device will reboot automatically.
Once booted, go to Magisk Manager and disable Audio Modification Library (not uninstall).
Open ViPER4Android and install the driver again. The device will reboot automatically.
Once the device finished booting, go check if the ViPER4Android is installed. If yes, congrats! You’re done! If not, there’s a few more steps you need to take. Do not install the driver, click on cancel.
Close ViPER4Android and go back to Magisk Manager to re-enable Audio Modification Library.
Go back to ViPER4Android and then install the driver again. The device will reboot.
Credits to this website source: V4a on Android 10

Viper4Android On Stock 8.0 Rom

Hi guys!
This is my first thread so sorry if i make any mistakes, so let me know if i did any!
So as the title says, We can get viper4android on stock rom but we need to
-Have unlocked bootloader
-Magisk
-Big brain, and focus to not f. it up!
-Back up your rom and data, just in case :silly:
So, we need magisk to install Viper4android module
-Magisk: https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
-Viper4Android magisk module:
https://zackptg5.com/downloads/v4afx_v2.7.1.6.zip
-App Uninstaller:
https://redirect.viglink.com/?key=e...uninstaller-remove-package-t3423910/amp/&ref=
So first we need to install app uninstaller and give it root and memory premissions, after that we need to find any app that is associated with miusic enchacments, like in my case: MiusicFX and Sound settings/Enchacments, And uninstall them!
After it uninstalls we refuse to automaticly reboot, then we launch magisk and install viper4android module either from Modules sections and selecting Viper4Android file or just searching it in Download section
After it downloads and installs we, again not reboot and just launch the viper4android app, give it root premisions after we click to accept the messange that tells us that it will intall an driver for itself let it istall.
After the viper installs itself phone will reboot automaticly.
Viper can not work on first boot, like in my case just open the app if it not works reboot the phone and it should work fine.
And Viola, You have Viper4Android on your stock Sony rom :laugh:
If you have any problems let me know. I will try to help you :silly:

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab S2 stock to Android 10

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab S2 stock to Android 10
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab S2 (models SM-T713, T719, T813, T819) stock to Android 10 Q / LineageOS 17.1
Supported models:
- SM-T713 (gts28vewifi)
- SM-T719 (gts28velte)
- SM-T813 (gts210vewifi)
- SM-T819 (gts210velte)
This detailed step-by-step guide helps you transform your Samsung Galaxy Tab S2 to a powerful one with Android 10.
Make sure your tablet is compatible: in Android, go to Settings > About tablet. Check Model number is listed above.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
### See all my tutorials at https://github.com/djibe/Android-tutorials
### Buy me a coffee: https://ko-fi.com/djibe
CHANGELOG
v3. TWRP 3.6, update pack, add download links
v2. Add support for Netflix and Disney+, Magisk updated
v1. Initial release for Android 10
1) DOWNLOAD
- djibe Galaxy Tab S2 pack: https://drive.google.com/file/d/1PcnZaQieCz3N0MJhOp6eC3MjAYYvx0wH/view?usp=sharing
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6 recovery for 4 models + Magisk Root). Unzip files.
+ ROM LineageOS 17.1 Unofficial: https://forum.xda-developers.com/t/rom-unofficial-10-lineageos-17-1-t713-t719-t813-t819.4070161/
SM-T713 (gts28vewifi): https://lineageos.wickenberg.nu/gts28vewifi
SM-T719 (gts28velte): https://lineageos.wickenberg.nu/gts28velte
SM-T813 (gts210vewifi): https://lineageos.wickenberg.nu/gts210vewifi
SM-T819 (gts210velte): https://lineageos.wickenberg.nu/gts210velte
Alternatives: https://los.rockhost.se/
### Camera doesn't work, 3G/Data network doesn't work
+ BiTGApps Package ARM64 10: https://github.com/BiTGApps/BiTGApps-Release/releases
+ Charge tablet to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug tablet to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything later.
3) FLASH TWRP 3.6 RECOVERY
Go to Settings > About tablet.
Tap 7 times on Build number to unlock Developer Options.
Go to Settings > Developer options and switch OEM unlock ON.
Shut down tablet.
Boot in Download Mode: hold Home + Power + Volume- until you see Warning screen.
Confirm access to Download mode by pressing Volume+.
Tab now displays "Downloading... / Do not turn off target".
Connect tab in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select corresponding twrp file for your model (ie: twrp-3.6.0_9-0-gts28vewifi.tar for SM-T713)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug tablet.
Restart tablet to recovery:
- hold Power + Home + Volume- until tablet screen becomes black.
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP PARTITIONS AND SYSTEM (Nandroid backup)
Boot in Recovery Mode : Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
I prefer to backup System, Data and Boot partitions. In case of problem, you will have your tablet in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect tablet to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access tablet's memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik / ART Cache, System, Data, Internal Storage, Cache then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
5) FLASH ROM, GAPPS +/- MAGISK ROOT
Back to TWRP main menu, go to Mount menu again to connect tablet to PC again.
Connect tablet to PC and use Windows explorer to copy files on tablet's internal memory.
Copy TWRP folder from your tablet to somewhere safe on PC.
This backup can restore your tablet to its original Samsung state.
Copy files of ROM + Bitgapps + Magisk on tablet.
Go back to TWRP Home menu. Then tap on Install > choose los*.zip,
then Add more zips and select bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
Again, go to Reboot > Recovery and swipe to reboot.
Optional: After restart, go to Install, select Magisk and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the tablet to boot.
It will be stuck with LineageOS animation on it's first launch. It is normal.
Force reboot using the Power and Volume Down buttons.
Now let LineageOS finish to start.
6) OPTIONAL: ROOT ACCESS
Configure Android as you like.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
7) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%: Settings > Display > Dark theme
- For better battery, remove Always on display
Settings > Display > Screen saver > Desactivated
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
### If you experience battery drain, stick to 20220312 build (thx to @yoblo)
8) OBTAIN GOOGLE MOBILE SERVICES (GMS) CERTIFICATION
Google now restricts Google Play and Google apps access to certificated devices. Since you have a custom ROM, you are banned.
We now need to subscribe for the Google Play Certification.
Download Device ID (by Evozi) app from Play Store.
Launch app.
Tap on the Google Service Framework (GSF) line, then tap on the COPY button.
In your Android webbrowser, go to: https://www.google.com/android/uncertified/
Connect to Google using your Google/Android account.
In the input field of the page, paste the 16 digits code.
Click on the Save button, a success message confirms your device is Certified.
Then go to Settings > Apps > Google Play Store > Storage > Clear storage
Do I need to re-certify it ?
"Your device’s GSF ID is reset every time your device is factory reset (or when you wipe the GSF app itself) since it is stored in your data partition, so you must re-register your GSF ID every time you perform either of these actions."
More info here : https://lineageos.org/Google-Play-Certification/
Enjoy,
djibe
Thanks: ripee, Luk1337, LineageOS team, TWRP team
---------------------------------------
Force Samsung Galaxy Tab S2 to restart
Hold Power + Volume down for 10-20 seconds
I have just followed this to update my T719 tablet. All seems to work other than the camera, when you try to open the camera app it freezes before eventually saying 'unable to connect to camera', then closes. Have tried another camera app but still get the same issue. Is this a known error?
Thanks
.
Hi @smarty79 , yes camera doesn't work.
I will be more precise about it.
Thx for reporting
Hi,
3G network doesn't work
Click to expand...
Click to collapse
Do you mean that RIL does not work either (no 4G)?
Are you working on a fix for the camera and mobile network?
bulldozerecske said:
Hi,
Do you mean that RIL does not work either (no 4G)?
Are you working on a fix for the camera and mobile network?
Click to expand...
Click to collapse
Hi, you have to be careful and download ROM according to your model.
EDIT: yes Data and camera are not working.
Sadly you won't find a ROM with these. Or tell me which one.
You may try this Oreo for camera: https://forum.xda-developers.com/t/...-resurrection-remix-os-6-2-x-discont.3865882/
djibe89 said:
Hi, you have to be careful and download ROM according to your model.
Only camera is working.
If netowrk is not, you probably have chosen the wrong ROM.
Click to expand...
Click to collapse
I haven't downloaded any custom ROM yet since I need the Radio Interface Layer funcionality as well as the camera.
I have the T819 (LTE variant) but I would like to have a newer Android version than 7 because some apps are not supported anymore.
bulldozerecske said:
I haven't downloaded any custom ROM yet since I need the Radio Interface Layer funcionality as well as the camera.
I have the T819 (LTE variant) but I would like to have a newer Android version than 7 because some apps are not supported anymore.
Click to expand...
Click to collapse
Hi, you won't find better ROM except that Data and camera don't work.
For camera you may try this Oreo ROM: https://forum.xda-developers.com/t/...-resurrection-remix-os-6-2-x-discont.3865882/
bulldozerecske said:
I haven't downloaded any custom ROM yet since I need the Radio Interface Layer funcionality as well as the camera.
I have the T819 (LTE variant) but I would like to have a newer Android version than 7 because some apps are not supported anymore.
Click to expand...
Click to collapse
LineageOS 16 has RIL working, at least on the T719.
succefully installed. Thnak you !
Tutorial updated for Netflix and Disney+
sorry for this but i failed and i need help
i did every thing until wipe but afterwards my PC unable to see device folders so i can load the files
side note: didn't backup also so stuck on recovery screen
help please!!!
Thanks for this, works exactly as stated...
However I misread it, "### Camera doesn't work, 3G/Data network doesn't work" - I thought oh I don't care about 3G, I'm always connected to LTE without my brain acknowledging that it's all cellular connectivity not just 3G. DOH.
Is there anything available for SM-T817V? Looking desperate help to update Android 10.
Thanks
fmc000 said:
LineageOS 16 has RIL working, at least on the T719.
Click to expand...
Click to collapse
any particular build? there are multiple versions Thanks
When I boot, I end up back in the TWRP main menu. I've tried:
"Reboot System and on Install TWRP App? menu, tap on button Do Not Install" after:
"Then tap on Install > choose los*.zip,
then Add more zips and select opengapps*.zip,"
(advice given in another forum) but it makes no difference: LineageOS animation continued for several minutes, then I get into RECOVERY REBOOT and back to TWRP menu.
Samsung SM-T813
lineage-17.1-20210918-UNOFFICIAL-gts210vewifi
open_gapps-arm64-10.0-nano-20210929
Magisk-v23.0
Hi @Tetenterre,
first boot leads to bootloop.
Flash > boot > force reboot and wait
Thanks for your reply, djibe89 - when I do that (ie Power & Volume down), I end up back in TWRP.
Installed successfully by following your guide to a T (although I used the latest TWRP). I know support for this old girl has probably reached it's limit, but it was tough to find the ROM file (most links in the thread are dead - had to use one from archive.org)
Thanks a lot for putting this together!
MouldeyWan_Kenobi said:
Installed successfully by following your guide to a T (although I used the latest TWRP). I know support for this old girl has probably reached it's limit, but it was tough to find the ROM file (most links in the thread are dead - had to use one from archive.org)
Thanks a lot for putting this together!
Click to expand...
Click to collapse
Hi, sorry for that.
Thanks for telling me. It's hard to keep up with all the models I support.
I'll try to fetch all files and backup these on Androidfilehost.
Thx for archive.org, didn't know it.
Enjoy

Categories

Resources