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

Dead Nexus 7

I got my son a 32GB nexus 7 for Christmas but it didn't turn out very well. Right out of the box it wouldn't turn on. No big deal I thought, i'll just plug in the charger and let it charge for a while. 2 hours later I try to power it up again. No luck. nothing happening at all. So now its 1:30 AM on christmas morning and i'm still messing with this thing. Hold power for 30 seconds, nothing. Hold power and Volume + to get into recovery, nothing. So back on the charger it goes. 7am. Still dead, nothing happening. Back on the charger. Kid's not happy that his new tech toy isn't working. So around 10 AM I'm standing there talking to my wife while holding the power button down for what seemed like 2 minutes and I look down and see the Nexus "X".... Holy cow, its alive. So we let it start up and dive right into setup. It rebooted 2 times while trying to setup. Third time we make it all the way through and get started downloading some apps. All updates applied up to 4.2 and I thought we were in the clear. So off my kid goes playing angry birds and Navy fighter happy as can be.... Yep, crashed again and was not able to power it back up again. So its in the box headed back to buydig.com I guess this one was a real lemon.
Did some looking around and couldn't find much that relates to my problem. It seems it was just my turn to get the lemon.

combattalon2 said:
I got my son a 32GB nexus 7 for Christmas but it didn't turn out very well. Right out of the box it wouldn't turn on. No big deal I thought, i'll just plug in the charger and let it charge for a while. 2 hours later I try to power it up again. No luck. nothing happening at all. So now its 1:30 AM on christmas morning and i'm still messing with this thing. Hold power for 30 seconds, nothing. Hold power and Volume + to get into recovery, nothing. So back on the charger it goes. 7am. Still dead, nothing happening. Back on the charger. Kid's not happy that his new tech toy isn't working. So around 10 AM I'm standing there talking to my wife while holding the power button down for what seemed like 2 minutes and I look down and see the Nexus "X".... Holy cow, its alive. So we let it start up and dive right into setup. It rebooted 2 times while trying to setup. Third time we make it all the way through and get started downloading some apps. All updates applied up to 4.2 and I thought we were in the clear. So off my kid goes playing angry birds and Navy fighter happy as can be.... Yep, crashed again and was not able to power it back up again. So its in the box headed back to buydig.com I guess this one was a real lemon.
Did some looking around and couldn't find much that relates to my problem. It seems it was just my turn to get the lemon.
Click to expand...
Click to collapse
I got mine from Buydig as well and have had no problems with it at all...

I feel bad for your son. That really sucks... Pretty awesome dad to get him the big 7 and not the cheaper one lol
Sent from my Nexus 7 using Tapatalk HD

You could take the back cover off and see if the battery connector is connected properly.
Sent from my Nexus 7 using xda premium

Gizmoe said:
You could take the back cover off and see if the battery connector is connected properly.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How is this accomplished without damage so I can send it back with no issues?
Edit- Nevermind, found the iFixit video.

combattalon2 said:
How is this accomplished without damage so I can send it back with no issues?
Edit- Nevermind, found the iFixit video.
Click to expand...
Click to collapse
If you have to call support to send it back, DO NOT tell them you opened it to check the batt connector as they insist this will void your warranty. Just a heads-up.

just do not tell them you did anything to it. they should give you a rull replacement
i also got a nexus 7 from parents for christmas and am loving it, hopefully he understands it is just a mistake and this is still a high quality product

I had multiple Nexus 7's and so far not one has had any issues.
Sent from my iPhone using Tapatalk

Status?
Sent from my Nexus 7 using xda app-developers app

zPacKRat said:
Status?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes
Sent from my PantechP9070 using xda premium

Original returned to buy dig.com. got a 32gb from staples and all is well. Never opened the case on the first N7 so I can't tell you what was wrong. After playing with the new one though, the original had screen issues. No charge animation when plugged in.

Screen broken?

A co-worker of mine gave me a touchpad he couldn't fix. He bought it for $50 because the seller said it was bricked.
The original owner said he replaced the battery so I am thinking that it is a hardware problem. Maybe he broke a connection or something?
CM9 was installed.
Here are the symptoms:
-When you turn it on you can see that the backlight is on even though it is a dark screen.
-You can only turn off the backlight by holding down the Power and the Home button.
-Every once in a while you get a vertical column of multi-color static off center to the right.
-Holding down the Power and Volume Up buttons doesn't have any effect
I took the TP completely apart, double checked all the connections when I put it back together.
If it is a software problem how do I unbrick it?
If it is a hardware problem which part needs replacing?

Does a computer sheet it at all? I would probably try the webos doctor program, but I'm just guessing.
Sent from my One X using xda app-developers app

lauterm said:
Does a computer sheet it at all? I would probably try the webos doctor program, but I'm just guessing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Webos doctor doesn't see it. Windows tries to install a driver but it fails.

Ok, I got webos doctor to see it but after 8% of it's process it gives me the message "We were unable to reset your device"
Anyone ever see anything like this?

My guess is that the LCD needs replaced. I've never seen a bricked tp that had anything on the screen. Could be the LCD socket isn't connected all the way.
Sent from my skz_tenderloin using Tapatalk HD

mixalot2008 said:
My guess is that the LCD needs replaced. I've never seen a bricked tp that had anything on the screen. Could be the LCD socket isn't connected all the way.
Sent from my skz_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
I thought that might have been the problem too. That is why I took it apart. I checked all the connections by taking them out and putting them in a securely as I could.
I'm thinking that the person who took the screen off the first time pulled the connector the wrong way and screwed up something.

Yeah that's pretty easy to do lol. I screwed up my digitizer control board and I've been working on em for a while.
Sent from my skz_tenderloin using Tapatalk HD

mixalot2008 said:
Yeah that's pretty easy to do lol. I screwed up my digitizer control board and I've been working on em for a while.
Sent from my skz_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Do you think that might explain why the back light turns on when it charges? I cannot get the back light to turn off. When I hold down the power and home button it turns off then comes right back a little later.

jimvsmij said:
Do you think that might explain why the back light turns on when it charges? I cannot get the back light to turn off. When I hold down the power and home button it turns off then comes right back a little later.
Click to expand...
Click to collapse
I helped replace a co workers iPod touch screen that was shattered & had to do it twice. The first screen we replaced we screwed up the ribbon connector and the screen looked very similar to yours. I bet all you have to replace is the LCD too. Good luck!

[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.