Hi everybody,
I'm running JellyBelly 1.0.0 with a stable thalamus kernel compiled by madd0g.
Recently my phone began to freeze relatively often, with the screen on. I have to remove battery
in order to make it restart. adb recognize the device, but it does not respond to any other command
(neither logcat nor shell)
At reboot I also noticed that a screen snapshot has been taken. In jelly belly by using the power button
a menu appear allowing, among other things to take screen shots. That's why I think that maybe the power
button is failing. As I do not see the poweroff menu, it may be that my hypothesis is not correct.
Is anyone else experiencing a similar problem?
Lionhe
EDIT: I found that in the SD folder bugreport a bugreport file have been generated with exactly the same time of the freeze. I've read somewhere that by simultaneously pressing vol up and vol down in jelly bean such a report would be generated. I though that I found the cause, but unfortunately I am unable to reproduce it.
EDIT2: The trouble occurs when volup voldown AND powerbutton are simultaneously pressed. I will look if this behavior occurs also in other ROMS
Such a trouble also occur if I give the command adb bugreport
It does not happen in AOSP chocolate
Related
Hi guys,
My Mrs. Orange SanFran has all of a sudden decided it doesnt want it's screen touched anymore. All the hard buttons are working and can not see any other issues. Seems there are several people who have experienced it but it seems to resolved itselfon a restart but her's isn't, no matter how long I take the battery out or pressing the reset under the battery cover I can't use the screen making it useless.
Any ideas? I stuck a custom Rom of 2.2 on it when first got it but can't remeber which one, maybe modaco Kitchen R12 Rom.
Cheers
Reboot to recovery, Wipe both Dalvik and normal cache, and restart. If that doesn't help, do a factory reset / wipe data, and restart. If that doesn't help re-install the rom.
Thanks for the tip, but I tried to enter recovery by holding down volume key when powering up but a screen breifly loaded that had the small text "android" written upsidedown but then just goes on loop of the screen and the standard screen, can't do anything.
Holding up volume whilst powering on doesn;t do anything and because I can't use the touch screen I can't access any recovery apps through the phone OS.
It's weird cause I've used to recovery mode on phone boot before as first ROM didn't work, so I know the recovery module worked before, no idea why not now. :-s
Could be either bad flash/root or faulty hw. Google "de-bricking a ZTE Blade".
Thanks again. Came across a very thorough article on modaco but unfortunately the phone won't do anything than a normal startup when holding the up volume or up and menu, so can't try any of the suggestions.
The volume buttons do work though as moved the volume in the OS
Just to be sure: you did first press & hold the volume down button, and then press & hold the power button? You have to hold them both down until the recovery menu pops up. I can take even 10 seconds or more.
If everything fails, try TPT flash. It should solve if there is no hardware issue.
Since i flashed TWRP "2.3.1.1 grouper" for my Nexus 7, on the Recovery partition (for some reasons it didn't had a Recovery software installed anymore), it seem like i have to hold the Power button for 10-15 seconds before the Google logo show up on the screen. Before that, i only had to hold Power button for about 2-3 seconds (default Power button holding time).
At first i was freaking out, thinking i corrupted something by flashing this and the device just refused to boot up. But then i thought "let's see if the tablet boot up if i hold the Power button long enough"
Why is it doing that suddenly? Is there a way i can shorten this?
infos:
-i have Glazed Jelly Bean 2.1 installed
-i used WugFresh's tools to flash TWRP, while i selected "Custom ROM - JB" in the Android version.
-i changed my boot animation using ROM Toolbox Pro (i don't think it cause the problem, as it was booting just fine before)
strange, when i enable Debugging, i just have to hold it for 3-4 seconds (normal). When Debugging is off, i have to hold it for about 15 seconds. Any idea why?
Do you always leave your Debugging feature on? it seem like it only give access to other hidden folders you wouldn't see normally, on your PC.
Hello! Got a problem with my Galaxy S 4. Removed T-Mobile brand, flashed the stock ROM MH5 and unlocked the device by code.
Do not know if the problem existed before, at least following phenomenon occurs: after a certain time (depending on how long the battery was out - more on that below) the volume down button no longer responds - initially Vol button respnds normally, suddenly the volume turns down and I can only press volume up, volume down does not respond anymore - when I reboot the device, it always boots in the mode where I can push vol up to install a custom Rom or volume down for restart - but neither Vol up nor Vol down respond. If I restart the device with volume up + Home + Power button, I can not get into recovery but in Safe Mode.
Only when I take out the battery and wait (approx half an hour), the unit boots normally and the error occurs again after some time...
I also made a factory reset - no success. Somebody knows this phenomenon? Thank you.
Maybe
liquidspace said:
Hello! Got a problem with my Galaxy S 4. Removed T-Mobile brand, flashed the stock ROM MH5 and unlocked the device by code.
Do not know if the problem existed before, at least following phenomenon occurs: after a certain time (depending on how long the battery was out - more on that below) the volume down button no longer responds - initially Vol button respnds normally, suddenly the volume turns down and I can only press volume up, volume down does not respond anymore - when I reboot the device, it always boots in the mode where I can push vol up to install a custom Rom or volume down for restart - but neither Vol up nor Vol down respond. If I restart the device with volume up + Home + Power button, I can not get into recovery but in Safe Mode.
Only when I take out the battery and wait (approx half an hour), the unit boots normally and the error occurs again after some time...
I also made a factory reset - no success. Somebody knows this phenomenon? Thank you.
Click to expand...
Click to collapse
Try replacing the battery with a different one then see if it works. if not do this:
Download the stock MH5 ROM from SAMMOBILE
Open Odin
Flash this ROM with Odin
make sure that only Auto Reboot and F. Reset Time are the only options ticked
I personally havent had this problem but it might help
EDIT: This sounds like a software issue but if it keeps happening it may infact be a hardware issue with the device itself
Thanks, but I already flashed Stock MH5 and now MH7 T-Mobile branded - when the device is off for about an hour, the S4 boots normally and the Volume up and down works fine, two minutes later Vol down doesn´t respond anymore...it´s weird
I still don´t belive it - tried the battery from a mate´s S4 - mine works fine again, no Vol button errors or startup problems...can somebody explain this to me...crazy ****...
Hello all:
I'm having a strange issue here. I have a Nexus 7 that won't boot past the X screen. I've managed to get it into recovery mode following the steps laid out everywhere on the internet, but the next step; using the volume rocker to select factory restore is not working. The screen has the word Start enclosed in an arrow, it has a little up arrow and a little down arrow, and information about bootloader version, fastboot, and its locked locked state. There are no other visible options, and nothing changes when the volume control is pressed or held.
Is there an easy solution here I'm not seeing? The only thing that works is holding the power button down to shut it off.
Have you tried "adb reboot recovery"?
Fixed
bobbytomorow said:
Have you tried "adb reboot recovery"?
Click to expand...
Click to collapse
Thanks for the reply. Adb was not an option, sadly as usb debugging was not enabled when the problems started. I did get it working however, based off that, and to explain for those who'll stumble on this with the same issue:
1. Boot into the fastboot screen (the place where you'd normally choose recovery mode)
2. Plug the Nexus 7 into your computer.
3. Enter device manager and see if you have an unknown android device.
4. Right click it and install the Google usb driver that you can find through the sdk manager part of the android sdk.
5. Try the volume keys again. Here's where it started working for me.
I hadn't realized that your computer treats fastboot mode as a separate device. It needed the same process you'd use to install the adb driver, but to be done from fastboot.
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
bftb0 said:
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
Click to expand...
Click to collapse
Interesting you should mention that @bftb0... when in the bootoader, if my Nexus 7 is USB connected to my laptop, the volume keys can (but not always) be completely non-responsive.
I've just attempted to replicate the problem... but with no success...
It last occurred after fastboot flashing TWRP with the intention of flashing Chainfire, as was recently required to re-root after the 4.4.2 OTA. With Chainfire's .zip already stored on my Nexus 7, and having successfully flashed TWRP... my next move was to use the vol keys to access recovery. The vol keys didn't work... UNTIL I DISCONECTED FROM MY LAPTOP... when they worked again. I was then able to flash Chainfire, and reacquire root without problems.
As I say, I've noticed this problem before... both with bootloader v4.23 and it's predecessor, v4.18. And you just sort of ignore it...
"oh, the volume keys are dead again - damn, forgotten to disconnect from the laptop!".
It just becomes one of those bizarre minor irritants that seem to bedevil all technology... you know how to fix it (pull the USB cable out), but you don't know what the cause is.
I suspect some bug in the bootloader itself... that is so innocuous and harmless and only occurs when the "stars-are-in-the-right-alignment", that digging it out and fixing it would just be more trouble than it's worth. Still a damned nuisance though.
I guess I'll just have to get into the habit of remembering to disconnect from my laptop after I've fastboot flashed something... if I want to access recovery afterwards.
Rgrds,
Ged.
Hi,
The problem I have is really very common to most Samsung Galaxy users, but I haven't found any solution to my particular problem. Well, basically my Samsung Galaxy won't get out of bootloop. It just won't go beyond Samsung Galaxy SIV I9500 screen. The phone never did this before this. The phone did, however, rebooted occasionally by itself when running normally.
My phone is rooted, but it runs the official version of Lollipop for Galaxy S4. I had to factory reset my phone one day, and I decided it to reset from the Recovery Mode. After successfully resetting the phone, it booted as usual. Soon after it suddenly turned off, and went into this complete bootloop and would not stop until I remove the battery. Whenever I insert the battery back in, the phone starts by itself, without me pressing any button, and goes in the bootloop again. I can only enter the Download Mode that too for a couple of seconds. When entering the download mode I don't have to press the power button.
Is there any solution to this? I am assuming that my power button suddenly failed. The power button is definitely not stuck. I have opened the entire phone and cleaned the motherboard, and rechecked, it still showed the same problem.
Really appreciate any kind of help.
Hardware issue. Lightly tap the side of the S4 against a table and see if that temporarily frees up the button. Regardless of the end result, you'll need to replace the power button.
Hi,
No need power button to boot in recovery.
Just hold Home+Volume up should do the trick.
@Yoanf_26: How do you expect the phone to get into recovery without turning it on? Volume up and Power are all that's needed to get into recovery. It's the Home button that is optional.
Try a different battery (ask a friend or something if possible). I had similar issues on an i9100 lately. It could only boot to download/recovery mode and was even producing write errors. Looked like brickbug first but was bad battery indeed. It starts slowly with weird behavior and you think you've just messed the rom and just need to reset but it gets worse and worse until you're stuck with download mode only. If you have a spare battery in range its worth a try for sure.
Strephon Alkhalikoi said:
@Yoanf_26: How do you expect the phone to get into recovery without turning it on? Volume up and Power are all that's needed to get into recovery. It's the Home button that is optional.
Click to expand...
Click to collapse
Hello.
I already to start my S4 without power button must just with Volume up and home.
I test with Volume up with power, and my S4 start to recovery.
Differents methods are good to start to recovery. May not for all S4
Guess what? You have a faulty power button, because being able to start the device in any mode without the power button is simply not possible. I tried it just now. Also, if Samsung themselves require the power button to enter recovery or download mode it's illogical to not need it on what is (broadly) the same device.
My power button is good. I test with a custom recovery.
May be not possible with stock. I don't test with stock.
I'm not running stock anything on my I9505. TWRP 2.8.7.0 and CM 12.1 Optimized (currently) installed here. To access Download Mode requires Volume - and Power (Home optional). Accessing Recovery requires Volume + and Power (Home optional, again). Safe Mode requires pressing Volume - and Power, and holding down Volume - throughout the boot process.
As you can see, all functions require power. The fact yours doesn't is not normal.
Maybe, but my S4 is good.
If you think so, who am I to try and persuade you otherwise? When you do encounter an issue with that button, just think back to this thread rather than making a post about it. That way we can both avoid the inevitable "I told you so" that will come out of my mouth.