Database Develop

Bricked?

This morning i woke up, and my touchpad wont boot. It was on the charger all night.
The most i can get is 1 of 2 states
1.) Battery icon with a question mark
2.) Home/Center button has an alternating light going left and right
Ive tried Power + Home, and thats how i get between the two states, though its sorta random which one i end up in.
I cant get to USB/Download mode(Power vol up)
Is there anything else I can try?

I know you said you can't get into USB/Download but I'm not sure which method you've tried. Are you trying to hit vol up just after powering the device on? I've had better luck with turning it off completely, holding vol up, then connecting the USB cable from the computer.
Also, there seem to be several threads in the Q&A section with the same or similar problem. Have you read through those and tried any of those methods?

jbradt said:
I know you said you can't get into USB/Download but I'm not sure which method you've tried. Are you trying to hit vol up just after powering the device on? I've had better luck with turning it off completely, holding vol up, then connecting the USB cable from the computer.
Also, there seem to be several threads in the Q&A section with the same or similar problem. Have you read through those and tried any of those methods?
Click to expand...
Click to collapse
I have tried that. Ive googled as much as i can and i cant find what the "alternating left and right lights on the home button" mean. Turns out our home button is 2 LED's.
I havent found a success story related to the battery Icon question mark.
Heres a pic:
https://www.dropbox.com/s/5f0zqdfa6jqj834/2012-06-10 19.21.01.jpg

Rekzer said:
This morning i woke up, and my touchpad wont boot. It was on the charger all night.
The most i can get is 1 of 2 states
1.) Battery icon with a question mark
2.) Home/Center button has an alternating light going left and right
Ive tried Power + Home, and thats how i get between the two states, though its sorta random which one i end up in.
I cant get to USB/Download mode(Power vol up)
Is there anything else I can try?
Click to expand...
Click to collapse
Does your pc see the tp if you connect it? If the home/center button is flashing it means you have power, so all is not lost (yet, at least). Did you have it charging on the wall charger or the touchstone. If the touchstone, try leaving it charging on the wall charger overnight. I hope this helps.

Rekzer said:
This morning i woke up, and my touchpad wont boot. It was on the charger all night.
The most i can get is 1 of 2 states
1.) Battery icon with a question mark
2.) Home/Center button has an alternating light going left and right
Ive tried Power + Home, and thats how i get between the two states, though its sorta random which one i end up in.
I cant get to USB/Download mode(Power vol up)
Is there anything else I can try?
Click to expand...
Click to collapse
Sadly, you have to replace the battery :/.
Sent from my Galaxy Nexus using Tapatalk 2

I contacted HP and theyre sending me a box to ship it back in. Seems like they have great service!
Hopefully they dont notice CM on it lol

Rekzer said:
I contacted HP and theyre sending me a box to ship it back in. Seems like they have great service!
Hopefully they dont notice CM on it lol
Click to expand...
Click to collapse
Mother of god... good luck with them. They're customer service is the worst I've ever dealt with. They've held some of my devices for ransom. True story.
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Mother of god... good luck with them. They're customer service is the worst I've ever dealt with. They've held some of my devices for ransom. True story.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How could they hold it ransom!?!?! its your device!

Rekzer said:
How could they hold it ransom!?!?! its your device!
Click to expand...
Click to collapse
Sent device in for repairs, they repair it and say it's customer damage (no matter what, haha) and refuse to send it back without like a $600 payment.
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Sent device in for repairs, they repair it and say it's customer damage (no matter what, haha) and refuse to send it back without like a $600 payment.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea, my fear is that since i couldnt power it on, i couldnt remove CM
Its gonna be pretty obvious once its fixed thats it there lol. If they try that **** with me, I wont be paying htem anything, i considered the TP dead, the warranty is a last resort.
What was wrong with your TP?

Rekzer said:
Yea, my fear is that since i couldnt power it on, i couldnt remove CM
Its gonna be pretty obvious once its fixed thats it there lol. If they try that **** with me, I wont be paying htem anything, i considered the TP dead, the warranty is a last resort.
What was wrong with your TP?
Click to expand...
Click to collapse
Nothing until like ten minutes ago, haha. It's not powering on... it does this sometimes. Good thing I have another tablet.
Sent from my Galaxy Nexus using Tapatalk 2

Warning Nexus 7 Owners.. JellyBean 4.2 Update Can Brick Your Device.

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

