Not sure what happend but a month or so ago, my vibration completely stopped working. I am unrooted on stock and fully up to date. I have seen others mention this and the previous thread (here: http://forum.xda-developers.com/z3-compact/help/vibration-t3271064) mentioned it but I received no response and the site shared (http://www.gogorapid.com/how-to-fix-vibrate-not-working/) did not work. Those codes are not taking on my device. Just trying to avoid a factory reset here, any solutions?
Related
Hi,
Starting a couple days ago the camera app on my HTC One will not work. I keep getting the error "unable to start the camera." I have a stock build, recently (about a week ago) upgraded to 4.3.
Now, I have determined that it is not simply the main camera app that is not working as no app that uses the camera (snapchat etc.) work either.
I have tried many things to fix this issue so far, rebooting, clearing the cache, doing a full factory reset, attempting to open in safe mode. I have come to the conclusion that since none of these attempts worked that this either has to be an operating system/4.3 build issue (although I'm not sure this makes sense as I had a working camera for many days after upgrading and the factory reset did not help) or this is a hardware issue.
Has anyone else encountered this or have any suggestions? I have read a couple scarce threads where others had this issue but a soft reset usually solved it. My problem seems to be a lot more severe unfortunately.
Any help is much appreciated.
Thanks,
Matt
Are you fully stock?
However, if a factory reset haven't help you, you can only send to the warranty...
hey everybody,
first post here, since I couldn't find any relevant help in the depths of this forum. So, my navbar buttons are not working anymore, well, two of the three, namely the "home" and the "show all active apps" buttons. "Back" is working like a charm. They all work in TWRP though, so I don't think it's an hardware issue.
How did this bug show first?
I flashed TWRP/RR/Magisk three weeks ago on my used Xperia T according to this post and it worked flawlessly. Yesterday I installed syncthing (an open source dropbox alternative) and configured it, but when I started syncing my phone shut down. When it rebooted the first thing that happened was SuperUser requesting access for "input devices" and I foolishly granted it (it never asked before) - since then vibration is on again (despite it being deactivated in the settings) and the two navbar buttons are selectable (and they react, too) but they have no function. I scanned every possible setting that might have resetted the keymapping but couldn't find any useful dialogue.
What to do next?
I assume I should try re-flashing RR, but 1) have not enough time to reconfigure my phone properly in the following weeks and 2) am a bit weary as I wouldn't know in what order I'd have to install it again. Would I just follow the post I linked above again?
Thanks in advance,
thoreau.
hmm, nobody experienced that before, huh? Can somebody pls tell me the correct order, when trying to reflash everything?
Hi,
I have a N9600 Snapdragon, currently on Pie.
The problem started occurring 3 days ago, for no particular reason, phone wasn't under water or dropped or anything.
When the fingerprint unlock is on, and the phone goes to sleep it shuts off.
Turn off the fingerprint unlock and everything is in order.
The fingerprint scanner functions within apps and for gestures.
Samsung support post here with people having the same problem on all 9s.
https://us.community.samsung.com/t5...f-when-usinf-fingerprint-security/td-p/346174
This cant be a hardware problem when its happening to so many people across models?
And yes, Factory Reset doesn't fix it, Its still there in safe mode as well. Ive even tried flashing a different region firmware, problem still there
Any help will be greatly appreciated.
Send it for repairs until fixed
tyrell22 said:
Hi,
I have a N9600 Snapdragon, currently on Pie.
The problem started occurring 3 days ago, for no particular reason, phone wasn't under water or dropped or anything.
When the fingerprint unlock is on, and the phone goes to sleep it shuts off.
Turn off the fingerprint unlock and everything is in order.
The fingerprint scanner functions within apps and for gestures.
Samsung support post here with people having the same problem on all 9s.
https://us.community.samsung.com/t5...f-when-usinf-fingerprint-security/td-p/346174
This cant be a hardware problem when its happening to so many people across models?
And yes, Factory Reset doesn't fix it, Its still there in safe mode as well. Ive even tried flashing a different region firmware, problem still there
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Either disable FP, or wait for a software update.
A quick search found this:
https://us.community.samsung.com/t5...usinf-fingerprint-security/td-p/346174/page/3
revert back to orio. Orio is most stable version.
Maybe make a factory reset with Odin
i had tried all of these ( Factory reset, back to oreo ) nothing fixes, to be honest, the problem begun on oreo.
Already sent it to samsung, they didn't find any problem, but after 3 times they gave me a new phone since those are the rules in my country
Open a RMA request and see what happens, ppl say that you should turn off FP, but it does make a substantial difference, at least for me, its pretty bad, using another method since i really don't like the iris scanner.
Same
My phone started shutting down on its own while in sleep mode out of the blue just the other day. Found this thread and discovered that this was the problem. This is super annoying. If a software patch is all that is needed, it can't come soon enough.
Hi guys, I've tried reaching out to the Samsung members community, seems no one has a fix. (https://us.community.samsung.com/t5...sung-galaxy-A70-no-network/m-p/1504196#M37558)
Problem: Woke up a morning, realized the phone is no longer picking up service. No aftermarket changes were done to the phone, I literally didn't install or making any changes to the phone over the night period, when this happened. No software were updated etc. The phone was about 6 months out of warranty.
Tried: Contacting Samsung members, email etc, but no updates. Lately I found the forum, linked above, where other used of different models of phones are having the same issue.
I also tried safe mode, resetting setting, then factory restore and finally flashing the phone using odin (respectively). Absolutely nothing has worked so far.
Now I'm here asking for help. I strongly believe that it has some sort of software issue which can fix this problem without actually taking apart the phone to change the antenna hardware etc.
Simcard is fine? Imeis are intact?
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.