Yesterday, 10 minutes before a major interview, my rog phone 5S locked up while reading a PDF. It froze for 5 min before rebooting itself. It responded to no input from me at all, not even attempts to get to the bootloader. When it started back up, nothing worked without crashing. I powered it off and switched to my old Pixel 4 XL to do the interview, which worked out fine. I then went back to my 5S and tried to get it working. At first it was fine and I could make and receive calls, but I could only receive texts. I couldn't send them. I left it be for a while longer and then it started rebooting on its own at random. At some point in this, texting started working again and it was fine for a few hours till I went to sleep. However, during the night it started rebooting at random, constantly waking me up. I turned it off, but that didn't stop it. It would turn itself on and reboot. I got next to no sleep till I buried it in my dresser and clothes. I did a reset last night, before going to bed, and I thought that had fixed it, but clearly it didn't do anything except cause me a **** load of unnecessary work.
I went to file for an RMA just now. I provided the serial and ASUS said they won't honor it because it's an international model and has to be returned to the country it was bought in. I have no idea where it's from. I assume China and I can't read Chinese to do any of that, much less know where I'd even go to start that process. It's an expensive phone and I'm without a job right now. I don't know what to do.
I've had nothing but problems with this damned phone since day 1 and I'm sick of it. It's awful. The ROG Phone 3, which I also have, is only slightly less problematic. At least it never did this. I only have it for the gaming controller at this point and I'm gonna get a new phone once a phone comes out with the new Immortalis GPU.
Any help would be greatly appreciated. I want to pot on the ROG Phone 5 subreddit, but they are restricted and IDK how long it'll take to get approved. The last restricted subreddit I applied to took 5 months.
Related
Hello, I am hoping someone can help me because I'm about to test out my 2 year square trade spill and drop (SMASH) warranty if not.
I've had my infinity for about a week and a half without ever having any issues. I rooted it about a week ago, which was impressively simple.
Today, after being pestered every 10 minutes about this BS update even after postponing it for 1 day multiple times I finally gave in and hit update. My prime reset, went to the animated android screen with the spinning icon in his belly. The progress bar finished and then the screen went black.
I walked away for a couple of minutes and came back it was still off. Now every time I try to turn it on I get no response. If I hold power approximately 10 seconds it vibrates, but still absolutely no screen response. I tried holding volume down and power, same thing. I've tried any combination of volume buttons with power, still just a vibrate after 10 seconds and nothing. WTF!?!?
I HATE THESE F#CKING UNNECESSARY UPDATES!
Asus, I'm very disappointed in you right now!
Sent from my Galaxy Nexus using Tapatalk 2
Have you tried plugging it in to the wall charger and letting it sit for a few hours before trying again?
I tried starting it plugged in earlier with no response, but I just replugged it in and I'm going to wait a bit before touching it. It was about 90% charged when I started the update.
The Amber charge light is on. If my memory serves right it changes green when fully charged, so I'll try again when the light changes.
Thanks for reply.
Sent from my Galaxy Nexus using Tapatalk 2
I had that issue with my prime. Something a little different though. I was using my camcorder one day taking video of my son. Got a freeze up, had to reboot. After that, I was able to hit power or hold it I should say for 10 seconds and it would vibrate but the screen never came back on.
I ended up RMA'ing it, only to find that the motherboard failed on it and had to be replaced.
I suspect your board is bad as well. Sorry dude, I know how it feels... asus quality control sux on their lineup. Always has, and probably always will.
Get a needle, put it in the hole on top of the mini HDMI port.
After putting the needle in and then trying to start it up it vibrates within 2 seconds of holding power, which seemed more normal to me. However the screen never turned on, just black screen and then if I try again it vibrates apprx 10 seconds after hold. I have tried again, same results. Battery is fully charged...
Thanks for the help guys, but I'm thinking it's toast, and I'm very disappointed. The thing is i normally never ota, and wouldn't if it had just postponed 24 hours at a time like it had given as an option. I was waiting on aokp to drop before I unlocked and rom'd it out.
I'm probably just going to return it to Amazon... I was going to have it replaced, but I'm now reconsidering waiting on something better to drop. QC seems to be an issue with Asus lately, and since I sold my laptop to pay for my infinity this is becoming a major inconvenience that I'm not trying to deal with again. I was reading on here somewhere a guy had gone through 5 or 6 of them.
I've been building computers for friends and family for more than a decade now and I've always bought Asus mobo's, and never had issues or complaints about them. I think I'll be reconsidering that loyalty next time I have a build.
Sent from my Galaxy Nexus using Tapatalk 2
My prime did that... The tablet vibrates but no screen... Tried even connecting the computer and it saw the tablet. Had to RMA it to get it fixed... then a month later the tablet wouldnt charge.. RMAed again to fix... If I were you return it for a new one or go for a different brand.
Just bricked mine too. OTA failed with dying android, then reboot only to first Asus screen. I can get into recovery but factory reset completed and same thing, only first Asus screen. I think I might be able to flash .26 from the Asus site since I'm still locked but internet is so show it will take 7 hours to download the file.
Edit: update zip in recovery worked. I think it is time to unlock since it is obvious Asus can't get there stuff straight.
I had the same problem with my first Infinity. I called the Asus support, but the guy had absolutely no idea and told me to RMA it.
I returned it to Amazon and got a new one.
fearsparks said:
After putting the needle in and then trying to start it up it vibrates within 2 seconds of holding power, which seemed more normal to me. However the screen never turned on, just black screen and then if I try again it vibrates apprx 10 seconds after hold. I have tried again, same results. Battery is fully charged...
Thanks for the help guys, but I'm thinking it's toast, and I'm very disappointed. The thing is i normally never ota, and wouldn't if it had just postponed 24 hours at a time like it had given as an option. I was waiting on aokp to drop before I unlocked and rom'd it out.
I'm probably just going to return it to Amazon... I was going to have it replaced, but I'm now reconsidering waiting on something better to drop. QC seems to be an issue with Asus lately, and since I sold my laptop to pay for my infinity this is becoming a major inconvenience that I'm not trying to deal with again. I was reading on here somewhere a guy had gone through 5 or 6 of them.
I've been building computers for friends and family for more than a decade now and I've always bought Asus mobo's, and never had issues or complaints about them. I think I'll be reconsidering that loyalty next time I have a build.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same story here. Last time it worked was the animation screen during the ota update last night. Get the vibration sensor as expected after holding power button or resetting with paper clip, but nothing on the screen, ever.
Got the RMA and shipping it in the morning. I bought it from newegg the week released so need to do warranty.
Time to wakeup the abandoned but reliable Viewsuckonic Gtab
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
robotsonic said:
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
Click to expand...
Click to collapse
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
abaaaabbbb63 said:
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
Click to expand...
Click to collapse
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
robotsonic said:
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
Click to expand...
Click to collapse
I'd fully charge it before doing anything else.
jd1639 said:
I'd fully charge it before doing anything else.
Click to expand...
Click to collapse
Have done now. It's charged and I'm about to retry the SIM.
Possibly of note, after I checked it and saw that it had restarted, I checked the battery log and it showed that it had been running for 29m 25s on battery...yet was on charge. I'd attach the screenshot but I haven't posted here enough times for the forum to let me
It was unresponsive no more than 10 mins previously. 10 minutes would be generous.
Anything I can learn from that?
So the phone lasted all night with some light use. Left my Nexus 4 on with no SIM for alarms so I knew I could wake up this morning, but instead, to my joy, I had two phones alarming at me together!
So it was to my dismay that after I'd read some mails, checked some sites, and left the phone to go and get ready for work for 10mins...I came back to it dead again.
I heard some notifications come through (and I was in the middle of a conversation on WhatsApp, so that was normal). I saw the notification light flashing too, so the messages coming through, or at least the first one, didn't crash it.
It did however start up again, with no SIM, after some cajoling.
Is there some way I can see an error log, or a crash log? Or anything I can install to log this for the next inevitable time? Or is this sounding like a permanent hardware issue and I'll need to return the unit?
There's a thread somewhere you can find it, it will show you how to install stock firmware again.
Do that and if it occurs again, call Google to get a RMA
Sent from my Nexus 5 using XDA Premium 4 mobile app
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
robotsonic said:
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
Click to expand...
Click to collapse
No, but you have to unlock the bootloader first before you can flash a factory image and install adb (platform-tools) on your pc, and afterwards relock the bootloader again before sending it to Google.
Hello people, first off lemme say I'm not necessarily new to this forum, I for sure have used it a hell of a lot in the past and I know roughly what goes on around here, I've recently created my account in order for me to actually be able to be able to plead for the amazing help the XDA is known for.
Anyway, long story short, I don't know what the hell happened, but allow me to start from the beginning. I went on a camping weekend with my OPO, phone worked flawlessly all weekend and lasted the whole time, everything was fab, went back to a mates house and asked if I could borrow his phone charger (He has a Lumia 625 incase anyone was wondering), we then went out shooting and I left the phone there for a few hours to charge. Came back to it and it was fully charged, but had turned itself off? Because it was on the power off charge screen when I came back to it, and was on lock when I left it, nobody touched it in that time. I took it off charge, powered the phone up and it must of boot looped about 3 times? Eventually it got into CM but there was no lockscreen, went straight to the homescreen. This is where it went nasty, the capacitive keys outright weren't responding, the device wasn't slow as such, nor was the CPU running hot or doing anything intensive (I have CPU load display enabled), but the date was set to Jan 1970, and the phone couldn't pull a signal at all. WiFi outright wouldn't switch on either. So I tried rebooting it a few times, to no prevail. For some reason, I accidentally tapped Bluetooth in the quick settings panel, the phone crashed and rebooted, and wouldn't stay on for more then 3 seconds? Before crashing and rebooting. I've since gone into recovery and tried a factory reset, cleared cache and media too, but to no luck. Phone still doesn't stay on for more than about 3 seconds once it actually gets into CM (The welcome to CM screen, it crashes 3 sec immediately after boot).
I have no idea what I'm supposed to do, can anyone try shed some light on this? Much help would be appreciated and I sincerely APOLOGISE for the wall of text. Many thanks.
^Dat wall of text doe (sorry about that)
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2922849
PS. You might want to consider using paragraphs in future posts, that's one hell of a long paragraph there [emoji13]
Transmitted via Bacon
Thank you man for the pointer, I'll give it a go. And yeah sorry for the wall.
No worries, I hope it works for you.
Transmitted via Bacon
I am having the same issue since last night. Put my phone to charge and when I picked it up it stayed on for about a minute unable to connect to Wifi or cellular signal. Then it went to a crazy boot loop. Wiped cache, media and at the end data. Now it boots and it stays on for a few seconds and reboots. I will try the solution when I get home tonight but I was just curious if it worked for you.
So I bought this Huawei Mate 8 and to be honest I really loved it, it's the best phone atm imo. And it's pretty expensive in my currency. I've owned the phone for a couple of months now, 4 months I'd say. And just 12 hours ago, problems started.
It all started when I attempted to use the fingerprint scanner and my phone randomly restarted. Huh, I ignored it. But it happened again when I tried to open settings. It'd crash randomly on random actions. But it almost always crashed when I tried to open settings or use scanner. I removed my SD card and then it worked fine for a couple of hours, then it restarted again.
And sometimes it restarted many times over to the point where I'd think it's boot looping. But it'd eventually start. I reset the phone hoping it'd fix the problem if it's software related. But it always restarted right before I could enter my Google account to start the phone. But it reached it's eventual death. It crashed again but it didn't restart this time. I tried connecting it to its charger, but no response and no heat at all, not even in the charger's adapter. And my laptop didn't detect it at all.
What should I do now? This phone is new and expensive. I'm very careful with my devices and it's in a perfect condition. The only incident with it was when my selfie stick got too tight on the power button for like 10 seconds then I took it out. That was the same day the issue happened, so I'm not sure if it's just a coincidence. Anyways please tell me what I should do right now, and yes, the phone is still in warranty but I doubt they'd change it for me, their customer service is **** where I live.
Update
A couple of hours later, it was completely and utterly dead. I tried to press the power button and it turned on, it froze on the Huawei logo for like 3 minutes then it restarted again. It's acting really random right now, random restarts and then completely dead, then alive again...
Update #2:
I hard reset again and it's working pretty fine for now, I'll update again soon, but I strongly doubt that the problem is gone.
I was walking around with my GS8+ in my pocket listening to a podcast when the audio suddenly stopped on my Bluetooth earbuds. I pulled out my phone and saw the Samsung logo. About ten seconds later I got back to a lock screen, and it told me that the phone had rebooted.
Is there anything I can look at to see WTF happened? This has never happened to me before.
Hi,
i also have this issue, I already wiped my phone. i think this is a hardware problem
Every Android as this problem the only question is how often. I got S8+ the 1st week when it came out in Czech and in all the time since now, it rebooted for no apparent reason like 3 times.... IMHO it depends on how often do you restart your phone. If I leave it like month or 2 it is more probably this will happen. Best to restart like every month or so....