Related
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk
Hi,
I want to install Viper on my GS4 i9500, i am currently running Aurora rom v7 based on lollipop 5.0.1. I tried dowbloading the zip for viper4android from XDA official forum (http://forum.xda-developers.com/showthread.php?t=2191223) however none of the zips were working; everytime i download and try to extract it says "bad zip file". So can anyone please point me to a working zip file for viper4android and also help me in installing and setting it up for the first time.
Thanks.
rbhanot2 said:
Hi,
I want to install Viper on my GS4 i9500, i am currently running Aurora rom v7 based on lollipop 5.0.1. I tried dowbloading the zip for viper4android from XDA official forum (http://forum.xda-developers.com/showthread.php?t=2191223) however none of the zips were working; everytime i download and try to extract it says "bad zip file". So can anyone please point me to a working zip file for viper4android and also help me in installing and setting it up for the first time.
Thanks.
Click to expand...
Click to collapse
Mediafire link works and zip ok. Don't use your mobile internet to download the zip but a computer with broadband.
Hi,
Thanks for the reply, i have downloaded and installed Viper and its driver as well; however it is still asking to install the driver every time i open it. Is it a known issue ? If yes then how to fix it; i have followed the instructions as given in the official forum.
rbhanot2 said:
Hi,
Thanks for the reply, i have downloaded and installed Viper and its driver as well; however it is still asking to install the driver every time i open it. Is it a known issue ? If yes then how to fix it; i have followed the instructions as given in the official forum.
Click to expand...
Click to collapse
The point is that for Anhdroid 5.0 and later you'll need to set your kernel to "permissive". You can use "SELinux Mode Changer" for doing so, if you have no option to install a permanent "permissive" kernel.
BTW Please press the "thanks" buton at the bottom of my posts
Its still the same issue, its still asking to install/update the drivers and even after changing the mode with the the app you posted it still shows SELinux in enforcing mode. Doesn't standard Linux commands like "sestatus" work android ? How to i permanently set the SELinux mode to Permissive rather than Enforcing ?
Isnt there any config file for selinux where i can make the change and then reboot the phone ?
rbhanot2 said:
Its still the same issue, its still asking to install/update the drivers and even after changing the mode with the the app you posted it still shows SELinux in enforcing mode. Doesn't standard Linux commands like "sestatus" work android ? How to i permanently set the SELinux mode to Permissive rather than Enforcing ?
Isnt there any config file for selinux where i can make the change and then reboot the phone ?
Click to expand...
Click to collapse
Are your sure about you granted root permissions for both apps? Which superuser app is actually installed on the phone?
LS.xD said:
Are your sure about you granted root permissions for both apps? Which superuser app is actually installed on the phone?
Click to expand...
Click to collapse
Yes i did gave root permission to both the apps; currently i am running SuperSU by Chainfire.
How can i fix this ?
Hey guys,
I'm into the Android from the very beginning and I would love to get rid of a problem which is driving me crazy for some time
I was trying to flash the Viper driver to get the great sound quality again. I'm now on the latest nougat.
Already unlocked the bootloader, rooted it and flashed the TWRP. Saw an thread about how to install it properly on the Honor8 and I did everything correct in my opinion.
I have the 1.26.2-meefik busybox now installed in system/xbin path (which seems to be working correctly overall) and otherwise everything seems working good except that when I try to open the Viper it says that I don't have root OR that i have to install the driver, and after pressing yes my phone just reboots and does the very same thing as previously.
Am I missing something?
Feel free to ask something more if you need.
I had this same situation, just kept installing the driver, reboot, repeat, making no progress... I finally got mine to work thank goodness! Are you remembering to use a root file Explorer and go to /vendor/etc and rename the file named audio_effects.config to audio_effects.config.bak after flashing but before installing V4A? That was my main problem. And you have to be sure to do it on a clean setup, so if you've already installed V4A you need to clean out and start again. Also u need a kernel auditor to set selinux to permissive upon boot. These two steps are key...
Sent from my HUAWEI FRD-L04 using XDA Labs
Have same problem but this fix BigBrad75 gave didn't work.
Isn't that what I suggested? Not being a smarta**, but seriously wondering if I have got a step messed up or backwards or something...? Cause it gave me tons of trouble till I finally got lucky and it actually took
Sent from my HUAWEI FRD-L04 using XDA Labs
Rommco05 said:
I got same problem, solutions for my was:
1. install BusyBox by Meefik ( Google play)
2. install Kernel Adiutor ( https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk ) ( Kernel Adiutor from Google play dont work)
3. opem BusyBox tap Install
4. open Kernel Adiutor and go to Misc Controls, change Current SELinux Status: Permissive (after reboot SELinux stay premissive :good
5. flash Viper4 via TWRP
6. go to folder: root/vendor/etc and rename file from audio_effects.conf to audio_effects.conf.bak
7. open Viper4
8. Install driver (thats can take 1-3 min)
9. reboot - done
Click to expand...
Click to collapse
Hi Rommco05,
there are different versions of V4A floating around. Which Version of Viper4Android did you use? Download from where?
Greets....
Rommco05 said:
Hi, Honor 8/Theme,Apps,Modes/https://forum.xda-developers.com/honor-8/themes/viper4android-2-5-0-5-installation-t3468389
Click to expand...
Click to collapse
Thanks, worked for me just as you described. I'm on L09C432B389 BTW, if anybody is interested...
Thanks
Has anyone managed to get V4A functioning on stock, rooted Oreo? I've tried every option out there. Usually end up with it acting like it didn't install the driver after rebooting. I've tried putting the system in RW, switching selinux to permissive, installing BusyBox, etc. Have tried flashing it through recovery, installing through the apk, installing the magisk module, no luck. Hopefully someone can steer me in the right direction.
Edit 12/5/17:
Navigate to downloads in magisk manager, download the latest version of viper4android by ahrion, flash the file, then reboot.
Using some form of root file browser, I use MiXplorer, navigate to /sbin/.core/img/ViPER4AndroidFX/system, create a new folder called vendor in there, then copy the folder called lib and paste it into the vendor folder you made.
The end result should be /sbin/.core/img/ViPER4AndroidFX/system/vendor/lib. The final step needs a terminal emulator app downloaded, using the app, copy and paste the following in:
su -c ln -s /sbin/.core/img/audmodlib/system/vendor /sbin/.core/img/audmodlib/vendor
Finally, navigate to /sbin/.core/img/audmodlib/system/vendor/etc and open htc_audio_effects.conf, there will be a line for v4a_fx followed by a line called "path" and the path for the library, just change "system" to "vendor", then reboot, you should be successful
Crimsonshadow774 said:
Has anyone managed to get V4A functioning on stock, rooted Oreo? I've tried every option out there. Usually end up with it acting like it didn't install the driver after rebooting. I've tried putting the system in RW, switching selinux to permissive, installing BusyBox, etc. Have tried flashing it through recovery, installing through the apk, installing the magisk module, no luck. Hopefully someone can steer me in the right direction.
Click to expand...
Click to collapse
please tell me how to root U11 Oreo?
dangtoi1993 said:
please tell me how to root U11 Oreo?
Click to expand...
Click to collapse
Just flash TWRP and then flash Magisk.
Crimsonshadow774 said:
Just flash TWRP and then flash Magisk.
Click to expand...
Click to collapse
what version of TWRP, the lasest version unoffical not work on me.
dangtoi1993 said:
what version of TWRP, the lasest version unoffical not work on me.
Click to expand...
Click to collapse
I flashed this version twrp-3.1.1-2_UNOFFICIAL-ocn.img
dangtoi1993 said:
what version of TWRP, the lasest version unoffical not work on me.
Click to expand...
Click to collapse
I grabbed the latest unofficial one as of 11/28 and everything flashes fine for me.
joshzdad2013 said:
I flashed this version twrp-3.1.1-2_UNOFFICIAL-ocn.img
Click to expand...
Click to collapse
Crimsonshadow774 said:
I grabbed the latest unofficial one as of 11/28 and everything flashes fine for me.
Click to expand...
Click to collapse
i tried this TWRP https://forum.xda-developers.com/htc-u11/development/unofficial-htc-u11-twrp-recovery-t3706264 twrp-3.1.1-2_UNOFFICIAL. flash process fine. but then i boot to recovery nothing happen, the phone go power off.
There is a new version out, 3.2,, go here and select your device https://twrp.me/Devices/HTC
Thanks to user Secone00, I was finally able to get Viper running. I have updated the OP with the instructions.
Crimsonshadow774 said:
Has anyone managed to get V4A functioning on stock, rooted Oreo? I've tried every option out there. Usually end up with it acting like it didn't install the driver after rebooting. I've tried putting the system in RW, switching selinux to permissive, installing BusyBox, etc. Have tried flashing it through recovery, installing through the apk, installing the magisk module, no luck. Hopefully someone can steer me in the right direction.
Edit 12/5/17:
Navigate to downloads in magisk manager, download the latest version of viper4android by ahrion, flash the file, then reboot.
Using some form of root file browser, I use MiXplorer, navigate to /sbin/.core/img/ViPER4AndroidFX/system, create a new folder called vendor in there, then copy the folder called lib and paste it into the vendor folder you made.
The end result should be /sbin/.core/img/ViPER4AndroidFX/system/vendor/lib. The final step needs a terminal emulator app downloaded, using the app, copy and paste the following in:
su -c ln -s /sbin/.core/img/audmodlib/system/vendor /sbin/.core/img/audmodlib/vendor
Finally, navigate to /sbin/.core/img/audmodlib/system/vendor/etc and open htc_audio_effects.conf, there will be a line for v4a_fx followed by a line called "path" and the path for the library, just change "system" to "vendor", then reboot, you should be successful
Click to expand...
Click to collapse
I don't have .core in sbin. Rooted with magisk. Please suggest a solution.
You are used SuperSU or Magisk for root.
You can share link file flash Viper4Andriod on android oreo version.
I am on stock Oreo with twrp 3.2.0 rooted with magisk 14.5 and magisk manager 5.4.3. when I try to install viper through magisk it fails saying magisk is not activated.
Sent from my HTC U11 using Tapatalk
Crimsonshadow774 said:
Has anyone managed to get V4A functioning on stock, rooted Oreo? I've tried every option out there. Usually end up with it acting like it didn't install the driver after rebooting. I've tried putting the system in RW, switching selinux to permissive, installing BusyBox, etc. Have tried flashing it through recovery, installing through the apk, installing the magisk module, no luck. Hopefully someone can steer me in the right direction.
Edit 12/5/17:
Navigate to downloads in magisk manager, download the latest version of viper4android by ahrion, flash the file, then reboot.
Using some form of root file browser, I use MiXplorer, navigate to /sbin/.core/img/ViPER4AndroidFX/system, create a new folder called vendor in there, then copy the folder called lib and paste it into the vendor folder you made.
The end result should be /sbin/.core/img/ViPER4AndroidFX/system/vendor/lib. The final step needs a terminal emulator app downloaded, using the app, copy and paste the following in:
su -c ln -s /sbin/.core/img/audmodlib/system/vendor /sbin/.core/img/audmodlib/vendor
Finally, navigate to /sbin/.core/img/audmodlib/system/vendor/etc and open htc_audio_effects.conf, there will be a line for v4a_fx followed by a line called "path" and the path for the library, just change "system" to "vendor", then reboot, you should be successful
Click to expand...
Click to collapse
HI, this method isn't working for me. I have audio_effects.conf instead of the HTC one.
However it keeps telling me that i need to install the driver.
Can you help me?
I have magisk 14.5
Having issues myself with this procedure, which I followed to a T. As the above member said, I too am not receiving a file named "htc_audio_effects.conf." Only audio_effects.conf, which I edited the "V4A" line from system to vendor.
When I downloaded/installed the specific V4A module from Magisk 14.5, I received the "Magisk is not running" error that someone else mentioned. I've never seen that error when installing modules. So I just flashed the V4A zip through TWRP and it showed up in my app drawer. After running the provided line in terminal, it seems that correct /folder structure was placed from /sbin/.core etc...
Note that I'm running the latest LeeDroid Oreo ROM, so I'm not sure if that matters. I also have selinux set to permissive.
After following all of the steps, when I launch V4A, I'm asked to download the driver immediately, but it fails every time, as well as after a reboot.
Any ideas? Definitely want V4A running on Oreo, but I've had no success with any possible installations.
hx3 said:
Having issues myself with this procedure, which I followed to a T. As the above member said, I too am not receiving a file named "htc_audio_effects.conf." Only audio_effects.conf, which I edited the "V4A" line from system to vendor.
When I downloaded/installed the specific V4A module from Magisk 14.5, I received the "Magisk is not running" error that someone else mentioned. I've never seen that error when installing modules. So I just flashed the V4A zip through TWRP and it showed up in my app drawer. After running the provided line in terminal, it seems that correct /folder structure was placed from /sbin/.core etc...
Note that I'm running the latest LeeDroid Oreo ROM, so I'm not sure if that matters. I also have selinux set to permissive.
After following all of the steps, when I launch V4A, I'm asked to download the driver immediately, but it fails every time, as well as after a reboot.
Any ideas? Definitely want V4A running on Oreo, but I've had no success with any possible installations.
Click to expand...
Click to collapse
I've got it working by using the latest team venom Oreo beta and then the v4a for viper rom zip in twrp.
Sent from my HTC U11 using Tapatalk
You may, or may not, have noticed Xposed for SDK27 came out today I for one, am hyped. However, I cannot get it to install. The app gives a 404 error when I try to download though through there. I can download through the official DB, but that doesn't work either, gives me a 'failed to mount /system'. I'm assuming there's some perms issue, but i'd rather not mess with it. I'm on a Verizon Pixel 2.
Edit:Systemless is out if you're having issues installing. But you won't pass safety-net.
D3RP_ said:
You may, or may not, have noticed Xposed for SDK27 came out today I for one, am hyped. However, I cannot get it to install. The app gives a 404 error when I try to download though through there. I can download through the official DB, but that doesn't work either, gives me a 'failed to mount /system'. I'm assuming there's some perms issue, but i'd rather not mess with it. I'm on a Verizon Pixel 2.
Click to expand...
Click to collapse
The Xposed zip failed to flash in twrp for me too. I'm on a Google bought device.
Edit
I get the same 404 error when attempting to download and install through the Xposed installer app.
jascolli said:
The Xposed zip failed to flash in twrp for me too.
Click to expand...
Click to collapse
Which is weird because @wanam is a tester on a Pixel 2 xD
D3RP_ said:
Which is weird because @wanam is a tester on a Pixel 2 xD
Click to expand...
Click to collapse
Yeah i was running it for almost a week now on my Pixel2.
You cannot flash it through TWRP, the zip installer doesn't support A/B partition yet.
I used to install it through Xposed Installer App, if it doesn't show up the framework screen, check "Show outdated versions", copy the zip file to "/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework" and re-open the app.
wanam said:
Yeah i was running it for almost a week now on my Pixel2.
You cannot flash it through TWRP, the zip installer doesn't support A/B partition yet.
I used to install it through Xposed Installer App, if it doesn't show up the framework screen, check "Show outdated versions", copy the zip file to "/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework" and re-open the app.
Click to expand...
Click to collapse
Ahhhhh my man! Thank you!
wanam said:
Yeah i was running it for almost a week now on my Pixel2.
You cannot flash it through TWRP, the zip installer doesn't support A/B partition yet.
I used to install it through Xposed Installer App, if it doesn't show up the framework screen, check "Show outdated versions", copy the zip file to "/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework" and re-open the app.
Click to expand...
Click to collapse
Ok wait, it can't flash now because read only fs. To flash it through recovery I would need to restore stock recovery, right?
wanam said:
Yeah i was running it for almost a week now on my Pixel2.
You cannot flash it through TWRP, the zip installer doesn't support A/B partition yet.
I used to install it through Xposed Installer App, if it doesn't show up the framework screen, check "Show outdated versions", copy the zip file to "/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework" and re-open the app.
Click to expand...
Click to collapse
Thanks wanam, it worked perfectly!!
@wanam
Are there any modules that you have had success running on you pixel 2?
Darn. Framework shows that it is installed OK, but whenever I try to download a module the installer forces closed.
jascolli said:
Thanks wanam, it worked perfectly!!
Click to expand...
Click to collapse
wait what, how tf, did you just click install? Or did you install through recovery?
D3RP_ said:
wait what, how tf, did you just click install? Or did you install through recovery?
Click to expand...
Click to collapse
Download the Xposed zip, copy it and paste it here
"/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework"
In the Xposed installer app settings, check off "show outdated versions"
Then the zip that you posted will show up in the app to be installed.
Hope that makes sense...
Upon that, I'm faced with this issue:
jascolli said:
Download the Xposed zip, copy it and paste it here
"/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework"
In the Xposed installer app settings, check off "show outdated versions"
Then the zip that you posted will show up in the app to be installed.
Hope that makes sense...
Click to expand...
Click to collapse
No I got that far. I can't get it to install.
lps1014 said:
Upon that, I'm faced with this issue:
Click to expand...
Click to collapse
Same here pixel 2 xl magisk 15.2
lps1014 said:
Upon that, I'm faced with this issue:
Click to expand...
Click to collapse
It's a beta xD
wanam said:
Yeah i was running it for almost a week now on my Pixel2.
You cannot flash it through TWRP, the zip installer doesn't support A/B partition yet.
I used to install it through Xposed Installer App, if it doesn't show up the framework screen, check "Show outdated versions", copy the zip file to "/storage/emulated/0/Android/data/de.robv.android.xposed.installer/cache/downloads/framework" and re-open the app.
Click to expand...
Click to collapse
Wanam
What's the trick getting /system/framework read only when installing from Xposed installer.
Thanks
Edit: those getting the read only error using a regular pixel 2 or all xl? This might help them figure it out.
I was able to get mine installed using the steps from wanam. Had to place the file in the framework folder. After that it installed fine
bigbean172018 said:
I was able to get mine installed using the steps from wanam. Had to place the file in the framework folder. After that it installed fine
Click to expand...
Click to collapse
Pixel 2 xl? If so why are some of us getting the read only error. Anything with magisk?
Pixel 2, I have magisk installed as well.
bigbean172018 said:
Pixel 2, I have magisk installed as well.
Click to expand...
Click to collapse
Would be interesting to know if anyone with 2 xl has been able to install it. It seems to be an XL issue since it has not been tested yet officially.
Like it was said it's a beta. Can't always expect it to work the first time.