Database Develop

Cappy turns itself off

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.

Bionic is Not Turning On.

It's not rooted and doesn't have anything on it. Pretty much stock. Sent a text msg this morning and checked my email from it. Came back to it abt 20 minutes later and it won't even turn on. Tried charging it. Won't turn on. Tried swapping with my regular battery (which was fully charged when I put it away. It could be dead by now.). Nothing. Tried removing the battery, waiting, replacing the battery. Nothing. I did briefly get the M Dual Core icon and then all went blank.
Suggestions?

Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD

rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
I second this.

Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
idefiler6 said:
I second this.
Click to expand...
Click to collapse
rduckwor said:
Back to VZW. Sounds like a faulty handset.
Good Luck,
RMD
Click to expand...
Click to collapse
Thanks, all.. Hauled my cookies 30 minutes over to Verizon. The sales rep assumed I hadn't bothered to charge my phone. When he realized it wasn't the battery, he was extremely helpful and replaced the phone on the spot. He said he'd never seen that before and with a phone less than 1 month old, I shouldn't have those kinds of issues. Kudos to Verizon for a pleasant experience. I've had some bad experiences in the past, but this gentleman was helpful and didn't try to sell me any accessories! ;p (They always try to sell me something when I'm there.)

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
This is referencing what one would do if the software had an issue, if it does this will fix it but kinda sounds like hardware. I have returned my Bionic to stock twice its fairly easy, computer does almost everything. Here is this to get you going if you wanna do it.
http://forum.xda-developers.com/showthread.php?t=1262540
Just remember, phone has to be in fastboot mode to be detected by RSD Lite and once its detected and the file starts flashing, if it seems like its not making progress while saying otherwise, dont unplug it just wait
Sent from my DROID BIONIC using xda premium

BFirebird101 said:
Without going through the pain of returning it, would you be able to connect it to your computer, and reflash the (is it TRZ?) file through the new RSD Lite through the stock bootloader? Definitely worth a try.
Click to expand...
Click to collapse
One would need the ability to turn the phone on in the first place for this to be attempted. That's why no one was mentioning the FXZ.

The phone booted to the dual core M logo, which with myself that happens to be as far as mine would go when i successfully flashed my FXZ. The phone needs to boot to the fastboot screen which can be done on many occasions that the phone can get to the first logo, as long as there is battery left.
....
But congrats on the new replacement i just saw that after i posted
Sent from my DROID BIONIC using xda premium

It hasn't happened to me but I have to pull the battery on my wifes Bionic at least once a week and twice in one day. It would just go away suddenly and act like it was dead. I may return it for a replacement.

if anyone has exchanged their Bionic for a replacement because of the BSOD defect, will you please provide feedback in this thread? thanks

hi all:
just bought a bionic off ebay for cheap ($20 + free ship) but it has problems
it was being sold as "battery with water damage but phone is not but wont power on"
he said one night he left it in his drawer and when he woke up it didn't work anymore he tried removing battery and all that.
to my understanding the battery was previously water damaged and he could still use it and then got the wont power on later on.
anyhow to my question
the phone comes today with just the phone, water damaged battery and wall charger.
should I cut the end off the charger and do the wires to the battery and insert battery into phone and plug usb cord from laptop to the phone?
isn't this the correct way for bsod and a non water damaged battery?
is there anyway to test the waterdamaged battery to see if it could still be good?
I have a multimeter

[Q] Battery defect or just a bug?

Hey Guys,
I have been searching for hours now and cannot find anyone having the same or similar issues with the One as me
and I am really becoming desperate..
So, the problem is that I cannot charge the phone anymore, whenever I try to do so the battery symbol becomes grey with an exclamation mark.
I have no clue what the reasons for this are and why it occurs, also this is the second time now that this happens to me.
I have already sent it to the repair service 3 days after I bought the phone, this time it lasted around 3 weeks until it happened again.
So far I am loving the phone and its features, but this problem is driving me mad, any help would be appreciated!
Edit: it ran out of battery and now I can neither turn it on nor is it charging

Lazngann said:
Hey Guys,
I have been searching for hours now and cannot find anyone having the same or similar issues with the One as me
and I am really becoming desperate..
So, the problem is that I cannot charge the phone anymore, whenever I try to do so the battery symbol becomes grey with an exclamation mark.
I have no clue what the reasons for this are and why it occurs, also this is the second time now that this happens to me.
I have already sent it to the repair service 3 days after I bought the phone, this time it lasted around 3 weeks until it happened again.
So far I am loving the phone and its features, but this problem is driving me mad, any help would be appreciated!
Edit: it ran out of battery and now I can neither turn it on nor is it charging
Click to expand...
Click to collapse
Have you been using the provided charger? Sounds like they didn't change out the battery you got a bad one. I have never seen android do that unless the battery or something is really broken.

nullkill said:
Have you been using the provided charger? Sounds like they didn't change out the battery you got a bad one. I have never seen android do that unless the battery or something is really broken.
Click to expand...
Click to collapse
Yes, I used the charger provided which is working just fine with my previous One X and I also tried to use the charger of the One X without success though..

Lazngann said:
Yes, I used the charger provided which is working just fine with my previous One X and I also tried to use the charger of the One X without success though..
Click to expand...
Click to collapse
Yeah it's bad. Too weird. You are not alone a couple other people are having this issue just this morning. Like four or so ONES decided they would all just say goodbye at the same time. It's odd as I have not seen any other problems like this until this morning.
Guessing this is a DEV edition or you can't go to a carrier and have to go through HTC? If so make sure to tell them this device has already been in before for the same problem and at this point you want a new device not this defective one.

nullkill said:
Yeah it's bad. Too weird. You are not alone a couple other people are having this issue just this morning. Like four or so ONES decided they would all just say goodbye at the same time. It's odd as I have not seen any other problems like this until this morning.
Guessing this is a DEV edition or you can't go to a carrier and have to go through HTC? If so make sure to tell them this device has already been in before for the same problem and at this point you want a new device not this defective one.
Click to expand...
Click to collapse
I will do so as soon as I get back to Germany where i purchased it, as I'm still in London for studies until the end of may :crying:

The charging time is ver bad. I had the same thoughts at first. I changed the calbe and the charger... In Elixier2 i don`t have more than 500-700 mA... I charge the Phone overnight. But my Battery lasts more than two days

[Q] [EMERGENCY] Sitting Brick - CM 10.1

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

Dead Fire....

My little Fire's been working great for a couple of weeks with CM installed then today it just refuses to switch on.... I've tried charging it but there is just no signs of life not even a dead battery indication, no Amazon logo or anything...
I'll take it back for a replacement tomorrow, still only 3 weeks old, hoping the replacement is still on 5.0.1
Anyone else has any similar problems?

Did you just return it?
Can you go to recovery?

FredBloggs13 said:
My little Fire's been working great for a couple of weeks with CM installed then today it just refuses to switch on.... I've tried charging it but there is just no signs of life not even a dead battery indication, no Amazon logo or anything...
I'll take it back for a replacement tomorrow, still only 3 weeks old, hoping the replacement is still on 5.0.1
Anyone else has any similar problems?
Click to expand...
Click to collapse
my replacement came with 5.0.1. saved me from the locked 5.1.1 i was on.

Welcome to the dead Fire club. CM12-1 is something you want to try - I moved my wipe to the front of flashfire, like was suggested. It wiped & then never finished the load. Probably some quirk in ff that doesn't like CM12-1 so much - who knows. Waste of $50, so I'll order another one after I try the support folks.