Last night I installed Manilla2D, then the GPS - all worked excellent (didn't get satellites, but didn't go outside - beside the point), until I tinkered with the weather XML file and installed the rest of the files for M2D in the "Not necessary but recommended" folder. Having installed so much at once, I am not sure what caused this problem.
Problem: certain events aren't happening - weather module used to work with any city in the default list - now, clicking a city just brings me back to the screen that says "select a city", and the unresponsiveness continues to other programs. So I began uninstalling a couple that I thought may be the culprit, and now on startup, I get a "tap here to launch touchFlo". After tapping, it says launching, then it goes back to "Tap here to launch touchFlo...".
At this point, what do I do? So far I haven't done anything but install CAB files. Is there some way to just restore this to whatever state (even factory defaults, etc)?
you can go into settings and click on clear storage to reset everything. Keep in mind you will lose all personal data including contacts, so back every thing up.
You could also try going to settings then remove programs and start uninstalling programs one at a time untill you find the culprit.
Which update did you install? The latest is update 20, but update 21 is an elfin update so that's the one I picked. (The Elfin is a t least related to the vogue, update 20 is meant for ALL htc devices)
Another thing, what did you mean by "then gps"?
The proper order would be to have an upgraded radio first, then install M2D
The only known fool proof way to completely remove M2D itself is a hard reset. While this is true for M2D itself, you can try selectivley unloading the "extras" starting with the last and testing one by one.
BTW, a hard reset is done by holding the power and camera buttons down together while pressing the soft rest button.
Hi all!
I'm new to DHD but NOT to android as I have a HD2 running android since July 2010!
However i made a fatal idiot error when i was so existed to the extent where i updated the software directly when getting it and now i'm stuck with it. I have:
-2.3.3 android
-2.42.415.1 build
-12.54.50.25U_26.09.04.11_M2 baseband.
- and of course a stock ROM unrooted and locked!
Ok so here's the minor issues i'm having:
1- Although i have disabled (unticked) all prediction and spell correction in keyboard settings, it's still giving me a red line under wrong words (or so it thinks) and gives me the ability to add it to custom words although i dont want that.
Any help on that?! (i know i can install another keyboard but the stock one is the perfect for me)
2- Weather animation (after unlock) plays 1 on 20 times with sound effects and the remaining 19 times without any sound!
Any help on that too?!
4- The magnification window that is created when u scroll on a keyword while typing is shifted upwards!!!
Example: if i write : asdaksdj asd midnight lkj asdakjd akj daklsj dalkjsd
asd asdl kjas dlkajsd lakjd laksjd daytime laskjd laskjd laskj dlakjfggjwpio
qweoiusdfkj dfknsdlfisdfop
and if slide on "daytime" i can see the word "midnight" magnified while i can see the top of the cursor moving on the word "daytime"!!!
However also 1 on 20 times it works normally!!!
Any help?!
3- Finally one irritating issue is that i cannot set a security lock screen for this phone!
In fact, i "can" set a "pattern" or a "PIN" or a "Password" without any problem, however it does only work once after unlock!!! After that it will be disabled automatically. When i go to settings i can see like if there's no security locks!!!
Any help on that please?! (PS whatever the duration of autolock (i mean immediately, after 3min, etc....) is set, it's still the same)
Thanks guys!
Anyone please?!
red dots are bug(or maybe htc didnt want to disable that) , also all htc gingerbread update have bugs, that's the reason i rooted my phone, because factory reset didnt help me.
i didnt have problem with weather.
try factory reset, and if that does not solve the problem, root is your friend.
before you done factory, remove battery for few seconds, and see if you still have problems.
I think you try doing 'Factory data reset'
Factory data reset will lose all data on your phone memory but not the data on SD card. So make sure you back up SMS, Contacts and calendar entries etc..
Then go to 'Settings > SD & phone storage > Factory data reset
then follow the instructions.
Hope this will help,
Good luck!
the question is
How in the hell you couldn't downgrade ...to get ROOT
Hello,
I have special SIM card issued by my operator which enables mobile ID use (with sPIN authentication) for connecting to bank or e-government. Works like this:
1. The user clicks the "Log in with mobile ID" option on a supported website
2. The phone displays a screen indicating that a connection is being made
3. The user is prompted to enter a mobile ID sPIN code into the phone
4. The screen on the phone disappears and the website is automatically reloaded with a logged in screen
It worked fine with stock firmware, but after I've rooted my HOX I'm not getting sPIN request screen anymore (step 3).
Have tried several custom AOSP or AOKP ROMs without luck, but found some of them partly working.
One I'm using right now is [ROM][4.2.2] Slim Bean - Endeavoru [STABLE][Build 7]. Mobile ID worked for first days after flashing it but later I was only able to use it for a few random times (after restarts). Then it works till next restart...
I was first thinking its an issue of incompatible apps I've installed or system settings I've mixed up, but somehow it works sometimes after restart (with very low success rate though). Also tried to restart into safe mode - it worked for the first time, but no luck for the next ~20 safe mode restarts after that.
I've also found hints it could be stk (SIM Application Toolkit) related problem. I can see SIM toolkit in my app list, though it doesnt' show up on running processes on developer tools.
If you're still reading this and have any ideas, please make some comments, maybe it would help me to get back on the right track, thanks!
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...
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.