Related
DISCLAIMER: I ASSUME NO RESPONSIBILITY FOR ANY DAMAGE TO YOUR DEVICE.
So, after countless hours of tinkering and searching around the forums, I was able to successfully install V4A and Dolby onto my Pixel XL.
I realized after a while, I realized that there were many others like me who wanted this, but some were not as vigilant and gave up as the process was different depending on who you asked and everyone was giving mixed results.
I decided that I could give back a bit to the community by writing up a step-by-step tutorial on how to do this.
Even after I installed V4A successfully, I, against my own sanity, wiped my phone again and followed my own steps one by one to ensure it worked.
SO, WITHOUT FURTHER ADO, here's what I did...
STEP 1: Back up all data. Unless you don't care about that junk, then move right along.
STEP 2: Download the factory image from here: Oreo Factory Images for Pixel XL
STEP 3: Follow the steps to unlock the bootloader (guide #3) and to install the factory image (guide #4 or #5). LINK TO GUIDES BY Homeboy76
STEP 4: Follow the steps to root the device systemlessly (guide #8) LINK TO GUIDES BY Homeboy76
STEP 5: Install this BusyBox, on the top right corner, tap the 3 dots, go to settings, set the install path to /sbin/supersu/xbin and then install BusyBox.
STEP 6: Download and flash ARISE Aroma and choose what you want through the Aroma installer. (The last options I kept default, the ones that are about removing deep buffer and all the ones following that, yes, this means set SELinux to permissive, it's one of the last options, this does, indeed break SafetyNet, so if Android Pay is a must have, I would not recommend continuing.)
STEP 7: Reboot to system and enjoy better sound!
I'm no developer, I take no responsibility for the development of any of the above linked or mentioned applications. All credits go to those hardworking developers, much thanks to them! However, if this guide did help, please feel free to thank and leave a reply and share this to those who are also in the search for better audio!
jamsoolee said:
DISCLAIMER: I ASSUME NO RESPONSIBILITY FOR ANY DAMAGE TO YOUR DEVICE.
So, after countless hours of tinkering and searching around the forums, I was able to successfully install V4A and Dolby onto my Pixel XL.
I realized after a while, I realized that there were many others like me who wanted this, but some were not as vigilant and gave up as the process was different depending on who you asked and everyone was giving mixed results.
I decided that I could give back a bit to the community by writing up a step-by-step tutorial on how to do this.
Even after I installed V4A successfully, I, against my own sanity, wiped my phone again and followed my own steps one by one to ensure it worked.
SO, WITHOUT FURTHER ADO, here's what I did...
STEP 1: Back up all data. Unless you don't care about that junk, then move right along.
STEP 2: Download the factory image from here: Oreo Factory Images for Pixel XL
STEP 3: Follow the steps to unlock the bootloader (guide #3) and to install the factory image (guide #4 or #5). LINK TO GUIDES BY Homeboy76
STEP 4: Follow the steps to root the device systemlessly (guide #8) LINK TO GUIDES BY Homeboy76
STEP 5: Install this BusyBox, on the top right corner, tap the 3 dots, go to settings, set the install path to /sbin/supersu/xbin and then install BusyBox.
STEP 6: Download and flash ARISE Aroma and choose what you want through the Aroma installer. (The last options I kept default, the ones that are about removing deep buffer and all the ones following that).
STEP 7: Reboot to system and enjoy better sound!
I'm no developer, I take no responsibility for the development of any of the above linked or mentioned applications. All credits go to those hardworking developers, much thanks to them! However, if this guide did help, please feel free to thank and leave a reply and share this to those who are also in the search for better audio!
Click to expand...
Click to collapse
If this works, you are a God! I can't find Arise aroma installer in that post you linked. Are you running Dolby in permissive or is that the original one by worstenbrood?
Golf c said:
If this works, you are a God! I can't find Arise aroma installer in that post you linked. Are you running Dolby in permissive or is that the original one by worstenbrood?
Click to expand...
Click to collapse
Here's the direct link to ARISE aroma: https://www.androidfilehost.com/?fid=457095661767141554
It's the first link in the post that I linked.
And at the end of the aroma installation, it asks if you want to set SELinux to Permissive and I just set that to yes, since that's the default value.
I installed only V4A and Dolby and they both work fine.
jamsoolee said:
Here's the direct link to ARISE aroma: https://www.androidfilehost.com/?fid=457095661767141554
It's the first link in the post that I linked.
And at the end of the aroma installation, it asks if you want to set SELinux to Permissive and I just set that to yes, since that's the default value.
I installed only V4A and Dolby and they both work fine.
Click to expand...
Click to collapse
Thanks, I forgot what a convoluted mess that ARISE OP is. Lol. Might want to mention the permissive for Dolby in your OP. Let you know if it works. Im confident you got it. ?
Golf c said:
Thanks, I forgot what a convoluted mess that ARISE OP is. Lol. Might want to mention the permissive for Dolby in your OP. Let you know if it works. Im confident you got it. ?
Click to expand...
Click to collapse
Haha, thanks man, and no problem, took me a while to find it myself. Best of luck to you!
And yeah, that's what I meant by keeping everything default, since I can't remember what the exact values and options were off the top of my head now while I'm writing this up at work lol. But I'll add that part in there in a bit. :fingers-crossed:
jamsoolee said:
Haha, thanks man, and no problem, took me a while to find it myself. Best of luck to you!
And yeah, that's what I meant by keeping everything default, since I can't remember what the exact values and options were off the top of my head now while I'm writing this up at work lol. But I'll add that part in there in a bit. :fingers-crossed:
Click to expand...
Click to collapse
Thank you so much for putting in the time. I have a few hours into it myself with no luck.
Golf c said:
Thank you so much for putting in the time. I have a few hours into it myself with no luck.
Click to expand...
Click to collapse
No problem! That's the great part of this community, everyone out here (well, most of us) to help each other out.
Plenty of times I've benefited from other's hard work and write ups, just trying to pay it back in full now.
Enjoy the music my friend, I sure have. It was between buying new speakers for my car or just putting in some time to figure out how to get this to work
I'll confirm that following this guide to the T will indeed get you working ARISE/V4A on your Oreo Pixel XL. Instead of using the ARISE version in the first post I used Magnum Opus 9/8 so I'm not sure it maters what ARISE version you use so long as it's fairly current.
giant22000 said:
I'll confirm that following this guide to the T will indeed get you working ARISE/V4A on your Oreo Pixel XL. Instead of using the ARISE version in the first post I used Magnum Opus 9/8 so I'm not sure it maters what ARISE version you use so long as it's fairly current.
Click to expand...
Click to collapse
Glad to hear it!
I tried with Opus for a while, and it didn't work once for me, so it might be hit or miss, but I'm happy it's working for ya'll!
Has anyone tried this with a custom kernel?
dark2099 said:
Has anyone tried this with a custom kernel?
Click to expand...
Click to collapse
I didn't try it on a custom kernel, but from my understanding, it should work, at least that's what I found when searching about.
Will this increase the max sound from the speaker?
krazekid7 said:
Will this increase the max sound from the speaker?
Click to expand...
Click to collapse
Yes it works for me on Elemental! Yes Dolby Digital Plus will increase sound volume of you have sound leveler enabled
john7760 said:
Yes it works for me on Elemental! Yes Dolby Digital Plus will increase sound volume of you have sound leveler enabled
Click to expand...
Click to collapse
Elemental Kernel has a volume mod itself.
Sent from my Pixel XL using Tapatalk
I had Arise installed then at some time my phone reboot (possible kernel panic?) and when I unlocked my phone it asked me to disable Arise. Now I have to do this process all over again.
r80ies said:
I had Arise installed then at some time my phone reboot (possible kernel panic?) and when I unlocked my phone it asked me to disable Arise. Now I have to do this process all over again.
Click to expand...
Click to collapse
Google Play Protect thinks it's malware and automatically disables it. Everything is still there. Go into app settings and enable it again. Everytime it scans apps this will happen. I have to find away around this or disable Google play protect.
r80ies said:
I had Arise installed then at some time my phone reboot (possible kernel panic?) and when I unlocked my phone it asked me to disable Arise. Now I have to do this process all over again.
Click to expand...
Click to collapse
Don't worry, as Golf c has said, it'll be there, you can ignore the warnings. I got these a few days in as well and just ignored them and everything was fine.
Golf c said:
Google Play Protect thinks it's malware and automatically disables it. Everything is still there. Go into app settings and enable it again. Everytime it scans apps this will happen. I have to find away around this or disable Google play protect.
Click to expand...
Click to collapse
Looking into what we can do about this, but honestly, I think it's fine to just ignore the warning whenever it pops up.
Thanks to this mod and you friend. Working good...
dark2099 said:
Has anyone tried this with a custom kernel?
Click to expand...
Click to collapse
Ya I'm on ex kernel and it works fine.
Couldn't make it work with Magisk. Might have to go back to SuperSU. Can't live without it for too long.
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?
First of all, excuse me if something is wrong or written. (Google translator)
I am one of those people who still use Xposed, the reason is that I use the variant of 2GB of ram and 16GB of internal memory and what helps me cope with it is Xposed and the module XinternalSD and ObbonSD.
The problem is that when installing Xposed both in its version flasheable and its version in magisk cause bootloop.
I read in the forums dedicated to the moto g5 that also happens to them this same thing they solved using a custom kernel.
What can be done?.
~Ángel Heldens said:
First of all, excuse me if something is wrong or written. (Google translator)
I am one of those people who still use Xposed, the reason is that I use the variant of 2GB of ram and 16GB of internal memory and what helps me cope with it is Xposed and the module XinternalSD and ObbonSD.
The problem is that when installing Xposed both in its version flasheable and its version in magisk cause bootloop.
I read in the forums dedicated to the moto g5 that also happens to them this same thing they solved using a custom kernel.
What can be done?.
Click to expand...
Click to collapse
You're right, I can say it for I've tried it myself.
I wanted to install it so as to use "gravity box"
For the moment, since there's no final stable version of the 8.1 firmware, I think nothing can really be done ...
But I wonder what developers think about it ... It's a challenge that's worth it ?
It's work, but you need to do a simple trick, check my post.
brundark said:
I installed normally on magisk, the trick is on restart, the first restart to enable the xposed module should normally be done using "normal reboot", then open the xposed and you will get a yellow error, click the three dots to show the settings of the xposed, and go on 'fast reboot', it will work. And you will not be able to do a normal 'reboot', whenever you need to restart, use the option 'fast reboot'. NEVER restart the phone using normal mode, just using the "fast reboot"
it's important you always have the magisk uninstaller ( https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/)
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...est-update-t3871136/post78508918#post78508918
brundark said:
It's work, but you need to do a simple trick, check my post. https://forum.xda-developers.com/mo...est-update-t3871136/post78508918#post78508918
Click to expand...
Click to collapse
¿but I would not have to restart in the traditional way, no ?.
brundark said:
It's work, but you need to do a simple trick, check my post. https://forum.xda-developers.com/mo...est-update-t3871136/post78508918#post78508918
Click to expand...
Click to collapse
I tried, it did not work.
Ok my friends, it's true that family moto g6 (specifically g6 play) will receive android 10? if it's possitive... When will we have news about this?
Also ... does anyone know if there is any rom in development with android 10 for this model (lineage, RR, etc.)?
If anyone knows about this, I think several would appreciate this valuable information.
Answer 1, just wait for Moto to announce it, usually they announce when there gonna do a soak test of a new Android version so whenever Moto does that will be some sort of answer however soak test usually go on for a few months basically it's prolly gonna be almost another year before we hear anything I mean we just got official pie about 2 months ago now after they did soak test for months.
Answer 2, there is not even a custom rom like rr or anything for this device for Oreo or pie so doubtable. Best you can do is try out gsi A only builds, custom rom means it's made specifically for this device where as gsi is compatible with any phone that shipped with Android 8. There is a gsi thread you can out
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
PimpMy5Ton said:
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
Click to expand...
Click to collapse
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Spaceminer said:
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Click to expand...
Click to collapse
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
PimpMy5Ton said:
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PCP29.118-41
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Glad to have it running with Pie and more stable, those are great news
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Can you guide us? I install the test img but cant boot on pie vendor
Grom9A said:
Can you guide us? I install the test img but cant boot on pie vendor
Click to expand...
Click to collapse
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
ry755 said:
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
Click to expand...
Click to collapse
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Grom9A said:
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Click to expand...
Click to collapse
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
I want to try but can't root this rom
Grom9A said:
I want to try but can't root this rom
Click to expand...
Click to collapse
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
ry755 said:
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Click to expand...
Click to collapse
Maybe I flashed the wrong boot.img... I might've mixed up Oreo and Pie boot images. I have both firmwares sitting right next to each other.
Spaceminer said:
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
Click to expand...
Click to collapse
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
ry755 said:
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
Click to expand...
Click to collapse
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Spaceminer said:
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Click to expand...
Click to collapse
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
ry755 said:
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
Click to expand...
Click to collapse
I'll check it out and see what I can do. That's not surprising though. It's extremely alpha, so he's probably just prioritizing stock functionality over everything else right now.
I can't get it rooted, but v202 just went up, so I'm going to try my luck with it.
Wait is over..
Installing viper in Realme UI is a nightmare..
Now it's a piece of cake..
Needed:
1. OS - Realme UI
2. Magisk 20.3 or above
3. Titanium apk
4. Overlay mount fix 2.1 magisk module
5. Viper module 2.7.1.6 magisk module
6. Root explorer
Steps:
1. Install Titanium apk and freeze Dolby apps ( 2 entries will there)
2. Install overlay in magisk and don't reboot
3. Install viper in magisk and don't reboot
4. Open viper app and provide root permission and install the drivers and reboot
5. After reboot open the viper app it shouldopen successfully but now WiFi ,camera,hotspot ,screen rotation will not work ( may be many things will not work but viper will work fine )
6. Now go to magisk and disable the overlay ( don't delete the module) and reboot
7. After reboot everything will work fine but viper app will say driver not found
8. Now open root explorer and go to location
/data/adb/modules/overlayfix , you will find 2 folders system and vendor , delete the culprits.. both..
9. And enable the overlay in magisk and reboot
10. Now everything should be working fine including viper will open successfully along with drivers installed
For C06 update
1. Follow steps till 5
2. In Step 6 , don't reboot
3. Skip step 7
4. Follow step 8 till end
Enjoy fellows
Tested in devices/version
1. Realme xt C05, C01
2. Realme 5 pro
Not sure on other version..may be you can try..
If any bootloops during restart then follow
https://forum.xda-developers.com/realme-xt/how-to/remove-magisk-module-cause-bootloop-t4093111
For autostart viper for every boot :You can enable startup in viper app info setting
It may work on realme.5.pro?
Madhuvrata said:
It may work on realme.5.pro?[/QUOTE
You can try..
If any bootloops during restart then follow
https://forum.xda-developers.com/realme-xt/how-to/remove-magisk-module-cause-bootloop-t4093111
Click to expand...
Click to collapse
I tried and it just works without any further gymnastics. Only after reboot I have to open manually viper app. Otherwise everything works
Madhuvrata said:
I tried and it just works without any further gymnastics. Only after reboot I have to open manually viper app. Otherwise everything works
Click to expand...
Click to collapse
Did you do as per above steps ? Or simply install viper app and working fine?
You can enable startup in viper app info setting
I can't find location to delete files. Can somone help please?
Madhuvrata said:
I can't find location to delete files. Can somone help please?
Click to expand...
Click to collapse
Use root explorer.
Then locate the folder
/data/adb/modules/overlayfix
Check if you installed overlay magisk module in magisk
If you have already deleted the folders then chk if viper is working fine
I have ainur narsil installed
Do i need audio modification library module with this?
Thank you.
mido hamdy said:
I have ainur narsil installed
Do i need audio modification library module with this?
Thank you.
Click to expand...
Click to collapse
I think yes..I'm not using ainur.
Hello developers,
I really need your help, I tried installing the viper with the mentioned method, it worked fine, and I deleted the folders/files in overlay fix, but still all my sensors have stopped working, I thought to give a try installing custom ROM would fix this, nothing happened, again installed stock relame UI ROM still no sensor working, please help me how to get it resolved.
Light
Gravity
Gyroscope
Magnetic
Not working...
Please help....
Thanks in advance.
tausif55555 said:
Hello developers,
I really need your help, I tried installing the viper with the mentioned method, it worked fine, and I deleted the folders/files in overlay fix, but still all my sensors have stopped working, I thought to give a try installing custom ROM would fix this, nothing happened, again installed stock relame UI ROM still no sensor working, please help me how to get it resolved.
Light
Gravity
Gyroscope
Magnetic
Not working...
Please help....
Thanks in advance.
Click to expand...
Click to collapse
Which Rui version, which phone model?
Have you installed any other magisk modules?
If you disable the overlay in magisk , gravity gyroscope working?
Hi, Thanks for your response.
I tried disabling the modules.
Right now I am again in Stock rom, Realme UI RMX1921_11_C.05, it has replaced my Orangefox recovery and I have unlocked bootloader.
I remember the fingerprint stopped working after unlocking bootloader and rooting, this is also one of the issue now.
Have gone through net that I should not lock bootloader again or i will end up again in crashing the bootloader.
I know how to flash stock firmware with MSM but it asks for username and password.
tausif55555 said:
Hi, Thanks for your response.
I tried disabling the modules.
Right now I am again in Stock rom, Realme UI RMX1921_11_C.05, it has replaced my Orangefox recovery and I have unlocked bootloader.
I remember the fingerprint stopped working after unlocking bootloader and rooting, this is also one of the issue now.
Have gone through net that I should not lock bootloader again or i will end up again in crashing the bootloader.
I know how to flash stock firmware with MSM but it asks for username and password.
Click to expand...
Click to collapse
Can you try viper method again and try ...delete both viper and overlay in magisk and try..
Alternate to V4A
If someone is looking for hassle free way with alternative for V4A ..Try Wavelet app full version ...Its sounds Engine for bluetooth is top notch almost good as V4A.
optimizations are way good from well know tuned sources to choose from.
Regards,
Diaz M
Hi....I don't have any laptop to format as of now....but today I tried otg and it is also not supporting now. :'(
I've faced 2 things
1. when searching in titanium for dolby can't find 2 items , i found one item named "dolby on 1.1.0"
and freezed it.
2. after installing modules ,opening viper it asks for root permissions that i agreed for it and it rebooted to install drivers , but after reboot it seems the driver not installed and ask for installing again.
What the problem with that ?
My Phone is R5 Pro global 128/4 On update C.05.
Mstf_Ata said:
I've faced 2 things
1. when searching in titanium for dolby can't find 2 items , i found one item named "dolby on 1.1.0"
and freezed it.
2. after installing modules ,opening viper it asks for root permissions that i agreed for it and it rebooted to install drivers , but after reboot it seems the driver not installed and ask for installing again.
What the problem with that ?
My Phone is R5 Pro global 128/4 On update C.05.
Click to expand...
Click to collapse
Follow the steps of installing the magisk modules..Did you delete the folders using root explorer..and enable the overlay ?
akashavel said:
Follow the steps of installing the magisk modules..Did you delete the folders using root explorer..and enable the overlay ?
Click to expand...
Click to collapse
Because i found that Viper driver not installed, i didn't do the next steps.
Mstf_Ata said:
Because i found that Viper driver not installed, i didn't do the next steps.
Click to expand...
Click to collapse
pls do all steps ..If not working follow the C06 steps ..
akashavel said:
pls do all steps ..If not working follow the C06 steps ..
Click to expand...
Click to collapse
Thanks , I'll Try and inform about my experience.