[Q] HTC One, won't turn on..

To preface this, the phone is completely stock and unlocked. I've been using the phone now for about 3 weeks with absolutely zero problems. I plug it in to charge over night, wake up the next morning and it's completely unresponsive.
Won't turn on.
No LED notification light (Green or Amber)
Isn't recognised by my laptop as a disc drive either.
Any ideas, tips or suggestions as to how I can get it working again, short of calling the supplier and getting a replacement?
Thank guys.

With adb or fastboot you pc will recognize your phone?

Guich said:
With adb or fastboot you pc will recognize your phone?
Click to expand...
Click to collapse
It might do but I have no idea how to do it.

Mine just did the same thing today, it discharged very quickly this morning and now it won't even charge at all. Not sure what to do....

My god. This has also happened to me. A few others have also had this problem. Contact HTC and file for a repair/replacement. I did today. Seriously sucks because its a solid phone otherwise.

hansmrtn said:
My god. This has also happened to me. A few others have also had this problem. Contact HTC and file for a repair/replacement. I did today. Seriously sucks because its a solid phone otherwise.
Click to expand...
Click to collapse
This is a worrying trend.. So there are no other alternatives just request a repair/replacement?

It really is. I've already contacted my brother, whom is pretty high up in att, about the matter. I'd consider myself a veteran of android and I have had no progress on the fix, it seems only to be hardware. In layman terms, yes you'll have to get it replaced.
Sent from my LG-E980 using xda app-developers app

hansmrtn said:
My god. This has also happened to me. A few others have also had this problem. Contact HTC and file for a repair/replacement. I did today. Seriously sucks because its a solid phone otherwise.
Click to expand...
Click to collapse
How long would the repair take? And would they send you a replacement first, because now I have no phone.....
Sent from my Nexus 10 using Tapatalk HD

I'd say about 2 weeks at most. But no, they'll repair or replace the phone depending on the issue. Likely replace.
Sent from my LG-E980 using xda app-developers app

hansmrtn said:
I'd say about 2 weeks at most. But no, they'll repair or replace the phone depending on the issue. Likely replace.
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
I have the T-Mobile version would I be able to go into a store and request a replacement ?
Only asking because I have never had an issue like this with any of my phones.
Sent from my Nexus 10 using Tapatalk HD

drop ship
When speaking to the HTC rep., try tossing around the phrase "can you drop ship a replacement phone?" Ask for a manager if its existence is denied. Once you find someone with enough power to "drop ship" the replacement phone, they'll take your credit card, then immediately send you the replacement phone and a box to ship back the defective phone. If you don't return the bad device, they'll charge your card.

happened to me twice - try holding power button for like 1min - it should turn on then

I opened a thread about this problem, but seems only some people have this defect.

I've had this problem too, it's currently with HTC (UK) to repair or replace. It arrived on Tuesday, still awaiting to hear back.

If I hold down the power button it turns on....it happens when u charge and turn it on while stll plugged into the charger...happened to all 3 of my ones..this is a software thing nothing wrong with phone imo just don't turn phone on after full charge while plugged in
Sent from my HTC EVO 3D X515m using xda app-developers app

gemini002 said:
If I hold down the power button it turns on....it happens when u charge and turn it on while stll plugged into the charger...happened to all 3 of my ones..this is a software thing nothing wrong with phone imo just don't turn phone on after full charge while plugged in
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
It seems that my phone isn't dead after all. Holding the power button down does seem to work... It's a strange bug..

I don't get why people turn the phone OFF in the first place? I never turn my phone OFF at all. I sometimes restart the phone but that is it.

[Q] Phone Died, weird happenings, time to be aware?

I plugged my phone in before I went to bed, it had 57% left and I need a full charge for work each day. I woke up 45 minutes late due to my alarm not going off, I immediately grabbed my phone and pressed the power button a few times and the screen would not turn on. It was then I noticed the led was not orange or green or whatever it is when its full charged. I grabbed my girlfriends charger for her S3 and plugged it in to see if it was the cord, no luck there so I took it to work and tried a few outlets there to no avail. The phone is dead, or sleeping really ****ing hard. I called sprint who gave my the number to asurion so I could file a claim, they charged me $150 for a new phone to be shipped out and they want my old one. Which seems kinda crazy considering I bought this phone full retail on pre order for my birthday. I've also tried booting to the boot loader, through the button system and adb on my pc. Anyone have any clues as to what happened? did my phone seriously take a crap a little over a month of owning it, I'm also another $150 in the hole on it and I'm just crossing my fingers it does not happen again, can't afford this. But if anyone has any insight, suggestions, or experiences please share, thanks.

