Last Saturday, my 2yr old child was playing with my screen lock lumia. Next thing I see, it display a factory reset. It's ok for me since I sync my data mostly online, not a real damage.
But after the factory reset, the main problem happen. It doesn't fully functioning, icon doesn't display right. Next thing I know, freeze and factory reset again. it happen 3-4 more time but mostly functioning ok after reset.
It seen ok after that. Except when I try installing back the app from marketplace, after about ten app, error msg displayed rejecting the app installation. Phone is giving feedback back can't even go into the dialer. Next few minutes, restart and stuck at nokia logo, on-off and it's back to factory default.
Happen few more time after installing app every time. The last try, use the phone half day, fully function. Error, restart, stuck at nokia, and factory default again after trying to install app.
Now, it's at Nokia Care (authorise service center).
It's horror for me since happily using it for 3 month. Could find anyone posting the same problem, maybe it is a hardware problem. But a bit of concern since it is just a 3 month old phone.
Sent from my iPad using Tapatalk HD
Hmmmm, 2yr old child + 3month old Lumia = Disaster, Maybe your child managed to get the device wet in some way? A lesson learnt the hard way unfortunately, At least its now in good hands and hope it's all sorted when you get it back
Sounds like a hardware problem. Did your child drop the phone, or did he eat some parts? (okay, just kidding on the last one).
Still not ok
Just got it back from Nokia Care yesterday, the problem is still there when installing back my apps. Will sent it back this afternoon.
I can use it as a phone, but a smartphone that cannot install app, useless.
Fyi, no water did got into my lumia & my child never put the phone into her mouth. I have a 3yr old 3gs (pass to my wife after buying lumia) and ipad which my child use more often, no problem at all.
It seems like the problem my HTC WM had but that happen after 2++ yrs of usage.
Getting frustrated because I know it is hard to explain the problem.
Thinking of selling this phone if the problem cannot be solve.
Just send it to Nokia Care.
Manage to get my Lumia to be error-ed, show it to the Nokia Care personnel. When she try to on-off the set, it 'factory reset'.
They said they will change the phone board.
Will update when I collect my Lumia 800.
Now, I'm happy...
I had the exactly same problem with my Lumia 800.
I set a new passcode and forgot the passcode later
After enter several wrong passcodes, it said it will do a factory reset, i clicked Ok.
Then I have the exactly same problem with yours.
So your kid is innocent
I'm going to give up this piece of ****! Too many troubles with phone since I own it.
Nice to hear this is not just my problem.
Although, it really a big problem when this occur.
Really need to be careful when factory resetting the lumia.
Hope you didn't give up the phone, it really is a nice phone.
Nokia should be aware of this problem.
Just sent it for warranty claim as I did.
Though I'm still waiting for them to repair the phone..
if any one want to have a good windowsphone you will buy an htc windows phone like titan , nokia phone not good windowsphone
Pick up my Lumia yesterday, so far running fine.
Manage to install back most of the apps without problem/error.
They change the main board of the phone.
Won't be setting my phone with pass lock after this.
Sent from my iPad using Tapatalk HD
Related
My wife has been waiting for her Star Trek since May (because the Norwegian importer couldn't get new mobos until recently), because the phone had been restarting at random. But this new mobo is worse! For two days it worked OK, but today it started locking up like crazy. First happened after a phone call, and when we got home, I discovered that turning it on made it lock up on the blue HTC/Qtek screen before the WM5 screen. I then had to remove the battery for a minute or so to make it start up again.
I had installed a couple of programs, so I wanted to wipe it clean to see if that was the problem. After 10-15 attempts I finally managed to do a full hard reset, and it lasted about five minutes of configuration, then it locked up again (on writing the owner's name). Does this sound like anything anybody here has seen, and is there any point in trying to upgrade/downgrade the ROM? This ROM was something with 5, not 4, as the May ROM. Thanks in advance!
Sounds like hardware issue. Sorry.
Yep, I'd say hardware. Especially if you're running the latest ROM. I'd contact HTC, it really should be a warrantied thing...
Thanks! It probably will be since they put in this mobo less than a week ago, and this was the second repair. In Norway there's a three strikes rule for repairs of stuff.
Every time I reset or turn on my fone after shutting down, it will stuck at the logo boot up. It wasn't like that when I first bought the fone. Now it's getting worse and worse since the issue happens so frequently.
I have to take out the battery and put it back, then wait for about 3 to 5 mn before I turn the phone on.Then it would boot up as usual.
Is there anyone facing the same issue as I am? Any suggestion guys?
Are you experiencing excessive heat when this occurs? Also, can you give more info such as: does this happen only after recent charging or does it ever happen when the phone has been turned off for a long time? Was there any recent apps you installed or ROM changes when this started happening? Was there any potential damage done to the phone -dropped it, got it wet, or microwaved
When you say frequently, does that mean every time you restart? every other time? every five times?
Lastly, do you have any other issues/symptoms other than freezing at startup? Does the phone ever freeze during normal use?
i'd suggest you do a hard reset of your phone (hold down both vol up and vol down keys while powering on/resetting). that should fix the problem. if the problem still persists, it's probably some hardware faults.
Me too
My HD2 just started doing this too. It was fine for 7 weeks I have owned it. However, as described in this by OP, when doing soft reset would it would also get stuck on bootup logo. I'd have to remove the battery for a few minutes before it would bootup.
However, my HD2 also crashes and upon reboot then get stuck on bootup logo. It appears to crashes randomly eg not with any particular program or action.
I figured it was software issue so did hard reset. This worked fine. After hard reset the only software I loaded were Total Commander and Cookie Editor.
After Cookie Editor install I did soft reset and it got stuck on bootup logo. : (
So I did another hard reset but it hung up again upon reboot on bootup logo.
This appears to be a hardware issue. But has anyone else had same issue?
T-Mobile HD2
Stock ROM
Purchased July 6 2010 from Expansys
yes i am experiencing the same problem and i have uploded a video on youtube showing this! Yes my phone heats up when this happens..
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Stormrider75 said:
Hi. I got this problem for quite sometime and am so used to taking out and putting back and taking out and putting back the batt.
But now I have another prob: my ringtone suddenly went soft and I now have to keep myself alert all the time to see if there's any incoming call or SMS.
I would like to do a hard reset but the question is: will it set my phone back to the stock ROM or still retain the updated version - 1.66.707.1?
Thanks in advance.
Click to expand...
Click to collapse
It will retain whatever rom you are using
Htc Hd2 vodafone UK
HD2 issue
After some more searching it appears this is not uncommon for HD2. Its not clear to me if it is specific to T-Mobile HD2 or HD2 in general.
It appears to be a hardware issue. Although that is not 100% clear either. I find it hard to distinguish what some people report as 'freezing' which i believe is different to the issue described in this post which is 'hanging up' or 'getting stuck' on boot up screen - in my case it is the T-Mobile 'stick together' pink and white screen/logo.
(The 'freezing' issue that i believe is different to this 'getting stuck on bootup logo' issue appeared to have been resolved iwth new T-Mobile ROM - and I never experienced it on my HD2).
The resolution for getting stuck on bootup screen issue described here appears to have been to exchange HD2 (although some people exchanged up to 6 times and keep getting same issue!)
I think it is important to note that my HD2 performed fine for 7 weeks with lots of soft resets, hard resets, and lots of software installs (though no ROM reflashing) but within last week or so, start crashing randomly, then upon reboot get stuck on bootup screen/logo. This also became more frequent as time progressed. After doing hard reboot, the issue is now acute, eg it gets stuck on every reboot, and crashes more often.
This leads me to think some hardware has failed or degraded and is getting worse, maybe a connection/soldering etc?
However, is there any possibility that a ROM could 'degrade'? Can a ROM have a setting that is modifiable? (I know it is 'read only memory' but is it really?)
Anyways, love to hear from others on this issue.
Same problem here. Bought my HD2 in june. Cooked my own rom with Chucky's kitchen. Flashed different radios, hard resets, task 29 etc. Absolutely no problem. Worked fine for several weeks. But sometime it begun to freeze, auto resets, stuck at boot logo. It was getting worse. Even flashing stock rom it hungs at boot logo.
Now my HD2 is out for repair. Now waiting for returning. Hope they will change the motherboard.
several people have had their motherboards replaced and that has seemed to fix it for them. You'll probably have to fight with htc or your carrier, but should be able to get it replaced.
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
HD2 is an odd one
Thanks for replies. I really don't want to send it in .. but it will probably be the only way to resolve the issue. It will cost me courier there and back, and $20 'triage' fee .. total cost to me will be ~$100 just to have them look at it. Price of doing business I guess.
Anyways, I realized that one of my issues was that it was crashing when syncing. A little digging reveals that HTC Sense does something to all contacts when syncing first time putting a bit of html in contact notes field (weird but it is true .. its their way of reminding you bought an HTC phone?) So once I got it up and running, I disabled Sense and syncing went fine, no crashing.
(Btw, Sense also appears to do something with SMS msgs too so if you have lots it crashes on due to this reason too).
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Still, important point is that it was ok for 7 weeks, and then started crashing, more and more, even after hard reset, though some of issues may have been due to Sense (which is reported by many users).
It is still not a 'normal' thing for a $700 consumer device to have such erratic behaviour. So, given others have exchanged crashing handsets for new handset that has no issues points to underlying hardware issues as suggested above eg motherboard.
As comparison I also have HTC Diamond 2 which has been rock solid for 2 years of continuous use even with lots of software install, tweaking, reg hacks, etc.
Stormrider75 said:
Hi guys. Another question:
I'm considering doing a hard reset. How do I store my messages before doing it? I can't seem to locate the folder that keeps all my messages.
TIA.
Click to expand...
Click to collapse
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
genoki said:
I don't text a lot so i just hard reset without saving .. but do a quick search on on XDA for SMS backup or PIM backup .. during my searches I am sure i have seen a couple of utilities that do what you want.
Click to expand...
Click to collapse
Thanks. Btw I read before we can actually 'disable' Sense.
How do we do that?
Sense - go to Today
Go to Start - Settings
- iI you see the black HTC Settings (has 'Personalize' on top of items) then go to Menu and select 'All Settings' (this will show Windows Mobile's Settings. HTC Sense 'Settings' doesn't everything Windows Mobile Settings has or shows it differently)
- Select 'Today'
- Select the 'Items' tab in Today
- Check 'Windows Default' and click OK in top right.
This will 'swap' out HTC Sense 'today' with Windows Mobile standard Today screen and voila you will have 'disabled' HTC Sense and you are back to using Microsoft's Windows Mobile 6.5 version of Sense (not anywhere near as useful or neat-o to look at but hey they are pretty happy with it )
genoki said:
However, even with plain Jane MS today screen (eg not using Sense) it still crashed once on sync and again when listening to radio. Both times had to remove battery for few minutes before it would reboot without getting stuck at bootup logo.
But so far it seemed to be working 'better' without using Sense.
So, I re-enabled Sense to see what would happen and over a day it has crashed twice. I am going to see how it behaves for few days before sending it in as RMA repair.
Click to expand...
Click to collapse
Just by disabling Sense is not going to make it work. I had this problem with my HD2 also and without using Sense it seemed to be working (there were fewer crashes), but only for few days. My HD2 was getting worse day by day - it was not crashing only if it was not touched (it was crashing just cycling between Sense tabs or by initiating a call).
At repair center they told me (after three weeks of waiting) that the motherboard must to be changed.
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
I have my HD2 back. Took me 2 weeks, the repair center changed the motherboard and got an new IMEI.
Now all is working, no more stuck at bootlogo.
But i'm on stock rom (1.66) with 2.07 radio. No way to run Android with this radio. Hmm...
axman79 said:
Is it possible to damage it by flashing custom ROMs?
For me, this problem appeared after just one month of usage. I was flashed some custom ROMs.
Now, I have a new HD2 but I'm affraid to flash a custom ROM (at least in the near future).
Click to expand...
Click to collapse
I'm afraid as well to flash any custom rom now. For Android i need to HSPL and flash a 2.08 radio or greater to use it. But i'm stick on stock rom for sure.
I want to know as well if it possible to damage it by flashing customs roms ?
As i stated earlier, i flashed plenty of roms, doing task 29 etc., in the end stuck on bootlogo.
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Yah, disabling Sense hasn't stopped my HD2 from crashing eith. Without using Sense it crashed several times while using Opera and more than a few times while syncing over the past three days. Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
genoki said:
Thanks for the feedback on your repairs axman79 and Kalip. Btw, aside from courier cost there and back, did you have to pay the $30 'triage' fee or whatever they call it? Also, did they challenge your observations at all or did they just replace motherboard without question?
Click to expand...
Click to collapse
Was flashing stock rom with stock SPL, was at the shop where i bought it and they send it. I told them it stucks at bootlogo. Repair center changed motherboard without any question. Cost me nothing.
genoki said:
Also, it still gets stuck on reboot often, requiring battery to be removed for few minutes before rebooting.
Click to expand...
Click to collapse
Ja ja, same here.
genoki said:
So, guess I will send my HD2 in for RMA repair too (and wait for up to 3 weeks) and hope I get a functioning device in return.
Click to expand...
Click to collapse
Yes you will, but dont forget to flash back stock rom regarding SPL !
genoki said:
Interesting though I didn't flash my HD2 but it went from 'good' to 'bad' in similar way that your two HD2's. From reading other posts around here on XDA and elsewhere it appears that HD2 motherboards fail with surprising frequency and for variety of reasons.
Would be nice to know if HD2 motherboards are unusually delicate and something physically breaks, or if there is some electrical operation, eg charging it on USB or unusual combination of button pushes that shorts something out?
The fact that battery has to be removed for few minutes in order to get thing to reboot hints that something requires charge to dissipate eg a component somehow 'locks up' which causes crash, and needs to be discharged by removing battery?
Click to expand...
Click to collapse
I want to know as well !
hey guys. I am so glad I found this post! I have exact same issues ith my HD2, it's driving me nuts.
I kept sort of log and described my problems in this post: http://forum.xda-developers.com/showthread.php?t=712729
I think I have to send my HD2 for replacement or repair.
Can you please tell me how can I get my phone fixed/replaced?
I got the US T-Mobile version, but I don't have account in T-Mobile. Can I deal directly with HTC? Where do I have to call to get RMA number etc.
I would greatly appreciate your help!
KML
Hi guys, I could really use some help.
I've a T-Mobile G2 variant which was running a stock HTC Sense ROM. I started getting weirdness happening on it though - the home screen moving on it's own - switching between pages and back again, pressing any buttons apart from the power button just switched the home screens to the thumbnail view. Dialogue boxes refused to let me press the okay or cancel buttons, and texting became impossible - key presses deciding for themselves what they thought I was pressing. Rebooting the phone made little difference, and I tried re-calibrating several times, but this only helped for a short time before it all went again.
Just before Christmas I decided to flash a new ROM, deciding upon the Froyo 2.2.1 final from Elelinux. I have the same problem though, and it's right annoying.
Has anyone else experienced a similar problem?
Apps I currently have installed are:
Google Sky Map
Jewels
Google Scoreboard
Shazam
Sky+
Superuser
Terminal Emulator
WiFi Analyzer
The phone is almost 18 months old, but had been working perfectly until recently - around the same time I installed Angry Birds (which I uninstalled assuming it to be the cause).
Well i had this behavior as well. You need to change your digitizer as your screen has become unresponsive. I tried to fix it myself following the guidelines in the according thread in General and ended up breaking my camera lens.
So what i am suggesting is you get it to an HTC Repair store and let them fix it under warranty. Mine is as good as new now.
Unfortunately sounds like an issue with the digitizer in the screen, which can be repaired but isn't a simple job. The fact that touching the screen anywhere shows the preview suggests the screen is already registering a touch (hence broker digitizer). Don't spose you have an extended warranty or insurance for a replacement?
Hi there,
I've changed mine a month ago, it has cost me about 40€ and was made in 30min with the official tutorial from Htc that you can find on youtube. It was yes.. Really eaaasy ;-)
gruß,
H.
Thanks for the replies - I had hoped it would be software, although I kinda knew it would be hardware. I've got a monthish left on my contract, so I don't think it'll be in warranty, see if I can hang on without it :/
Isn't HTC giving 2 year of warranty for hardware? I've still got a year to go in mine.
mine's not from HTC - it's a T-Mobile one (albeit from a 3rd party supplier), and T-Mobile warranties are usually rubbish from my experience.
Well you won't lose anything by trying. Get in touch and bust their balls so you can get your digitizer changed. It's a hardware fault, not yours. I was treating mine very very well and still it broke after 9 months of use.
Get them to change it, it's not your fault they use crap material to make them.
from what you've said, Id say its maybe more likely to be a trackball issue, which probably doesn't make much of a difference to you, but might be slightly easier to fix
CyberWalrus said:
from what you've said, Id say its maybe more likely to be a trackball issue, which probably doesn't make much of a difference to you, but might be slightly easier to fix
Click to expand...
Click to collapse
He cannot type a message because letters type themselves in, it's clearly a digitizer problem, not a trackball issue i'm afraid.
Reflashed stock T-Mobile ROM this morning - hopefully I can get to my local T-Mobile shop at lunchtime to get them to fix it. Thanks for all your help.
and then I returned. T-Mobile said there was a long processing time for repairs at the moment, and they had no loan phones I could use whilst mine was away. Did say I could upgrade early though which was nice. Spent my lunch hour trying out several new phones (including a couple of nokias, sorry). Came back with a Motorola Defy, and a still broken Hero.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
I have been very happy with my Nexus 9. I bought it at Best Buy the first day it came out. I just returned from a holiday trip, and I kept thinking what a great
traveling device I had, so compact, yet so nice to use, so much better than the laptop I used to carry. I liked the screen, the aspect ratio, the performance.
Well, as soon as I returned, I was surfing Firefox and the screen went all crazy with an abstract pattern and I could only reboot with the power button.
Since then, this has started to happen repeatedly when my battery level drops below about 40%. The screen is white or white with some sort of geometric pattern
and the device is completely frozen. This morning I rebooted, played with it a few more minutes and it happened again.
I have found a few mentions of similar problems online and none of them were fixed by a software reset. Of course, I will do that, but I'm convinced this is not going to help.
So I've had my tablet for a few months beyond the year warranty. And I paid full original price. And I can live with it and keep the battery above 40%, assuming things don't
degrade, but of course, they usually do. Or I can try to work with HTC to pay for an expensive repair (motherboard replacement was said to work). Or I can write it off
and replace it.
I like Android. I am thinking the Pixel C would even be a step up. But I have some big concerns. My first Nexus 7 (2012) failed after warranty was up. Now my Nexus 9 is failing
very soon after warranty is up. I really hate the Apple way of doing things, but I do know that if I get an iPad, I won't have any problems getting it fixed, plus I think it would
be much more mature than a new Google tablet that has sold to a handful of Android enthusiasts.
So I'm just disappointed. With 20/20 hindsight, I should have gotten Best Buy's extended warranty, but that's life. Anyway, I would be grateful for any suggestions. Thank you.
Monday update: For those who may be interested. I contacted HTC customer service and they told me that my warranty expires in 5 days. So I am sending it back under warranty.
As I tried to back up data prior to wiping it clean, I discovered that the Nexus 9 mounts on my Windows 7 computer as it always did, but there is no longer a file system that shows up. I had to back up my data over wifi
using FTP. So this is a very clear and repeatable problem, which means the HTC people will not have to try to reproduce an intermittent freeze up.
Anyway, it will go back tomorrow and I hope for the best.
Hey,
I have the same issue with my tablet, was it fixed?
tunenut said:
As I tried to back up data prior to wiping it clean, I discovered that the Nexus 9 mounts on my Windows 7 computer as it always did, but there is no longer a file system that shows up. I had to back up my data over wifi
using FTP. .
Click to expand...
Click to collapse
There is an extra step involved from Marshmallow deices to see the filesystem: - http://www.androidcentral.com/inside-marshmallow-usb-connection-options
Thanks corkiejp I did figure this out. I was so stressed backing up all my files before sending it back I sort of freaked out when the file system was gone. But yes, it is just another step to get it back.
In response to "was it fixed?" I am not yet sure. I called HTC and they called it a software problem and reinstalled the OS. I told the guy I was sure this would not fix it (based primarily on other peoples' reports online) and he "noted" my irritation, but that was the extent of their fix.
So I got all my apps installed from the image (very convenient) which took a few hours, then it gave me 3 system updates and now I'm back to where I started. I have let it run down to 25% battery a few times
and there has been no failure so far.
I do have a gut feeling that this was actually not a software problem and it will show up again. At least I will be able to push for warranty service if that happens.
I sure do love this tablet. I was using my 2013 Nexus 7 while it was gone. I was crazy about the Nexus 7 as my first tablet in 2012, but the Nexus 9 makes it seem quite antiquated and the bigger screen is much better for everything I use it for. If the Nexus 9 does fail again, I'll send it back, but I was quite serious about trying an ipad. I will need to jailbreak it to get it anywhere near a product I can use, but that seems to be a breeze. But anyway, Nexus 9 is working great at the moment.
Latest update. So for about 3 weeks I used my Nexus 9 and charged it whenever it got down below about 30% battery and no problems. So I thought OK maybe this was a software problem after all and it was fixed.
However, yesterday, it froze on white screen at 39% battery. Clearly this is not fixed. I will wait until I see this happen once or twice more, then contact HTC and tell them I need to claim warranty service even though I am
now out of warranty, since their first fix under warranty did not work. Then I will see if they will fix it under warranty and most importantly, whether or not they just reinstall software again and call it fixed.
tunenut said:
Latest update. So for about 3 weeks I used my Nexus 9 and charged it whenever it got down below about 30% battery and no problems. So I thought OK maybe this was a software problem after all and it was fixed.
However, yesterday, it froze on white screen at 39% battery. Clearly this is not fixed. I will wait until I see this happen once or twice more, then contact HTC and tell them I need to claim warranty service even though I am
now out of warranty, since their first fix under warranty did not work. Then I will see if they will fix it under warranty and most importantly, whether or not they just reinstall software again and call it fixed.
Click to expand...
Click to collapse
This happened to my first N9 after 4 months. They k ow it's not a software problem. It's ridiculous that they present they've never seen this issue everytime someone reports it. I demanded replacement for mine. I tried flashing a factory image myself before that and it changed nothing.
You are not alone - my N9 fails below battery 60% https://youtu.be/-ISHFFZVJVw and http://goo.gl/1i50x4