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?
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
Hu guys. Long story short. I was out for awhile yesterday and when i got home i could not connect to my wifi. I tried turning wifi off and back on but it would not even turn off! When i toggled wifi to off nothing would happpen..................almost as if it got 'stuck' and also some apps started randomly forced quitting. I turned the phone off and back on and all was fine again
Then last night i woke in the middle of the night and hit the power button to wake the phone so i could check the time but the phone didnt respond. Puzzled i figured i must have turned the phone off accidentally so i pressed again but this time holding the button down as if to power on the device but again, nothing! I started getting worried at this stage and eventually though wait, the battery must be dead (no idea how but it must be) but when i plugged in the charger again nothing happened! It was as if the device was literally dead! I went back asleep and figured i would just have to bring the phone into the store i bought it from and hopefully be given a replacement but when i woke up this morning i decided to hold the power button and the volume button (a hard reset?) anyways the phone vibrated as if to be revived back to life and then powered on and has been fine ever since??
Should i be worried or what? Anyone have any ideas what happened? I can honestly say i havent tampered with the phone or tried to root or anything like that so i have no idea what happened! Iam just worried incase its a problem with the device as i have it around 3 weeks now and i think it has to be returned as faulty within 31 days to get a replacement! The weird thing is, its working fine again now with no issues?
if it's the sleep of death whilst charging, try a free app called safe charge from the store - admittedly, this doesn't account for the wifi issue though - I'd roll with it, but then take it back if there's any recurrence - 12 month statutory guarantee minimum presumably?
deepershades said:
if it's the sleep of death whilst charging, try a free app called safe charge from the store - admittedly, this doesn't account for the wifi issue though - I'd roll with it, but then take it back if there's any recurrence - 12 month statutory guarantee minimum presumably?
Click to expand...
Click to collapse
It wasnt while charging! Its as if the phone just died for no reason and wouldnt respond to anything until the following morning when i did a rest i think its called ( press the power and volume button together) Hopefully its not a serious problem as Vodafone are difficult to deal with when it comes to faulty handsets! I was told before the device has to be returned as faulty and confirmed THREE times before they will give you a replacement! In other words iam not entitled to a new phone . Iam only entitled to have it sent away for repair (which can take 2/3 weeks) and ive no insurance so not entitled to a replacment phone until it comes back! They will only hand out a new phone if the current one is verified as being faulty after THREE attempts to fix the issue! This is what i was told at least although i was told this 3/4 years ago
Blaalad12 said:
It wasnt while charging! Its as if the phone just died for no reason and wouldnt respond to anything until the following morning when i did a rest i think its called ( press the power and volume button together) Hopefully its not a serious problem as Vodafone are difficult to deal with when it comes to faulty handsets! I was told before the device has to be returned as faulty and confirmed THREE times before they will give you a replacement! In other words iam not entitled to a new phone . Iam only entitled to have it sent away for repair (which can take 2/3 weeks) and ive no insurance so not entitled to a replacment phone until it comes back! They will only hand out a new phone if the current one is verified as being faulty after THREE attempts to fix the issue! This is what i was told at least although i was told this 3/4 years ago
Click to expand...
Click to collapse
You're not entitled to a new phone - you could well get a repair or a refurb. Are you sure you've not enabled stamina mode, or one of its variants, and it was just offline overnight?
So basically, I fell asleep and left my phone charging and when I woke up, the green full charge light was on but nothing made the phone turn on. I tried holding the power button for 30 secs, holding the power and volume down button for awhile, and basically all sorts of button configurations but nothing seems to work. The light stayed on for a couple hours until I'm assuming the phone died. I spoke to a samsung employee and after I told him about the root, he said that the samsung had some kind of ota update that kinda bricks a rooted phone and that I'm basically screwed. Im not sure if that was just him being a samsung employee or not, but either way I'm sure it has something to do with it. Is there any way I can completely reset the firmware in it so I can at least use it again? I plugged it into my wall charger and computer with absolutely no sign of life. This seems like a very hard brick that most likely is the end for the phone, but before i go spend 200 dollars on a phone upgrade, is there anyway for me to get the phone working? Or on? Any help or advice is appreciated, thank you.
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