Related
Bad Kernel? Bad Radio? What?
I've used quite a few different ROMs. (Enom, Kang [CM], MIUI, and most recently, Rodriguezstyle's miui.)
But, the problem keeps happening, despite wiping between each ROM.
is it the radio? or the kernel? I think it might be, but I'm fairly certain I have the right kernel...and I upgraded my radio when I went to Froyo...
Gah.
I dunno about the kernel, but from what I've heard, if you have the wrong radio your n1 will be bricked. So I guess it's not the radio.
It's not a problem, I've been living with it. It's just rather annoying...
Maybe it's an app I have installed? Or things aren't...done right? Augh idk.
Change the Kernel and that will fix it, pershoot's worked the best for me.
Do you have to pull the battery when it reboots?
cmarti said:
Change the Kernel and that will fix it, pershoot's worked the best for me.
Click to expand...
Click to collapse
I've changed it to many kernels. Right now i'm using this one:
2.6.35.4-950mV-BFS-SVS-AIX-720p-Monks-082710
rickytenzer said:
Do you have to pull the battery when it reboots?
Click to expand...
Click to collapse
No. I will be chilling on the phone, and then I will randomly see the boot image.
if your nexus is still less than a year old, get a new replacement device
watch the logcat output (adb logcat), and also kernel messages http://bootloader.wikidot.com/linux:android:kmsg
khanh1289 said:
if your nexus is still less than a year old, get a new replacement device
Click to expand...
Click to collapse
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
hollywooder said:
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
Click to expand...
Click to collapse
Are you overclocked?
SiNJiN76 said:
Are you overclocked?
Click to expand...
Click to collapse
Not that I'm aware of. I don't even have setcpu installed anymore.
So unless the roms themselves overclock, then no. I upgraded my
kernel, but it has done a random shut off once since then. But it's
not that often. Not as often as it was at least.
Do you have more than one battery to try? My phone locked up or randomly rebooted several times a day when I was using Cyanogen 6rc1, but it only did it with one battery and ran fine with the other. The problem went away after I updated CM though.
My theory is that my "bad" battery is damaged slightly enough that it conflicted with something particular in that rom (also happened with 3-4 different kernels). I don't know anything about batteries, but if that's accurate, I don't see why a battery couldn't be damaged enough to conflict with all roms.
It doesn't sound like your problem exactly, but might be one of the simpler things to try, especially if you have a spare or could borrow one or something.
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
wsrider said:
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
Click to expand...
Click to collapse
My phone isn't that bad, and no luck with the sd card thing.
hollywooder said:
My phone isn't that bad, and no luck with the sd card thing.
Click to expand...
Click to collapse
I bought my nexus one in may. It got worse over time and i had it repaired in september
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
khanh1289 said:
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
Click to expand...
Click to collapse
I don't believe I ever filled out the warranty, can I still get it replaced?
Sorry for the double post, but I'm really curious...about the warranty thing.
sergioalvarezmac said:
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
Click to expand...
Click to collapse
This is my suggestion as well. A friend of mine had this problem. There was a corrupt video on his sd card that caused the entire issue.
Ok, so this has happened a few times now on various ROMs
I'll put my cappy on the charger for the night turned on with my alarm set. When I wake up (somehow on time luckily lol) it's turned off... I don't get it. What gives?
Regards
Smith
smithisize said:
Ok, so this has happened a few times now on various ROMs
I'll put my cappy on the charger for the night turned on with my alarm set. When I wake up (somehow on time luckily lol) it's turned off... I don't get it. What gives?
Regards
Smith
Click to expand...
Click to collapse
Maybe its time u got urs exchanged saying urs have sleep death issue
Sent from my GT-I9000 using XDA App
diablo009 said:
Maybe its time u got urs exchanged saying urs have sleep death issue
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Maybe. To do that, all I have to do it flash back to stock right? Then return?
Regards
Smith
smithisize said:
Maybe. To do that, all I have to do it flash back to stock right? Then return?
Regards
Smith
Click to expand...
Click to collapse
Yes please. Format the internal SD (optional, but I would prefer this), flash it to stock so all traces of messing with it are cleaned up.
diablo009 said:
Yes please. Format the internal SD (optional, but I would prefer this), flash it to stock so all traces of messing with it are cleaned up.
Click to expand...
Click to collapse
I also security unlocked it. Do I need to take care of that or do they even check that?
Also, I have a zagg screen cover on it which I adore and I've only had this phone for a couple months now at the most, I would hate to get rid of it
Will they replace that?
Regards
Smith
smithisize said:
I also security unlocked it. Do I need to take care of that or do they even check that?
Also, I have a zagg screen cover on it which I adore and I've only had this phone for a couple months now at the most, I would hate to get rid of it
Will they replace that?
Regards
Smith
Click to expand...
Click to collapse
By "security unlock" if u mean network unlock, once u flash back to stock it should get reset again.
I unlocked mine on stock, n then when I loaded stock back when changing roms, i found it got locked again. So shouldn't be an issue.
And well, nothing can be done abt the screen protector.
Believe, I've the 4th captivate after 3 replacements for sleep death issue.
diablo009 said:
By "security unlock" if u mean network unlock, once u flash back to stock it should get reset again.
I unlocked mine on stock, n then when I loaded stock back when changing roms, i found it got locked again. So shouldn't be an issue.
And well, nothing can be done abt the screen protector.
Believe, I've the 4th captivate after 3 replacements for sleep death issue.
Click to expand...
Click to collapse
Well, at that rate, a screen protector isn't even really important lol. We'll see if the problem persists :/
Thanks for all your advice, you're great!
Regards
Smith
smithisize said:
Well, at that rate, a screen protector isn't even really important lol. We'll see if the problem persists :/
Thanks for all your advice, you're great!
Regards
Smith
Click to expand...
Click to collapse
Thanks Smith. When u get ur replacement I would recommend u wait for 3-4 days, confirm it does not have sleep death or charge death issues, and then apply screen protector.
Like the dood said - Flash back to stock.. but I would test to see if it keeps happening. If you have a Build 1008 phone - it seems to be more prevalent on that build then others.
Mine happens when the phone is fully charged especially. I would test that to see if you can get it to repeat or AT&T will just give you a replacement battery instead of a refurbed phone.
Will do, if I even get one this time around. We will see...
Thanks again!
Regards
Smith
I have a 1008 build phone and I'm hoping to exchange mine within the week. I flashed back to stock with Odin 1Click on Tuesday and I noticed it isn't entirely the same as when I bought the phone. There are some default apps missing, QuickOffice for one. Anyone have ideas?
avgjoegeek said:
Like the dood said - Flash back to stock.. but I would test to see if it keeps happening. If you have a Build 1008 phone - it seems to be more prevalent on that build then others.
Mine happens when the phone is fully charged especially. I would test that to see if you can get it to repeat or AT&T will just give you a replacement battery instead of a refurbed phone.
Click to expand...
Click to collapse
Hmm. How would I get it to repeat lol, charge it all the way and wait? And do you think they would really sit there and wait for the battery to charge to 100 to test or just swap?
Regards
Smith
You can download Quick Office from ATT Market. It's not needed for returning it back to AT&T. All of the base bloatware is returned to the phone after you Odin it.
avgjoegeek said:
You can download Quick Office from ATT Market. It's not needed for returning it back to AT&T. All of the base bloatware is returned to the phone after you Odin it.
Click to expand...
Click to collapse
+1
Don't think too much. Format the internal SD, and revert to stock and return in. One click odin to stock gets it close to how AT&T gave u the phone. A couple optional apps missing shouldn't matter.
avgjoegeek said:
You can download Quick Office from ATT Market. It's not needed for returning it back to AT&T. All of the base bloatware is returned to the phone after you Odin it.
Click to expand...
Click to collapse
diablo009 said:
Don't think too much. Format the internal SD, and revert to stock and return in. One click odin to stock gets it close to how AT&T gave u the phone. A couple optional apps missing shouldn't matter.
Click to expand...
Click to collapse
Great, thanks. That is all I needed to hear. Hopefully returning it today. Then as long as I can use the three-button mode to get into download and recovery, I think I'm going to try flashing my first ROM bundle.
So I exchanged my phone tonight. They gave me a 1007 build, however my IMEI ends in 0652. The guy at AT&T told me that Samsung had replaced the bad component causing the shutdown problem and was re-issuing old phones. They apparently don't change the IMEI. I'll see what happens. If it starts shutting down again, I'm back in the store for a new one.
trekie86 said:
So I exchanged my phone tonight. They gave me a 1007 build, however my IMEI ends in 0652. The guy at AT&T told me that Samsung had replaced the bad component causing the shutdown problem and was re-issuing old phones. They apparently don't change the IMEI. I'll see what happens. If it starts shutting down again, I'm back in the store for a new one.
Click to expand...
Click to collapse
Yes. AT&T person is right. After multiple exchanges, my 4th n current phone is a 10.07 build, been using for over 2 months now n its been good.
I have a phone that is in the range of phones effected by the standby of death thing and i didn't want to return it but it started affecting my phone, or at least i think it is. I almost always have a custom rom on it so could that be it. And also if i need to return my phone what should i do, should i just return it to jh7 and then call them to make a return or what? My IMEI ends in 3918.
yamato2 said:
I have a phone that is in the range of phones effected by the standby of death thing and i didn't want to return it but it started affecting my phone, or at least i think it is. I almost always have a custom rom on it so could that be it. And also if i need to return my phone what should i do, should i just return it to jh7 and then call them to make a return or what? My IMEI is ********3918.
Click to expand...
Click to collapse
First of all, never expose ur IMEI like this.
Try changing the kernel/ROM and see if it still is exhibiting the same behavior.
diablo009 said:
First of all, never expose ur IMEI like this.
Try changing the kernel/ROM and see if it still is exhibiting the same behavior.
Click to expand...
Click to collapse
Second, don't quote his mistake because now even if he edits his post the IMEI is still exposed.
tsk3
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm on the same boat.
Honestly, I'm switching over to a more stable ROM to avoid it, and then once the refurb Atrix/Infuse/Inspires come out, I'll ring warranty and pick one up.
what defines standby of death? 10% hr?
5% hr?
Really?!?!?!
cappyandroid said:
I'm on the same boat.
Honestly, I'm switching over to a more stable ROM to avoid it, and then once the refurb Atrix/Infuse/Inspires come out, I'll ring warranty and pick one up.
Click to expand...
Click to collapse
So your saying that i can keep my phone and since it has that standby of death thing i can return it and get a atrix/infuse when they come out instead? If so that is awesome, because i got my captivate right before they announced them and i was really angry. But how would i go about doing that once they came out? And about the imei thing, sorry i forgot.
You can't return it for a different phone can you?
opcow said:
Second, don't quote his mistake because now even if he edits his post the IMEI is still exposed.
Click to expand...
Click to collapse
I am sorry. Thanks for pointing out. Edited my post to mask out the IMEI.
JJ133169 said:
what defines standby of death? 10% hr?
5% hr?
Click to expand...
Click to collapse
standby death means - phone turning itself off when in standby mode, irrespective of battery level.
mine used to turn off whenever it wanted be it the battery was in 90s, or in 80s, or anything for that matter. Never could I predict when I would find it turned off.
grave101 said:
You can't return it for a different phone can you?
Click to expand...
Click to collapse
Under normal instances no they will send you the same device (at least ATT) as long as they have them.
you have 30 days from date of purchase to get a different phone, after that your stuck with what you have.
diablo009 said:
First of all, never expose ur IMEI like this.
Try changing the kernel/ROM and see if it still is exhibiting the same behavior.
Click to expand...
Click to collapse
Why not? What can someone do with it?
JJ133169 said:
you have 30 days from date of purchase to get a different phone, after that your stuck with what you have.
Click to expand...
Click to collapse
Phone bought in July.
1. Phone exchange (August)
2. New battery sent (Nov)
3. Phone exchange (Dec)
4. Phone exchange (Dec) <-- At this point AT&T said they would let me pick a different device if this too didn't work and was suffering sleep death issue
nydriek said:
Why not? What can someone do with it?
Click to expand...
Click to collapse
In short, security reasons. Anyone could clone ur device if they know ur IMEI number.
diablo009 said:
Phone bought in July.
1. Phone exchange (August)
2. New battery sent (Nov)
3. Phone exchange (Dec)
4. Phone exchange (Dec) <-- At this point AT&T said they would let me pick a different device if this too didn't work and was suffering sleep death issue
In short, security reasons. Anyone could clone ur device if they know ur IMEI number.
Click to expand...
Click to collapse
good thing 2 know thanks
diablo009 said:
Phone bought in July.
1. Phone exchange (August)
2. New battery sent (Nov)
3. Phone exchange (Dec)
4. Phone exchange (Dec) <-- At this point AT&T said they would let me pick a different device if this too didn't work and was suffering sleep death issue
-----------------------------------------------------------------------------
Yes, they can exchange your phone, I had a nokia mural replaced so many times I called the presidents office of AT&T, long story short I got a captivate for $99 dollars from that and a 3 month extension to my contract.
You can in special circumstances get a new phone, but unless you have it replaced 3+ times there not going to do much...
Click to expand...
Click to collapse
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
I received my Vz Dev Edition phone on Mon. Still running bone-stock with the 4.4 update. The first night, while I was talking on the phone, the phone rebooted twice. Once more in the evening, it rebooted while in its holster.
Since then, it's rebooted once or twice a day, always when I haven't been using it (I've felt it buzz, and taken it out of the holster and seen it booting).
Anyone else experience anything like this? I'm holding off on unlocking, since I'd prefer no argument if I need to send it back.
-Jim
Not normal at all. You can try a reset to default(wiping the phone) and/or reflashing it completely with rsdlite. If that doesn't fix it then I'd most certainly have it replaced. I've never had a random reboot on either of my Moto X's.
That was my suspicion. I've had occasional reboots with prior phones, but never with a stock image. The fact that no one's posted here about reboots made me pretty suspicious.
-Jim
BeagleBoy said:
That was my suspicion. I've had occasional reboots with prior phones, but never with a stock image. The fact that no one's posted here about reboots made me pretty suspicious.
-Jim
Click to expand...
Click to collapse
I posted this before. Nobody responded :crying: lol. I had the same exact problem. I called them up and had the replace it. It took another 10 days, but it was worth it. My new one has no problems as of now. I ran a logcat and saw that basically, the RAM was failing.
aooga said:
I posted this before. Nobody responded :crying: lol. I had the same exact problem. I called them up and had the replace it. It took another 10 days, but it was worth it. My new one has no problems as of now. I ran a logcat and saw that basically, the RAM was failing.
Click to expand...
Click to collapse
Well now we know who they shipped your original phone too...
Steve-x said:
Well now we know who they shipped your original phone too...
Click to expand...
Click to collapse
lol. I almost knew for a fact that Verizon did that when I was with them. Their "like new" was basically just someone else's defective phone.
I've come to two realizations.
1) my phone has always been in my holster when it rebooted (when it happened while I was talking, I was using Bluetooth).
2) you can reboot this phone by long-pressing the power button, even when locked.
You can guess where I'm headed with this. So for the next few days, I'm putting my phone in the holster with the buttons up instead of down. Then I'll see if I need to post an embarrassed-smiley follow-up.
Sent from my XT1060 using Tapatalk
BeagleBoy said:
I've come to two realizations.
1) my phone has always been in my holster when it rebooted (when it happened while I was talking, I was using Bluetooth).
2) you can reboot this phone by long-pressing the power button, even when locked.
You can guess where I'm headed with this. So for the next few days, I'm putting my phone in the holster with the buttons up instead of down. Then I'll see if I need to post an embarrassed-smiley follow-up.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
lol. Hopefully, because getting a replacement is a HUGE pita.
My phone did it sitting on a table without it even being setup.