Related
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
vybztymz said:
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
Click to expand...
Click to collapse
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Rootk1t said:
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Click to expand...
Click to collapse
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
vybztymz said:
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
Click to expand...
Click to collapse
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
marcusorwen said:
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
Click to expand...
Click to collapse
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Use flashtool and simply flash any stock version on top.
Alternatively, you can use some non stock ROM, but for that your first need to install the custom recovery via fastboot.
vybztymz said:
Any suggestions welcomesed
Click to expand...
Click to collapse
Have a look at this guide for installing a CM ROM
vybztymz said:
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Click to expand...
Click to collapse
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Lost Root after installing CN12 Nightly (Lollipop 5.0x)
marcusorwen said:
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Click to expand...
Click to collapse
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
vybztymz said:
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
Click to expand...
Click to collapse
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
marcusorwen said:
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
Click to expand...
Click to collapse
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
[EDIT] In Developer Options, and under "Root Access" it says "Disabled"
[EDIT 2] Downloaded a RootChecker and it tells me I'm not rooted
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
vybztymz said:
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
Click to expand...
Click to collapse
Yea i know what you mean by guides not being written to include alot of details and missing out on small stuff that might be important, but anyway.
In the Developer Options there should be a box called Root Access, and it should be defaulted to Disabled ones you have installed CM12 for the first time, its just a matter of enabling this.
Im guessing you already know how to enable Developer Options, but if you dont here is how:
Go to About Device (or Phone/Tablet) and click on Build number a bunch of times (i think its 5-6 times), and the developer options should be visible in the settings.
If that dosent work you might want to try and flash the SuperSU binary through recovery, the zip to use is the one found in chainfires xda-thread here: http://forum.xda-developers.com/showthread.php?t=1538053
But here is the direct link for the zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Just put that on your device internal memory (or SD-Card) and flash it in your recovery of choice, it should work in CWM, TWRP and Odin (but you dont have a samsung so the last one dosent matter).
This should install the SuperSU app, and its basic su binary onto your CM12 rom.
In both cases i would recommend you install root checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck) and see if root is available to you.
Also to note is that the Root Access option built into CM12 isnt that customizable and i would still recomend you install SuperSU, but if the Root Access option is working you can just download the SuperSU application from the play store and let it install SU binary and then you can disable CM12's built in root option ones you make sure the SuperSU was installed correctly.
Thanks so much for your help/patience......but i'm afraid im giving up (for now).
Will try again in a few days......so its back to rooted stock 444
By the way, why have CM decided to go with their own (as good as useless) recovery????
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
vybztymz said:
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
Click to expand...
Click to collapse
No problem, if you have any other questions just tell me and i might be able to help you
I have also been in the dark about this stuff before, and im still not used to other manufacturers style of rooting and unlocking the bootloader (sony is the next best after Nexus) since samsung and the others usually you have a harder time unlocking and rooting.
But good luck if you try it again :victory:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
EDIT: New OTA [YNG1TAS17L]:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS17L-bacon/e816218e8a/cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Credits to @julian_klode:
https://forums.oneplus.net/threads/flashable-zip-enable-integrated-superuser.75511/
Note: I initially wasn't aware about the source of the base zip file that I used to pack the necessary files until julian_klode mentioned it in the Q&A thread.
There is no difference between this one and his, just the fact that I update mine manually. So, I think you should follow his thread instead.
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Outstriped! I was thinking to make Debug kernel, but they released it sooner
Thank you so much. Puzzle and Dragons doesn't like Supersu, but works perfect with CM's superuser.
works fine here, thanks!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
thank you , works perfectly!
inscythe said:
Some people, like me, prefer CM's own root. Integration with Privacy Guard is pretty nifty, you know?
Click to expand...
Click to collapse
thx:good:
Works great please keep this updated with each OTA if possible!
Vivek_Neel said:
Or just flash the SuperSu zip via recovery.
Sent from my A0001
Click to expand...
Click to collapse
That did not work for me
droidextra said:
That did not work for me
Click to expand...
Click to collapse
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
srgudhka said:
sorry for my noob question. but i actually flashed supersu. that wont affect anything. i am asking this cause yesterday i had to factory reset my device 4 times as it got stuck at cyanogen boot animation. It would boot fine couple of times and then get stuck.
Click to expand...
Click to collapse
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
inscythe said:
I have never tried SuperSU in my OPO Lollipop since I found out about the built-in root support, so I can't say what's wrong with it. Bootloops may be caused by stuck up boot process, which may be caused by kernel.
If I'm not wrong, I remember last time when Lollipop launched that SuperSU need to patch the kernel in a certain way for it to run properly. My solution also works with a different kernel, albeit it is provided officially by Cyanogen.
If you really want SuperSU for some reason, you can try flashing SuperSU and then flash the boot.img from the link above (or extract it from my zip). Latest TWRP will do it just fine.
Click to expand...
Click to collapse
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
All good here! I went into the Supersu settings and did a FULL UNINSTALL OF ROOT. Once that was done, I went into TWRP and flashed CM zip provided by OP... Bam. Done and no problems. Thank you, OP!
Wisiwyg said:
SuperSU plus CM root don't play well together. Take a look through Caulk's stock 5.0.2 thread and you'll see several people having problems - manifested by flashing SuperSU and then trying to open Developer Options. It FCs. Just use the built-in CM root or disable CM root before you flash SuperSU.
Click to expand...
Click to collapse
I perhaps wasn't very clear about my above suggestion.
What I meant is that, there is an official insecure boot.img (the kernel) which I linked above and included in my zip package. I'm not telling him to install both SuperSU and the built-in root.
SuperSU has some features that is not present in the built-in root though, like logging or tapjacking protection. Privacy Guard is pretty nifty, but I still miss the old interface of SuperSU.
inscythe said:
Hi all,
Just want to help a bit with the CM12S. Flash the attached zip if you want root in apps and ADB.
I grabbed a debuggable boot.img from the official CM servers here:
Code:
http://builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-boot-debuggable.img
Then, I simply put them in a flashable zip format together with su binary from the latest CM12 nightly. I have tested it on my own phone and so far, there is no issue.
I have only tested it using TWRP, flash on your own risk.
Click to expand...
Click to collapse
Is there any way to make this work with franco kernel r41? Thanks...
ten_tickles said:
Is there any way to make this work with franco kernel r41? Thanks...
Click to expand...
Click to collapse
I think it's the issue with Franco's own kernel... Even the nightly CM12 users with the built-in root enabled also had the root access disabled.
SuperSU works in this case because it relies on an init.d su-enabling service.
Just wait for Franco to fix it, since the CM11S versions works well with the built-in root. I am also a FK paid user, so this is a bad situation for me as well...
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
I uploaded it here sorry it's not a better host but I'm on my phone ATM lol. http://uploadmirrors.com/download/R8ADOYOG/icial-12.0-signed-YNG1TAS17L-bacon-superuser.zip All I did was get the ota URL from here and changed the ending to cm-12.0-YNG1TAS17L-bacon-boot-debuggable.img I guess the system automatically makes the debug images when the ota rolls out. So I imagine the same thing would work for next ota. You just rename it to boot.img and replace the one in the zip from this thread and rename the zip and flash.
Link_of_Hyrule said:
If you could update this asap to the YNG1TAS17L build that would be awesome thanks a lot for your hard work! Edit: nvm was able to make my own.
Click to expand...
Click to collapse
Not that hard to make, right? But super practical to keep this if you often jumping ROMs.
SimonTS said:
Care to share it? I presume that the version in the OP won't work with the new v5.02 OTA?
Click to expand...
Click to collapse
Sorry, was doing overtime at work. I've updated the OP too.
Hi everyone!
I know this is asked many times about rooting and you must had enough of it, though I am new to rooting scene and would like to know more about rooting.
Recently I have tinkered around my old Xperia Tablet Z WiFi (pollux_windy). I managed to unlock the bootloader (warranty is long gone at this point), installed TWRP for recovery and also installed a custom ROM Lineage OS in one of the trending topics. I must say it runs very well and love how it supercharges my device.
There are some features and specialty apps I want to try out and they require root access. I have read the advantages and disadvantages of rooting, I am not too keen on the idea of bricking my device if I don't know what I am doing, so I figure I get some directions on how to do this from you guys.
I have searched the web as much as I can but would like some reassurance in my findings so I know I am in the right track, as the information dates back in 2013-2014 which sounds very old and I am unsure if that info is outdated. I basically need to know what I need to do. Do I have to reinstall the original stock ROM and use the exploit there? or there is a simpler way to go around it? I basically want to know the tools required and the files to make it happen on my current situation, where do I go from there?
I appreciate your time for tuning in and look forward to reading some feedback.
Kind Regards,
One confused guy.
dude777 said:
is or there is a simpler way to go around it? I basically want to know the tools required and the files to make it happen on my current situation, where do I go from there?
Click to expand...
Click to collapse
On custom ROMs it's pretty simple. On CM14.1 you need to enable root in settings. On lineageOS just install SuperSU or SU zips from recovery.
Rootk1t said:
On custom ROMs it's pretty simple. On CM14.1 you need to enable root in settings. On lineageOS just install SuperSU or SU zips from recovery.
Click to expand...
Click to collapse
Oh wow it's that simple? So I just download the SuperSU zip, install through the recovery and it will be rooted? Does this process reset any settings alone? I would also assume if move to a different ROM then I'll have do this again?
Look forward to your response.
dude777 said:
Oh wow it's that simple? So I just download the SuperSU zip, install through the recovery and it will be rooted? Does this process reset any settings alone? I would also assume if move to a different ROM then I'll have do this again?
Look forward to your response.
Click to expand...
Click to collapse
It will not reset any settings. If you move to a different ROM you''ll need to do it once again. Though it depends on ROM, as some (Resurrection Remix, CrDroid) have built-in root, which can be enabled in settings.
Rootk1t said:
It will not reset any settings. If you move to a different ROM you''ll need to do it once again. Though it depends on ROM, as some (Resurrection Remix, CrDroid) have built-in root, which can be enabled in settings.
Click to expand...
Click to collapse
Rootk1t, you're the man it worked very well and now I can do some root stuff, thanks for your help.
Kind Regards,
Happy Guy!
Hey guys, I have a rooted US998 with magisk running on oreo. I was able to successfully install the latest viper4android, version 2.5.0.4, and driver installation went well. I rebooted, and when I check driver status, it says "enabled: yes status: normal". So you would think everything would be working fine. However, when I enable V4A, I hear no difference in the sound. I have an eq and several other changes, so I should definitely hear a difference in SQ when I enable V4A. I have tried both in neutron and poweramp. In poweramp, I turned off DVC (direct volume control), as the app suggest.
Any suggestions? To me, it seems that something on the phone is "overriding" the V4A output settings.
Thanks!
i can also confirm that turning the quad dac on or off makes no difference. Viper still doesn't do anything.
[/ATTACH]Working fine here
I've installed it with magisk
It's version 2.5.05
ricohz said:
Working fine here
I've installed it with magisk
Click to expand...
Click to collapse
you are using an earlier version than I am. I am going to uninstall the version I have now, and try to install through magisk modules the version you have and see if it works.
The version I installed was an apk downloaded from the official xda app thread.
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
You can edit your thread topic to say SOLVED.
Sent via open market LG US998 V30/V30+
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
If you like the material design that much, you can get the material look back. Reflash that same Viper4Android. Just pay close attention to the installation log in Magisk Manager and press Up on the Volume when it says "Test mode". Then you can select the "Material" design instead of Original before selecting which sound driver version you'd like.
I would like to know what you are saying about the sound with DAC in connection with Viper4Android. Is there now Rome, where you can turn on the DAC, but not the default settings of LG has? because I found that faked the sound with Viper. Would be glad about feedbacks. I'd love to use only viper, but with the built in DAC together it sounds better again. but just without the stupid sound profiles of LG.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
So are you saying you chose the older version in the magisk module?
Nothing I do seems to work.
Sent from my LG-H932 using XDA Labs
Install the fallowing Magisk Modules ViPER4Android FX, Audio Compatibility Patch, Audio Modification Library and Selinux Permissive reboot and you should be good to go.
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
AndreSkywalker said:
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
Click to expand...
Click to collapse
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
nazagato said:
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
Click to expand...
Click to collapse
So a more modern android version won't work? That's a huge bummer to be honest.
Maybe try to get Dirac like in HavocOS cause it seems realy good
Triparadox said:
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
Click to expand...
Click to collapse
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
AndreSkywalker said:
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
Click to expand...
Click to collapse
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Triparadox said:
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Click to expand...
Click to collapse
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Triparadox said:
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Click to expand...
Click to collapse
Happened same to me yesterday.I tried dolby and it crashed.So now I'm using Viper4Android, it works great.I can send you settings for headset:
Headset
Master Power: ON
PlaybackAGC: ON
Effect Strength: Moderate
Firequalizer: ON
Preset: R&B
Headphone Surround: ON
Effect Level: 2
Viper Bass: ON
Bass Boost: 3.5dB
Viper Clarity: ON
Clarity: 3.5dB
Cure Tech+: ON
Binaural Level: Extreme
Cheers
AndreSkywalker said:
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Click to expand...
Click to collapse
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Triparadox said:
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Click to expand...
Click to collapse
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
AndreSkywalker said:
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
Click to expand...
Click to collapse
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Triparadox said:
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Click to expand...
Click to collapse
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
AndreSkywalker said:
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
Click to expand...
Click to collapse
i don't see any module.
Triparadox said:
i don't see any module.
Click to expand...
Click to collapse
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
AndreSkywalker said:
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Click to expand...
Click to collapse
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Triparadox said:
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Click to expand...
Click to collapse
I use dolby atmos with viper4android. Dolby atmos is effective with the headset, without the headset it doesn't work very loudly, while viper4android works both ways.