Related
Hello.
I recently got myself a Samsung Galaxy Tab 3 7in and everything seemed to be working just fine until the system eventually prompted me to update the Samsung software. I followed the steps, the tablet downloaded the update files itself and rebooted in order to install the updates. Problem is, during the reboot/installation process the screen remained black with just 2 lines of pixels on across the screen, I though this was part of the booting process but it just stood there for more than 10 minutes so I decided to turn it back on. Everything seemed to be fine, but then an error message came up saying there could be problems with the software (i didn't pay too much attention), but after this it won't let me install any apps. After an app is done downloading a message pops up saying "unknown error code during application install -110", plus my computer (or any other computer) doesn't detect when it's plugged in via USB cable. I've tried doing several factory resets and wipes and still have the same issues. Tried installing Kies but it won't detect it either.
How can I repair the firmware without having to connect the tablet to my computer? Is there anything I can download directly to it or transfer via Bluetooth to re-install the software?
Any help will be very much appreciated
Try resetting it back to factory defaults. You can google it easily.
hypnonaut said:
Hello.
I recently got myself a Samsung Galaxy Tab 3 7in and everything seemed to be working just fine until the system eventually prompted me to update the Samsung software. I followed the steps, the tablet downloaded the update files itself and rebooted in order to install the updates. Problem is, during the reboot/installation process the screen remained black with just 2 lines of pixels on across the screen, I though this was part of the booting process but it just stood there for more than 10 minutes so I decided to turn it back on. Everything seemed to be fine, but then an error message came up saying there could be problems with the software (i didn't pay too much attention), but after this it won't let me install any apps. After an app is done downloading a message pops up saying "unknown error code during application install -110", plus my computer (or any other computer) doesn't detect when it's plugged in via USB cable. I've tried doing several factory resets and wipes and still have the same issues. Tried installing Kies but it won't detect it either.
How can I repair the firmware without having to connect the tablet to my computer? Is there anything I can download directly to it or transfer via Bluetooth to re-install the software?
Any help will be very much appreciated
Click to expand...
Click to collapse
my friend has the same problem. did you fix the issue? if so how?
I am using the Apex Launcher but I think this is possible with stock launcher as well hopefully it helps someone. This is one way to do a factory reset is:
You will need your MSL TO DO THIS. If you don't know it put the "Factory Mode" shortcut on your home screen then skip down to the 2nd part of this post & install the msl app.
FACTORY RESET:
1) long click on the home screen
2) click on shortcut
3) select Activities
4)Scroll down to "Factory Mode" tap it then select the dropled down one. This will put a Shortcut on the Home Screen.
5) Find the Factory Mode shortcut you just made & tap it to open it.
6) Dial ##786# then on the screen that pops up
7) select "RESET"
8)enter your msl in the box that popped up then select ok then the device will reboot & when it powers backup it will be like it was from the factory & if you don't know your MSL follow the instructions below.
TO GET MSL:
1) In a browser type bit.ly/mslutility - can sideload if needed
2)install app
3) Open app & click get MSL it will most likely fail this is fine.
4) click on the factory mode shortcut you made to open it
5) dial ##3282# & put in 6 zeros-it will tell you that it's incorrect this is fine. Go back to home screen
6) Open the MSL App & click on Get MSL-this time it should give you your devices 6 digit MSL Code. Write it down. Then do step # 6 above to reset your Device.
This shortcut will allow you to put the Sprint SGT3 into DIAG MODE(##3424#) , get into the ##data#(##3282#) menu, do the factory reset ##RTN# (##786#) & most likely any other Dialer/hidden menu's for this device.
Thanks to the MSL App builder(not sure who it is so let me know please)
Sent from my SGT3 SM-T217S using Tapatalk 4 I Flashed 2 Selectel
What is it trying to update to? 4.2.2?
Levi Woodard
Woodardwoodworks.com
Sent from the XDA premium app.
I haven't used my nexus in a couple months, turned it on today and there's a PIN lock.
I don't remember ever setting this up, I tried my usual PINs and none work.
I keep trying but I never get a forgot password log in with google option. I always get 5 wrong entries, wait 30 secs.
I'm at 35 incorrect PINs so far.
-I've also tried going to device manager but my device is always unavailable so I can't send a lock screen to it.
-I can't do a factory reset because my recovery is broken and I can't get into it to erase my data.
-I can't flash a new recovery because my computer isn't a trusted device to access it and I can't allow it because I can't log in.
I'm not sure what else to do.
I have a secondary user on it but I can't turn on the developer options for it because it's not the primary account.
Any ideas what I can do?
If you can get your driver issues figured out, so that the Fast Boot driver works, you can just reflash images from the Bootloader. You do not need to get into Recovery, or get passed the pin lock to reflash. To make it easy, you can use something like Wug's NRT and use the "Bricked Device" option to flash images from the bootloader screen.
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
Please ensure you REALLY use the correct key combo! Just saying bla does not tell us what exactly you tried.
If you really can't get in you can try to Boot into download mode
https://m.youtube.com/watch?v=0cbLhpWq5C8
Then use lgup to reinstall stock ROM and do all the stuff again to get twrp, root and a custom ROM.
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
raptorddd said:
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
Click to expand...
Click to collapse
Thank for your answer ! No it couldn't even boot in download mode
I resolved my problem by forcing again the buttons to reset completely, it finally showed me after about 30 boots or more the reset screen, I said "ok" ; and in fact it just rebooted saying "updating Android", I did not lost anything.
I still don't understand how it happened but anyway !
I don't know if it's possible to set the topic as resolved ? I don't find it
Hello everyone,
Yesterday, after I tried to charge my LG G4, it stopped booting properly: it seems to boot "normally" under the hood, except that the system UI is not properly loading so instead I get a black screen and a message "Unfortunately system UI stopped working". If I click "ok", it comes back within two seconds (the screen stays black apart from the error message). I cannot do anything, like unlock the phone or access anything on it, despite the fact that I can hear notifications coming in.
Unfortunately phone is not rooted, developper mode isn't enabled, and I don't have a custom recovery. I would do a factory reset if it weren't for my Google Authenticator codes, some of which I haven't properly backed up like an idiot. Thus I was wondering what I could do to back up my phone or solve the issue.
Here is what I've already tried:
Press down VOLUME DOWN + POWER to enter recovery mode, but since I don't have custom recovery this only gives me the option to do a hard factory reset and lose all my data.
Use adb commands to access my phone, but I get "unauthorized device" because I haven't enabled developper tools on the phone.
Use the app "LG Bridge" on my mac, but it also doesn't work for the above reason.
I see three possibilities, but I don't know whether any is genuinely doable:
Solve the issue of the error message, which from what I've read requires me to wipe the cache. But how to do that without custom recovery?
Somehow bypass the UI to unlock the phone and unable developer tools
Manage to backup the phone from my computer while its locked without developper tools enabled.
Note that obviously this is my phone, I know my passwords, I have access to my Google account, etc.
Any help would be greatly appreciated, without my Google Authenticator data I'll be locked out of an important email account.
satiricon22 said:
Hello everyone,
Yesterday, after I tried to charge my LG G4, it stopped booting properly: it seems to boot "normally" under the hood, except that the system UI is not properly loading so instead I get a black screen and a message "Unfortunately system UI stopped working". If I click "ok", it comes back within two seconds (the screen stays black apart from the error message). I cannot do anything, like unlock the phone or access anything on it, despite the fact that I can hear notifications coming in.
Unfortunately phone is not rooted, developper mode isn't enabled, and I don't have a custom recovery. I would do a factory reset if it weren't for my Google Authenticator codes, some of which I haven't properly backed up like an idiot. Thus I was wondering what I could do to back up my phone or solve the issue.
Here is what I've already tried:
Press down VOLUME DOWN + POWER to enter recovery mode, but since I don't have custom recovery this only gives me the option to do a hard factory reset and lose all my data.
Use adb commands to access my phone, but I get "unauthorized device" because I haven't enabled developper tools on the phone.
Use the app "LG Bridge" on my mac, but it also doesn't work for the above reason.
I see three possibilities, but I don't know whether any is genuinely doable:
Solve the issue of the error message, which from what I've read requires me to wipe the cache. But how to do that without custom recovery?
Somehow bypass the UI to unlock the phone and unable developer tools
Manage to backup the phone from my computer while its locked without developper tools enabled.
Note that obviously this is my phone, I know my passwords, I have access to my Google account, etc.
Any help would be greatly appreciated, without my Google Authenticator data I'll be locked out of an important email account.
Click to expand...
Click to collapse
Well at least you can backup your phone in download mode with SALT ( https://bit.do/SALTatXDA ) but restoring is another story.
Sent from my LG-H815 using XDA Labs
Thanks a lot for your reply! I'll try backing up with SALT tonight. There are two things I'm wondering:
How do you think I could extra data from the backup?
Will I be able to wipe the cache or enable usb debugging with SALT? That might solve the issue.
satiricon22 said:
Thanks a lot for your reply! I'll try backing up with SALT tonight. There are two things I'm wondering:
How do you think I could extra data from the backup?
Will I be able to wipe the cache or enable usb debugging with SALT? That might solve the issue.
Click to expand...
Click to collapse
You can mount the userdata partition on Linux (e.g in FWUL) and then browse through it like it's on your phone.
You can wipe the cache paetition in SALT yes. It's in the advanced menu there (erase partitions -> select cache and only that). It will not wipe the dalvik cache though.
I dunno about the USB debugging though. Maybe there is a way but if so you would need a very unrestricted download mode (depends on model and firmware). And the whole process is not easy.
It requires again SALT and there you have in the advanced menu the option to open a shell.
Here you can mount userdata with
mount /data
But it's usually mounted already. Then it's a try and error. You could e. G. try to delete the dalvik cache etc.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
You can mount the userdata partition on Linux (e.g in FWUL) and then browse through it like it's on your phone.
You can wipe the cache paetition in SALT yes. It's in the advanced menu there (erase partitions -> select cache and only that). It will not wipe the dalvik cache though.
I dunno about the USB debugging though. Maybe there is a way but if so you would need a very unrestricted download mode (depends on model and firmware). And the whole process is not easy.
It requires again SALT and there you have in the advanced menu the option to open a shell.
Here you can mount userdata with
mount /data
But it's usually mounted already. Then it's a try and error. You could e. G. try to delete the dalvik cache etc.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hi!
I've found out that the Google Auth keys are in /data/data/com.google.android.apps.authenticator2/databases/databases. So I need to backup /data/. However, when I show the list of partitions with SALT, I don't see /data/. Is there a way to backup /data/ on my unrooted device?
Secondly, I haven't managed to wipe the dalvik cache with the command shell, would you be able to point me in the right direction?
Thank you so much!
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.