As the title implies, I'm stuck.
Notification popped up last night informing me an update was available. I had checked for any and all other updates just last week to make sure I was up to speed on things. I'm not a newb, but the tab is for my wife, so I keep it plain jane stock to avoid potential problems that could cause her to brick it.
Anyway, this morning I decided to finally click on the notification asking me to update. Device powered down and has been stuck on the 27% sign for 2 hours now. It's plugged in the entire time. It's also getting kind of warm. I'm afraid to do anything at this point for fear of bricking it.
Any help would be appreciated. I specifically talked her into the galaxy tab over the ipad, so avoiding "I told you so" from my wife would be icing on the cake with this one.
Any ideas? I can't seem to find any other threads here or via google that mimic this situation.
27% is where it starts to gettting really slow inching forward but not for 2 hours. For me it is like 30 miuutes or so.
But with Samsung updates, you take that risk everytime.
Good luck. You need it.
So where should I begin? Hold the power button and force a reboot? Leave it sitting all day and pray that it magically continues with the update?
Update: held power button, it rebooted on its own and is now stuck at 26%. I wonder what happens if I do it 25 more times?
Is this sort of thing covered under warranty?
do you know how to use odin? if you do i will set you up with a process to get you on the latest firmware without out dealing with Samsungs utterly horrible update process.
You end up fixing this?
I have the same issue!
I stumbled into a fix:
Hold down power button until it dies. Press and hold power button and volume DOWN button until the splash screen appears. Release power button.
Shows 2 options, one is an icon of an android getting out of a box. the other has "download" in it. Choose the one on the left of the android getting out of a box. Use the VOLUME selector to choose which one, and use the power button to select it. It will load the menu, using the volume button again, select the option to reboot and hit power button again. Should reboot you back to pre-update status with an error that says update failed and to try the update using Kies.
I'm a little hazy on whether or not I released the volume down button during booting. Keep trying it until you get there. You won't hurt it any worse than it already is, that's for sure.
Related
Hi all,
I had a terrible catastrophic failure today with my 1-month old HTC Wildfire. I bought my device new, unlocked, in Singapore.
Here's what happened:
Today I received an ordinary SMS (like I have hundreds of times before in the past few weeks) and when I picked up the phone off of the desk, flipped on the screen, and slid my finger to unlock it, I saw a brief error message in a dialog on top of the Messages app. It was something like "com.something .... ", I didn't get a good look at the error but it didn't really mean anything to me at the time. The SMS that I received was then lost (I knew who it was from, but the message was not showing up). A few minutes later, I heard another SMS notification. No error message this time, but again the message did not show up in my Messages app.
So, I pressed the power button to power cycle the phone. After I shut it down, I turned it back on, saw the white screen with HTC logo, then black. It was dead. No amount of pressing buttons did anything.
After a few minutes, I removed the battery and it turned on again. Again, white splash screen and then darkness. Repeated this several times and same result.
Finally, I googled how to do a hard reset. I followed the instructions, held the volume down button while pressing power, cleared the memory, after it restarted it went right back to the white bootloader screen, flashed some error messages, and now I'm stuck in the bootloader. When I select the RECOVERY option, I get a quick screen with something like:
SD Checking ...
Loading [SOMEFILE.zip] ...
No Image!
Loading [SOMEFILE.zip] ...
No Image!
....
....
No Image or Wrong Image!
Can anybody help??! I don't know what to do now. I've searched for this "No Image or Wrong Image" message on these forums, but all the results are about rooting and loading different ROMs. I've never rooted or anything out of the ordinary, I just want the stock OS back and operational.
Btw ... I'm an Android noob, but an experienced Linux/Mac user and 10-year software developer.
Any help is greatly appreciated.
Thanks,
Nate
Recovery mode is something else.
To do a hardreset try the following:
Performing a factory reset using phone buttons
If you cannot turn on your phone or access the phone settings, you can still perform a factory reset by using the buttons on the phone.
1. With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Note: If you are not sure whether your phone's power is turned off, remove and then reinsert the battery.
2. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
3. Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
4. Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
Source : http://www.htc.com/www/howto.aspx?id=3567&type=1&p_id=316
Call HTC support. I had a problem with my previous HTC phone, and they took me through diagnositcs over the phone, and when they diagnosed a hardware fault, sent a courier to pick it up from me the next day. This was when the phone was 18 months old. No receipt was necessary, they used the serial number/manufacture date.
Downside: the phone was gone a week, and came back still broken. It was sent away again, and came back fixed. So painfully without it for two weeks, but not a bad experience.
(edit: it was a similar problem: I upgraded to windows 6.1, and my phone wouldn't get past the initial hardware/boot screen)
I tried the hard reset procedure several times. Every time it's the same thing. After it clears the memory, it says "Reboot in 5 seconds..." and then when it reboots, it goes back to the bootloader screens.
I've contacted HTC support via email, and I'm bringing it in to their support center in Singapore tomorrow. I really hope it doesn't take a week ... I'll keep you updated.
Fixed.
I just got my Wildfire back today after a full week in the repair center. Apparently they replaced the main system board. No other explanation for the problem was given.
The repair process itself was hassle free, although I was frustrated by not having my phone for a week. Ended up having to buy a cheap basic phone for $55 to get by on SMS and voice.
Just gonna throw this out there and hope that somebody will have some insight…
Right now, my Xoom won’t turn on... or atleast "all the way on".
If I hold in “Volume Up” and the power button for 3 seconds (as described on the support site), it boots, gets past the moto screen and to the honeycomb animation. The animation plays for a few minutes… yes minutes until it either goes dark/off or presents a bare-bones lock screen that doesn’t respond to touch input.
Occasionally, when it reboots, it gets to the screen that has the Motorola logo and in the upper left corner, it has the text: "Starting RSD Protocol support 0". When that happens, it just freezes there. This has only happen a couple of times and I believe it had to do with variable durations of holding down the power and volume buttons. The phrase quoted doesn’t appear in either bing or google’s indexes.
Right now, the honeycomb animation has been playing for several minutes and 2 notification sounds just played… WTF
Any help would be GREATLY appreciated.
FWIW
Whatever happen, it did so under the follwoing circumstances:
1. Sent gTalk invite
2. Changed background image
3. While it was applying the new background, gTalk popped up with an incoming call.
4. I accepted the call
5. I then saw my video image in the lower right and nothing else on the screen.
6. Approx 10-15 seconds later, the Xoom rebooted.
7. Never finished the reboot, just turned off during honeycomb animation.
8. Tried that again a few times.
9. Tried the hard reboot, where you hold in the volume and power in... no dice
Sometimes, it will play a notification sound when in the honeycomb animation.
Sometimes, it will get to a generic unlock screen that doesnt respond to touch input. When that happens, and once the screen goes to sleep, I'm back to square one.
Just got off the phone with Motorola. I explained to the lady on the phone the situation and she was confident that she could help. Unfortunately, the volume / power button combo was all she had up her sleeve. She advised me to return it to BestBuy tomorrow.
Willing to bet BestBuy wont have any tomorrow... This isnt the "experience" i was hoping to get.
Just return it and get a new one? its obviously defective...
martonikaj said:
Just return it and get a new one? its obviously defective...
Click to expand...
Click to collapse
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
gigglebox said:
Yeah, that's what I'll have to do. Just sucks because they probably won't have any and I'll end up having to wait for another. It's lame, but I suppose its one of those "it'll do what it do" scenarios.
Sent from my Evo using the XDA App
Click to expand...
Click to collapse
The quicker you take it back, the better off you are. They'll get new stock in and you'll be better off.
If you see that it doesn't mean its defective, it means your stuck on the fastboot screen
do this:
"Holding vol up down & power does a force normal reboot"
I just returned the device to BestBuy, exchanged it for a new one… so I’m all set.
Here are my current thoughts as to what happened (and what may happen in the future):
It really seemed / behaved like an unhandled combination of circumstances exposed what might be a couple of holes in Honeycomb. Obviously, we’re still pretty early on in the life span of this thing and many things that fell through the software validation process will likely be corrected as they are found.
Best I can figure, while attempting to write a change to (what I imagine is) a config file somewhere (when changing the background image), the process was interrupted by an incoming connection (inbound gTalk video call). That, perhaps in conjunction with the set of apps that I had loaded and were likely still present in ram, somehow made Android lose its marbles.
Throughout the night, I tried lots of different ways to reboot, and lots of attempts with no luck. However, on 3 occasions, after 30-40 minutes of not touching the device, it would start to make noise. Each time, I found that the noise was that of an incoming gTalk call and the caller (that seemed to initiate the failure) appeared on the screen accompanied by the Accept, Deny buttons. The pressing of any of the on-screen buttons resulted in the powering off of the device. Whats puzzling is that the device maintained any awareness of a call, etc, hours after it was initiated and had been hard-rebooted several times. Something wasn’t getting flushed…
I assume that once folks get a solid handle on rooting and custom ROM procedures, there will be an iron-clad way out of the hole I found myself in.
Have the same problem
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
Thats the fastboot screen, you could try flashing it at your own risk. But if it was a software glitch that would fix it.
VanVlack said:
I am having the same problem. will not get past the honeycomb startup animation. Did try up/down volume + power with now luck. I can get to a screen that says Starting RSD protocol support 0 but wont get past that.
Click to expand...
Click to collapse
FastBoot or not, I never succeeded in getting it out of that funk (any combo of either proscribed or "creative" button pushing). I dicked with it for about 5-6 hours before I cut my losses and went to bed. In terms of flashing it, I would imagine that it would work, but I personally wouldnt be comfortable enough yet. The process will get a hell of a lot more tested and vouched for in the near future.
The day after launch, I just called around to see what BestBuys had them in stock and drove out there to exchange it.
I hope that you guys are reporting your issues to Google...
never got it fixed
I never did get it out of that loop or what ever was going on. I am too an advanced user of android, from day one and it seem like more of a hardware or software problem then anything. Took it back to costco and they had me call up verizon. Went up a few tech levels. He tryed to help me get into the factory reset menu but no go on that. Got a replacement. I had my new xoom crash and go to the startup screen. Held my breath as it started back up.
Will send out a message to google and motorola letting them know.
All you had to do is hit sound up and power button it would have shutdown and once you power back up it will go into the regular boot
broken xoom
mine is stuck at the duo core screen with failed image lnx 0x002
starting RSD mode 2
i can hold the down volume button and put it in the fastboot protocol support. but when i plug it in and try to unlock it to run the factory reboot protocol from motorola my command prompt says waiting on device. i have the correct mot driver installed. any help out there
Try this post http://forum.xda-developers.com/showthread.php?t=973355
Sent from my HTC HD2 using XDA Premium App
Yesterday I have updated my TF101/US to 9.2.1.17 (not rooted, serial B50) and now my power button does not work at all. I cannot either shut it off (I can hold it for minutes, nothing happens), nor can I wake it up (the only possibility is to plug in the power). Reset to factory setting does not help
I talked to Asus, they suggested to send it to RMA, but I want to try to discharge it completely and check whether it helps.
Will keep this post updated if I find out something more.
Update: battery discharge did not fix the issue. Going to send the device to RMA.
Thanks for this post, this if for no other reason is why I will be dealing with my random reboots (they only occur once a week or so, if that often, for me so not a big problem, not like a broken power button would be) rather than updating the patch. However, this belongs in general or Q&A not development
Also for me you have to call assistance for a RMA: i could understand that power button does not turn off screen, but i can't understand, a part an hardware problem, how it does not shut down keeping power button down or why it does not turn on.
Yes, that sounds like hardware issue, but that must be very weird coincidence.
The complete story is that I just received device from RMA yesterday (LCD backlights were broken). I turned it on, it happened to have ICS already (it was sent with Honeycomb) and I was able to install all my software. Then a message re. new OTA update poped up, I decided to upgrade, and right after that power button stopped to work.
Yes, that can be hardware issue as well, that is why it goes to RMA. If I were 100% sure that this is software issue, I would wait some days hoping that ASUS will release bugfix for it.
Hmmm..the device will not power on if it is shut down? (How would you know this unless you shut down, and then can't turn it back on I don't know).
I re-read this and it is unlikely IMO that a firmware update could break your hardware, but I guess if a computer virus can break nuclear centrifuges anything is possible? Could be a coincidence..I feel for you, I had an over-discharge issue one night and my TF didn't want to boot up, and then flashed the red battery on the screen, but for those first few seconds my heart wasn't beating..I get the same feeling when I get a bad flash too lol
Luckily, the device wakes up when you plug the charger in. So, currently my choice is either to keep it running (disable sleep) or to have a charger and plug the charger in when I need to wake it up.
The bad thing is that the RMA "cycle" takes about two weeks.
Maybe it isn't a coincidence..
http://forum.xda-developers.com/showthread.php?t=1546640
Mine started this about two weeks ago before I picked up the update today... I thought i was the only one until I saw this post
I have misunderstood something: post says WAKE ON not TURN ON, ok this could be software related, but long press power button should be FORCE A SHUT DOWN...
Click this link on how to remove the front bezel. Then you can check the inside power switch to see if it's working:
http://www.techrepublic.com/photos/cracking-open-the-asus-eee-pad-transformer-tf101/6270147
That's the way I fixed my TF101 after I dropped it and the power button got stuck in the chassis.
Also read this thread:
http://forum.xda-developers.com/showthread.php?t=1391254
I think this is a solution to your problem, if it's not software related, which I doubt.
I get the same problem all the time, I leave it sitting for a couple hours come back and it won't turn on or off...
I also sometimes get the non functioning power button. I cannot consistently replicate it.
Sometimes it happens after it sleeps for awhile.
Sometimes it turns on when I open the tablet up while connected to the dock.
I have to hold the power button until it reboots itself. This is annoying after while. And even getting more so.
I'm also having a power-on related issue since the ICS update but didn't want to start a whole new thread for it. Ever since the update my Transformer boots into CWM by default. If I power it down completely then press the power button the EEE Pad logo flashes on the screen, I hear an audible "click" (best way I can describe it) from the device and it boots into CWM. If I select "Reboot device now" from the CWM menu it boots right back into CWM.
The only way to boot properly now is to hold the volume down/power buttons until the menu comes up to choose between Android and recovery and choose Android. (It actually defaults to this so I can just let it sit 10 seconds or so)
Any ideas?
Headcase_Fargone said:
I'm also having a power-on related issue since the ICS update but didn't want to start a whole new thread for it. Ever since the update my Transformer boots into CWM by default. If I power it down completely then press the power button the EEE Pad logo flashes on the screen, I hear an audible "click" (best way I can describe it) from the device and it boots into CWM. If I select "Reboot device now" from the CWM menu it boots right back into CWM.
The only way to boot properly now is to hold the volume down/power buttons until the menu comes up to choose between Android and recovery and choose Android. (It actually defaults to this so I can just let it sit 10 seconds or so)
Any ideas?
Click to expand...
Click to collapse
exactly same problem as me now. holding volume down and power is the only way to start it up if it has been left alone for awhile. since the update.
nosup4u said:
exactly same problem as me now. holding volume down and power is the only way to start it up if it has been left alone for awhile. since the update.
Click to expand...
Click to collapse
Apparently it's a pretty common issue with the new version of CWM, as explained in this here thread.
So far the only solutions I'm seeing involve ADB commands or flashing a custom ROM.
fixed for now....
I had the same issue the power button would only cold power off the device. The only way to power back on is by connecting the charger.
I solved it for no in the following way which i do no recommend to anyone. I have opened the device and disconnected the battery for 5minutes. After connecting it back the device powered on with the power button as it should.
In my opinion it looks as if there's some power related controller that was "hang" and ignored the power button .
Any ideas ? Asus ?
Hey guys, I was wondering if anyone could help me troubleshoot my Galaxy S4 which turns itself off every time I power it on. Basically, I'll hit the power button and the Samsung logo will pop up with the the lock icon showing that the device has been rooted. Then, after a few seconds the screen will go black at which point I am unable to do anything to it other than pull the battery out and repeat the process. If I wait a few minutes though, I am able to push the power button without having to pull the battery out. In addition, if I attempt to pull the recovery menu up, it will begin to load but as before, the phone will turn itself off before I'm able to do anything useful. At one point I was able to somehow get it to load Android though that may have just been pure luck at work.
I don't believe that my root access is at fault here because I've had it for several months with no trouble to note. Immediately before this happened my power button began acting strangely in the OS. I attempted to factory reset in order to fix this and that's when this problem started. The only other which that I can think of that may have caused this is Safestrap which I uninstalled shortly after the power button began acting up.
Does download mode also reboot? Then it's definetely some hardware malfunction.
By the sound of it it's a malfunctioning power button.
Thanks!
Lennyz1988 said:
Does download mode also reboot? Then it's definetely some hardware malfunction.
By the sound of it it's a malfunctioning power button.
Click to expand...
Click to collapse
Thanks for the help Lennyz, I was starting to think the same thing myself. I'll have to take it in for repairs.
I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?
It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.
It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.
Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!
Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.