I saw this it's worth a shot
http://forum.xda-developers.com/showpost.php?p=41782209&postcount=9

This should be a warranty claim and not an insurance claim!
Sent from my HTCONE using xda premium

gutrrob said:
This should be a warranty claim and not an insurance claim!
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
+1 This isn't an insurance claim. This falls under warranty and wouldn't be subject to a deductible. You should take it by a store and get it replaced.
Sent from my HTCONE using Tapatalk 4 Beta

You could also try the put it under a bright light while you're booting it trick
Sent from my HTC One running ViperROM v1.1.0

bigdaddy619 said:
I saw this it's worth a shot
http://forum.xda-developers.com/showpost.php?p=41782209&postcount=9
Click to expand...
Click to collapse
Not sure how this works...
Anybody have any EDIT: hypotheses?

HTC One Water damage

Why on earth did this moderator '' ghost '' think my thread about my phone falling down the toilet and me asking for assistance was '' off topic '' and was subsequently closed, seriously mate your well out of order closing that thread it's as relevant as any thread, I only hope something like this nightmare never happens to you!!!
Anyway again I'll start what is a very relevant thread, long story I dropped my One in the toilet managed to scoop it out straight away and it continued to work, woke the following morning and phone was dead but after charging it booted up but wouldn't recognise my SIM card so tried another SIM and won't accept that either.
Came home to find the phone dead it was on 78% battery last night after charging it, screen is washed out too as you'd imagine , so charged it and it has rebooted several times since but booted up eventually, but will not recognise any SIM I put in.
I recall reading a thread on here before saying if you put the phone in a bag of rice that sometimes works so will be doing that I do have insurance but if at all possible I'm hoping to rescue this phone.
I'm asking for any assistance from anyone who was unfortunate enough to be in the same situation.
DO NOT LOCK THIS THREAD it's as relevant as anything posted on here.
Thank you.
Sent from my Nexus 7 using Tapatalk

Hello, I have htc one which doesn't recognize sim cards, but not because of water damage:laugh:
To fix/change it, you should disassemble almost everything - it's under screen.
here is more info

Thanks mate but I'm no good when it comes to this type of thing, software I'm OK with but not the hardware side of things.
Sent from my Nexus 7 using Tapatalk

jonny68 said:
Thanks mate but I'm no good when it comes to this type of thing, software I'm OK with but not the hardware side of things.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Me too. I'm afraid of teardown.
What will you do?

I've no idea mate, the phone now bizarrely won't turn off, I've left it in a bag of rice so will check tomorrow night and see if that done any good.
I put in a claim on my insurance as and its been accepted but have to pay an outrageous €95 excess which I could really do without, using my Moto G as a spare but badly miss my One.
If anyone has any suggestions feel free to post.
Sent from my Nexus 7 using Tapatalk

jonny68 said:
I've no idea mate, the phone now bizarrely won't turn off, I've left it in a bag of rice so will check tomorrow night and see if that done any good.
I put in a claim on my insurance as and its been accepted but have to pay an outrageous €95 excess which I could really do without, using my Moto G as a spare but badly miss my One.
If anyone has any suggestions feel free to post.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
to be completely honest if your phone was usable when you scooped it out of the toilet, you should have IMMEDIATELY turned it off. and stuck it in a bag of rice for like a week. the reason your phone went all wonky after is probably because there was some left over water inside the phone and as you were using it, it probably moved around and shorted something.

I was in the pub at the time and very drunk.
It's not looking good at all though, Left in a bag of rice overnight and now the power button won't work, have to keep plugging in USB cable to wake the phone while I bluetooth my photos and videos,etc to my Moto G.
Gonnab just wipe the phone completely after I've taken all I need to take off it and give it to the courier who will deliver my new HTC One after I pay the excess next week (they said I have to return this phone, no idea what they'll do with it)
So thanks anyway but I'm just gonna sell the new one sealed and unlocked and use my Moto G until new HTC M8 is released.
Sent from my Nexus 7 using Tapatalk