ViperAudio on latest betas/Magisk 13+ - OnePlus 3 Themes, Apps, and Mods

Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.

I believe It's because it requires new magisk template. Give developers some time to update.

working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.

MarcTremonti said:
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
Click to expand...
Click to collapse
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.

theduke7 said:
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
Click to expand...
Click to collapse
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.

MarcTremonti said:
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
Click to expand...
Click to collapse
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!

theduke7 said:
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
Click to expand...
Click to collapse
Yea bluspark is enforcing. I guess they are on gitlab from freedomOS.(check FOS thread for gitlab link)
But i guess easiest way would be just to flash freedomOS. Its nothing else anyway, than debloated stock ROM with a few tweaks. Everything selectable in aroma to your needs.

Try this...
kokesh said:
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
Click to expand...
Click to collapse
You can try this:
Update to the latest Magisk version and get everything set. for example, Snapchat and other apps that you might need to pass safety.
After that, you can downgrade to the V.12.0. And V4A it should work fine.
The only bad thing here is that you can't use Android pay or pass safetynet.

This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342

I use the one from ahrion, too. Works fine.

I am 6
Sent from my ONEPLUS A3000 using Tapatalk

siwan05 said:
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
I've tried both. It installs, but once I launch Viper, it asks either for driver install, or shows the driver state as abnormal. Never has any effect on the audio.

Related

Problem with Xposed + COS13

Hi guys, after a long time out i've come back to XDA and installed COS13 (S2JK release).
I rooted my OnePlus One with SuperSU v. 2.65 (stable) then i downloaded and flashed xposed-v84-sdk23-arm.zip, then installed the XposedInstaller_3.0_alpha4.apk.
But when i tried to activate Xposed i got the infamous "xposed not yet compatible with SDK 23 or your processor architecture (armeabi-v7a)" error.
After some reading here and there, i found out that ppl is still fine with Xposed v.80, so i installed everything again...and i got the same error. I also tried to install supersu v 2.68 burt to no avail.
What's wrong with that? Isn't COS13 supposed to work with Xposed?
Can anyone point me out in the right direction?
Thanx in advance
i dont know how to solve your problem but I have xposed-v84-sdk23-arm working perfectly on a clean flash of COS 13 from the official full zip from cyanogen. Using supersu 2.65 stable
ben.k said:
i dont know how to solve your problem but I have xposed-v84-sdk23-arm working perfectly on a clean flash of COS 13 from the official full zip from cyanogen. Using supersu 2.65 stable
Click to expand...
Click to collapse
Thank you for confirming that it works....now that really bothers me.
Why do i get that error? I have a fresh clean COS13..
As far as i know, Xposed should work fine in selinux enforced mode..but just to make sure...are you in enforced mode?
P.S. Should i first install the app and THEN flash the framework? Does that make any difference?
Vonnegut said:
Thank you for confirming that it works....now that really bothers me.
Why do i get that error? I have a fresh clean COS13..
As far as i know, Xposed should work fine in selinux enforced mode..but just to make sure...are you in enforced mode?
P.S. Should i first install the app and THEN flash the framework? Does that make any difference?
Click to expand...
Click to collapse
xposed working fine for me, I'm using cos 13 latest rom,
Rooted
Xposed
Custom kernel
All working fine
Ok, i solved the problem...i'm a moron. I put both the kitkat and the marshmellow Xpsed apk inside the same folder...and guess which one i installed on marshmellow? LOL!

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted

Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.

Viper4Android Patch for MIUI 11 base on android 10

