Hey guys I've been searching all over and haven't seen my particular issue.
Phone: Verizon Dev Galaxy S5 w/ CM12 Android 5.0.1 and TWRP
LG G Watch: Latest Gohma 2.2 rom Android 5.0.1 and TWRP
I've been on 5.0.1 on my phone for a couple weeks now and my G Watch has worked fine on 4.4.4. A few days ago I got an update alert that tried to install but failed in TWRP. It still worked fine for a couple days. Yesterday I noticed that my watch wasn't vibrating on alerts. It would vibrate for calls but not any other alerts.
So yesterday I updated to Gohma 2.2 and it seemed to work fine. Texts and other alerts would vibrate fine. Today I notice again that I'm not getting any alerts on my watch.
I've checked everywhere I can think to check. All apps are set to vibrate. I didn't disable any alerts in the Wear app. The watch vibrates fine when I but my palm to it to darken the screen. It also does fine on calls.
Any ideas? Do you think my watch is going bad (vibrator dying)?
Also note that I just tried to reboot recovery to wipe cache with the Wear Control app and it's not doing anything in the "system" section of the app (Reboot Recovery or Reboot Bootloader). I may try to do a full restore to stock tonight and run it that way for a few days.
joshw0000 said:
Also note that I just tried to reboot recovery to wipe cache with the Wear Control app and it's not doing anything in the "system" section of the app (Reboot Recovery or Reboot Bootloader). I may try to do a full restore to stock tonight and run it that way for a few days.
Click to expand...
Click to collapse
try to put theather mode off, i had the same problem, if i turn on theatre mode wath have not vibrations, but if its on, yes.
I hope be helpfull
Related
OK lost sound about a WK ago after a factory reset, have got it rooted now and I am still on stock rom. A total stock ROM would be nice; however, any knowledge of how the sound on android can be fixed would be much appreciated. Also, I get a popping sound while typing even when turned all the way down; although, it is silent when mute.
Firmware flash curtis website firmware download
Pa®aD®oid said:
OK lost sound about a WK ago after a factory reset, have got it rooted now and I am still on stock rom. A total stock ROM would be nice; however, any knowledge of how the sound on android can be fixed would be much appreciated. Also, I get a popping sound while typing even when turned all the way down; although, it is silent when mute.
Click to expand...
Click to collapse
In an attempt to fix the sound I have ran into an issue. RKbatch tool error download firmware fail at 97% happens every time. Used plenty different drivers and tools, event the ones with the firmware. Tab is broke with no os or recovery, can get it to show on device manager; however, can not get firmware downloaded, for the following problem.
I have had my S4 (SCH I545) rooted for at least a year now, and today while I was walking down a sidewalk to my house I felt my phone vibrate. Thinking I received a message, I pulled it out, and was greeted by the white "Samsung Galaxy S4" boot splash. 5 minutes before, I was using my phone normally. Battery was on at least 50%. Since then, I have been completely unable to boot up my phone. I can only turn it off by removing the battery - it is completely frozen. Booting into (TeamWin) recovery works, and I backed up my phone to an SD card before completely wiping it. Even after the wipe I am still stuck on the splash screen. Again, I was not attempting to change anything, only using the phone normally. Nothing OS-related on my phone has changed since I rooted it a year ago. Have never even updated .Any ideas? I've been looking for hours.
EDIT: Plugging the phone into either an outlet or a computer will cause it to freeze on a picture of an empty battery with a (non-moving) loading circle. It is still completely unable to be interfaced with in any way (Other than recovery booting).
What battery percentage does twrp say?
Sent from my OtterX running AICP using Tapatalk.
---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------
You should charge it in twrp, then push a ROM or backup to your phone.
Sent from my OtterX running AICP using Tapatalk.
So I got it working fine after flashing from odin. Today I flashed a Google Play edition ROM and it seems to be working fine with one exception, messages are not being received. The default messaging app will not open at all (Crashes immediately). Using Hangouts will allow me to send messages (confirmed with another device) but even after wiping messaging data and clearing cache I cannot receive texts. Any ideas?
EDIT: I tried flashing to a more updated version of the Google Play edition and apparently now my bootloader is locked because I got message saying to go to a verizon store for help. Guessing I now need to use Odin install a default to re-unlock the bootloader?
UPDATE: Tried to use ez-unlock considering I am on android 4.2.2 with MDK and I hard bricked my phone. Why did that just happen?
___Pyro___ said:
So I got it working fine after flashing from odin. Today I flashed a Google Play edition ROM and it seems to be working fine with one exception, messages are not being received. The default messaging app will not open at all (Crashes immediately). Using Hangouts will allow me to send messages (confirmed with another device) but even after wiping messaging data and clearing cache I cannot receive texts. Any ideas?
EDIT: I tried flashing to a more updated version of the Google Play edition and apparently now my bootloader is locked because I got message saying to go to a verizon store for help. Guessing I now need to use Odin install a default to re-unlock the bootloader?
UPDATE: Tried to use ez-unlock considering I am on android 4.2.2 with MDK and I hard bricked my phone. Why did that just happen?
Click to expand...
Click to collapse
I'm not completely sure but from the looks of it ez-unlock was made to unlock the s3 bootloader
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
I've got a number of Moto G that have been working fine for months. Suddenly, one of them is constantly having apps crash. I'm talking literally every second. As fast as I can close the crash notification popup another one pops up for another app. android.process.acore, com, com.google.process.gapps, dozens of others. A reboot will fix it for a few minutes, but then it goes on a frenzy again. I've tried wiping the cache and dalvik cache with clockworkmod recovery. I've tried uninstalling updates for google play services. I unfortunately don't have a backup created for this device. I would try to factory reset, but the last time I tried factory resetting a rooted Moto G through the android interface it bootlooped. If I can't fix this, is there a way in clockworkmod recovery to "reset" back to just after I rooted the phone? If not, I may be able to copy over a backup from a similar phone, but I'm not sure if that would work.
EDIT: I think this phone might have just **** the bed. Bootloops when trying to turn on normally (unlocked bootloader warning screen, then motorola spinning world graphic, then off). Volume Down + Power in off state does nothing so I can't even get into the bootloader.
I've Galaxy S4 Verizon - SCH1545 with 5.0.1 Lollipop and Baseband 1545VRUGOF1. Bought a month ago, it worked fine for 15 days but then sound went off. Also I was unable to play any video nor any application is working. Getting error of Unfortunately UI has stopped and(App) is not responding. Upon trying below steps, sound comes sometime and app works fine then but it doesn't stay long when again starts same behavior. I get it when start phone and it doesn't play the sound when shows Samsung logo.
1. Cleared the cache of Play Store, Google Framework and Google Play Services
2. Wiped cache partition and Factory Reseted
3. Rooted the device
4. Unable to install TWRP or CWM
5. Odin gives Nand write error
6. If phone stuck with "Use Verizon Software Repair Assistant...", able to bring it back by CF Auto JFLTEXX-GTI9505.tar.md5. Although Odin gives error but after error, I disconnect the USB cable and phone starts
7. Tried Verizon Software Repair Assistant and Samsung Kies to update the firmware but same issue
8. Can't find GooManager in Play Store. Installed by APK but GooManager doesn't find any list or unable to find Script (to install TWRP)
9. Rooted the phone. Confirmed by Root Checker but Flash Fire shows "are you rooted?"
will be very thankful for anyone who has idea or had same problem.
As far as I understand custom recoveries are only available for MDK. Your best bet is to odin your current build and start there.
Jalh said:
As far as I understand custom recoveries are only available for MDK. Your best bet is to odin your current build and start there.
Click to expand...
Click to collapse
I don't mind any rom or whatever settings are. Just want to solve sound and other issues I'm facing.
I tried Samsung Kies and Verizon Software Repair Assistant to reload the firmware but still the same issue of sound goes off, youtube, apps and videos don't play.
I know its not hardware problem because this all gets ok sometimes after maybe reset, wipe cache, clear play store/services storage or factory reset... then goes off again after some time.
thanks for the reply
noticed one more thing. If I keep it off for few hours, the sound come back. And again goes off after some time.