Related
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
mr23 said:
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
Click to expand...
Click to collapse
I also bought my device about a week ago but im still on 4.1. i think i will wait before i apply any update, to make sure things getting stablized with a new version
Edit.. Nevermind.. I'm in a jumping to conclusions bad mood.. Away from the keyboard I go.
4.2 update won't brick your device. It is a Nexus - just about impossible to brick. You had a problem - but it was not the update.
Sent from my Nexus 7 using xda app-developers app
There are many running 4.2 Builds (Eclipse being one of them) and are having no issues.
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I concede with approximately three million people updated by now, you could have been the one to find the error in the update.
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Jellybean 4.2 Ruined my Asus nexus 7.
X_Fact0r said:
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Click to expand...
Click to collapse
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Kpennett said:
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
Click to expand...
Click to collapse
The guy you were replying to was talking about the OP's issue which was supposedly a bricked Nexus as a result of upgrading to 4.2. It has nothing to do with the items you mentioned, so I would suggest that he is not the one who needs to "get a clue".
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Click to expand...
Click to collapse
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
mr23 said:
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed.
Click to expand...
Click to collapse
THANK YOU. The term brick started with the Linksys routers and a brick was just that, a brick, a paperweight, doorstop, and was a very real possibility (though rare).
Before that PCs would be called anchors or door-stops but those terms were also used for PCs that were beyond any possible usefulness rather than just being beyond repair.
At least say soft-brick.
Sent from my Nexus 7 using xda premium
---------- Post added at 02:07 PM ---------- Previous post was at 01:51 PM ----------
dilldoe said:
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
Click to expand...
Click to collapse
If you can pull or remove the battery you can leave the battery out for 15 minutes. That can revive a device that has become non responsive.
I dunno is the battery on the N7 soldered in or use a ribbon connector?
Sent from my Nexus 7 using xda premium
OP, your device probably wasn't bricked, you need to press the power button for 5>7 seconds and it would of powered on, if for you get the count wrong the Nexus 7 wouldn't power up, this is why you thought it was bricked, in any case, all you needed to do is press and hold the power button for 20>30 seconds and i would of powered on.
fernando sor said:
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
In some parts of the world the day comes before the month, the UK > 24/11/2012, US > 11/24/2012.
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I only mentioned the above because you didn't say in any of your posts that you had tried this.
Just what this forum needed, more *****ing.
May be a defect device most likely due to hardware. Other than the some performance issues and some minor ones here and there, I don't think anyone got their device bricked. I hope the new one will be a better experience. Also it'll be informative if you could have mentioned the first four alpha numeric serial number.
Sent from my Nexus 7 using xda premium
Hello,
I've recently started having a strange issue with my Galaxy Note. The screen starts to ranomly flicker like crazy and then the device turns off. When I restart the phone it shows that I have 1% battery... which is not true because if left alone the phone starts to "magically" charge on its own over the course of the next 15-30 minutes. I've read that the flickering screen occurs when the battery is low and the screen tries to maintain its brightness, but this isn't my case as i've had this happen even at 80% battery charge.
Has anyone encountered this problem before? I've already tried restoring to factory settings to no avail.
Any help would be much appreciated.
Thanks in advance !
Yep, I experienced this last month. I had my galaxy note for just over one year when I started to have this problem.
Sent it back to Samsung and they fixed it free under the two year warranty (EU law). It seems to be an issue they are aware of. My battery now lasts a couple days and everything is back to normal. 4 day turn around for the repair straight to my door.
Give Samsung customer service a call A.S.A.P.
Good luck!
Sent from my GT-N7000 using xda app-developers app
May be you need a new battery
Sent from my GT-N7000 using xda premium
yep classic battery, cool you got it fixed under warrantee!
denialnw10 said:
Yep, I experienced this last month. I had my galaxy note for just over one year when I started to have this problem.
Sent it back to Samsung and they fixed it free under the two year warranty (EU law). It seems to be an issue they are aware of. My battery now lasts a couple days and everything is back to normal. 4 day turn around for the repair straight to my door.
Give Samsung customer service a call A.S.A.P.
Good luck!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply! I will contact them immediately and hope to get things fixed as soon as possible.
I'm actually thinking of selling it in favor of an S2, as this is the second time my note breaks down. Everyone with S2 doesn't seem to have a single problem
robertpas said:
Thanks for the reply! I will contact them immediately and hope to get things fixed as soon as possible.
I'm actually thinking of selling it in favor of an S2, as this is the second time my note breaks down. Everyone with S2 doesn't seem to have a single problem
Click to expand...
Click to collapse
The S2??? I would prefer the S3 or Note 2. Jelly bean will probably be the last update for the S2 and possibly the N7000!
Make sure when you call the service department that you explain the issue as you have here on the forum... Don't say that you think the battery is gone... As with my repair it wasn't the battery... They said they changed a chip set or something like that.... Plus even if it is the battery, they are more likely to just replace it for free if you plead ignorance!
P.S. The best way to say thanks is to use the "thanks" button next to my post!
Sent from my GT-N7000 using xda app-developers app
Hm, this is what is now happening to me as well ... Not cool, will see, whether it lasts, or it was just temporary ..., as it looks to me it happens when I leave Wifi switched on.
Edit: The SGN started to do it all the time, it is fine only while charging, looks like battery is going to dye ... http://forum.xda-developers.com/showthread.php?t=2061307&highlight=flickering, so looking for replacement .
Sent from my SGN using xda app
robertpas said:
Hello,
I've recently started having a strange issue with my Galaxy Note. The screen starts to ranomly flicker like crazy and then the device turns off. When I restart the phone it shows that I have 1% battery... which is not true because if left alone the phone starts to "magically" charge on its own over the course of the next 15-30 minutes. I've read that the flickering screen occurs when the battery is low and the screen tries to maintain its brightness, but this isn't my case as i've had this happen even at 80% battery charge.
Has anyone encountered this problem before? I've already tried restoring to factory settings to no avail.
Any help would be much appreciated.
Thanks in advance !
Click to expand...
Click to collapse
Dear bro..
My note n7000 have same issue.. Did you got it fixed? Help me please...
New battery. Why don't you read what is written before?
hello everyone,
just a quick question really, has anyone else been suffering from random reboots?
My T seams to have a mind of its own, for days on end it wont reboot, but sometimes it will reboot 3 times before I can walk to my train ( 20 mins )
I've noticed the reboots to be more common when im walking or on the move ( and listening to music ) but it does do it other times as well.
this isn't the only issue I've had with this T, I sent it off last month because it wouldn't charge when the phone died completely.
anyone have any ideas?
It seems like some sort of a hardware problem. You should request a replacement if it's possible. The phone shouldn't behave like that of course.
romcio47 said:
It seems like some sort of a hardware problem. You should request a replacement if it's possible. The phone shouldn't behave like that of course.
Click to expand...
Click to collapse
I figured as much. I'm getting quite frustrated with having to keep sending it off. this is the first phone ive bought in recent years that isn't an iPhone and there's been nothing but issues.
it makes me sad. fingers crossed I get one back with an unlockable bootloader
Did you root it? if so which rom/kernel.
If not then have you tried repairing it with pcc? Might save sending it off for several days
Sent from my LT30p using xda premium
av4tar said:
Did you root it? if so which rom/kernel.
If not then have you tried repairing it with pcc? Might save sending it off for several days
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
i have rooted/flashed many times. and this was my assumption when I noticed the reboots. but I have also repaired and returned to stock with no luck. as for the Kernel, because of my locked boot loader i'm on the Stock Kernel.
thanks for the suggestion though
If you've already repaired via pcc, then it needs to go for service.
Sent from my LT30p using Tapatalk 2
Hi. Before I went to the gym recently, my XZ was working perfectly. Nothing was wrong. After the gym (I use it to listen to music), suddenly my volume down button was not working. Power up did. And then, my power button stopped, and nothing start working, then everything started working again and then nothing, screen going on and off :S Turning off the phone wont go, because it just reboots itself, and then into safe mode.
Can't turn it in to warranty either because I am rooted and have addes som mods. Can't go into flashmode, because volume down button won't work... What has happened to my XZ?
Just checked the ports, no water has touched the white dots so they are still white. But phone are still crazy
UPDATE!
Alright guys, here is an update. I was at the store to return it for warranty, since the phone went all mad, turning off, turning on, vibrating. I opened my flap the headphone jack.. The water indicator was PINK! As I am very carefull with my phone, all in general. I always make sure that all the flaps are closed 100%. I know, that I have to close all the flaps, since if it is going to be submerged in water, it must be closed. But here is the funny part. The flap where we put the simcard in... As the flap is only opened at first to put in the simcard... There is no other reason why I should open that. And guess what.. The water indicator there was also pink! I saw that when I was turning the phone back in to warranty since I got asked to take out my simcard. So I am thinking on how my simcard port/opening whatever got pink since it clearly has been to contact with water..
So now I am worried that I am not gonna get my phone back repaired. Now it is my word against Sony's word.. But how did water actually get in the simcard flap...
Send it for repair, they won't even check if you've rooted
Michealtbh said:
Send it for repair, they won't even check if you've rooted
Click to expand...
Click to collapse
I think I have to do that. Just wierd what happened to it. But is there a way to flash it back to stock? Since going into flashmode is hard when volume down is not working.. Don't want to take any chances that if the check the phone. Right now the phone is just sitting there, don't want to touch anything.
Sweaty or damp after gym wait few hrs and it should work again
[email protected] from XDA premium
indycar said:
Sweaty or damp after gym wait few hrs and it should work again
[email protected] from XDA premium
Click to expand...
Click to collapse
Happened to you before?
Did you use it in the sauna?
Sent from my C6603 using xda premium
gm007 said:
Did you use it in the sauna?
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
No sauna. Went right home when I was done. Put my phone on my table, made som food, took a shower and checked my phone, turn volume down, then I noticed it didn't do anything. And a little moment later everything is as described at the top..
indycar said:
Sweaty or damp after gym wait few hrs and it should work again
[email protected] from XDA premium
Click to expand...
Click to collapse
I don't think so.
I go to gym and sweat a lot while I listen to music.
I even touch my XZ with my sweaty hand.
Noting wrong happen to XZ
Sent from my C6602 using xda app-developers app
abd_alazeez2002 said:
I don't think so.
I go to gym and sweat a lot while I listen to music.
I even touch my XZ with my sweaty hand.
Noting wrong happen to XZ
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
Usually this is not a problem for me either. I also used to wash my XZ with all the flaps shut ofc under the spring, because of all the sweat. But after today, this is new for me. And this time, I didnt wash it..
So don't know what to do now.
I think in your case you can flash a firmware with flashtool cause the volume down button is stuck.
Did you try it?
Connect the usb and start the flashing and when you see the pop up about connecting your phone in flashmode than reboot your phone.
Sent from my C6603 using xda premium
gm007 said:
I think in your case you can flash a firmware with flashtool cause the volume down button is stuck.
Did you try it?
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
The problem is that volume down button is not reacting to anything. Right now, the only functioning button is volume up. Power button and volume is not doing anything. That is why it is hard to use flashtool or SUS..
UnLucky12 said:
The problem is that volume down button is not reacting to anything. Right now, the only functioning button is volume up. Power button and volume is not doing anything. That is why it is hard to use flashtool or SUS..
Click to expand...
Click to collapse
I have edited my previous post try it.
Sent from my C6603 using xda premium
gm007 said:
I have edited my previous post try it.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I saw it now! It is now flashing back to stock. It was actually a struggle. Just pressed volume up button and apparently that worked.
Thanks!
Update: All back to stock. Seems like something is damaged... Sending back to warranty tomorrow
UnLucky12 said:
I saw it now! It is now flashing back to stock. It was actually a struggle. Just pressed volume up button and apparently that worked.
Thanks!
Update: All back to stock. Seems like something is damaged... Sending back to warranty tomorrow
Click to expand...
Click to collapse
Good luck
Sent from my C6603 using xda premium
so does your xz work now
indycar said:
so does your xz work now
Click to expand...
Click to collapse
No i don't think so but he managed to flash a unmodified stock rom to send it for a repair.
Sent from my C6603 using xda premium
UPDATE!
Alright guys, here is an update. I was at the store to return it for warranty, since the phone went all mad, turning off, turning on, vibrating. I opened my flap the headphone jack.. The water indicator was PINK! As I am very carefull with my phone, all in general. I always make sure that all the flaps are closed 100%. I know, that I have to close all the flaps, since if it is going to be submerged in water, it must be closed. But here is the funny part. The flap where we put the simcard in... As the flap is only opened at first to put in the simcard... There is no other reason why I should open that. And guess what.. The water indicator there was also pink! I saw that when I was turning the phone back in to warranty since I got asked to take out my simcard. So I am thinking on how my simcard port/opening whatever got pink since it clearly has been to contact with water..
So now I am worried that I am not gonna get my phone back repaired. Now it is my word against Sony's word.. But how did water actually get in the simcard flap...
indycar said:
so does your xz work now
Click to expand...
Click to collapse
No, sadly my phone is not working. Went all crazy. Just updated what happened when I was returning it.
the gym is possess...quit the gym...return for an exchange and go to a new gym.
the white thing inside the ports only reacts to water, so it does not make sense at all if it just happened to turn pink without any contact with the water. Seems to me that someone might had gained access to your phone without you knowing and damaged it in purpose..
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Oh yeah. I don't have S-off, I got my version of CM from get.cm, no custom kernel, or any mod of any sort. The phone was not actively doing anything, except for sitting in my pocket. I held the power button and the power + volume for a good 20-30 seconds.
EDIT: Is my only option to play dumb and ask for warranty? D': I don't want to do that because the rep who traded in my GS2 noticed that it was rooted. I'll probably get denied.
Seriously, anybody? What are my options? What caused this? Is it my fault?
I wish I had some insight on why that happened to you or how to fix it. What I can say is that I was thinking about flashing my first AOSP rom in the near future but was iffy on it. Now I'm super iffy.
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker? Hopefully someone more knowledgeable than myself can comment.
try posting this in the CM 10.1 forums and you will get a result. sorry.
Sent from my SGH-I747 using xda premium
SantinoInc said:
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker?
Click to expand...
Click to collapse
That's a possibility, and what I'm thinking too. Surely someone would have noticed if their phones blew up when they received a call right? The phone wasn't doing anything I hadn't done before (i.e. receiving calls).
You think Sprint will replace it? It's pretty much mint other than the software.
And there is no HTC One Cyanogenmod forum yet.
EDIT: So is it safe for me to go to the store and tell them it crapped out on me? Will they be able to tell that I rooted it?
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
rrusek said:
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
Click to expand...
Click to collapse
First off, Lithium ion batteries do not completely discharge, ever. If they do, they are ruined. Your phone will turn off before it lets the battery drain.
Second, I had at least 80% charge left when it bricked this morning. But what the heck, might as well.
EDIT: Wow. I googled hard bricks and pretty much every case is some kind of update or flash gone wrong. Nobody was just walking around when their phone bricked. This is weird. Considering how rare hard bricks are and the fact that the only apps with root access I had were Ti, File Manager, Spirit and Nova, I'm inclined to believe this is a hardware issue. But I can't be sure.
Bumping. I only have a little while before my charge runs out.
Hmmm, do you know, or have an idea what the battery life was when the incident occurred?
==
EDIT: Oh I see...
I unplugged it about 3 maybe 4 hours before it bricked. It had maybe an hour of screen time then. I'm assuming I had around 80% when it bricked. I have no idea how much power the device is currently consuming. But if it's truly bricked, prolly not much, so it'll last for a while.
If it isn't truly bricked, then probably not that long...
Guys, I'm desperate. I'll try absolutely anything.
All right, it seems like I'm done. This device is toast. Even though it seems like I didn't make any mistakes. I know that almost for sure because my phone was ringing when it bricked at 12:36 P.M. today.
Based on what I've said, does anybody think I am COMPLETELY to blame for this? I don't want my conscience to eat me alive when I take this is for warranty and play dumb. I truly believe this has nothing to do with rooting/custom ROM. I really believe this is a defective phone. Am I wrong?
Did u try the bright light trick
Sent from my HTCONE using Tapatalk 4 Beta
Try the bright light trick...
You can't even get into the boatloader? Or does anything show up when you plug it into the computer?
Sent from my HTCONE using xda app-developers app
sauprankul said:
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Click to expand...
Click to collapse
i knew there was something going on here, between cm10.1 and the sprint htc one ? sure makes me wonder, i've been on my replacement for nearly 2 weeks now running stock rooted with s-off. http://forum.xda-developers.com/showthread.php?t=2310750
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
sauprankul said:
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
Click to expand...
Click to collapse
I was told I would be refunded on my next bill so i'm waiting it out to see before I send back the bricked one. no i was stock-cm and what I mean by that is i installed cm10.1 added my apps, set up my home screens and used it like that until it died. i changed nor tweaked any of the settings from cm defaults
The same thing happened to my room mates HTC One yesteray. I first installed CM, and it was getting extremely hot, so I decided to try rootbox, similar issue, and the device was discharging far too fast. He turned the phone off to wait for me to get home so I could try to fix it. I got home, and there was no sign of life, it was charged fully before he turned it off. It wouldn't turn on at all. I had him take it to sprint and do warranty, they said they needed to open it(LAWL). He went back an hour later, they couldn't open it of course. They handed him a new phone.
Have you tried plugging it into a pc to see if it recognizes anything in device manager? Checked adb devices and fastboot devices?
I have. And nothing. No charge no power no recognizing
Sent from my HTCONE using Tapatalk 4 Beta