Google App keeps crashing due to XML messup! Can't reflash! - Nexus 5X Q&A, Help & Troubleshooting

So I saw on this reddit post that there was a way to get DayDream on a Nexus 5X by editing an XML document in the system permissions folder.
I'd post the link to the Reddit Page, but XDA is being a stickler about links for new accounts...
Just search "Reddit Daydream Nexus 5x" and you should be able to find it.
I decided to try it out and what I THINK I did was screw up the formatting in the XML document and when I restarted the phone, the google app keeps crashing. I tried a factory reset, didn't fix it. Not only that, I kinda screwed myself over because the factory reset shut off the USB Debugging in the developer settings. Now when I try to use ADB to reflash the stock ROM, it won't connect.
I was able to access the drop down menu and get to the settings, but when I try to access the developer settings it crashes.
I think I'm screwed, but I want to know if there's any other option to fixing this. I really need help guys...

Related

[Q] Google Talk Authentication Error...please help...

So for the past couple days I've been getting an error message pop up with a notification sound talking about Google Talk Authentication Error and says how it cannot connect and what not. I have made no changes to my phone and now I cant even download anything from the market now. I cant download free apps when i try i get the error "name of the app" could not be downloaded due to an error and when i try to buy apps i get this error saying Error processing purchase. Any help would be appreciated and thanks in advance.
Delete your google account from the phone, then try signing back into it.
teh roxxorz said:
Delete your google account from the phone, then try signing back into it.
Click to expand...
Click to collapse
It says that I would have to do a factory reset on the phone. I wonder if that will cause it to unroot.
Edit:
Got it fixed did factory reset and put in my google account again and boom all good, thanks for the help
Real solution
soco224 said:
So for the past couple days I've been getting an error message pop up with a notification sound talking about Google Talk Authentication Error and says how it cannot connect and what not. I have made no changes to my phone and now I cant even download anything from the market now. I cant download free apps when i try i get the error "name of the app" could not be downloaded due to an error and when i try to buy apps i get this error saying Error processing purchase. Any help would be appreciated and thanks in advance.
Click to expand...
Click to collapse
After cloning a samsung gio s5660 through a CWM backup I started experiencing the same issue. Heres What REALLY happens.
Google authenticates you in their services trought unique "keys" which are automatically generated upon system installation / factory reset, so if you clone your device or install a rom which has these "keys" pre-installed, obviously, your rom will only autheticate you in google servers if your phone is the only one using the service at that given time... Upon failure, your phone assumes to be the one who's wrong, and google servers won't autheticate you until you either tell your phone he is not wrong (by deleting the data from play store, which resets its status and errors) or you change the "keys". SO, what can we learn from this? deleting the play store data IS a temporary solution, and won't solve a thing. Let's delete the duplicated keys shall we?
Navigate with your favourite folder explorer on your android (I use X-plore, you can tell me anything, there's nothing better) to the following directory:
- "(root)/data/data/com.google.android.gsf"
Now you have two real options, either you may delete the all folder, which was the perfect solution for me, since my rom is prepared to re-create it upon phone restart and new keys will be generated, OR, you might want to just delete the contents of app_sslcache inside com.google.android.gsf whish are THE KEYS I HAVE BEEN TALKING ABOUT THIS ALL TIME, YEEEIHHHH and reboot your phone...
Needless to say, take a nandroid backup before you do any of this...
Thank me later
For those who remember me from symbian s60v3 phones, yes, it is me, I'm back, and I've moved to the droid world, it's much better indeed

[Solved] Broke permissions settings, nandroid can't fix, need help

Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.
Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.

Need Help Recovering Pictures

It's a Verizon Pixel XL 32gb running build NDE63X fully stock.
I've tried everything mentioned in normal and safe mode through multiple reboots, power downs, etc.
Phone won't connect to cell data but will connect to wifi. It states that cell data is turned off but if I turn it back on it immediately turns back off without ever connecting.
Windows 10 file manager as well as Thunar and Nautilus file managers for Ubuntu 16.04 all show the pixel as a network device but won't show anything there.
Fastboot will show ID from bootloader
ADB won't show anything anywhere.
When I click developer options it says "Developer options are not available for this user" (This seems damned suspicious and seems likely to be what's grieving me)
Home button ONLY does the animations and nothing else. The recent apps button doesn't do anything however the back button works.
I tried using google cloud to back up the photos but it never uploads anything anywhere, just sits there saying it's uploading X images (I've tried single pictures as well as sets of pictures, videos, and anything else I could think to try.
I'm pretty confident that a factory reset will resolve everything but I can't do this until I can get photos off. I've been googling, DDGing, and all around scraping xda, reddit, and anywhere else I can think of. Any help or suggestions would be great!
themadmech said:
It's a Verizon Pixel XL 32gb running build NDE63X fully stock.
I've tried everything mentioned in normal and safe mode through multiple reboots, power downs, etc.
Phone won't connect to cell data but will connect to wifi. It states that cell data is turned off but if I turn it back on it immediately turns back off without ever connecting.
Windows 10 file manager as well as Thunar and Nautilus file managers for Ubuntu 16.04 all show the pixel as a network device but won't show anything there.
Fastboot will show ID from bootloader
ADB won't show anything anywhere.
When I click developer options it says "Developer options are not available for this user" (This seems damned suspicious and seems likely to be what's grieving me)
Home button ONLY does the animations and nothing else. The recent apps button doesn't do anything however the back button works.
I tried using google cloud to back up the photos but it never uploads anything anywhere, just sits there saying it's uploading X images (I've tried single pictures as well as sets of pictures, videos, and anything else I could think to try.
I'm pretty confident that a factory reset will resolve everything but I can't do this until I can get photos off. I've been googling, DDGing, and all around scraping xda, reddit, and anywhere else I can think of. Any help or suggestions would be great!
Click to expand...
Click to collapse
What you could do is download "ES File Explorer" from the play store and when opened, navigate to Network>remote management. It will give you an IP and a port. Pop this into an ftp client on your computer such as Filezilla Client. It will list your device and you can copy to a desired location on your computer
Can you email, bt file share, install Dropbox or OneDrive and turn photo back up on, plug in the otg adapter and a flash drive, adb pull files, share to google drive? Last resort display them on screen and take a pic with another camera.
Go into settings and see which user you are signed in with. Maybe that is the problem.
larsdennert said:
Can you email, bt file share, install Dropbox or OneDrive and turn photo back up on, plug in the otg adapter and a flash drive, adb pull files, share to google drive? Last resort display them on screen and take a pic with another camera.
Click to expand...
Click to collapse
I'm not sure you read my post... adb isn't doing anything. It should, but doesn't. This is likely due to developer options being inaccessible as I mentioned in the OP. Uploading the files hasn't worked with Google Drive and should. I admit that I haven't tried with Dropbox or OneDrive due to not having accounts with either group but if other solutions don't work I can try making a dropbox. Wired transfer has been a bust, again, thoroughly mentioned in OP.
larsdennert said:
Go into settings and see which user you are signed in with. Maybe that is the problem.
Click to expand...
Click to collapse
I'm signed in as Name being the correct name of the user. I've tried clicking on it to switch users to attempt to resolve the issue but to no avail. There should only be the one user on the device and they should have full permissions but this doesn't seem to be the case, though I can find no alternate user account.
Maybe dd the data partition from fastboot and mount it in Linux to copy the files
I had exactly the same issue. This seems to be an issue of a "dirty" flash. On Marshmallow this issue happened sometimes, and the cause was that Android expects the Setup Wizard to be running. There is a flag which forces the WIzard to start, but I couldn't get this fix running on 7.1.1.
I installed an FTP Server on my Pixel and fetch the data off there.
There was no other way that to completely wipe the device. This will be the last time I will ever buy a phone without a SD card slot. With my Samsung device I could easily flash forth and back, because all my data was on my SD card, not being affected by a full wipe / reflash.
---------- Post added at 09:59 AM ---------- Previous post was at 09:52 AM ----------
Also I assume the home button does not work like properly, correct?
XtraArrow said:
What you could do is download "ES File Explorer" from the play store and when opened, navigate to Network>remote management. It will give you an IP and a port. Pop this into an ftp client on your computer such as Filezilla Client. It will list your device and you can copy to a desired location on your computer
Click to expand...
Click to collapse
This worked, thank you for the suggestion! I was able to pull all the pictures then factory reset the phone. Good to go.
themadmech said:
This worked, thank you for the suggestion! I was able to pull all the pictures then factory reset the phone. Good to go.
Click to expand...
Click to collapse
Glad I could help!

Need desperate help. Unlocking Huawei y6 pro (SLAL02)

After factory reset I'm stuck at google account screen which I don't remember since it wasn't my main google account.
After a lot of research I've tried the talkback->youtube but chrome or any browser doesn't open so I can't use it
Tried the gmail path but whole menu' doesn't show up, only account section and no options
Tried the keyboard "assist" but google search bar doesn't appear.
Tried to flash stock rom from sdcard but fails at 5%
Phone wasn't rooted and everything is stock
How do I get past google account screen? Is it as good as bricked?
UPDATE: I managed to get past FRP through the stock email app exploit! I cannot post links however due to forum restrictions.
In case anyone needs:
1. Follow guide with normal talkback->share link->email(select stock email app instead of Gmail)
1.1 Create a hotmail or whatever account on an other device.
2. Sign in, compose email, attach file from sd card (QuickShortcutMaker apk, you can google it)
3. Send email! you can send to random address
4. Go to outgoing, open sent email and open attached file and install
5. After install open and scroll down to "Huawei Home", open first option, then tap "try"
6. You now have access to whole phone, go to Settings->Accounts and delete all accounts
7. Go back to settings->backup&restore->Factory reset and confirm
8. Phone is now clean of FRP, enjoy!
A friend of mine asked about this. It's never a problem I've had, but thank you for sharing the solution. This could come in handy!
XDA-Nexus-User said:
A friend of mine asked about this. It's never a problem I've had, but thank you for sharing the solution. This could come in handy!
Click to expand...
Click to collapse
Indeed! Most common solutions weren't working for me so for a few days I was going crazy, but finally found one that works. Maybe someone else doesn't have to go crazy too!

Stuck at "Pixel is starting..." after boot

Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it. :good:
So it seems that entering your PIN in the Settings app also unlocks the phone!
Thanks for describing this and how you ended up resolving it. I am seeing the same "Pixel is starting". Flashing the (March 2020) factory image didn't fix mine either.
I was able to get into Settings by pulling down the notification shade while the "Pixel is starting" message shows. I removed my fingerprints and PIN.
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
I've tried this:
Settings-->Apps & notifications-->App info--> {select any app and tried clicking on icon at top of screen} Nothing. Poked around a bit and tried various things but couldn't figure out how to launch an app from here. Thanks in advance.
docdl said:
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
Click to expand...
Click to collapse
There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app).
_Ra1n_ said:
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
Click to expand...
Click to collapse
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described. I'm also stock, rooted with Magisk, on the January update. I just found that I can get into adb, but I'm a loss of what do to from here. I can't believe toggling a system UI tuner setting could cause a catastrophic crash. How did you end up solving this? Were you able to flash the full factory image while preserving your data? I honestly have no idea what do to at the moment. I'm gonna have to use an older device and research this more after work.
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Ditamae said:
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described.
Click to expand...
Click to collapse
Interesting! Exact same order of events.
Ditamae said:
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Click to expand...
Click to collapse
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
_Ra1n_ said:
Interesting! Exact same order of events.
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
Click to expand...
Click to collapse
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
I did utilize the system UI tuner to disable my alarm icon from showing in the status bar, so I'm hoping I can perhaps find the file associated with the plugin specifically and rename that. Hmm. Only this is systemless... Might not be possible. This is my first rooted device without full read/write capabilities. Not sure how I feel about systemless.
Otherwise, other than time, the only bummer to all this is that I think I'm going to lose the Magisk module YouTube Vanced, as it's not longer supported.
Anyway, thanks very much for your help so far.
Ditamae said:
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
Click to expand...
Click to collapse
If your luck is as good as mine, you should be able to just plug in the device and enable file transfer (Settings > Connected Devices > USB > "Use USB For ... File Transfer."
Note that, as explained above, I had to remove my security PIN in settings before that worked, though.
_Ra1n_ said:
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
I was able to backup my data, and use Solid Explorer with root to search through system files. But, I don't see that directory. I see: data/data/com.android.systemui but no systemui.tuner. Any other idea where those systemui tuner files might be lurking? I'm an RN with a kindergartener home from school, and as much as I love tinkering with Android, now is not a good time.
_Ra1n_ said:
Interesting! Exact same order of events.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Ditamae said:
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Click to expand...
Click to collapse
Sorry for the slow reply. Unfortunately I'm mostly out of ideas.
I'd ask in the general Android Help subforum: https://forum.xda-developers.com/android/help
You'll likely get more eyes on the question (where does SystemUI Tuner store it's settings & how to reset them) and hopefully someone with better knowledge on Android settings/preferences can provide some incite.
Homeboy76 said:
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Click to expand...
Click to collapse
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
_Ra1n_ said:
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
Click to expand...
Click to collapse
@Ditamae Rain is correct. I have edited my post.

Categories

Resources