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
Related
I have the Samsung Galaxy S3 with Wind Mobile. Recently Updated to 4.4.2 and rooted with Towel Root. Everything was good until TitaniumBu couldn't access the externalSD card.
I tried using a couple of xposed modules (Handle External Storage & then KitKat SD Card Full Access), but they didn't allow Titanium to access the SD card either.
So I tried the manual method of modifying platform.xml (also changed permissions on the modified file) but I have the same issue as some other people I've read about (bluetooth stopped working, whatsapp crashed, maps, youtube, play store, titanium backup, touchpal keyboard, web browsing all stopped working). Also when I connect my phone to my PC, the phone and the sd are shown as empty.
I tried copying back the original platform.xml that I had saved and still no luck.
I'm not worried about the titanium accessing the sd card right now. I'm just trying to get the apps and bluetooth working. Anybody have any other ideas?
Try ktoonsez' kt747 kernel.
Thanks
DocHoliday77 said:
Try ktoonsez' kt747 kernel.
Click to expand...
Click to collapse
Thanks for the info Doc, but I'm not too confident flashing kernels (never done it) so I ended up wiping everything and starting from scratch. I installed? kitkat 4.2.2 and then rooted again with towelroot.
I then installed SD fix and TWRP, but the funny thing is that when I restarted my phone, I no longer had wifi.I tried a few things that I found in XDA and on other websites, but I couldn't get wifi back.
So then I redid everything again. Kit Kit & towel root, but no TWRP, no external sd fixes, and I am able to use my phone. The problem for me is that my apps have no access to the extSD and I can't do a back up without that access. I'm thinking that the extsd fixes that i have tried over the last few days mess something up with my phone. Or maybe towel root & the fixes are not good together? Maybe I should have used Root 66 like I used before?
I don't want to risk messing anything up right now, so I'm just going to wait around, and see if anyone else runs into my problems.
Thanks again.
Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!
Thanks Again
DocHoliday77 said:
Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!
Click to expand...
Click to collapse
Thanks again for your response.
I tried sdfix and thats when my wifi got messed up.
I've spent 2 days getting my phone almost back to where it was before, so I think I'll wait a few days/weeks before I mess with it again.
Thanks for the explanation, but sooner or later I think I will try the ktoonsez kt747.
I'll update here whenever I try something.
Thanks again. Your help is appreciated.
DocHoliday77 said:
Towelroot, or any other root method shouldn't have any effect on the actual operation of the device. What is happening is there are new seLinux security enhancements built in to kk. Apps can now only read/write to folders they create/own. If another app created the folder, or if it was created by the owning app before the new security was implemented, seLinux will not allow that app to use it. More and more people are having problems even after the platform.xml edit which makes me believe its got to be done before flashing, or a factory reset may be needed. Im not sure on that right now.
The platform.xml edit is only for the external sdcard btw. You have to disable seLinux to solve this on the internal one. (Looks like this may also be true for external now, but like I said, im not sure about that yet)
There's an app in the store, I think its called sdfix, or sdfixer or something similar (search seLinux mode changer) that people have had some success with, so try that first.
Alternatively, I can mod the stock kernel to disable seLinux there. (May do this today anyway).
It's perfectly fine if you're not comfortable flashing kernels, but its really nothing to be too worried over. A custom one like ktoonsez kt747, will flash and run normally, and you have the option to learn more if you like so you can configure it how you want.
If you have any specific concerns about it, feel free to ask us. But in the end its up to you if you still want to refrain from flashing one.
Another thing you can try is to rename the apps folders, then reinstall it and let it recreate them. Then copy the contents of the old into the new. Not totally sure it would work as I expect, but in theory it should.
Anyway, if nothing else, try that app I mentioned. And let us know how ut goes!
Click to expand...
Click to collapse
FYI Doc. I tried the updated KitKat SD Card Full Access (version 1.2) Xposed module that came out today. It worked, and now Titanium can back up to my external SD card. Finally.
Thanks for letting us know! I don't use xposed so wouldn't have known about it otherwise. Still, I am sorry you had so much trouble with all of this and that I couldn't help you better. Glad to hear you finally got it sorted out though!
Thanks Doc
DocHoliday77 said:
Thanks for letting us know! I don't use xposed so wouldn't have known about it otherwise. Still, I am sorry you had so much trouble with all of this and that I couldn't help you better. Glad to hear you finally got it sorted out though!
Click to expand...
Click to collapse
No worries. I browse XDA a lot, and I see your answers, and they're always helpful. I appreciate all your help.
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
So, I'm new to rooting and this is my first Nexus device.
I'm loving it and all the options but now I'm getting a notification to update.
I see all the forums about hooking it up to a computer and using commands to do it all and then rerooting.
I was looking for an easier way.
I bought a Nexus 5 to play with because I liked this one so much and when OTAs came up, it would let me download them and reboot into CWM recovery and ask if I want to flash the ZIP.
This one just boots into TWRP (No CWM for 5x) and does nothing.
I found the update as a zip here:
<https://gist.github.com/jduck/744a6c8a9042e9c792b7>
My question is: can I just download it and use TWRP to flash it or is the sequence of commands on a computer the only way to do it?
Thank you in advance for your help and I apologize for my ignorance.
Gotta start somewhere though, right?
Hi !
I personnaly use NRT from Wugfresh for my Nexus 5x and my Nexus 7 2013, both rooted.
In "model type", select Nexus 5x and your build.
In "Restore/upgrade/downgrade", select "device is on/normal", then click "Flash stock+ unroot".
Select the build you want to install, it can dl and extract it for you, and select "No Wipe Mode" in order to keep your data and apps. (don't try to put your ota file here)
Go through the steps, and in the end, hit "Root" to root again.
I know there are others methods to apply just the OTA with command lines, but I never did it cause I never took the time to learn. I should do it, maybe it's faster with command lines.
Anyway this works, even if it takes a little time, and it is kind of automatic. But I strongly recommend you try both method to find what suits you most. Or wait for someone else to reply so you'll have more points of view !
Have fun with your N5x !
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
erichjelm said:
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
Click to expand...
Click to collapse
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Darke5tShad0w said:
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Click to expand...
Click to collapse
It's not working.
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
erichjelm said:
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
Click to expand...
Click to collapse
Are you using flashfire v0.28?
Xposed modifies the system so while you maybe able to get the ota it can prevent you from installing them even with flashfire.
Go to the flashfire thread and see if this is a problem with the app or because or xposed (most likely answer).
Otherwise find the ota threads and see if you can flash it through recovery (not the N version)
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
erichjelm said:
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
Click to expand...
Click to collapse
Thats at the end of my ability to help you with this particular problem, I have only owned a Nexus for 2 months and they are completely diff to Samsung plus I run pure nexus rom, you may just have to use a computer.
And I really appreciate it.
I'll just use a computer and do it.
Don't want to risk trying to flash the zip and bricking but I'm still curious.
Just not curious enough.
Haha.
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
erichjelm said:
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
Click to expand...
Click to collapse
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Greedybro said:
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Click to expand...
Click to collapse
This one didn't unroot. Just uninstalled Xposed. Kept all my data and stuff. Apps stayed signed in even. I was afraid because I heard "factory reset" in yours. Or something to that nature. The only thing I'm having problems with now is Tapatalk told me to check my adblock settings and won't load anything. I'll have to look up what's wrong with it. Other than that, it's doing all right.
You are right and wrong, it unroots but reroots in the process. Same I did when I used nrt. And as i didn't wipe data, apps stayed sign in as Well.
But i tried flashfire on my nexus 7 and I it is way more useful and faster than nrt. I am adopting it !
Hello XDA,
I can't seem to get zANTI(the merged version of dSploit) to work properly. When it scans my network in it's initial auto mode as well as in its nmap mode no open ports are detected nor are any operating systems. Conversely cSploit see open ports and operating systems, as does fing.
I'm guessing that this is a problem with the nmap binary however I'm not entirely sure how to go about installing it. I've read the various instructions online without luck. I wish we had apt or were able to use a standard makefile! (maybe we can... I've never tried)
Does anybody have any idea how to fix this? It's kind of annoying because zANTI seems like a great pentesting tool. I just don't want to play around too much as I've broken my Android installs in the past!
-MeeGz
EDIT: I'm curious if systemless root has anything to do with this... Also, I've noticed that there is no bin in /sdcard/opt/nmap-6.46(I'm in the process of installing 7.12)
EDIT: Meh... Turns out that it was bad permissions in /data/data/com.ziperium.zanti/files/nmap
I actually replaced the nmap binary with a newer version and then replaced it with the older binary before realizing that the permissions were fubar'd... Good thing I installed 'MiXplorer' because 'ES' wouldn't even show me the directory. I've never had to play with an apps file's in the past....
How did you fix it?
Also have you tried cSploit.org
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
MeeGz said:
EDIT: Meh... Turns out that it was bad permissions in /data/data/com.ziperium.zanti/files/nmap
I actually replaced the nmap binary with a newer version and then replaced it with the older binary before realizing that the permissions were fubar'd... Good thing I installed 'MiXplorer' because 'ES' wouldn't even show me the directory. I've never had to play with an apps file's in the past....
Click to expand...
Click to collapse
I have not been able to get zanti or cSploit to work like they did back on 4.4.4
I can't really help you with cSploit because I haven't had any issues with it. With zANTI just go to the above mentioned directory and make sure that everything you need is executable and that the "owner" matches the correct app id. A word of advice though; use "miXplorer" to browse for the files and makr sure that you're rooted before attempting any of this...
I put 755 permissions on all files in that directory. All files have the same owner and group app ID, but still I can't get open ports in Zanti.
Can you be more specific.
Thanks!
Sent from my ONEPLUS A3003 using Tapatalk
Did you find any solution?
I have the same issue on my lg v10.
Thank you
Yeah, having the same problem with my 3T. Tried fixing the permissions to the app but with no success.
Still no info on a fix? Same issue on zanti 2.5, S8+ , Nougat.
Batman ROM and kernel. Aswell as OP3 on MM and nougat. This issue has been around for a LONG time. I was told by Zimperium that this is known issue and would be fixed with the next major update. This was at version 2.4.
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.