Related
Is there any way to get the original "market"/play back?
The legacy play is not working with new purchases an don't filter comments on version / device.
I tried restoring an old backup from titanium backup but that failed, do i have to do something to clean out legacy play first?
Sent from my LG-P920 using Tapatalk 2
First connect your phone with USB Debugging turned ON, on your pc and open ADB shell...
Then type:
su [hit enter]
mount -o rw,remount /system [enter]
rm /system/app/PhoneskyLegacy.apk [enter]
pm uninstall com.android.vending [enter]
reboot [enter]
After rebooting you will see the old market app just open it and you will be able to update it to the new Google Play 3.8.16 If you don't find the app (but I am pretty sure that you will) download it here!
HIT thanks if it worked
Awesome, that did indeed work
Thanks!
Sent from my LG-P920 using Tapatalk 2
Bender303 said:
Is there any way to get the original "market"/play back?
The legacy play is not working with new purchases an don't filter comments on version / device.
I tried restoring an old backup from titanium backup but that failed, do i have to do something to clean out legacy play first?
Click to expand...
Click to collapse
Strange. I've got both Play apps on ThiaiZ 2.8, the new and the legacy one, and both are working like they should. I just freeze the Legacy app when I don't use it with Titanium backup.
makaramk said:
First connect your phone with USB Debugging turned ON, on your pc and open ADB shell...
Then type:
su [hit enter]
mount -o rw,remount /system [enter]
rm /system/app/PhoneskyLegacy.apk [enter]
pm uninstall com.android.vending [enter]
reboot [enter]
After rebooting you will see the old market app just open it and you will be able to update it to the new Google Play 3.8.16 If you don't find the app (but I am pretty sure that you will) download it here!
HIT thanks if it worked
Click to expand...
Click to collapse
hi dude. i install everything for adb, but when i tipping "adb shell su", without ", i riceive that messagge: error: device offline.
i try with another cable but nothing change.
when i type adb devices-----> number offline
i have usb debugging turned on and all drivers install.
what is wrong?
tnx.
botson71 said:
Strange. I've got both Play apps on ThiaiZ 2.8, the new and the legacy one, and both are working like they should. I just freeze the Legacy app when I don't use it with Titanium backup.
Click to expand...
Click to collapse
That's strange, i read about that there would be a separate market app for legacy but mine only had legacy.
However I did a dirty flash from Promethius, maybe something to do with that.
Sent from my LG-P920 using Tapatalk 2
speedyranger said:
hi dude. i install everything for adb, but when i tipping "adb shell su", without ", i riceive that messagge: error: device offline.
i try with another cable but nothing change.
when i type adb devices-----> number offline
i have usb debugging turned on and all drivers install.
what is wrong?
tnx.
Click to expand...
Click to collapse
Did you write "adb shell" and then "su"?
Sent from my LG-P920 using Tapatalk 2
Bender303 said:
Did you write "adb shell" and then "su"?
Sent from my LG-P920 using Tapatalk 2
Click to expand...
Click to collapse
adb shell and then su.
now is ok.
i make a reboot.
thanks for answer.
I am glad that I helped
Bender303 said:
That's strange, i read about that there would be a separate market app for legacy but mine only had legacy.
However I did a dirty flash from Promethius, maybe something to do with that.
Sent from my LG-P920 using Tapatalk 2
Click to expand...
Click to collapse
There will be both.
Sent from my Transformer Prime TF201 using XDA Premium HD app
I installed a tempered glass screen protector on my S4 and it messes with the proximity sensor. I contacted the manufacturer and this is what they told me to do:
Thanks for reaching out to us! Any issues with the S4 proximity sensor can be fixed by recalibrating the proximity sensor by issuing the following command:
echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
I entered that command in my TE and I keep getting an error. I can't really tell where there are spaces, where there are possible spaces, etc. Can anyone look at that command and break it down for me? Like:
echo (space)1(space)>(space)/sys/devices/virtual/sensors/proximity_sensor/prox_cal
That is what I tried and no go.
golfinglenn said:
I installed a tempered glass screen protector on my S4 and it messes with the proximity sensor. I contacted the manufacturer and this is what they told me to do:
Thanks for reaching out to us! Any issues with the S4 proximity sensor can be fixed by recalibrating the proximity sensor by issuing the following command:
echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
I entered that command in my TE and I keep getting an error. I can't really tell where there are spaces, where there are possible spaces, etc. Can anyone look at that command and break it down for me? Like:
echo (space)1(space)>(space)/sys/devices/virtual/sensors/proximity_sensor/prox_cal
That is what I tried and no go.
Click to expand...
Click to collapse
What is the error you are receiving in terminal emulator when entering the command? Also you could try entering the command from adb shell. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
shimp208 said:
What is the error you are receiving in terminal emulator when entering the command? Also you could try entering the command from adb shell. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
/system/bin/sh; can't create /sys/devices/virtual..........prox_cal: Permission denied
golfinglenn said:
/system/bin/sh; can't create /sys/devices/virtual..........prox_cal: Permission denied
Click to expand...
Click to collapse
Is your device rooted? Try running the command as the root user which should fix the error.
Sent from my SCH-I535 using xda premium
shimp208 said:
Is your device rooted? Try running the command as the root user which should fix the error.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks for your help. This may be a stupid question, but how do I run the command as the root user? My device is rooted, confirmed with tibu. When I open TE I get the $ sign in the command prompt. Do I need to get that to #, and if so how. I tried to do the same process when I rooted but still didn't work.
Thanks,
Glenn
golfinglenn said:
Thanks for your help. This may be a stupid question, but how do I run the command as the root user? My device is rooted, confirmed with tibu. When I open TE I get the $ sign in the command prompt. Do I need to get that to #, and if so how. I tried to do the same process when I rooted but still didn't work.
Thanks,
Glenn
Click to expand...
Click to collapse
To run the command as root in terminal emulator type the following (Don't actually input the $ and # symbols):
Code:
$ su
#
Entering "su" gives you a root shell from which to run commands from. After you have a root shell in terminal emulator try running the original command you were given.
Sent from my SCH-I535 using xda premium
Okay, I typed su, got the # sign and entered the original code I was given. Hit return and this is what I got:
[email protected]:/ #
How do I know if it calibrated? I broke the tempered glass protector lol trying to "fix" it another way so waiting for another one.
Thanks,
Glenn
golfinglenn said:
Okay, I typed su, got the # sign and entered the original code I was given. Hit return and this is what I got:
[email protected]:/ #
How do I know if it calibrated? I broke the tempered glass protector lol trying to "fix" it another way so waiting for another one.
Thanks,
Glenn
Click to expand...
Click to collapse
If your get a root prompt in terminal after entering the command and not an error message the command was executed successfully and your display should now be calibrated.
Sent from my SCH-I535 using xda premium
Awesome, thank you!!!
Glenn
Wouldn't it be cool to be able to automate the swicthing data between SIM 1 and SIM 2 using Tasker given the location of the device? Let's figure out how to do it together. Do we need root? ADB command comes to mind...
@MishaalRahman any ideas?
What do you mean by "switching data?" Sorry, I usually don't use two SIMs so I'm not sure what you mean.
MishaalRahman said:
What do you mean by "switching data?" Sorry, I usually don't use two SIMs so I'm not sure what you mean.
Click to expand...
Click to collapse
The dual sim version mha-l29 has an option to set the default 4g slot from within the settings menu
I have found already a system variable that can be changed using secure settings plugin for tasker, and running the adb command adb shell settings list system I can see that the variable switch_dual_card_slots does change from 0 to 1 when doing it from the ui, but when done from a put command nothing happens. Any ideas?
dmorales023 said:
The dual sim version mha-l29 has an option to set the default 4g slot from within the settings menu
I have found already a system variable that can be changed using secure settings plugin for tasker, and running the adb command adb shell settings list system I can see that the variable switch_dual_card_slots does change from 0 to 1 when doing it from the ui, but when done from a put command nothing happens. Any ideas?
Click to expand...
Click to collapse
The screenshot shows you doing the command from the Secure Settings plug-in, not from shell. Have you tried it from shell?
MishaalRahman said:
The screenshot shows you doing the command from the Secure Settings plug-in, not from shell. Have you tried it from shell?
Click to expand...
Click to collapse
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
dmorales023 said:
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
Click to expand...
Click to collapse
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
dmorales023 said:
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
Click to expand...
Click to collapse
Yeah, that seems like it would do it.
dmorales023 said:
@MishaalRahman The shell command I am using is "adb shell settings put system switch_dual_card_slots 0/1"
Click to expand...
Click to collapse
Is it working? I am trying to do same thing on my phone. No luck till now
midhunmanohar said:
Is it working? I am trying to do same thing on my phone. No luck till now
Click to expand...
Click to collapse
No luck on my side either. Did you find a solution? This seems so trivial...
dmorales023 said:
Yes, same results executing directly from shell. Nothing happens. Is there a trigger like command to update ui from settings or something like that? Sort of:
1. adb shell command x
2. Commit?
Click to expand...
Click to collapse
I am using the shell command successfully on my Honor 6X.
First I set switch_dual_card_slots to 0 or 1 , and to commit I simply kill the phone process, which will automatically restart instantly.
It is not the most elegant solution, but works flawlessly for me.
The two commands I run (with root priveleges)
1: settings put system switch_dual_card_slots 1
2: pkill phone
dual SIM data switch
RealParity said:
The two commands I run (with root priveleges)
1: settings put system switch_dual_card_slots 1
2: pkill phone
Click to expand...
Click to collapse
i tried the above.
1 executes something, no msg.
2 gives an error message: pkill: TERM->24469: Operation not permitted
the data SIM does not change. but i guess it can't, as the 2nd command fails. what other things i might try?
and yes, i'm a noob on terminal commands - please walk me through how to automate this.
Bump after disabling one sim on location has I get no signal at work
zdoe said:
i tried the above.
1 executes something, no msg.
2 gives an error message: pkill: TERM->24469: Operation not permitted
the data SIM does not change. but i guess it can't, as the 2nd command fails. what other things i might try?
and yes, i'm a noob on terminal commands - please walk me through how to automate this.
Click to expand...
Click to collapse
Not sure if you got this figured out but you need to be rooted. Then in adb shell/terminal you must type "su" first then do the pkill
Anybody tried with a Xiaomi phone?
There's an app 4 this (dual sim switch widget) but it doesn't work on Xiaomi phones
Hi, I have a xiaomi mi 9t, I wish I could change the default sim for data, how much I receive or send a call.
What command can I give tasker for modifying the data sim?
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
s1dest3pnate said:
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
Click to expand...
Click to collapse
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Acid0057 said:
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
s1dest3pnate said:
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
Click to expand...
Click to collapse
Awesome!
Sent from my Pixel XL using Tapatalk
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
GBpfan95 said:
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
Click to expand...
Click to collapse
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
s1dest3pnate said:
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
Click to expand...
Click to collapse
Does that work even if I am locked and not rooted?
GBpfan95 said:
Does that work even if I am locked and not rooted?
Click to expand...
Click to collapse
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
I just ended up factory resetting. Most of everything is backed up anyway. Definitely learned my lesson
Could you please post the SubstratumRescue.zip? I cannot get to the directory on my phone via ADB and want to try running the script commands manually.
EDIT: Nevermind, I tracked it down on the dev's AFH page.
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
pR0wl3r said:
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
Click to expand...
Click to collapse
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
jeremywh7 said:
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
Click to expand...
Click to collapse
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
bobby janow said:
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
Click to expand...
Click to collapse
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
jeremywh7 said:
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
Click to expand...
Click to collapse
Yeah still shows an x.
Sent from my Pixel using XDA-Developers Legacy app
Thanks!
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Thanks so much mate this worked for me perfectly!
This can be done in a less manual fashion. It looks like many of you are on Windows, but I'm sure theres a way to accomplish something similar. I'm on Linux and this is how I did it.
Code:
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 echo cmd overlay disable
cmd overlay disable com.samsung.android.app.aodservice.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.smartmirroring.StatusBarIconsforSamsungextras
cmd overlay disable android.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.app.smartcapture.StatusBarIconsforSamsungextras
cmd overlay disable com.android.settings.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.lool.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.navbars.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.tiles.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.statusbars.StatusBarIconsforSamsungextras
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 adb shell cmd overlay disable
For reference, ag is very similar to grep. So the explanation is adb shell allows you to pass a command to it so it can run that command immediately. So adb shell cmd overlay list is the same as typing adb shell followed by cmd overlay list except it prints the output and immediately exits. So I take that output, grep (using ag in this case) for the enabled overlays and then programmatically disable them. xargs -n 1 says take at most one of the arguments passed to this command and append it to the rest of the line. So this calls adb shell cmd overlay disable __insert-overlay-here__ repeatedly.
I messed up good....
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first one was apparently not removing my overlays. So anyway...
My device rebooted after Chainfire, and was on the G/progress bar for like 5 mins so I knew something was up.
I decided to flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread, so I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
EDIT: Resolved. I was able to delete all overlaid apk's from /data/app.
Hi there,
Question, I got a non-rooted S8, Stock in like everything, and it runs everything fine, including Substratum!
I am wondering about one thing though after reading this thread, imagine something went wrong, what would be my options? I found the Rescue ZIP on my phone, can I apply this if needed with the original recovery from the S8? Or do I need TWRP for that?
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
s1dest3pnate said:
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
Click to expand...
Click to collapse
Hi mate, do I read correctly, that its possible to only boot TWRP temporaly without flashing it?
I have to put the folder/files in the same folder as platform tools?
Hey. I've been reading through all the threads on the Pixel 3a in preparation to root my new device (thanks to all for the great guides). The last version of Android I rooted was MM. I have never used systemless root, but have always rooted and customized the look/performance of my phones. For example, in the past I've simply used a root file explorer to replace system fonts and the boot animation. I also use Substratum (Layers) to theme other apps and system menus, and then Xposed for a few other mods. One of my questions is: will I have read/write permissions in order to make some UI changes with Magisk/systemless root on the Pixel 3a (running stock Android 10)? From what I have gathered, the answer is no, but I'm not clear. I've also never been without a persistent recovery like CWM or TWRP. This is all very new and uncomfortable. But I hate the thought of not having root access, even if I can't customize everything I'd like to change. Does anyone with a rooted Pixel 3a use Substratum or have a method to customize system fonts? The native theme options do not come close, in my opinion. It appears I can create a module and flash in Magisk for system fonts?
Ditamae said:
Hey. I've been reading through all the threads on the Pixel 3a in preparation to root my new device (thanks to all for the great guides). The last version of Android I rooted was MM. I have never used systemless root, but have always rooted and customized the look/performance of my phones. For example, in the past I've simply used a root file explorer to replace system fonts and the boot animation. I also use Substratum (Layers) to theme other apps and system menus, and then Xposed for a few other mods. One of my questions is: will I have read/write permissions in order to make some UI changes with Magisk/systemless root on the Pixel 3a (running stock Android 10)? From what I have gathered, the answer is no, but I'm not clear. I've also never been without a persistent recovery like CWM or TWRP. This is all very new and uncomfortable. But I hate the thought of not having root access, even if I can't customize everything I'd like to change. Does anyone with a rooted Pixel 3a use Substratum or have a method to customize system fonts? The native theme options do not come close, in my opinion. It appears I can create a module and flash in Magisk for system fonts?
Click to expand...
Click to collapse
Modules for fonts are not a problem.
https://forum.xda-developers.com/pixel-3a/themes/fonts-t4017299
Ditamae said:
Hey. I've been reading through all the threads on the Pixel 3a in preparation to root my new device (thanks to all for the great guides). The last version of Android I rooted was MM. I have never used systemless root, but have always rooted and customized the look/performance of my phones. For example, in the past I've simply used a root file explorer to replace system fonts and the boot animation. I also use Substratum (Layers) to theme other apps and system menus, and then Xposed for a few other mods. One of my questions is: will I have read/write permissions in order to make some UI changes with Magisk/systemless root on the Pixel 3a (running stock Android 10)? From what I have gathered, the answer is no, but I'm not clear. I've also never been without a persistent recovery like CWM or TWRP. This is all very new and uncomfortable. But I hate the thought of not having root access, even if I can't customize everything I'd like to change. Does anyone with a rooted Pixel 3a use Substratum or have a method to customize system fonts? The native theme options do not come close, in my opinion. It appears I can create a module and flash in Magisk for system fonts?
Click to expand...
Click to collapse
Pretty much on Android 10 you can't directly modify the filesystem, however magisk can systemlessly modify it using modules. With the latest template, it's actually quite easy to create a magisk module now, you just need to follow this guide and create a zip with the file structure described https://github.com/topjohnwu/Magisk/blob/master/docs/guides.md
If you were able to directly modify the filesystem before, then this is pretty much just as easy.
Just a word of caution as we don't have twrp for Android 10, you should enable adb access and grant root permissions to an adb shell before messing with anything just incase you bootloop.
If you do it's as easy to recover as
Code:
adb shell su -c rm -rf /data/adb/modules/<module id>/
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Pretty much on Android 10 you can't directly modify the filesystem, however magisk can systemlessly modify it using modules. With the latest template, it's actually quite easy to create a magisk module now, you just need to follow this guide and create a zip with the file structure described https://github.com/topjohnwu/Magisk/blob/master/docs/guides.md
If you were able to directly modify the filesystem before, then this is pretty much just as easy.
Just a word of caution as we don't have twrp for Android 10, you should enable adb access and grant root permissions to an adb shell before messing with anything just incase you bootloop.
If you do it's as easy to recover as
Code:
adb shell su -c rm -rf /data/adb/modules/<module id>/
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Thanks @Skittles9823 and @Tulsadiver. As soon as my USB C to USB A cable arrives I can get started.
Ditamae said:
Thanks @Skittles9823 and @Tulsadiver. As soon as my USB C to USB A cable arrives I can get started.
Click to expand...
Click to collapse
If you have a male to female USB-A to USB-A cable you can use that with the OTG adapter that came with the phone as well.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
If you have a male to female USB-A to USB-A cable you can use that with the OTG adapter that came with the phone as well.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
I know! I looked but couldn't find one. Figured a male to male USB-A to USB-C would come in handy in the future for more than just the Pixel. On another note, your how-to guide on Magisk Modules is super thorough, but it might be a little above my ability (at the moment). Time to get reading/researching. Would you be open to questions in the future? I definitely want to modify this thing. I have a day off work tomorrow and school hasn't started yet, so I should have time to unlock/root tomorrow evening.
Skittles9823 said:
Pretty much on Android 10 you can't directly modify the filesystem, however magisk can systemlessly modify it using modules. With the latest template, it's actually quite easy to create a magisk module now, you just need to follow this guide and create a zip with the file structure described https://github.com/topjohnwu/Magisk/blob/master/docs/guides.md
If you were able to directly modify the filesystem before, then this is pretty much just as easy.
Just a word of caution as we don't have twrp for Android 10, you should enable adb access and grant root permissions to an adb shell before messing with anything just incase you bootloop.
If you do it's as easy to recover as
Code:
adb shell su -c rm -rf /data/adb/modules/<module id>/
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Wait, how are you able to access adb from bootloader? It's a bootloop, so getting into the phone shouldn't be possible.
Bramton1 said:
Wait, how are you able to access adb from bootloader? It's a bootloop, so getting into the phone shouldn't be possible.
Click to expand...
Click to collapse
i have put it into bootloader mode by holding the key combination during a bootloop. i have had to hold the keys maybe 6 to 10 secs but it does eventually go to bootloader mode. this was on a op2 though and not my 3a but i'd expect it to work with the 3a also.
Bramton1 said:
Wait, how are you able to access adb from bootloader? It's a bootloop, so getting into the phone shouldn't be possible.
Click to expand...
Click to collapse
Not from the bootloader, during boot.
Once the G logo appears you have full ADB access as long as you've granted shell super user permissions, you're good to fix any issue.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Not from the bootloader, during boot.
Once the G logo appears you have full ADB access as long as you've granted shell super user permissions, you're good to fix any issue.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Just to be clear, this:
Code:
adb shell su -c rm -rf /data/adb/modules/<module id>/
will remove the incompatible module in question during a bootloop? Do you open an active shell while installing all modules? If I grant shell root permissions now I should be able to access it at a later time, correct? Sorry for all the questions. I just want to have a method to undo modules before I start flashing. This seemed easier with TWRP.
Ditamae said:
Just to be clear, this:
will remove the incompatible module in question during a bootloop? Do you open an active shell while installing all modules? If I grant shell root permissions now I should be able to access it at a later time, correct? Sorry for all the questions. I just want to have a method to undo modules before I start flashing. This seemed easier with TWRP.
Click to expand...
Click to collapse
Yes, you'll need to replace <module id> with the folder name (which you can get by running
Code:
adb shell su -c ls /data/adb/modules
and then run the rm -rf command.
Yea, definitely grant root to shell in advance otherwise you won't be able to grant su access when you bootloop. But you just need to grant it once and make sure to check the box in the adb prompt that remembers your PC and keeps its access, then you'll be good.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Yes, you'll need to replace <module id> with the folder name (which you can get by running
Code:
adb shell su -c ls /data/adb/modules
and then run the rm -rf command.
Yea, definitely grant root to shell in advance otherwise you won't be able to grant su access when you bootloop. But you just need to grant it once and make sure to check the box in the adb prompt that remembers your PC and keeps its access, then you'll be good.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
Got it. Thanks again. Just to clarify, when you say to "check the box in the adb prompt that remembers your PC" you're referring to the the USB debugging authorization?
Ditamae said:
Yes, you'll need to replace <module id> with the folder name (which you can get by running
Got it. Thanks again. Just to clarify, when you say to "check the box in the adb prompt that remembers your PC" you're referring to the the USB debugging authorization?
Click to expand...
Click to collapse
Yes
Sent from my Google Pixel 3a XL using XDA Labs