Hi,
I have a Z520e running MaximusHD for 4-5 months now, but last two weeks were quite difficult to me. All started with my phone random rebooting and sometimes it was just turned off. Later issue started to be more and more annoying reaching reboot after 3-4 minutes after screen off.
The thing is it never reboots while I'm using the phone (only when screen is off) and it never reboots when it's connected to a charger.
Since I was using ElementalX kernel I reflashed to stock but it didn't help I even tried to change Radio to 1.15 (originally 1.20). Since I thought it was ROM related I reflashed rom and firmware but it didn't help.
`
Now sometimes I have problem powering the phone I try pressing vol- + power, vol+ + power or both vol with power with charger connected or disconnected end eventually I manage to power it on but it's difficult to say which combination actually worked. Sometimes I have problems to get into recovery because phone just reboots. And sometimes charging led isn't lit even the phone is connected (of course when it won't power up).
I would thought it's a hardware problem and I even started to look for a new MoBo but one day after flashing 1.20 radio and stock kernel It was all ok, I run for around 4 days with no reboot so I thought now is a moment to try ElmentalX - it run for around 1 day with no problem, but after that everything came back.
I tried flashing also bulletproof and Bricked kernels - but I think I did something wrong cause it won't power up (black screen instead of boot logo with button leds lit).
I've also tried reflashing recovery and flashing kernel via fastboot - no help.
But if I manage to flash kernel, or just clearing dalvik - phone will power up, set everything again and it will work as long as I will use it - because when I turn off the screen it's hard to predict anything. Now most of the time I keep charging phone so it is working.
I even found a thing of HOX about reseting charging circuit by pressing both vol buttons and power for 2 min. Once I by doing that I managed to power on, when I had a problem doing that - but it didn't solve anything.
And in last_kmsg I found restart reason 0x776655AA which is kernel panic - but I didn't find anything helpful
Any ideas what can I try instead of changing mobo or trying stock rom - because I really want to stick to maximus and I was running several months without a problem ;/
Try flashing awesome kernel cleaning tool from [URL="http://d-h.st/HDi" ]here[/URL] and flash a kernel afterwards.
Sent from my One S
It didn't help. I'm starting again to think maybe it's voltage control or something but hardware related. Curious is that I've managed to run smoothly for 3-4 days, but I'll start to look for another mobo.
Karuk
Last chance will be going back to stock, but I really hate do that ;/
Karuk
Related
Hi,
I've been running Megatron ROM for the last couple of weeks with no issues. Tonight when I turned on my tablet it offered me a ROM update to 1.1.3, so I downloaded the update, rebooted into recovery and installed the zip.
When the tablet restarted it kept saying "unfortunately system ui has stopped" and I couldn't access the menu buttons at the bottom of the screen. I managed to get the tablet to power off and I was going to boot into recovery, wipe and reinstall the full ROM again but I couldn't get the tablet to power on.
I plugged it into the wall charger and managed to get it to boot (system ui crashed again) so I powered it off again and now it's completely dead.
I've tried to power on with all combinations of the Vol Up/Down and power button, nothing.
I guess I wait for the battery to discharge and try again?
Any other ideas? Am I bricked?
1.1.3 is a update only. Install 1.1.2 from the thread and then 1.1.3
and delete this directory "/data/data/com.android.providers.media"
I can't get the tablet to power up, it's dead!
I'll wait until the battery has discharged and try to power on.
mappy24 said:
I can't get the tablet to power up, it's dead!
I'll wait until the battery has discharged and try to power on.
Click to expand...
Click to collapse
connect the charger. if it doesn't power up, hold the power button until it does
I held the power button for 5 minutes, nothing.
Will try again tomorrow, the battery was at 45% when it died.
Still couldn't get it to turn on this morning, i'll keep trying over the weekend.
If I still can't get it to turn on after a few days I'll try charging it overnight to see if I can revive it. It's looking very bricked at the moment though
Let sit for a full day or so
Plug in the charger to the tf but not the wall and ground it somehow (piece of metal etc.)
Hold the power button for 3-5 mins (to discharge)
Shout, PRAISE ODIN!
Plug in tf to wall for a minute.
Unplug
Hold power.
This is how I revived a Sph-d700 that I had in a really bad state, the odin step is crucial. Good luck.
Is it not even possible to boot into the recovery mode when you only plug the tablet to the PC?
Sent from my Galaxy Nexus using Tapatalk 2
last case scenario, try and boot into APX and use adb to reinstall your system
I had it attached to my pc last night and tried all combinations of vol-up/down and power, the tablet never appeared in device manager. I understand that APX mode the screen stays blank but something should appear in device manager, right?
I'll see if I can get any life out of it tonight and if not, i'll give it a charge and try again tomorrow.
Thanks for the advice everyone.
Guys, after a 1 hour charge i've managed to get the tablet to boot again.
System UI stops on loading.
I've used adb reboot to get into CWM, the up and down buttons work but the power button doesn't respond. I can't choose any options in CWM.
How should I proceed to get the tablet usable again?
mappy24 said:
Guys, after a 1 hour charge i've managed to get the tablet to boot again.
System UI stops on loading.
I've used adb reboot to get into CWM, the up and down buttons work but the power button doesn't respond. I can't choose any options in CWM.
How should I proceed to get the tablet usable again?
Click to expand...
Click to collapse
You can use the "touch" recovery. Use the repacked by Roach.
It only read from the internal SD card so put all your files you need to flash there.
Just DON'T use a superwipe script or you'll have nothing to flash.
Right, i've managed to flash Megatron 1.1.2 again, the system ui error is gone.
However, it looks like my power button has failed which would explain why I couldn't turn the tablet on or work with CWM.
I guess I try and flash to stock and contact Asus....
It looks like the power button isn't broken, it just needs to be pressed harder than usual to get the tablet to turn on. I've changed the settings so that the volume rocker wakes the tablet.
Flashed Megatron 1.1.2 then 1.1.3 and we're back in business
Edit: PRAISE ODIN!
Just a quick update, I noticed that my power button was at a slight angle, it looks as though it had slipped and the bit of plastic behind the button was sitting below the actual button on the tablet, meaning that I had to push the button harder to turn it on (if that makes sense).
I got a small bit of blu-tac and pulled the button up, which appears to have reseated it and it's now working as it was before.
Glad to here everything is working again. The question now is why this happened in the first place?
Did you go from 1.0.4 to 1.1.3? I am on 1.1.3 with no issues but as said in the Megatron thread, you have to fully wipe coming from 1.0.4 plus 1.1.2 has to be installed before installing the 1.1.3 update.
I don't know, I was on 1.1.2 and installed the 1.1.3 update then when I rebooted I started to get the UI error. That's really the only problem that I had with Megatron, it would have been easily fixed by just wiping and reinstalling.
It was just at that point that my power button started to play up which confused the issue.
So I left work today at 5, paired my phone with the bluetooth in my radio, after I installed Skyfall last night. Pandora was supposedly playing and connected to the radio, but nothing was playing. I toggled the radio a few times and noticed that now only media was playing but no phone. I turned off the bluetooth on the phone thinking that was the problem.
The phone immediately disconnected from my pebble, expected. The bluetooth quick toggle was spinning like it was busy, so I waited. When the light turned green I put the phone in the cupholder. By the time I got to the next light the phone was off, not connected to anything and a bit warm.
The entire 40 minute ride home the phone was hot, and would not turn on or connect to anything. I tried holding the power button down for 10-30 seconds at a time to reset it, but it would not reset. I have tried this multiple times.
I'm home now, connected to the charger but have no charging light, and it still won't turn on. It has cooled off a lot in the past 10-30 minutes
Past couple days I've tried flashing a few things. After the last reset I installed Skyfall, power saver mod, faux kernel, set cpu (and changed some settings) and restored my app backups. Everything was running fine until I tried to connect to the bluetooth on my raido.
I can connect the phone to my computer, and windows recognizes a device connected, but neither ADB or Fastboot see the phone
Am I missing something on the hard power off?
Insertnamehere12 said:
So I left work today at 5, paired my phone with the bluetooth in my radio, after I installed Skyfall last night. Pandora was supposedly playing and connected to the radio, but nothing was playing. I toggled the radio a few times and noticed that now only media was playing but no phone. I turned off the bluetooth on the phone thinking that was the problem.
The phone immediately disconnected from my pebble, expected. The bluetooth quick toggle was spinning like it was busy, so I waited. When the light turned green I put the phone in the cupholder. By the time I got to the next light the phone was off, not connected to anything and a bit warm.
The entire 40 minute ride home the phone was hot, and would not turn on or connect to anything. I tried holding the power button down for 10-30 seconds at a time to reset it, but it would not reset. I have tried this multiple times.
I'm home now, connected to the charger but have no charging light, and it still won't turn on. It has cooled off a lot in the past 10-30 minutes
Past couple days I've tried flashing a few things. After the last reset I installed Skyfall, power saver mod, faux kernel, set cpu (and changed some settings) and restored my app backups. Everything was running fine until I tried to connect to the bluetooth on my raido.
I can connect the phone to my computer, and windows recognizes a device connected, but neither ADB or Fastboot see the phone
Am I missing something on the hard power off?
Click to expand...
Click to collapse
Have you tried holding down power and volume up? When I was using the stock rom rooted with the insecure kernel my phone was running hot and I turned it off and it wouldn't power back on. Nothing worked until I pressed power and volume up - give it a shot.
bloodiedwraith said:
Have you tried holding down power and volume up? When I was using the stock rom rooted with the insecure kernel my phone was running hot and I turned it off and it wouldn't power back on. Nothing worked until I pressed power and volume up - give it a shot.
Click to expand...
Click to collapse
I swear I was trying this in the car... and several attempts after... But that worked! Maybe it was because I had it on the charger when I did it this time?
Why would they ever make you hold two buttons for a hard reset ><
Phone is on now, Thank you for your assistance!
They gave us back our SD Cards... Now give us back our removable batteries!
Insertnamehere12 said:
I swear I was trying this in the car... and several attempts after... But that worked! Maybe it was because I had it on the charger when I did it this time?
Why would they ever make you hold two buttons for a hard reset ><
Phone is on now, Thank you for your assistance!
They gave us back our SD Cards... Now give us back our removable batteries!
Click to expand...
Click to collapse
Awesome, glad it's up and running.
Hi everyone!
I think my bootloop problem may be a unique one because it only occurs whenever I press the power button (and I've kinda searched other threads and couldn't find a bootloop issue like mine). But before I explain in depth, here are my specs:
Stock 4.4.4 rom
Rooted, with xposed + gb
ElementalX 1.00 kernel
This problem is a randomly occurring one; when my phone is fine and I press the power button, it almost usually goes into a bootloop. It can either stay on the google screen or last all the way up to the x-boot one. Sometimes from the x-boot screen, it'll reboot again. So I realized that if I randomly press the power button a few times (usually trial and error), the problem goes away sometimes and I boot normally again. However, if I hit the power button again for any reason, the bootloop issue relapses.
Also another thing to note is sometimes when my phone is switched on and operating normally and I press the button, it doesn't always reboot immediately. Sometimes it behaves as if the power button is held down and the power menu pops up in the lockscreen... then subsequently it boot loops.
So I'm not sure if this is a hardware issue to do with the button itself (because I very rarely ever drop my phone. Perhaps about 3 times in the past 8-9 months since Dec 2013?) or it's a software issue...which will mean I've to reflash my stock rom.
Anyone with a similar issue please help! It's kinda driving me nuts cos I can't even unlock my phone without triggering a bootloop...:crying:
ultimaflux said:
Hi everyone!
I think my bootloop problem may be a unique one because it only occurs whenever I press the power button (and I've kinda searched other threads and couldn't find a bootloop issue like mine). But before I explain in depth, here are my specs:
Stock 4.4.4 rom
Rooted, with xposed + gb
ElementalX 1.00 kernel
This problem is a randomly occurring one; when my phone is fine and I press the power button, it almost usually goes into a bootloop. It can either stay on the google screen or last all the way up to the x-boot one. Sometimes from the x-boot screen, it'll reboot again. So I realized that if I randomly press the power button a few times (usually trial and error), the problem goes away sometimes and I boot normally again. However, if I hit the power button again for any reason, the bootloop issue relapses.
Also another thing to note is sometimes when my phone is switched on and operating normally and I press the button, it doesn't always reboot immediately. Sometimes it behaves as if the power button is held down and the power menu pops up in the lockscreen... then subsequently it boot loops.
So I'm not sure if this is a hardware issue to do with the button itself (because I very rarely ever drop my phone. Perhaps about 3 times in the past 8-9 months since Dec 2013?) or it's a software issue...which will mean I've to reflash my stock rom.
Anyone with a similar issue please help! It's kinda driving me nuts cos I can't even unlock my phone without triggering a bootloop...:crying:
Click to expand...
Click to collapse
Might want to send it in for repair. Mine had the same symptoms about a month ago--spontaneously displaying the power menu, boot loops where I'd need to do a hardware reboot (or whatever it's called, vol up + power) and sometimes it won't wake the screen when I press the power button and act as if I turned it off. Tried to reflash recovery and change roms, same banana. Then suddenly it won't go out of bootloop, sometimes gets to the x-boot and sometimes only until the Google logo. Sent it for repair and lo and behold, hardware problem. I think this is really inherent on some older Nexus 5's with the wobbly power button.
I suggest you do a nandroid backup while you have the chance. Never had a chance myself
kisetsu17 said:
Might want to send it in for repair. Mine had the same symptoms about a month ago--spontaneously displaying the power menu, boot loops where I'd need to do a hardware reboot (or whatever it's called, vol up + power) and sometimes it won't wake the screen when I press the power button and act as if I turned it off. Tried to reflash recovery and change roms, same banana. Then suddenly it won't go out of bootloop, sometimes gets to the x-boot and sometimes only until the Google logo. Sent it for repair and lo and behold, hardware problem. I think this is really inherent on some older Nexus 5's with the wobbly power button.
I suggest you do a nandroid backup while you have the chance. Never had a chance myself
Click to expand...
Click to collapse
sigh, i reflashed stock rom and the problem persisted. i can't even stay on the bootloader screen without it rebooting itself all over again. i guess it's an old nexus 5 hardware problem like you said :/ thanks for sharing!
ultimaflux said:
sigh, i reflashed stock rom and the problem persisted. i can't even stay on the bootloader screen without it rebooting itself all over again. i guess it's an old nexus 5 hardware problem like you said :/ thanks for sharing!
Click to expand...
Click to collapse
http://forum.xda-developers.com/goo...lease-stop-talking-hardware-versions-t2597276
Sounds like the power button is getting stuck, or shorting out.
Hello,
I flashed the latest LRX22C image on my nexus 5 today.Had flashed it clean,wiping data,cache and system etc except the Internal Storage.Then I flashed the SUPERSU 2.37 ZIP .Everything was fine for about 4 hours.Then suddenly when I pressed the power button to turn the screen off,it was not turning off and the "Switch off" mode was popping up instead .Then, when I got a call,it switched off.The phone won't turn on again.It starts,the Google Boot Splash appears and the bootanimation starts for like 2 seconds and it switches off.Same thing for bootloader mode.
Please Help me!
EDIT: Now its turning on by itself and switches off in 2 seconds!
Sounds like a bad power switch to me, but of course that is just my opinion. :good:
sounds like a mech issue.
legit isue
I have the same problem on mine now... Basically my phone powered down around 45%. Battery. At the time i thought it was dead... But it wasnt. When i would plug into external power, either usb or through wireless charging it would power cycle continuously at the android splash screen.... (1 to 2 second intervals - even if i booted into fastboot) Interestingly it would never go to the battery charging mode. But automatically boot on charge... It did this for about 6 hours then i gave up and left it unplugged for a day. I plugged it back in and it started power cycling again, however this time on its third boot it came back to life . thats when i discovered i still had 40% battery... I dont know what exactly made it boot but it did. Oddly also on boot, it started optimising apps and finishing install again. I checked the md5 before I installed the update so no issue there. Since it powered up i have powered the phone off using the power button long push and let the phone power down. After doing this when i plug the phone in to usb charge it goes to the charge screen. No issue. That said, if i try to power up while tethered and charging it will not allow it. It just stays at the charge screen. As soon as i unplug the usb the power button allows the phone to power up and work... When booted up it charges as normal when plugged in. Im convinced there is an issue with the power management drivers or drivers for the button controls. My phone worked fine until the 5.0.1 update was installed. On my nexus 5. Anyone else or just us two? Ive had a hard time finding people posting on this issue.
So my nexus 5 had the power button problem so i opened up the phone and cleaned it with alcohol and blew air, it would work but then start having random reboots every often. i have tried using a custom recovery, flashing a custom os, rooting the device, remapping the power button to volume buttons(which just makes it reboot even more) , tried cleaning the power and volume button 3 times again but still having random reboots.
please help me I've heard that this may be a power button problem and that i might need to replace it but isnt there any other way or is it some other problem?
also the phone heats up over 65 degrees due to constant reboots
currently on stock 6.0.1 .