Hey Everybody
I have troubles since i clicked a button in my status bar. I removed EVERYTHING from my home and lock screen (i cant even tell witch one i see). There are no Icons at all. only my desktop background is visible and working (animated bubbles). there is no button working except from power button (and its menu to restart). a friend of mine was able to get a screenshot with some button-combination (vol+ + home?)
first: i am not an expert with android, but have a lot of experience in working with Linux shells.
what i have done:
maybe it has something to do with it or not, i don’t know:
i enabled multi view / multi window or extended desktop (sorry i don’t know the name, and as there is nothing shown...)
i opened my status bar and there were some new icons (next to the small watch in the right corner), witch i haven’t seen so far and clicked it. than it opened a "new" screen with only my background.
as i thought it is maybe only a "dead" app i tried to restart my phone. but: there is only that screen working. no PIN question, or something.
i tried to reset dalvic and normal cache. -> no change.
i use RESURRECTION REMIX 5.7.3. on N7100
Recovery TWRP 3.0.2-0 is still working and
i hope somebody can help me to solve my problem without factory resetting. i wont reinstall everything.
thanks a lot
Are you able to restore a TWRP back up? You could try flashing the ROM again without wiping.
theoretically, yes, but i did not have on. so i cannot flash it.
i am searching for an commandline option to change the settings. but i have no clue where to search, and in what files the configuration lies...
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
A strange thing happened yesterday. My phone OP3 was idle for few hours. When i picked it up, i saw that it had shutdown. On restarting it, I noticed that few of my settings had changed as below
Buttons swap : I had enabled it, but was disabled
Sound: Section System (Touch Sounds, Dial pad tones screen locking sounds) had been enabled from earlier disabled state
Gestures: All gestures disabled
I see no new notifications
I cant pull down the notification panel/tray. only see one line of shortcuts
Developer options menu is present but when i click it, I get message "Developer options are not enabled for this user"
My power long press options were reset to default (without recovery).
I cleared cache from recovery/launcher (oneplus) yet #4,#5,#6 are not fixed.
I found similar problem with solution for marshmallow but it doesnt work for me. http://forums.androidcentral.com/sa...ton-settings-button-dnt-work.html#post5083902
Last option would be a factory reset. Anyone faced similar issue?
PS: I had clean installed OB9 and then OB10 OTA with stock recovery.
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.