There seems to be no way to mount /system rw on Q/10 or am i missing the workaround somewhere?
I don't know how to mount /system rw, but you can use "MagiskHide Props Config" to change prop value.
I noticed this also and just factory reset my phone before seeing this about magisk. I'll try that when I get back up and running.
in twrp is shows you can't mount /system or /vendor
I thought I did something wrong when preserving root through the OTA with Magisk. Must be a new A10 thing??
drt054 said:
I noticed this also and just factory reset my phone before seeing this about magisk. I'll try that when I get back up and running.
in twrp is shows you can't mount /system or /vendor
I thought I did something wrong when preserving root through the OTA. Must be a new A10 thing??
Click to expand...
Click to collapse
yes, since Q beta 3, see https://forum.xda-developers.com/pixel-2-xl/help/android-q-beta-3-wont-mount-rw-t3929443
editing build.prop is the first thing I do after root. I need tethering badly.
also cannot do a nandroid backup in twrp because of this.
I figured out if you are rooted with Magisk you can use the prop editor on the terminal. just type props and follow the menus
DebianDog said:
I figured out if you are rooted with Magisk you can use the prop editor on the terminal. just type props and follow the menus
Click to expand...
Click to collapse
Hey, I know I'm extremely late to this but I just tried this and it's working for me so far. I used MagiskHide Props Config and a terminal window and I have tethering working again on my Pixel 2 XL. Thank you for your instructions!
DebianDog said:
I figured out if you are rooted with Magisk you can use the prop editor on the terminal. just type props and follow the menus
Click to expand...
Click to collapse
Trying to do that right now, can't quite work it out. Did you select option #4--'add/edit custom props'? That doesn't seem to get where I wanna GO, which is adding a line to the default prop. None of the other options looks right
Mejud said:
Trying to do that right now, can't quite work it out. Did you select option #4--'add/edit custom props'? That doesn't seem to get where I wanna GO, which is adding a line to the default prop. None of the other options looks right
Click to expand...
Click to collapse
Mejud, Yes, I selected option # 4 and followed what was posted earlier and entered "net.tethering.noprovisioning=true" in selection n- New custom prop. After that, I rebooted my Pixel 2 XL and was able to enable tethering again. I did it so fast that I didn't think of listing the missing steps I figured out on my own.
rsnyc said:
Mejud, Yes, I selected option # 4 and followed what was posted earlier and entered "net.tethering.noprovisioning=true" in selection n- New custom prop. After that, I rebooted my Pixel 2 XL and was able to enable tethering again. I did it so fast that I didn't think of listing the missing steps I figured out on my own.
Click to expand...
Click to collapse
Finally got it--Apparently I'm either supposed to do it twice (after selecting 'new prop' ) else I'm supposed to hit enter, and THEN type in the line
Anyhow, it works now, thanks
Mejud said:
Finally got it--Apparently I'm either supposed to do it twice (after selecting 'new prop' ) else I'm supposed to hit enter, and THEN type in the line
Anyhow, it works now, thanks
Click to expand...
Click to collapse
Glad you got it up and working. Now I'm hoping this will continue to work after updating to December's update. By the way, would you know how to get Google Pay to work? Thanks in advance.
Sorry, never tried it
is the net.tethering.noprovisioning=true prop edit still working on April update? I've tried unsuccessfully with MagiskHideProps. Looks like I was able to add using terminal,but not hotspot. Looking a build.prop in file explorer doesn't show the edit?
forepj said:
is the net.tethering.noprovisioning=true prop edit still working on April update? I've tried unsuccessfully with MagiskHideProps. Looks like I was able to add using terminal,but not hotspot. Looking a build.prop in file explorer doesn't show the edit?
Click to expand...
Click to collapse
It's still working for me, only now I'm running it on my Pixel 3 XL instead of the 2 XL. It was working with the March update and thankfully I didn't need to do anything when I updated to April.
Is it possible to get wifi calling enabled on the Verizon network in the USA with a Google unlocked pixel 2 xl?
I've not touched my phone since doing the Nov 2019 update, now I'm hesitant to
Mejud said:
I've not touched my phone since doing the Nov 2019 update, now I'm hesitant to
Click to expand...
Click to collapse
I understand. I get nervous about updating my Pixel 3 XL also but thankfully the forums have been a huge help.
My concern is not being able to keep the hotspot running, monumental nightmare for me
Mejud said:
My concern is not being able to keep the hotspot running, monumental nightmare for me
Click to expand...
Click to collapse
It's always a good practice to make a backup so, God forbid something goes wrong, you're good.
I want to edit the build.prop file and add the below two lines to enable me to add the APN settings on ROG 3 phone.
ril.sales_code=LOL
ro.csc.sales_code=LOL
How can I do it?
While terminal solution seems good for tethering, it doesn't have
the option for a full fletched editing of the build.prop file.
Related
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end
deleted
All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
Update: TWRP install method added for those not using Magisk. Just flash the zip and good to go.
Magisk Module v2.1a: Update Sep 5, 2017
https://www.androidfilehost.com/?fid=817550096634797320
TWRP Install:
https://www.androidfilehost.com/?fid=889764386195918352
Thanks intall working
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Great Tweak mate! Thank you so much
I'm expecting an important call today, but will test thoroughly later.
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
badcrow35 said:
Thanks intall working
Click to expand...
Click to collapse
I don't own a OnePlus 5, I have a 3 but I saw a Turkish text and decided to write. How did you get access to OnePlus 5? Have you imported it from abroad or are you living in abroad?
Brought with my friend from abroad UK
ilia1985 said:
Thanks can you make a non magisk flash able zip? I'm decrypted and magisk only works on encrypted setup as far I know.
Click to expand...
Click to collapse
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Can anyone confirm if the zip works?
dustintinsley said:
All the methods of installing the Google Dialer on the OP5 kinda worked but would not allow the user to answer/decline calls from the notification popup. Well, did some digging on this and found a solution. This is a Magisk Module, so for those that use Magisk, simple flash and restart. Be sure you select the new Phone app as default for calls. Also, need to go in and manually set the permissions for the app.
This can be done by going to "app info" for default OnePlus phone app and disabling, then by going to Google Phone "app info" and clicking on Phone App, then on the "Configure apps screen, changing the default Phone App to the only option you should have (after disabling the default one) which is the Google "Phone". Then make sure your new Phone app has all it's permissions.
Enjoy!
https://www.androidfilehost.com/?fid=889764386195917884
Click to expand...
Click to collapse
Work like a charm wish everything went this easy
Awesome, works just fine. This has been driving me bonkers lol.
Working great! I use xxx rom with latest Magisk. Thx! :highfive:
dreams.sri said:
Can anyone confirm if the zip works?
Click to expand...
Click to collapse
I have not tested it as I use Magisk, but it should work. Worse case is that it will still not answer from notification. Should not cause any boot loop or anything like that. Have you tried the zip? There should be no issues with it, if you have issues please let me know so I can fix it...
Binary Assault said:
Awesome, works just fine. This has been driving me bonkers lol.
Click to expand...
Click to collapse
Same here man. It was driving me nuts. I'm kinda OCD so I had to figure it out. Glad others find it useful...
But OnePlus Dialer Is Better Than Google One ?
Krsambhav16 said:
But OnePlus Dialer Is Better Than Google One ?
Click to expand...
Click to collapse
Not sure that I agree, but to each his own...
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Donald Nice said:
Can someone explain how to flash the magisk module? Flash it via TWRP or via Magisk?
Click to expand...
Click to collapse
You can do it either way. I prefer doing it via Magisk, but either should work.
does it vibrate when the call connects?
dustintinsley said:
This *may* work. I am new to installer scripts, so hopefully I wrote this correctly... Please let me know.
Click to expand...
Click to collapse
Thanks for taking time to make it. Just tried and TWRP throws error 6.
Back on Oreo, all we had to do was bring the Framework-res__auto_generated.apm from the Pixel 2 (or Pixel 2 XL) and install it in System/vendor/overlay. Since we don't have root (yet) for P, is there any other way to do it? I tried via TWRP (ADB in TWRP and making a flashable zip) but I'm honestly not extremely experienced with this. Via TWRP I can't get system/vendor/overlay to show, and putting the APK in Vendor/overlay doesn't seem to activate it. Any ideas, or just wait for root?
YTSec said:
Back on Oreo, all we had to do was bring the Framework-res__auto_generated.apm from the Pixel 2 (or Pixel 2 XL) and install it in System/vendor/overlay. Since we don't have root (yet) for P, is there any other way to do it? I tried via TWRP (ADB in TWRP and making a flashable zip) but I'm honestly not extremely experienced with this. Via TWRP I can't get system/vendor/overlay to show, and putting the APK in Vendor/overlay doesn't seem to activate it. Any ideas, or just wait for root?
Click to expand...
Click to collapse
Looks like root is working sorta with magisk, just an issue with magisk manager. You might be able to get unrestricted root access to a file explorer app and compete your task. Let me know how it goes because id like to get AOD working too :good:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page543
Jackaroop said:
Looks like root is working sorta with magisk, just an issue with magisk manager. You might be able to get unrestricted root access to a file explorer app and compete your task. Let me know how it goes because id like to get AOD working too :good:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page543
Click to expand...
Click to collapse
Trying that now, I'll update if it works out.
YTSec said:
Trying that now, I'll update if it works out.
Click to expand...
Click to collapse
Confirmed working!
YTSec said:
Confirmed working!
Click to expand...
Click to collapse
Steps please and thanks.
Do you have the framework APK?
---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------
muppetmaster916 said:
Steps please and thanks.
Click to expand...
Click to collapse
Read that area of the thread
https://forum.xda-developers.com/pi...firehound-v4-1-pixel-xl-t3744866/post75492280
To get this working, flash Magisk 16 via TWRP, boot up and use a file manager (I used ES file manager) to move the APK here to system/vendor/overlay overwrite the original. The phone will either reboot, or systemui will crash, when you get back in, go into the file manager again and set the correct permissions.
Make sure you remove your passwords, just incase something goes wrong while installing it.
YTSec said:
To get this working, flash Magisk 16 via TWRP, boot up and use a file manager (I used ES file manager) to move the APK here to system/vendor/overlay overwrite the original. The phone will either reboot, or systemui will crash, when you get back in, go into the file manager again and set the correct permissions.
Make sure you remove your passwords, just incase something goes wrong while installing it.
Click to expand...
Click to collapse
How do we install the burn in protection? Sorry for bugging you I've been googling for hours and you're the only person who seems to know how to do this or that this is possible.
SubjectGinger said:
How do we install the burn in protection? Sorry for bugging you I've been googling for hours and you're the only person who seems to know how to do this or that this is possible.
Click to expand...
Click to collapse
I took a screen recording for 20 mins and skipped around in the recording, the charge level, notifications, and clock all move around slowly. So it seems to be enabled by default.
YTSec said:
I took a screen recording for 20 mins and skipped around in the recording, the charge level, notifications, and clock all move around slowly. So it seems to be enabled by default.
Click to expand...
Click to collapse
Awesome, thanks! I tried installing it but now all the apps are crashing and I can't get back into my file manager to set the correct permissions, it crashes too. Is there a way to get the file manager to work? I'm using Solid Explorer on 8.1
SubjectGinger said:
Awesome, thanks! I tried installing it but now all the apps are crashing and I can't get back into my file manager to set the correct permissions, it crashes too. Is there a way to get the file manager to work? I'm using Solid Explorer on 8.1
Click to expand...
Click to collapse
If you are on 8.1, you need to use the APK extracted from a 8.1 system IMG for the Pixel 2 or Pixel XL 2. As for the file manager, try Amaze, I used it when ES was crashing non-stop.
YTSec said:
If you are on 8.1, you need to use the APK extracted from a 8.1 system IMG for the Pixel 2 or Pixel XL 2. As for the file manager, try Amaze, I used it when ES was crashing non-stop.
Click to expand...
Click to collapse
Yeah I was, I used the 8.1 Feb 2018 file you provided here. I'll give that a try next, installing the March security update to try and fix the crashing
SubjectGinger said:
Yeah I was, I used the 8.1 Feb 2018 file you provided here. I'll give that a try next, installing the March security update to try and fix the crashing
Click to expand...
Click to collapse
I provided the one for Android P DP1 here, not 8.1. I put the February one in the foreground ROM thread I think though.
YTSec said:
I provided the one for Android P DP1 here, not 8.1. I put the February one in the foreground ROM thread I think though.
Click to expand...
Click to collapse
Yeah the one from the foreground thread is the one I used. This might be a dumb question but how did you open the system image from the pixel 2 factory image to get the framework file? I can't open the .img as an archive and it fails to mount on both windows and Mac saying it's a corrupted image (downloaded straight from Google's site)
SubjectGinger said:
Yeah the one from the foreground thread is the one I used. This might be a dumb question but how did you open the system image from the pixel 2 factory image to get the framework file? I can't open the .img as an archive and it fails to mount on both windows and Mac saying it's a corrupted image (downloaded straight from Google's site)
Click to expand...
Click to collapse
Honestly it's a pain, I installed Ubuntu via virtual box, and went through a extraction process. https://forum.xda-developers.com/nexus-5x/general/guide-how-to-extract-nexus-factory-image-t3562665
YTSec said:
Honestly it's a pain, I installed Ubuntu via virtual box, and went through a extraction process. https://forum.xda-developers.com/nexus-5x/general/guide-how-to-extract-nexus-factory-image-t3562665
Click to expand...
Click to collapse
I went through that link, installed the extractor for Windows and tested it with the March 8.1 for Sailfish. Worked flawlessly. Download the March 8.1 for Walleye, "imgextractor has stopped working" and only extracts about 1/4 of the system img. You weren't kidding it really is a pain
SubjectGinger said:
I went through that link, installed the extractor for Windows and tested it with the March 8.1 for Sailfish. Worked flawlessly. Download the March 8.1 for Walleye, "imgextractor has stopped working" and only extracts about 1/4 of the system img. You weren't kidding it really is a pain
Click to expand...
Click to collapse
It doesn't work on windows, needs to be Linux. Try installing it in a virtual machine, only way I was able to get it working.
Here's the 8.1 March 2018 apk from Pixel 2 XL
reddv1 said:
Here's the 8.1 March 2018 apk from Pixel 2 XL
Click to expand...
Click to collapse
I really appreciate the help, but I have a Pixel 1 (non-xl)
Any chance I could get you to post the March 2018 from the Pixel 2 non-xl?
I've been trying to get this system image extractor to work and even on Linux am running into issues.
Anyways, if not no worries but I'd be very thankful if you could find the time!
SubjectGinger said:
I really appreciate the help, but I have a Pixel 1 (non-xl)
Any chance I could get you to post the March 2018 from the Pixel 2 non-xl?
I've been trying to get this system image extractor to work and even on Linux am running into issues.
Anyways, if not no worries but I'd be very thankful if you could find the time!
Click to expand...
Click to collapse
I don't think it's much different honestly, it SHOULD still work the same. The original XL and 2 XL are significantly different and it works fine, I have also used the APK from the normal Pixel 2 on my XL with no issues.
Anyone running Android Q beta 2 ? Can you make a comparison to Pie in terms of speed or apps that crash or hang? TIA
I have no apps crashing and no apps unable to start. Performance and battery are identical to Pie.
The Android Q is definitely a daily driver for me.
EDIT: The only single issue I have is that double-tap or lift to wake are not working.
Guys how to root? Android Q?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Will this work on beta 2 ??
spleenandcigars said:
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Click to expand...
Click to collapse
not work on Beta 2, bro
How best to backout of the AndroidQ beta2?
Installed but Android Auto is playing up so want to go back to v8
Can't mount system partition R/W on Marlin using TWRP 3.2.3-1 once updated to AQB2 (although I did a dirty update by removing the -w erase flag from the bat file before executing.) Guess I'll try nuking everything and rebuilding from scratch to see if the partitions will mount R/W to install Magisk...
Is anyone able to set his own mp3 ringtone on this?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
George_Bushels said:
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
Click to expand...
Click to collapse
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Homeboy76 said:
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Click to expand...
Click to collapse
Yes.
sonpro10x said:
not work on Beta 2, bro
Click to expand...
Click to collapse
As you can see in this screenshot, it's working just fine. You have to install the latest Magisk canary build. TWRP won't work to do some backups, but you can flash it fine.
Been running Q2 for a few days and is a great daily driver. As soon as Nova paid was installed I have no complaints
and battery life has been excellent. Coming from the Essential phone rooted this has been a pleasant surprise. For 180.00 new
unlocked on Sprint this is a good deal. I also prefer the 16x9 screen and camera.
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
tufyuma said:
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
Click to expand...
Click to collapse
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
bonfire62 said:
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
Click to expand...
Click to collapse
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
tufyuma said:
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
Click to expand...
Click to collapse
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
bonfire62 said:
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
Click to expand...
Click to collapse
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
tufyuma said:
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
Click to expand...
Click to collapse
After clean flash, still having the same issue with the downloads. Going to Solidexplorer shows that the sdcard partition never created a Download folder. Chrome also is completely not working now, so definitely rolling back until it's resolved.
Okay I was able to modify /system on android Q beta 2 just fine but on beta 3 I cant do it no matter what I do. Everything I do either results in "invalid argument" or "/dev/block/sda7 is read only" Heres what Ive done so far:
1. Magisk Canary
2. Boot into TWRP and try mounting there
3. Flashing Q again but with -w
4. Custom Kernel
5. Issuing any mount commands I can think of
6. Resetting back to Pie then updating to Q again
7. Relocking the bootloader and then unlocking it again but this time with unlock_critical (for some reason the phone wouldnt let me do unlock_critical before)
Any help would be greatly appreciated, I need access to /system to edit build.prop to get rid of the navbar and to disable carrier provisioning
Also yes I have verified root works, as my kernel manager can modify kernel related settings
I don't have a "fix" for it unfortunately, but I just wanted to let you know you're not alone. I've experienced the same thing. I tried Magisk Stable and Canary, FX Explorer, Root Explorer, ES Explorer, and a couple of other root file explorers, several busy boxes "versions," setting SELinux to permissive, upgrading to beta file explorers in the Play Store, and on and on. Regardless of what I tried, nothing work to make /system read-writable. I can only assume it's a new security "feature" in Q that apps devs are going to have adjust for. I've left a few messages with some of the devs letting them know about the issue.
Unfortunately, in situations like this, most non-XDA, Play Store devs wait until the new version is official before they bother "fixing" their apps. That means it could be several months from now before it works again, unless it's a bug in Q3, which is entirely possible. If that's the case, the maybe we'll get lucky and Q4 will fix it.
In the meantime, coming to that realization was enough for me to go back to Pie. I've got to be able to make manual changes to /system.
I had a really hard time when I tried to Google search this issue. This issue specifically to do with the Android Q beta 3 doesn't seem to be mentioned anywhere that I came across. I'm going to subscribe to this thread. We can use it to post updates on this issue as new betas come out, or if someone actually finds a way to "fix" it.
Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.
all43 said:
Yep having the issues,been through the same processes,I have posted up in the q thread yesterday, apart from this issue the ROM is looking great.
Click to expand...
Click to collapse
Someone mentioned MiX explorer in that thread, did you try that one. I think I looked for it when I was on Q, but couldn't find it. I don't think I checked XDA though. In any event, they posted a link to it. If you're still on Q, try it out and let us know.
Sent from my Moto G6 using XDA Labs
Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me
all43 said:
Mixplorer silver sees system and confirms it's deleted files until you refresh,sadly not working for me
Click to expand...
Click to collapse
Someone in the MiX thread said something that makes it's seem like it's a Magisk issue and not a file explorer issue. I've asked them to clarify.
Sent from my Moto G6 using XDA Labs
nice one sharkie, would be a bonus!
Same goes for A10 OTA. There is a updated Magisk 19.4 but still didn't fix /system problem yet.
MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?
adeelsmatrix said:
MiXplorer doesn't mount system rw on android 10. Anyone knows any other method. It has been quite time since we are facing this problem...?
Click to expand...
Click to collapse
It's due to a fundamental change in Android Q. Topjohnwu had an article explaining it in more detail somewhere. I wouldn't hold your breath for it to be worked around any time soon. You'll have to make due with Magisk modules to accomplish whatever it is you want to do.
I can try and help you out with whatever it is you want to do, either by giving you a link to a module that already exists, or helping you create your own.
Sent from my moto g(6) using XDA Labs