I was JUST trying to manually flash android 9 to my AT&T s9+. I bought it used, so I do not have access to the original Samsung USB (figured that was worth mentioning upfront).
After doing some research online, I found a site called firmware.science that offered the manual update files I was looking for... or so I thought. I followed the directions and flashed this firmware (G965USQU3ZRJ9), which DID give me Android 9, but it gave me a few problems...
The phone vibrates once right after screen off - I cannot find a way to turn this off.
I cannot turn the screen immediately back on after turning the screen off - For some reason, the power button stops responding after screen off for about 5 seconds. Then, I can turn the screen on again.
The phone vibrates 3 times about 3 or 4 seconds after screen off - Oddly, it is after these vibrations that the power button starts working again and I can turn the screen back on.
The phone ignores the S-View Cover - The phone just goes right to the lock screen instead of the always on display when the S-View Cover is closed.
Whenever I factory reset it, I constantly (every few seconds) get nagged by the "reminder" app crashing. This happens until I disable it.
I constantly get security alerts about com.samsung.lool and com.google.android.gms.unstable (I can't remember exactly what the packages were): "Security Notice - This Pop-up is only for Develop Phase (noship). Please do the following to fix permission denial. (QA) please attach Log(*#9900#) and screenshot(Module Info) (PL) Please assign PLM to module TG.
I cannot update the Google app from the playstore
I would like to get from this to a stable android 9 firmware. Even if that involves going back to android 8.
simmonsdeux said:
I was JUST trying to manually flash android 9 to my AT&T s9+. I bought it used, so I do not have access to the original Samsung USB (figured that was worth mentioning upfront).
After doing some research online, I found a site called firmware.science that offered the manual update files I was looking for... or so I thought. I followed the directions and flashed this firmware (G965USQU3ZRJ9), which DID give me Android 9, but it gave me a few problems...
The phone vibrates once right after screen off - I cannot find a way to turn this off.
I cannot turn the screen immediately back on after turning the screen off - For some reason, the power button stops responding after screen off for about 5 seconds. Then, I can turn the screen on again.
The phone vibrates 3 times about 3 or 4 seconds after screen off - Oddly, it is after these vibrations that the power button starts working again and I can turn the screen back on.
The phone ignores the S-View Cover - The phone just goes right to the lock screen instead of the always on display when the S-View Cover is closed.
Whenever I factory reset it, I constantly (every few seconds) get nagged by the "reminder" app crashing. This happens until I disable it.
I constantly get security alerts about com.samsung.lool and com.google.android.gms.unstable (I can't remember exactly what the packages were): "Security Notice - This Pop-up is only for Develop Phase (noship). Please do the following to fix permission denial. (QA) please attach Log(*#9900#) and screenshot(Module Info) (PL) Please assign PLM to module TG.
I cannot update the Google app from the playstore
I would like to get from this to a stable android 9 firmware. Even if that involves going back to android 8.
Click to expand...
Click to collapse
According to ATT's website, the Android Pie update for their S9+ was G965USQU3CSAB. The firmware number you downloaded does not match the Pie firmwares that ATT has on their website.
Click on the past versions to see their firmware history.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U&gsi=5avrp3
Related
hi all !
just a quick post for a few little questions i have, and havnt seen answer for in the forum. ive had my s3 for a little over 2 weeks, and have noticed a few minor issues which i havnt been able to fix,
firstly, i cannot work out how to get the address bar back on the browser, but only on the facebook mobile site, i have to scroll all the way to the top, where as other site the address bar remains there the whole time.
also i cannot save photos from the facebook site, but can other sites.
secondly , if the screen is off and i plug in the charger, the screen comes on and stays on, unless i press the power button, whereas with any other phone i have had, the screen just turns itself off after about 5 seconds. note this only happens when charging any othertime it turns itself off
edit : also wifi dropout on wpa/psk2 (bt home hub) wifif drops out, but comes back almost instantaniously, , have tried the powersave mode as suggested by others *0011# but to no avail,
and last but not least, i rooted my phone but unrooted it to update it, but it wont update comes up with some sort of signature verification failure, with OTA update, im going to try a usb update later though
thats about it for now, any help will be much appreciated
Perhaps this forum could help.
I received a used Xperia Mini [ST15i] as a xmas present from my bro-in-law.
It has Android 2.3.4 – Kernel is 2.6.32.9-perf
Build is 4.0.2.A.0.62
It had a lot of his apps on and foolishly I went into application manager and deleted a whole lot of stuff when suddenly the phone went into what I originally thought was a Haptic Feedback loop.
I was unable to power off so I had to remove Battery and restart from there. The loop starts slowly with one or two vibrates every 10 seconds then it becomes rapid and settles into an almost clock like rythm, two vibration per second.
I tried to get into settings to turn off the haptic feedback indicator but it seems like for each vibration [or tick] , an invisible ‘enter’ has been pressed somewhere on the screen so the only way to get into settings is to press the ‘back’ button and at the same time press the ‘settings’ button to interrupt the loop and after 5 vibrations or so I am able get into the ‘settings’ menu and un-tick the Haptic indicator. The phone goes quiet but the ‘clock’ or what ever process is looping continues. It completely blocks me out from doing anything unless I can interrupt it via pressing the back button.
To try get over this, I have reloaded the complete 150mb software via sony update. Afterward the problem still persisted. I have done both factory resets and still the loop process continues.
Have I screwed the Kernel? Any help or advice would be great. The phone is locked .
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Soda_47 said:
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Click to expand...
Click to collapse
Thanks Soda. Just chatted with Sony. Luckily phone is still under warranty. Cheers
I'm happy to help
Okay, I will be as detailed as I can be. First things first, it's my moms phone. Me and my dad are the "tech people" in my house, and he doesn't know as much about Android as I do, so he referred her to me, and I'm lost...
What is it: Samsung Galaxy SII (GTI-1900), running Android 4.2 I believe (I upgraded it previously to fix some problems)
Now it seems some of the problems it used to have, have returned with a vengeance! For some reason, when she tries to shut it down by holding the power/sleep/wake button, it just shuts down. Upon being off, it simply goes through a cycle of showing the battery loading, then the battery being fully charged, then shutting off again, this is all while UNPLUGGED!
But wait, there's more!
Upon turning on, which you have to plug it in first to turn it on, the task menu, whatever it may be called, task monitor/manager I suppose, says that two things are running, the clock, which is understandable due to alarms that are set daily, and Google Play Music, which she doesn't use Ever. Somehow it has started at boot... Upon tapping "close all" it closes all, but the widget still shows 2 processes running, which does not show up after tapping the widget and opening the task monitor. My dad's phone is perfectly normal, yet is the SAME PHONE. any idea how this is happening?
EDIT: It also, after being unplugged, will show "Charged" on the lock screen. the lock screen is the default for the device.
P.S. The ROM I flashed to it is NOT CUSTOM. I got it direct from Samsung updates. It is however, I believe, the European version, as I could not find an american version. The phone is also not rooted.
nocht420 said:
Okay, I will be as detailed as I can be. First things first, it's my moms phone. Me and my dad are the "tech people" in my house, and he doesn't know as much about Android as I do, so he referred her to me, and I'm lost...
What is it: Samsung Galaxy SII (GTI-1900), running Android 4.2 I believe (I upgraded it previously to fix some problems)
Now it seems some of the problems it used to have, have returned with a vengeance! For some reason, when she tries to shut it down by holding the power/sleep/wake button, it just shuts down. Upon being off, it simply goes through a cycle of showing the battery loading, then the battery being fully charged, then shutting off again, this is all while UNPLUGGED!
But wait, there's more!
Upon turning on, which you have to plug it in first to turn it on, the task menu, whatever it may be called, task monitor/manager I suppose, says that two things are running, the clock, which is understandable due to alarms that are set daily, and Google Play Music, which she doesn't use Ever. Somehow it has started at boot... Upon tapping "close all" it closes all, but the widget still shows 2 processes running, which does not show up after tapping the widget and opening the task monitor. My dad's phone is perfectly normal, yet is the SAME PHONE. any idea how this is happening?
EDIT: It also, after being unplugged, will show "Charged" on the lock screen. the lock screen is the default for the device.
P.S. The ROM I flashed to it is NOT CUSTOM. I got it direct from Samsung updates. It is however, I believe, the European version, as I could not find an american version. The phone is also not rooted.
Click to expand...
Click to collapse
I too faced a similar problem. The "UNPLUGGED CHARGING" was due to some fault in my micro usb cable in the phone. I resolved it by cleaning the usb port with a brush/needles. BTW dont force too hard. This may not be the only solution. But do try this. :fingers-crossed:
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
UPDATE: I'm an idiot / Samsung's instructions on how to do a hard reset are awful.
I decided to Google how to do a hard reset and discovered that when in the Recovery Menu, you need to hold down the Power button to choose an option (Samsung's instructions just tell you to press the Power button until you highlight what you want and I assumed it would automatically choose that after a few seconds because the phone would restart for me). Watch is now factory reset and so far the screen issue appears to be resolved. Another four hours of transferring music it is then.
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
allow to power down
BOZG said:
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
Click to expand...
Click to collapse
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
theroblog.com said:
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
Click to expand...
Click to collapse
samsung gear s screen on and off..looping
There you go. Not much to read there though as it's just me and OP. The problem re-emerged for me after a few days again so I was forced to do another hard reset to actually use the watch. I noticed it when I woke up in the morning and noticed that another update had been pushed to the Gear app. That's twice now that this has happened shortly or immediately after the Gear app was updated.
I haven't been able to uninstall an app / change clock face to see if it works as the watch is completely unusable when it happens to me. The Gear app registers that it's connected but it's impossible to change anything from there either and if I turn the watch off and back on again, the Gear app will no longer connect.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Not sure if I've actually tried letting the battery drain. I'll try that the next time it happens (if it happens).
I had the same problem after the update, a reboot didn't solve the problem. Eventually the battery drained. After a recharge most is fine but I never know which watch face will suddenly appear.
Same issue again. Didn't see the Gear app updating but there was an update released the day before. Going to switch off auto-updates and see if it definitely the problem. Just seems too coincidental that this problem starts right after an update is released for the Gear App.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Started doing it again yesterday so let the battery die and charged it fully and it didn't help. Left it on the box overnight and brought it to a Samsung Service Centre this morning and of course it was working again when I took it out of the box! Left it with them anyway so I'll see what happens.
I've had my Gear S a few weeks and it has also started doing this, I will give some of the suggestions here a go.....
EDIT: So opening the Gear Manager App once Bluetooth was connected brought my Gear S back to life. Phew!
It's only entered this state after I turned it off at night and then turned it back on in the morning - so it had been off roughly 8 hours. Upon turning it on the screen would cycle from the right time and notification numbers and the wrong time and wrong notification numbers too off again.
@ BOZG - Just wondering if you got your S back yet and if so, were they able to tell you what was causing this on/off problem. Mine just started doing it yesterday.
Also, how did you find the "Samsung Service Centre"?
holding the screen seems to cause it...
Had to send mine to Samsung for a new charging cradle and they updated the software to latest, when i got it back it seemed fine. Then i was messing about with it and was holding the screen to my chest for a while and that seemed to cause it to happen. It seems to be the screens gets too much activation and it flips out. I think this is what started the problem last time it happened.1
Switching to power saving mode seems to fix it for me... have to wait until it gets low on battery and when the low bat warning comes on, switch then... leave for a bit then switch back to normal.
I called Samsung Thursday and they sent me a UPS label and told me to send the watch, charging cradle and AC charging cord back in for service. She told me it takes about 7-14 days. We shall see.
Happy to have found this. </rant>I'm starting to get enough of this Samsung stuff. I had the note 2 and now I have the note 4 and gear S. That is mote then 1000 euro of equipment. And today when I tried the restore to fix this, both the phone and the watch rebooted. Crazy that they can not build good software and hardware for this price. </rant>
To me it seems that is freezes somehow when this happens. It kept jumping back to 22:10 time and changed to the watch-face and settings keep rolling back. It seems to happen to me, when the watch is off for some hours. The samsung way... no update to fix this.
solved for me
hi first of all sorry if i do any mistakes because English is not my language
i had similar problem and i found the solution at least in my case . THE PROBLEM IS NOT WITH THE GEAR S
all was ok using 4.4.2 kitkat on my note 3 before few months i upgrade with lollipop 5 official from sammobile via odin
from that moment the problems begin with the reconnection of the gear with the note
long time to connect and no auto reconnection only manual by turning off-on the bluetooth
i was boring to do format to the note3 so i left it as it
few weeks ago probably of gear manager update the gear start freezing and the screen turning on and off
first i do a factory reset and the gear was ok for a while but after it do the same but the next time the screen was not ok the colors was different so i send to service in Athens
the service in Athens is very fast and very helpful , is one of the reasons that i will difficult go with other manufacture , so they return me the gear saying that they change the motherboard and now there is new imei
but the gear that they send me was brand new except the band and the box. BUT after some time the same problem ..... i call them and they tell me to send it back so i send it and i receive it again but this time the say that the watch is ok
GUESS NOW .... i turn it on and after a while of the connection with my note AGAIN the same problem the screen on and off and freezing plus was overheat underneath
i was ready to call them and to say few words but they was closed ..... then i search the net and i found this post and i thing probably is not the gear the problem ,no hardware problem, i decide to do a test
i download the last working rom to my phone 4.4.2 and magically the problem disappears .... but now there is a software update on my phone lollipop 5 so i do the update and i was ready if the phone cause again the same problem
to return and stay with 4.4.2 But now all is ok the problem solved .... now is more of 24h and all are ok
i hope this will work for you also
Same problem
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
JALUK said:
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
Click to expand...
Click to collapse
Ok but doing a downgrade and all working ok you can do update again.... i am not with 4.4.2 i went to the latest 5.0 for me now and all are ok.
Maybe something was wrong with the update procedure.
UPDATE
the touch function of the 2nd gear stop working so i send it back and they send me new device
for a few days all was ok . But today when i restart the phone while the gear was disconnected the problem with screen turning on repeatedly appears again .
for sure is not problem of the gear , this is the 3rd device in my hands, something is wrong with the gear manager software .
i have also reconnection problems .... if the phone is far away and they lost Bluetooth connection the most of the times i must reconnect manually , the gear say disconnected but the note think is still connected
I wonder has anyone tried to reset the watch as a stand alone device and see if the problem happens? I know you might lose a lot of the blue tooth functionality but I think I will test it and see if the problem still happens.
my xperia iii just started acting up. I tried to log in to siriusxm and the screen timed out because I was away for a bit. I tried to turn the screen back on when it got stuck in accessibility mode with the screen off and constantly fired the Google assistant. pushing and holding power does nothing except fire off the assistant three more times. if I can't get it to come back to me I can do a factory reset since I just received this phone yesterday and haven't done much with it. anything I can do here?
This isn't normal behavior. If you can return it.
Assuming you didn't install something stupid it's likely a firmware or hardware issue.
+ 1
Was this a new device? Rooted?
Are you sure that you long pressed the power button and not the Google Assistant button by mistake?
ctkatz said:
my xperia iii just started acting up. I tried to log in to siriusxm and the screen timed out because I was away for a bit. I tried to turn the screen back on when it got stuck in accessibility mode with the screen off and constantly fired the Google assistant. pushing and holding power does nothing except fire off the assistant three more times. if I can't get it to come back to me I can do a factory reset since I just received this phone yesterday and haven't done much with it. anything I can do here?
Click to expand...
Click to collapse
Try pushing and holding power + vol up until it vibrates it'll force restart the device.
1. bought via swappa, listed as mint.
2. unrooted
3. it was the power button. it's below the volume rocker, first button on the side. the assistant is the second (and smaller) button on the side.
4. eventually the phone unfucked itself. I did nothing but wait. this actually happened a second time later on except this time the screen displayed my wallpaper at least. I rebooted as soon as I had control and so far so good. I will try power + vol up next time. btw I'm guessing it may have been a software issue. I was moving from a note 8 that had a bixby specific app that got transferred and activated. however a similar thing happened to me with a galaxy tab 4 (without any kind of software mod) so I don't know. I had to wait for that device to unfuck itself too.
ctkatz said:
1. bought via swappa, listed as mint.
2. unrooted
3. it was the power button. it's below the volume rocker, first button on the side. the assistant is the second (and smaller) button on the side.
4. eventually the phone unfucked itself. I did nothing but wait. this actually happened a second time later on except this time the screen displayed my wallpaper at least. I rebooted as soon as I had control and so far so good. I will try power + vol up next time. btw I'm guessing it may have been a software issue. I was moving from a note 8 that had a bixby specific app that got transferred and activated. however a similar thing happened to me with a galaxy tab 4 (without any kind of software mod) so I don't know. I had to wait for that device to unfuck itself too.
Click to expand...
Click to collapse
Try Safe Mode. It will temporarily disable a lot of user-space configurations that can cause boot loops. It's good for broken launchers, bad widgets, impossible settings, etc.
Take the microSD card out too. Google worked hard to disable expandable storage starting with Android 11. There's the floppy-disk-slow, absolutely useless SAF and nothing else. Performance workarounds from other phones, even if they're as simple as legacy mount options, will cause bootloops.