Related
Hey everyone.
I just got a brand-new G-Tablet through Sears. I'm checking here to see if anyone has any ideas before their tech support opens in ~two hours.
I got it to my office, plugged it in and charged it until the light turned green. Then I turned it on and played with it a bit. I didn't have a method to put it on the network right then to sync anything, so I really just poked around and then set it to the side. One thing to note is that I wasn't presented with a setup screen at all, it booted straight to home.
Then later that afternoon when I went to go home, it wouldn't power on. I'm not sure if it went to sleep or powered off, but nothing happens no matter what button combination I press. I've tried just pressing power, holding it down for 4 seconds, holding it down for 30 seconds, power and volume + at the same time, and power and volume - at the same time.
I tried hooking it up to my computer last night, thinking that maybe the display didn't come back from sleep and maybe I could force a reboot via ADB, but it must be off alltogether since it didn't trigger a USB installation on the computer.
When I plug it in to charge, the little light turns red, then a while later turns green, indicating that it is fully charge, yet still no joy.
Your thoughts?
Press the power button for a really long time to see.
Sent from my GT-I9000 using XDA App
Just held it down for 90 seconds, no dice. I tried pressing it briefly afterwards too just in case.
I think Roebeet and a few others had a similar issue. I believe they had to wait 24+ hours for the battery to drain. I can't find the thread but the search button may help
You didn't update the firmware, correct? This is a known issue with the older firmware and it's happened to me.
I believe that the device is frozen - and yes, when it gets in that state you cannot reset it, even when holding down the power button. You have two choices, when this happens:
1- Open up the back of the device (and thus voiding the warranty) and press the reset button on the system board. That will fix it immediately. I know this probably isn't the best option, but I wanted to mention it.
2- Unplug the device and wait for the battery to completely drain. This takes about 24 hours. Once drained, you can press the power button and it will boot up for 10-15 seconds before stopping - that's your queue that the device is "fixed" so you can start re-charging it.
Fortunately, this probably seems to be resolved on newer firmware, tmk. I've only had this happen on a device with the original stock firmware.
The two of you are gentlemen and scholars. I'll let you know how it turns out. I was on the phone to get the RMA when the line went all fuzzy and I couldn't talk to them. Then it did the same thing when I called back. Then I saw this post. Divine Intervention...
Going on 28 hours now and still nothing...I'll probably give it at least 3 days before I send it back.
Give it a few more hours, and then plug it in for a minute and try powering it up. the battery could be so drained at this point that it needs to be plugged in to go on.
Mine took 24 hours to drain, but I wasn't sure if it was at 100% charged, at the time.
Almost to the 48 hours mark and still nothing. I tried plugging it in briefly just to check and the red light still comes on, but it won't power up. Anyone know the possible standby time of a fully charged batter on these things? I was thinking if the system locked up and it isn't hardly doing anything, it could last a while...
Maybe a return to the store you purchased it from at this point. The battery should be dead by now. You should be able to get an exchange or you can try the other route Roebeet suggested but that will definitely void your warranty
thebadfrog said:
Maybe a return to the store you purchased it from at this point. The battery should be dead by now. You should be able to get an exchange or you can try the other route Roebeet suggested but that will definitely void your warranty
Click to expand...
Click to collapse
The problem is that I'm in Guantanamo Bay, Cuba. Shipping time is at least 2 weeks and sears won't do an advance replacement. Neither will the Viewsonic support folks. So I'm either stuck having to buy a second one and waiting for them to get the original back before the refund, or waiting a month or more for a repair...
Are there any seals inside the case that get broken if you open it?
I don't know the answer but this may be of some help
http://forum.xda-developers.com/showthread.php?t=842354
thebadfrog said:
I don't know the answer but this may be of some help
http://forum.xda-developers.com/showthread.php?t=842354
Click to expand...
Click to collapse
I think I'm just going to give it anther day then send it in for repair.
Still nothing. Since its going to be over a month before I get a replacement, I'm just going to return it and wait for the new crop of tablets to come out. Thanks for the help guys.
Sent from my Dell Streak using XDA App
Sorry to hear that. I think the reset button on the board would have worked, but I understand why you wouldn't want to open the device up. We shouldn't have to void our warranty to be able to do a hard reset.
Rhodizzle said:
Still nothing. Since its going to be over a month before I get a replacement, I'm just going to return it and wait for the new crop of tablets to come out. Thanks for the help guys.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You might try nvflash.... worked on a friends.
GTO777 said:
You might try nvflash.... worked on a friends.
Click to expand...
Click to collapse
But was your friend's responding at all? I get absolutely nothing. the only thing the tablet does is give me a red light when it's charging and a green light when it's done. The power button does nothing and volume down + power does nothing. doesn't nvflash require a connection over USB before it can do anything?
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
ZMaissi said:
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, that is sort of what I was thinking. I suspect the boot partition is corrupt. But, wasn't sure being a new customer with Verizon.
Hey can you link me something about how you downgraded your droid ultra from SU6-7.2 to SU6-7
LOL, just flash SU6-7 (CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml) with RSD-Lite. That's the easiest way.
rfunderburk39 said:
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Click to expand...
Click to collapse
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Mangu said:
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Click to expand...
Click to collapse
In the case of my phone, you could hold the power button in for a long period of time and then release and still nothing, not a flicker. I did not try voice commands, not a bad idea, but I did not want to open the phone due to the fact it was being replaced (further risking a decline on replacement).
On a similar note, the new unit seems to reboot at least once daily.
This details is going to be long...sorry about that, but I'm extremely worried so please help me soon.
My nexus 5 is 1 year 2 months old, bought in india, currently out-of-warranty. I never ever rooted or made any software changes, it's on 6.0 Marshmallow on legit OTA software updates.
When I'd updated to Lollipop, few days it'd do random reboot, but it'd complete the reboot and the problem ended automatically in sometime.
Now, I'd installed 6.0 OTA, but now from past night the phone started doing these activities to be exact:
" While operating yesterday night, it randomly showed me 'Google' (which's shown when the phone starts) and the phone turned off. It was just a start. Today morning, it again doing same things when I turned phone on. If I press "Power+VolumeDown" it shows me the bootloader menu, but immediately switches to 'Google' screen, but here it starts showing in an infinite loop. So the "Power+VolumeDown" isn't working, only direct power button is turning phone on. Now when directly phone is turned on, if I press the power button once, it immediately goes to sleep and wakes up, I repeat this and the phone repeats this 2-3 times; if by-chance the phone sleeps by normal power button click and again if I try to turn it on, then on clicking power button it directly shows 'power off' (which is normally shown after waking up device and holding the power button, I try removing the option of 'power off' but it doesn't go and after 2-3 tries it goes, unlocks the screen, hangs for 2 seconds, shows google and repeats the same story.
Now I just did factory reset, now the phone had started but it again swiched off and now it isn't turning on again.
Please please help me what can be the problem? As in first thing I'm going service centre tomorrow morning, but as it's out of warranty how much they'll charge Idk, I mean can anyone along with solving above problem give a solution that what can be the cost, is this only a software issue (as I said I never made any roots anything, only thing phone ever might have got damaged would be by falling off from height, which last was dropped atleast 6 month ago, and I updated to 6.0 in mid-beginning of October, while this is the end, so what can be the problem exactly and only software issue it will be? What can be expected cost? In India, Mumbai and would be going to service centre tomorrow, I really don't trust Indian Service centres as they idk how much will they overcharge and how should I tackle them please tell?
Can anything mentioned till now be a hardware issue and be charged more for?
I'd also like to mention that I've absolutely zero idea about rooting and any other advance things so please don't provide any advanced resolutions which go completely above my head.
Please help me soon, I never did any modifications to the phone, and I wouldn't be getting a new one anytime soon, so I don't want my phone to be like this because i'm scare that at this moment it's either beyond repair or would be charged too much to repair..
Arko Sarkar said:
This details is going to be long...sorry about that, but I'm extremely worried so please help me soon.
My nexus 5 is 1 year 2 months old, bought in india, currently out-of-warranty. I never ever rooted or made any software changes, it's on 6.0 Marshmallow on legit OTA software updates.
When I'd updated to Lollipop, few days it'd do random reboot, but it'd complete the reboot and the problem ended automatically in sometime.
Now, I'd installed 6.0 OTA, but now from past night the phone started doing these activities to be exact:
" While operating yesterday night, it randomly showed me 'Google' (which's shown when the phone starts) and the phone turned off. It was just a start. Today morning, it again doing same things when I turned phone on. If I press "Power+VolumeDown" it shows me the bootloader menu, but immediately switches to 'Google' screen, but here it starts showing in an infinite loop. So the "Power+VolumeDown" isn't working, only direct power button is turning phone on. Now when directly phone is turned on, if I press the power button once, it immediately goes to sleep and wakes up, I repeat this and the phone repeats this 2-3 times; if by-chance the phone sleeps by normal power button click and again if I try to turn it on, then on clicking power button it directly shows 'power off' (which is normally shown after waking up device and holding the power button, I try removing the option of 'power off' but it doesn't go and after 2-3 tries it goes, unlocks the screen, hangs for 2 seconds, shows google and repeats the same story.
Now I just did factory reset, now the phone had started but it again swiched off and now it isn't turning on again.
Please please help me what can be the problem? As in first thing I'm going service centre tomorrow morning, but as it's out of warranty how much they'll charge Idk, I mean can anyone along with solving above problem give a solution that what can be the cost, is this only a software issue (as I said I never made any roots anything, only thing phone ever might have got damaged would be by falling off from height, which last was dropped atleast 6 month ago, and I updated to 6.0 in mid-beginning of October, while this is the end, so what can be the problem exactly and only software issue it will be? What can be expected cost? In India Mumbai and would be going to service centre tomorrow, I really don't trust Indian Service centres as they idk how much will they overcharge and how should I tackle them please tell?
Can anything mentioned till now be a hardware issue and be charged more for?
Please help me soon, I never did any modifications to the phone, and I wouldn't be getting a new one anytime soon, so I don't want my phone to be like this because i'm scare that at this moment it's either beyond repair or would be charged too much to repair..
Click to expand...
Click to collapse
I had nearly the same behaviour ... changing the battery solved this for me.
Battery Charging didn't resolve
dirk0504 said:
I had nearly the same behaviour ... changing the battery solved this for me.
Click to expand...
Click to collapse
I did 100% charge my phone, but nothing is helping. At this moment the phone isn't turning on and I'm waiting for battery to drain now as charge isn't helping. Even now if I put on charge, it won't charge and continuously show "google" "google" instead of charging.
Sir i think you have a problem with the power button. Its stuck. I have the same problem before. I had it fix and til now my nexus 5 is doing fine.
I have been having a similar problem for the past 3 months or so. I thought that it was my power button but I also saw in a few of these threads that it was a battery issue. My phone would act OK as long as I had 75% or more battery but once it got below that it would randomly boot loop. The last couple of weeks, when it boot looped, it would drop from +60% down to 4% after one reboot. That was when I decided to try replacing the battery even when the other symptoms seemed to point toward the power button.
I found a battery on line and changed it out last week and haven't had a problem since. I believe the phone was just getting erratic battery indication and shutting itself down thinking it was out of juice. Cracking open the phone and changing the battery was easier than expected provided you take your time and don't force anything.
Tip: There is a clip just above the "S" in Nexus that needs to be pressed back in when you put your cover back on or the wireless charging will not work.
Had this issue, replaced the battery. All is well now
My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Try pressing and holding all three.
Power + vol up + vol down. Should force a reboot.
isthisadagger said:
Try pressing and holding all three.
Power + vol up + vol down. Should force a reboot.
Click to expand...
Click to collapse
No response. Not even a vibrate.
That is unfortunate. I had this multiple times. Black screen but phone was on. Just did not react to power button or screen did not turn on. The button combo helped.
Only other idea I have is to let the battery run out. If the phone is even on in your case.
How could you tell if the phone was actually on? Could you receive calls or something?
And this was on your Zenfone 6 too?
I've left it off charge for the last 5 days now. I don't think it's gonna run flat soon, considering that it's not even on.
I think I will send it back to the seller (Taiwan!) tomorrow
The notification led was blinking. Yeah on zf6. It stopped happening a few month ago. Probably fixed in a few update. But yours seems to be a different problem.
CVonV said:
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
I am not sure where, but I think when I was trying to fix my hard bricked Z6, some post said that a red LED without any other notion from the phone means that you may be able to get this running in QD-Loader mode - check this: https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
Can you get the phone to register as a COM-device?
abprie said:
Can you get the phone to register as a COM-device?
Click to expand...
Click to collapse
My post on here: recognised as an Android ADB Interface but I can't do an adb reboot as "device not found"
I am not sure where, but I think when I was trying to fix my hard bricked Z6, some post said that a red LED without any other notion from the phone means that you may be able to get this running in QD-Loader mode - check this: https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
Click to expand...
Click to collapse
Thanks for this. I actually saw this a few days ago but was reluctant to try as I'm worried it might void the warranty.
CVonV said:
No response. Not even a vibrate.
Click to expand...
Click to collapse
Try again the Power + vol up + vol down combo, but hold it 30 secs. If still does not reboot, get worried...
papete said:
Try again the Power + vol up + vol down combo, but hold it 30 secs. If still does not reboot, get worried...
Click to expand...
Click to collapse
I did hold them for 1 minute and no response before. Is there a specific order which they should be pressed and held?
No, no order. Just all pressed together at once. I think you should return the phone. Last year there was a similar issue with an update and many phones had to be returned, but it was solved.
If the combo don't reboot the phone I would return it. I don't want to give them excuses not to honor the guarantee.
papete said:
No, no order. Just all pressed together at once. I think you should return the phone. Last year there was a similar issue with an update and many phones had to be returned, but it was solved.
If the combo don't reboot the phone I would return it. I don't want to give them excuses not to honor the guarantee.
Click to expand...
Click to collapse
It was never solved. It's still happening even to new ASUS phones.
To OP: Return the phone immediately. Your mobo is 95% dead. It's a hardware issue so trying to fix that is not worth losing the warranty.
aleksander002 said:
It was never solved. It's still happening even to new ASUS phones.
Click to expand...
Click to collapse
Yeah so weird as I only did an OTA firmware update from the shipped Android 9 to Android 10. It installed successfully and rebooted once. But only died once I shut it down. Was there a thread about it?
To OP: Return the phone immediately. Your mobo is 95% dead. It's a hardware issue so trying to fix that is not worth losing the warranty.
Click to expand...
Click to collapse
Yeah it actually just got back to Taiwan yesterday. Seller is being annoying though and not wanting to send me a replacement. But instead wanting to refund me and then asking me to repurchase (at a potentially higher price like seriously -_-).
Such a hassle.
CVonV said:
Yeah so weird as I only did an OTA firmware update from the shipped Android 9 to Android 10. It installed successfully and rebooted once. But only died once I shut it down. Was there a thread about it?
Yeah it actually just got back to Taiwan yesterday. Seller is being annoying though and not wanting to send me a replacement. But instead wanting to refund me and then asking me to repurchase (at a potentially higher price like seriously -_-).
Such a hassle.
Click to expand...
Click to collapse
might be you received damaged Cell because I faced the same issue when I bought LG G4 Cell, Seller told it was new but after I sent to Service Center they told its repaired cell and not new, it was motherboard issue, so might be you also picked up cell like that, other I never faced any problem in Asus 6z since I bought last year
sunnymodh said:
might be you received damaged Cell because I faced the same issue when I bought LG G4 Cell, Seller told it was new but after I sent to Service Center they told its repaired cell and not new, it was motherboard issue, so might be you also picked up cell like that, other I never faced any problem in Asus 6z since I bought last year
Click to expand...
Click to collapse
They refunded me and couldn't get stock of a new one. The repair centre apparently can't fix it either lol.
Anyway it's a blessing in disguise as I'm gonna buy the Zenfone 7 or 7 Pro now.
CVonV said:
They refunded me and couldn't get stock of a new one. The repair centre apparently can't fix it either lol.
Anyway it's a blessing in disguise as I'm gonna buy the Zenfone 7 or 7 Pro now.
Click to expand...
Click to collapse
Yes..Nice Choice, Hope Asus 7 Series Price not like onePlus & others
Same thing just happened to my wife's phone. She received an OTA update from ASUS which resulted in her phone rebooting itself during the night and getting stuck at the ASUS splash screen totally unresponsive.
I waited for the battery to die and after charging the phone powered up. It lasted 12 hours before suddenly shutting itself down when the wife was changing settings to pull the time from the network.
Now dead as a brick. Charge light no longer lights. Totally unresponsive. No amount of power button/volume button combination or time will do anything to make it work again.
Pretty pissed off as it was purchased early Sep last year and has already been sent back to ASUS in Taiwan for the USB charge port board replacement. Now 1 yr and 17 days old.
I do not know what to do now except push for a repair under warranty.
Nearly on the day when my warranty went out the ZenFone did it to.Used Bluetooth to my headphones and suddenly it went dead for good.Was reading that others on the net had the same problem and guess its a major built in fault on a rather expensive phone when i bought it. Got a new phone of a different brand and will for sure never return to any Asus phones when quality aint a strong word for that brand. Over and out.
Wow. I was looking at these phones but there are issues it seems.
Rule #1 if your OS is fast, stable and fulfilling its mission...
Do Not Update!
This goes double for carrier phones. AT&T for example can wreck your user experience with their later updates.
With Pie and above security isn't an issue unless you do something stupid.
Don't get sucker in by scare hype.
Always redundantly backup critical data to at least 2 hdds and always be ready to reload. Reload if you can't resolve a malware issue asap. Cover your ass...ets