Related
Hi all,
I have had loads of problems with this phone, so I decided to do a factory reset.
It rebooted as normal until it got to the Motoblur setup page
It asks for the Motoblur details to be entered, but once you have entered them and pressed the 'next' button, it goes back to the previous screen instead of the next step and then gets stuck in a never ending loop.
I've tried skipping the sign in process but instead of skipping it, it just goes back to the first Motoblur account setup screen instead.
Out of desperation, I have tried to make several new Motoblur accounts but every single time, it gets to 80% completion, then stops.
I have even left running all night (plugged in) and it still freezes at 80%
I can't do another factory reset because it won't get past the Motoblur setup screen.
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Only had it for 7 weeks and am awaiting a response from Expansys on what to do.
Any help from you guys will be greatly appreciated.
Apply a debrand image of your system and do a full wipe
phorenzik said:
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Click to expand...
Click to collapse
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
StevePritchard said:
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
Click to expand...
Click to collapse
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
I notice there was an option to boot from SD in the recovey mode.
Would this allow me to boot an official motorola rom?
If so, where would I get the rom from?
A walkthorugh on exactly how to do this would be appreciated if this method could fix my issues.
I'm really annoyed because I sold my HD2 for this phone and I'm regretting it.
Thanks
phorenzik said:
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
Thanks
Click to expand...
Click to collapse
I think you need internet connection in order to validate your account or create a new one. Check your APN settings first, or do it on wifi.
Hi,
I've tried it whilst connected to my wifi router. I've even tried it via the data connection but nothing happens.
It seems that despite the data/wifi connections being there, it just ignores them.
I think this is the issue. It's not connecting and I don't know why
The phone displays the wifi/3G data symbols in the task bar but it doesn't seem to be using them during the Motoblur setup
Mine is dead too!!!
Hello everybody,
Greetings from sunny, flooded, blown away, Queensland Australia!
Long time lurker, first time poster...
I have a...
Vodafone-Australian-2.2-Milestone2
2 weeks old and its an expensive paper weight. It was rooted and thats about it, had a bunch of root required apps on there, installed the bootstrap, but hadnt installed Xrecovery yet.
I was playing around the other day. changing settings, installing and uninstalling a heap of apps, testing them. Some app suggested I restart or it restarted itself, cant recall, and that was the end. Boots until it gets past the M, and then its just bootloop city.
Won't register on comp in RSD or anything. Will boot to stock recovery and cleared cache and data several times, but that didnt fix anything. Won't even charge the battery. It will run an update but has to be signed. Problem is, we havent had any updates yet on these phones in Australia and there are no custom roms. What update.zip could I get to try to fix it, because I think thats about my only hope.
While recovery was wiping the data and cache it would stop frequently and each time I would touch the ok in the bottom corner of the screen and it would continue, and seemingly despite the 10 or more stops, completes fine. Surely thats not normal.
Out of ideas, I would just send it back with a story but the vodafone boot animation is replaced with disco flashing lights. and thats all it does, non-stop. Do you think they will notice someone has been tinkering?
Ideas? Thoughts?
Oh, and forgot to mention, when I first got it I had the same problem with the Motorola sign in wizard on startup, for quite a while, cant remember how I got around it though. Stop trying to sign in and just get out of that wizard, install ADW Launcher or similar and dont go near any Moto apps. You are only required to do a Gmail sign in, not Moto.
That's the problem though.
I'm stuck at the Motoblur sign in and it will not skip.
Whenever I select skip, it just goes back to the motoblur sign in page instead of going to the home screen.
Basically, in a nutshell, this is what's wrong:
I can't sign in to motoblur (gets stuck in a loop)
I can't create a new motoblur account (crashes at 80% every time)
I can't skip the sign in process (takes me back to the motoblur sign in page instead of loading home screen)
This is my first and last Motorola phone. Not good at all.
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
benking1972 said:
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
Click to expand...
Click to collapse
It just goes back to the motoblur setup/signin screen no matter how many time I press home, back or skip. It's as if a dll is missing and it's unable to boot to the home screen.
How do I flash a new SBF?
Motorola have agreed to let me return it but if I can do it myself I'd rather do it.
I have found this guide http://forum.xda-developers.com/showthread.php?p=11155476#post11155476
but the link to the UK SBF is dead
Yeah, that's the one, and the link to UK SBF works fine for me. If you can't get it to flash that way, then you are going to have to do it the way I am about to do mine, which is...
http://forum.xda-developers.com/showthread.php?t=804088
Failing that, send it back and be done with it.
since its so new id send it back. you shouldnt be having this problem at all. the milestone 2 is a very solid phone. i had mine running for 90 days straight not even a reboot or crash or anything lol. sounds like you just got a duff one. with any piece of technology theres bound to be a few that slip through the net. even if you find a fix for your problem you dont know what is causing it. and if youve had problems before then somethings obviously wrong. since theyve agreed to let you return it then thats your best option.
Probably i should send mine one back as well.
Bought a new Milestone 2 yesterday (from ebay, Chinese guys but as per retail package phones are for UK market). Put the SIM in just to check before wiping out everything from my old Defy. Made a call, checked the version and the menu and put the SIM back to Defy to backup all I needed. Plugged Milestone to the mains. 3 hours later found promising "Fully charged" on the screen and put the SIM in. That was it... Since I can't power the phone whatever I do. I thought the Power button went off as I tried to perform hard reset (x+Pwr), BRM (Arrow up+Pwr) and nothing happent at all. But then I put the phone on the charger again and the Power button worked fine switching the screen off and back on.
Any other methods to get the phone running?
UPDATE: It's strange and weird, but I've just had an idea to remove SD card and it worked - the phone powered on immediately!! Formatted the card using card reader, put it back - the phone works flawlessly. Fantastic! =))
I powered down my 7.7 and it automatically re-started in downloading mode. I've tried holding the power button down and that makes it disappear but then it comes back again. I recently did an OTA official upgrade to the firmware when it was offered and that might be causing the problem. It had worked fine for several days since I did the upgrade. My 7.7 was bought from Amazon UK.
Has anyone else experienced this problem or know how to fix it?
Thanks for your help
Gaugerer said:
I powered down my 7.7 and it automatically re-started in downloading mode. I've tried holding the power button down and that makes it disappear but then it comes back again. I recently did an OTA official upgrade to the firmware when it was offered and that might be causing the problem. It had worked fine for several days since I did the upgrade. My 7.7 was bought from Amazon UK.
Has anyone else experienced this problem or know how to fix it?
Thanks for your help
Click to expand...
Click to collapse
Here is an update of my previous post. I have contacted Amazon who are happy to send me a replacement on Monday but suggested that I phone Samsung technical support first to see if they can help. I was going to try replacing the official ROM using Odin but I don't have a suitable USB cable.
On my previous P1000 tablet I could use the charging lead to connect it to the laptop but on the 7.7 there is no USB connector. So my 7.7 is sitting with the green android and the message "Downloading" Do not switch off target. I've disconnected the power supply cable but it will probably take days for the battery to go flat. I should be able to get a USB cable tomorrow so that I can try connecting the 7.7 to my laptop.
Although holding the power button down for 10 seconds clears the downloading screen it re-appears almost immediately. I've tried pressing power+volume down and that shows a warning about installing custom ROMS, but when I select volume down to re-boot I just get back to the downloading screen. If I select volume up I also get the downloading screen and if I had a data cable then I could try re-flashing. This is one occasion where battery removal would be handy, but not an easy option with the 7.7.
Do you think it will harm the screen having the downloading screen on all the time? Also, do you think I should just return it to Amazon without trying to re-flash in case they accuse me of bricking it?
Update. My battery went flat overnight because of the stuck downloading screen and I was able to re-boot after re-charging. I'm going to keep the tablet on standby and avoid powering down until I get a USB cable which should allow me to re-flash the stock ROM if I get another problem.
Update: I received a USB data cable today so I tried shutting down the 7.7 and when I re-started it went into downloading mode again. I rang Samsung technical support and they said there was no need to shut down and that would avoid the problem and could not suggest any other solution. I felt the solution of never shutting down was not good enough so I re-flashed with LB3 and then tried KL3 but got the same problem each time
I would be most grateful for any help with this problem before I contact Amazon for a replacement.
Update: I have requested a return for my 7.7 and re-ordered. The good news is that the price has dropped £100, probably due to competition from the drop in the iPad2 price because of the iPad3 release.
Your own private thread; sweet! Thanks for the story
jabbermacy said:
Your own private thread; sweet! Thanks for the story
Click to expand...
Click to collapse
Thanks for your response for I was beginning to think I was being boycotted. I am not very knowledgeable on these matters and I was hoping someone could help or at least explain why I still had the problem after re-flashing the latest and previous stock ROMS.
I have discovered that the downloading loop problem can be fixed by doing a factory reset but you need to re-flash the stock ROM first or let the battery go flat to get out of the download loop.
how?
Gaugerer said:
I have discovered that the downloading loop problem can be fixed by doing a factory reset but you need to re-flash the stock ROM first or let the battery go flat to get out of the download loop.
Click to expand...
Click to collapse
Hi men, this problem just happen to me like 3 hours ago, i am waiting to the battery goes flat but i think is gona take to much because it was just unplugged from the adapter... before this happen an actualization of the AIDE was performed and it ask me t reboot the tab, when I turn it off the Downloading android appear and i cant turn it off.... u said that waiting for the battery to go flat function? and if there are more procedure to perform?? thanks....
---------- Post added at 05:17 PM ---------- Previous post was at 05:04 PM ----------
Elsanty said:
Hi men, this problem just happen to me like 3 hours ago, i am waiting to the battery goes flat but i think is gona take to much because it was just unplugged from the adapter... before this happen an actualization of the AIDE was performed and it ask me t reboot the tab, when I turn it off the Downloading android appear and i cant turn it off.... u said that waiting for the battery to go flat function? and if there are more procedure to perform?? thanks....
Click to expand...
Click to collapse
well this is kind of fun... i manage the issue.... it seems that this tab have the unique program buttons in the on/off button and the volume button... result that if this problem happen to U u just have to press the power button and keep pressing the button while u continuously press the up volume button for several times until it reboot correctly... thanks god this works :fingers-crossed: :laugh: :victory::victory::victory:
I had a galaxy tab 2 with the similar problem and what i found out is that it had only one solution for getting back into system (beside battery drain, battery removal), that solution was to hold Val Up and Val Down simultaneously for a couple of seconds. With that combination the tab would reset and boot up correctly. So, this COULD be a solution for your problem too.
So, a few days ago, I started having some problems with my stock Nexus 7 (not unlocked, no ROMs or anything like that). Some apps just wouldn't open, they would force close within a second of opening. Anyway, I think it might have stemmed from the game "Let's Golf 3", as problems started after playing that, and when going back in to it after a day of issues, a message appeared saying "Unfortunately, launcher has stopped" - it gave me the option to report or cancel, but whatever I pressed, the message popped back up. I pressed the sleep button, which seemed to turn my Nexus off somehow.
Then, when trying to to turn my Nexus back on, it just stays on the 'X' screen. I have done a factory wipe through the fastboot menu a few times, but it still stays stuck on the 'X' screen. To turn it off, I hold down the power button, but it just starts the process again automatically. The only way to actually turn the device off is through the fastboot menu.
I have seen talk of 'factory image' and drivers etc... but I am not too comfortable with that sort of thing. I know the basics of troubleshooting devices, but not much more. I am very wary of doing anything more than what the device provides me with.
Any idea how I can get my Nexus started, or am I going to have to look for a replacement?
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Leonhan said:
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Click to expand...
Click to collapse
Is that not for rooted devices?
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
AW: [Q] Nexus stuck on 'X' screen, even after full wipe
Gawge said:
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
Click to expand...
Click to collapse
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
mihahn said:
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I too had the same problem. Tried everything. Finally gave it to ASUS service centre in Nehru Place. They will replace the mother board. May take 15 more days. So sad!
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
FYI,
The tablet can "play possum" when it is in APX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown APX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
bftb0 said:
FYI,
The tablet can "play possum" when it is in AVX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown AVX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
Click to expand...
Click to collapse
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
Service centre seems to be the only solution. My sympathies!
Gawge said:
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Click to expand...
Click to collapse
Call Asus first. Make sure to let them know it is less than 2 months old. If they want you to perform the return through the original retailer, they will tell you. But it's best to eliminate any other middlemen if that is possible, as I suppose that the tablet ultimately goes back to Asus anyway.
(Might be different through other channels, e.g. PlayStore - I dont know).
So I was using my N7 as normal last night, starting up Kodi (Previously XBMC) to watch some shows before I went to bed, and as Kodi was starting, my tablet froze. I let it sit there for a good 10 minutes, nothing happened, so I proceeded to hold the power button down to force it to reboot, it turned off, and now it seems to be off forever..
It is showing up in my device manager as APX. I've tried all the tricks of holding down the power button + volume button to get into the bootloader, and it just won't give in. It is rooted, and it's been that way for a long time..
Is there maybe something that I missed in my research? It seems that there are two results; those who can hold down the power and volume and get into bootloader and go from there, and those who never revive the N7.
What are your thoughts?
-Seth
nightfox7 said:
So I was using my N7 as normal last night, starting up Kodi (Previously XBMC) to watch some shows before I went to bed, and as Kodi was starting, my tablet froze. I let it sit there for a good 10 minutes, nothing happened, so I proceeded to hold the power button down to force it to reboot, it turned off, and now it seems to be off forever..
It is showing up in my device manager as APX. I've tried all the tricks of holding down the power button + volume button to get into the bootloader, and it just won't give in. It is rooted, and it's been that way for a long time..
Is there maybe something that I missed in my research? It seems that there are two results; those who can hold down the power and volume and get into bootloader and go from there, and those who never revive the N7.
What are your thoughts?
-Seth
Click to expand...
Click to collapse
try removing the batt then wait for 2 min then put it back then plug it in pc then hold power button atnd up and down button
ngoralph said:
try removing the batt then wait for 2 min then put it back then plug it in pc then hold power button atnd up and down button
Click to expand...
Click to collapse
Tried this multiple times as well..
How did you even remove the battery? We're talking about Nexus 7 aka grouper, right?
nightfox7 said:
Tried this multiple times as well..
Click to expand...
Click to collapse
hmm i think its hardware problem, i also have this problem till now but got it working, but turning off the tablet makes it dead again
hmm for me i just kept repeating the process
---------- Post added at 02:58 PM ---------- Previous post was at 02:57 PM ----------
l33ch0r said:
How did you even remove the battery? We're talking about Nexus 7 aka grouper, right?
Click to expand...
Click to collapse
yes watch some youtube video bout it
l33ch0r said:
How did you even remove the battery? We're talking about Nexus 7 aka grouper, right?
Click to expand...
Click to collapse
It's super easy to pop the back off and unplug the battery.
ngoralph said:
hmm i think its hardware problem, i also have this problem till now but got it working, but turning off the tablet makes it dead again
hmm for me i just kept repeating the process
Click to expand...
Click to collapse
That's what I think as well. I read somewhere that its a CPU failure.
I'll keep on trying, i left it unplugged all night.
nightfox7 said:
So I was using my N7 as normal last night, starting up Kodi (Previously XBMC) to watch some shows before I went to bed, and as Kodi was starting, my tablet froze. I let it sit there for a good 10 minutes, nothing happened, so I proceeded to hold the power button down to force it to reboot, it turned off, and now it seems to be off forever..
It is showing up in my device manager as APX. I've tried all the tricks of holding down the power button + volume button to get into the bootloader, and it just won't give in. It is rooted, and it's been that way for a long time..
Is there maybe something that I missed in my research? It seems that there are two results; those who can hold down the power and volume and get into bootloader and go from there, and those who never revive the N7.
What are your thoughts?
-Seth
Click to expand...
Click to collapse
Mine did this...Stuck at the Google Boot Logo and when I rebooted all i got was APX mode. Unfortunately for me the only way I got it fixed was to buy a Nexus 7 from Ebay with a broken screen for parts. Then I removed the motherboard from the broken one and replaced my bad motherboard with the good one. I tried everything before going this route.
Just an update:
I never was able to revive the old girl. Tried just about everything short of reflowing the board.
I found a logic board on ebay for pretty cheap and dropped it in, it works great and now I have more space! I used to have a 16, now it's a 32.
Also, I put Cyanogenmod on it, and I love it. Much more responsive than it used to be.
-Seth
Another update, she's still going strong, so it wasn't any other failures, only something on the motherboard.
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
That's a tough one. Usually with a soft brick, if you can make it to recovery, your phone can be saved but since you can't... I hope you get it working!
Sent from my SPH-L720 using XDA Free mobile app
puresublimie said:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
Click to expand...
Click to collapse
Go to sprint galaxy s4 thread. All answers there. You need Odin 3.09 then stock ng2 tar. To flash through computer.
Sent from my SPH-L720 using XDA Free mobile app
I already have odin and the tar files for stock. When plugged into my computer it will not even register that it is connected and so I can't use odin to flash it.
The same thing is happening to me. I get to the Galaxy S4 splash screen, then it shuts off. Even if I try to boot into recovery
I'm going to pile on in here as I seem to be having a similar issue. I had my S4 (not rooted, stock rom) on my dock streaming google music. A phone call came in and the phone started vibrating like crazy and wouldn't stop. The screen shut off and the phone was still vibrating. Finally it stopped and was shut off. When I try to start it a few things happens. It will sometimes boot to my lock screen and the screen goes black and I think it is powered off. Sometimes it will get past the lock screen and then die shortly after. After like 2 or 3 times of that it won't even boot. It loads the Samsung screen but never gets to the Sprint screen or boots. If I leave it for some time shut off with battery out it will go back to booting to the lock screen then dying etc... When I press the buttons to get into recovery it says recovery is loading and then the screen goes black. I swapped batteries and that didn't do anything. I tried pressing the menu button or the home button to try and boot safe mode and it just loads normally not that I think that would help anyway.
Any ideas on things I can try next? What is this odin thing? Would that work for me?
---------- Post added at 07:09 PM ---------- Previous post was at 06:16 PM ----------
Ok... I can get into recovery now and will try a factory reset. Are you sure you are going into recovery correctly. Apparently I was not. Hold volume up power and menu button and when the phone vibrates let go of power only.
Before I do a hard wipe is there any way to get data off the internal memory from recovery mode?
So I got a custom recovery installed, reinstalled stock rom, things worked ok for awhile. Then it started random reboots every 10 mins or so. Now it is back to instant crashing and rebooting. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=