I am here to share the patch Viper4Android on MIUI11 BASE ON ANDROID 10.
IT'S WORKING FOR ME
PRE REQUISITE
TWRP AND ROOTED also magisk is installed.
1. INSTALL SELINUX And set it to permisive, set the app on autosatart, and reboot your device
2. Install VIPER4ANDROID APK
grant root access with ask to install driver click install then reboot device.
"You will get bootloop after you install the driver just go to recovery mode by pressing volume up and power down
3. Flash Viper4Android patch on TWRP and reboot. And Viola you have now Viper4Android perfectly installed.
Selinux
https://androidfilehost.com/?fid=4349826312261708284
Viper apk
https://androidfilehost.com/?fid=4349826312261708285
Viper patch
https://androidfilehost.com/?fid=4349826312261708283
Credits to Munchy
Just subscribe to he's channel on YouTube
does it work on other android 10 base phone?
locolyric said:
does it work on other android 10 base phone?
Click to expand...
Click to collapse
Only for Miui base custom rom
It has successfully installed, but it doesn't work at all. Mi8 UD, miui 11 20.1.16, A10.
Drivers Version: 2.5.0.4
NEON: off
Driver: off
And so on...
Attach audio effect is on and writes "all sessions but 0"
Compatibility moed doesn't help.
It works for me after installed mod systemless hosts from Magisk Manager settings. Also, i enabled auto start and other permissions for Selinux and ViPER4Android FX. Didn't get any bootloops and i don't install ViPER patch with twrp. After reboot first time phone from ViPER app, you will be prompted to install again drivers. Just repeat steps. Reboot phone when you ask in app and finally you will have mod installed and enabled.You can also delete Selinux after finish. Miui 11 with android 10
Works great on miui eu 11.0.4.0
Thank you!
Nice! Works on global stable 11.0.4.0 even without patch. Took some reboots, but now it is installed and processing. Yay! Thanks!
Any one having working DTS X IN MIUI 11 Q... getting empty screen.. can you share the steps pls
Not here. Following the steps, bootloop.
Found this link. And followed same but in middle I have used that patch mentioned in this thread to resolve the boot loop issue.
Finally my viper is working.
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-how-to-install-viper4android-t4037959
All perfect here - pocophone f1 / miui 11 android 10 / no gravity kernel last build
tatuboy said:
I am here to share the patch Viper4Android on MIUI11 BASE ON ANDROID 10.
IT'S WORKING FOR ME
PRE REQUISITE
TWRP AND ROOTED also magisk is installed.
1. INSTALL SELINUX And set it to permisive, set the app on autosatart, and reboot your device
2. Install VIPER4ANDROID APK
grant root access with ask to install driver click install then reboot device.
"You will get bootloop after you install the driver just go to recovery mode by pressing volume up and power down
3. Flash Viper4Android patch on TWRP and reboot. And Viola you have now Viper4Android perfectly installed.
Selinux
https://androidfilehost.com/?fid=4349826312261708284
Viper apk
https://androidfilehost.com/?fid=4349826312261708285
Viper patch
https://androidfilehost.com/?fid=4349826312261708283
Credits to Munchy
Just subscribe to he's channel on YouTube
Click to expand...
Click to collapse
thank you very much for this great job.. you are the best, man ???
tatuboy said:
I am here to share the patch Viper4Android on MIUI11 BASE ON ANDROID 10.
IT'S WORKING FOR ME
PRE REQUISITE
TWRP AND ROOTED also magisk is installed.
1. INSTALL SELINUX And set it to permisive, set the app on autosatart, and reboot your device
2. Install VIPER4ANDROID APK
grant root access with ask to install driver click install then reboot device.
"You will get bootloop after you install the driver just go to recovery mode by pressing volume up and power down
3. Flash Viper4Android patch on TWRP and reboot. And Viola you have now Viper4Android perfectly installed.
Selinux
https://androidfilehost.com/?fid=4349826312261708284
Viper apk
https://androidfilehost.com/?fid=4349826312261708285
Viper patch
https://androidfilehost.com/?fid=4349826312261708283
Credits to Munchy
Just subscribe to he's channel on YouTube
Click to expand...
Click to collapse
This method works for poco f1 miui eu 11.0.4.0 Android 10.
Works well in my poco f1 miui.eu 11 Android Q , Magisk 20.3, No Gravity Custom Kernel :fingers-crossed:
I use with other mods (Dolby Atmos and ICE ICESound) in this link:
https://forum.xda-developers.com/redmi-note-7/how-to/dolby-digital-plus-viper4-miui-pie-rom-t3958080
hey, you seem like you know your way around the Viper mod, I saw your posts in other threads.
yesterday I followed instructions from the link you provided and got stuck in bootload screen after installing drivers. should I have flashed the patch which was given in the OP of this thread?
What about SELinux, I'm not sure what it is, do I need to apply it? if yes, how to in this case? I have the same configuration as you, MIUI 11 FOR POCO from Xiaomi.eu +Magisk 20.3 + No Gravity Kernel
thank you in advance
If anyone else knows the answers, please share, I'd appreciate it
also, is there any place where I can find information on what is the difference between Viper 4Anroid + DDP and Airun/Sauron mod? I'm totally lost
krzylew said:
hey, you seem like you know your way around the Viper mod, I saw your posts in other threads.
yesterday I followed instructions from the link you provided and got stuck in bootload screen after installing drivers. should I have flashed the patch which was given in the OP of this thread?
What about SELinux, I'm not sure what it is, do I need to apply it? if yes, how to in this case? I have the same configuration as you, MIUI 11 FOR POCO from Xiaomi.eu +Magisk 20.3 + No Gravity Kernel
thank you in advance
If anyone else knows the answers, please share, I'd appreciate it
Click to expand...
Click to collapse
Easy, selinux changer is used to change from enforcing to permissive mode so viper can run as per normal. You need to set it as auto start for this app.
Now that you stuck in bootloop is because you haven't used twrp to install the patch. Once install, it should boot into screen.
Hey, thank you!!! Managed to install everyting and seems to work
Just one quick question, when I exit the Dolby app, there is a notification saying "Remote service has stopped" - is this the way it's supposed to be?
krzylew said:
Hey, thank you!!! Managed to install everyting and seems to work
Just one quick question, when I exit the Dolby app, there is a notification saying "Remote service has stopped" - is this the way it's supposed to be?
Click to expand...
Click to collapse
No idea on Dolby app. I'm using poco too with miui Eu Android 10 rom. Bet this is not dolby atmos app.
Have you tried to reinstall it? Or maybe try audio modification library module?
thomas140 said:
No idea on Dolby app. I'm using poco too with miui Eu Android 10 rom. Bet this is not dolby atmos app.
Have you tried to reinstall it? Or maybe try audio modification library module?
Click to expand...
Click to collapse
I think that occasional reboots during phone configuration solved the problem. Thank you for your input.
[/QUOTE][/QUOTE][/QUOTE]Does it work for pixel based evo X roms and
---------- Post added at 09:13 PM ---------- Previous post was at 09:05 PM ----------
Johnjamess said:
Does it work for pixel based evo X roms and
Click to expand...
Click to collapse
Tested it out on evo x latest build works perfect!

Is V4A working on 10.3.7?

Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Use magisk for v4A
"I've updated V4A to the 2.7.2.1 version through magisk"
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Juwapa said:
Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Click to expand...
Click to collapse
Julortiz said:
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Click to expand...
Click to collapse
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Mr.FREE_Bird said:
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Click to expand...
Click to collapse
Thanks for the shout, Mr. Freebird. So yeah I guess it is a problem with new versions of Magisk. I tried on the newest update as well, 21.2, and still couldn't get it to work.
For Julortiz and anyone needing help getting it to work again, the exact steps I did were
- Downgrade Magisk to 21.0
- Download V4A 2.7.2.1 from Magisk and open the app but do not install driver yet
- Go back to Magisk and install Audio Modification Library but do not let Magisk reboot
- Go back to V4A and let it install the driver and reboot
- After reboot, open V4A, go to settings and check Legacy Mode
- Enjoy
Also this is probably really obvious, but make sure you screenshot or take note of all other modules you have installed because downgrading will delete all modules. Again this is probably obvious, just don't be dumb like me and lose all your other modules lol

New Pixel 4a owner - have a few questions!

Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!

Categories

Resources