Related
So I have a US Transformer, did the 4/23 OTA update a couple days ago. Everything works fine. Haven't even rooted yet because I was holding off for a little bit. Then today I was switching wallpapers, it rebooted, now it gets to the lockscreen and wont register finger touches So it's just stuck on the lockscreen. Haha. Currently searching the forums if anyone else has had this problem, but just wanted to rant.
Going through stock recovery, currently wiping data, hopefully it will restore to usable state **Crosses fingers**
I find it odd that you used so many smiles on such a horrible situation.
It's doubt it's bricked. Use the force power off method (10-12sec power button hold). Then wait 30 secs, restart (5-6 power button hold), then disable the lockscreen if it boots. Repeat this a few times, if still no joy RMA it.
doronster195 said:
I find it odd that you used so many smiles on such a horrible situation.
Click to expand...
Click to collapse
Eh it sucks yes, but I'm being hopeful something I try will work to fix it instead of sending it back to ASUS / returning it, and waiting 50 million years for a replacement.
stuntdouble said:
It's doubt it's bricked. Use the force power off method (10-12sec power button hold). Then wait 30 secs, restart (5-6 power button hold), then disable the lockscreen if it boots. Repeat this a few times, if still no joy RMA it.
Click to expand...
Click to collapse
How can I disable the lockscreen? It boots straight up to the lockscreen and it wont register any finger touches to unlock. Then if I press the power button, black screen and I have to force power off. I tried the stock restore method, vol down + power, press power up when prompted, then power up again, but it just ends with the android and (!) symbol, then reboots and begin cycle again, I tried it again just to make sure.
Haha. I think I'm going to ADB in, put in CWM and pray I can flash a ROM over that way. Was waiting to root, but I guess I might as well jump the gun now.
Have you tried attaching a mouse? Maybe the touchscreen is not working but with mouse you will be able to unlock the screen?
Magnesus said:
Have you tried attaching a mouse? Maybe the touchscreen is not working but with mouse you will be able to unlock the screen?
Click to expand...
Click to collapse
how do you attach a mouse without the keyboard dock? female/female usb adapter?
worminater said:
how do you attach a mouse without the keyboard dock? female/female usb adapter?
Click to expand...
Click to collapse
indeed
10char
Magnesus said:
Have you tried attaching a mouse? Maybe the touchscreen is not working but with mouse you will be able to unlock the screen?
Click to expand...
Click to collapse
Thanks for the tip, but I don't have the proper cables
But I had enabled USB debugging a while ago, so I think I'm going to try get this rooted, CWM flashed, and then I can flash a ROM on top and hopefully that will clear it up.
neilkarunatilaka said:
How can I disable the lockscreen? It boots straight up to the lockscreen and it wont register any finger touches to unlock.
Click to expand...
Click to collapse
You're right you cant then. That's not bricked, it's just faulty. Looks like the digitiser is kaputsky. Probably something as simple as a loose wire inside but in order to check you would have to open it up and that would invalidate your warranty of course. Bad luck man, that's defintely an RMA job.
Do you guys over in the US have different consumer laws to us in the UK, all this talk of RMA on a brand new product is slightly baffling.
Assuming you bought it over the counter from somewhere like Best Buy, why can you not just walk into the shop with it, put it down on the counter with your receipt and (politely) say, this is brand new, its knackered, please give me another one out of your stock room.
Even if it was mail order, return it and demand a replacement by return of post, or a refund. If they won't replace straight away get a refund, and then walk into Best Buy and get one.
Surely there is no need to be hanging around waiting for Asus to fix a product that is only a week old.
I will be picking up Transformer number three from Comet tomorrow, what they do with the faulty one is their business.
And I will continue to take them back until I get a good one.
Sent from my Transformer using Tappy Fingers
markteacher said:
Do you guys over in the US have different consumer laws to us in the UK, all this talk of RMA on a brand new product is slightly baffling.
Assuming you bought it over the counter from somewhere like Best Buy, why can you not just walk into the shop with it, put it down on the counter with your receipt and (politely) say, this is brand new, its knackered, please give me another one out of your stock room.
Even if it was mail order, return it and demand a replacement by return of post, or a refund. If they won't replace straight away get a refund, and then walk into Best Buy and get one.
Surely there is no need to be hanging around waiting for Asus to fix a product that is only a week old.
I will be picking up Transformer number three from Comet tomorrow, what they do with the faulty one is their business.
And I will continue to take them back until I get a good one.
Sent from my Transformer using Tappy Fingers
Click to expand...
Click to collapse
Most brick and mortar's do not have and have not had units, so taking them back isnt an option if you want a replacement. Since most people bought online, an rma to the etailer is the only option.
Update : Fixed
well, i rooted, flashed cwm, then flashed prime 1.2 on top of stock, and now it looks like everything works? no idea what the hell happened but now it registers my fingers lol. i guess mods can lock/delete this thread?
markteacher said:
Assuming you bought it over the counter from somewhere like Best Buy, why can you not just walk into the shop with it, put it down on the counter with your receipt and (politely) say, this is brand new, its knackered, please give me another one out of your stock room.
Click to expand...
Click to collapse
There are very few in stock, you can't just walk into most places and pick one up. The only option is to RMA back to Asus and wait some undetermined amount of time for a replacement.
Hi folks,
I suspect I'm having what some people around here appear to refer to as a Hboot problem. But this is my first Android phone, and I couldn't know any less about RUUs or booting or roms or anything like that. I'm posting a new thread because it seems like anyone who had a problem like mine had tried to, or wanted to know how to root their device. I didn't do that and am not trying to, but I've still got these problems.
I bought the phone "new", and it came in just today, from eBay, supposedly in a sealed box. Maybe that's part of the problem, I'm not sure. All I've done is: turn it on, install some apps, get in over my head with Apex launcher, and try to update Android.
I chose update from the menu, left my phone plugged in, and when I came back to it, nothing was on the screen. I pressed power, and it showed a screen similar to the first image (black screen, phone icon, green arrows in a circle). I assumed it was installing. I let it be and came back to the white screen with the numbers and barcodes. I panicked and chose "recovery" from the menu, and after a reboot it seemed to be back to normal.
However, just now, as I was attempting to reboot the phone due to not having any volume, I again got the white screen followed by the green arrows and finally the red warning icon.
Somehow or another, the phone resets itself and comes back on, but where is this coming from? Did I do something wrong? What does the screen mean, and did I get hosed by my seller? Thanks all
zbo-50 said:
Hi folks,
I suspect I'm having what some people around here appear to refer to as a Hboot problem. But this is my first Android phone, and I couldn't know any less about RUUs or booting or roms or anything like that. I'm posting a new thread because it seems like anyone who had a problem like mine had tried to, or wanted to know how to root their device. I didn't do that and am not trying to, but I've still got these problems.
I bought the phone "new", and it came in just today, from eBay, supposedly in a sealed box. Maybe that's part of the problem, I'm not sure. All I've done is: turn it on, install some apps, get in over my head with Apex launcher, and try to update Android.
I chose update from the menu, left my phone plugged in, and when I came back to it, nothing was on the screen. I pressed power, and it showed a screen similar to the first image (black screen, phone icon, green arrows in a circle). I assumed it was installing. I let it be and came back to the white screen with the numbers and barcodes. I panicked and chose "recovery" from the menu, and after a reboot it seemed to be back to normal.
However, just now, as I was attempting to reboot the phone due to not having any volume, I again got the white screen followed by the green arrows and finally the red warning icon.
Somehow or another, the phone resets itself and comes back on, but where is this coming from? Did I do something wrong? What does the screen mean, and did I get hosed by my seller? Thanks all
Click to expand...
Click to collapse
to get to the bootloader menu (the white one with the pink writing), you have to reboot and allow it to boot with the volume down button held. It looks like your volume rocker is getting stuck on down - given that you are losing volume and it keeps booting into the bootloader menu. If it is in a case, try removing it from the case and see if the issue persists.Otherwise, it is likely a hardware issue. so you should return it for a warranty repair/replacement (as you said you bought it new in a box).
codeprimate said:
to get to the bootloader menu (the white one with the pink writing), you have to reboot and allow it to boot with the volume down button held. It looks like your volume rocker is getting stuck on down - given that you are losing volume and it keeps booting into the bootloader menu. If it is in a case, try removing it from the case and see if the issue persists.Otherwise, it is likely a hardware issue. so you should return it for a warranty repair/replacement (as you said you bought it new in a box).
Click to expand...
Click to collapse
You coulsnt be more wrong I'm [email protected] op ill get you back up and running in a sec
tactical kitten said:
You coulsnt be more wrong I'm [email protected] op ill get you back up and running in a sec
Click to expand...
Click to collapse
lol!
tactical kitten said:
You coulsnt be more wrong I'm [email protected] op ill get you back up and running in a sec
Click to expand...
Click to collapse
Kitten - what do you think is the problem? The OP says they lost volume and they keep rebooting into the bootloader. The stuck volume rocker sounds like the easiest way to explain both issues. I might be wrong, but not given the symptoms listed in the OP. If more information is required to diagnose the issue, we can at least start by eliminating the obvious.
codeprimate said:
Kitten - what do you think is the problem? The OP says they lost volume and they keep rebooting into the bootloader. The stuck volume rocker sounds like the easiest way to explain both issues. I might be wrong, but not given the symptoms listed in the OP. If more information is required to diagnose the issue, we can at least start by eliminating the obvious.
Click to expand...
Click to collapse
Thank you very, very much - I believe that's exactly the issue. I had no idea pressing the volume down button during a reboot would get you to that menu, but I am using the Trident Kraken case which apparently has an issue lining up with the volume down rocker on this particular phone.
I will try to reproduce the problem sans case to make sure, but this sounds absolutely right. Thanks for helping a complete newbie - I don't think I'd ever have put that together. I was very worried I'd been sold a bill of goods.
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
wushdishmeen said:
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
Click to expand...
Click to collapse
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
buhohitr said:
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
Click to expand...
Click to collapse
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
wushdishmeen said:
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
Click to expand...
Click to collapse
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
buhohitr said:
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
Click to expand...
Click to collapse
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
wushdishmeen said:
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
Click to expand...
Click to collapse
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
ASUS Infinity Won't Boot Into Recovery BRICK ($50 IF YOU CAN HELP FIX IT)
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Yea I am seriously baffled by this. ASUS just lost another customer. I was doing the reset so I could sell the device and put the money towards something else. It figures this happens...It's almost like the ASUS gods are trying to screw me over so I am stuck with their crap device. This is shady business considering all my other android devices are so easily recoverable and they don't even offer a tool to unlock the bootloader. You have to do it via a third party method and somehow even that is recoverable easily. You don't find it strange that ASUS offers the tool themselves and it's the only tablet that is unbrickable?
Again... $50 to the first person who can help me unbrick this thing. I will send it via PayPal for sure. The money is not the issue it's the principle of giving ASUS $200 more of my money when I know for a fact they programmed this thing to brick so they could pick my pockets. I'm getting really angry just thinking about it and I am close to smashing this thing with a hammer and filming it for YouTube.
Here is the exact chain of events.
1) I went into Android settings, backup/restore, and then choose Factory Reset. It restarted the tablet and just froze on the ASUS screen where it says "the device is unlocked" in the top left corner.
2) I waited 15 minutes and nothing happened. So I was forced to hard reset. After resetting the same crap happened and it just stayed on the ASUS logo screen.
3) I tried booting it with Power + Vol Down and got the recovery options. (i seriously wish I stopped here and checked the forum because I could of possibly fixed it). Figuring it would help, I went over to the WIPE DATA option in the recovery menu.
4) It said "wiping data.." and then said it was initializing bootloader or something and it just froze at that point.
5) Waited another 15 minutes and nothing happened. At this point I wasn't worried because every other device I have I would have ODIN as the last resort and it ALWAYS works.
6) Reboot the device again and that's where I'm at now. It stays on the ASUS boot screen and goes nowhere. I've tried getting back into recovery with Power + Vol Down but the options never appear again. Just goes to the normal boot screen no matter what I do and hangs there. It's clearly setup to brick itself which is incredibly ridiculous.
Do you think a method to fix it will come out eventually or is it impossible to unbrick this thing? Would replacing the motherboard from another tablet that was never unlocked fix the issue? I see the motherboard for this tablet selling for $175 and the iFixit teardown shows how to take it apart. It doesn't look too difficult.
I just cannot believe that an hour ago I had a $500 tablet and now the thing is worthless unless I want to shell out another $200. I seriously wish I didn't buy this thing. Maybe I can take it apart and sell the parts separately as is and hope to salvage my money back.
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Also I did have CWM because I remember going through a tutorial and it being different than all my other devices. I had the RCK icon as the first option when I booted with Power + Vol Down.
The options were an RCK icon, a USB icon, something else I don't remember, and then Wipe Data/reset icon. I chose the wipe data icon and that's when my device was bricked. But FIRST I used the factory reset in the android settings under Backup/restore and it froze during that which is what caused me to try the factory wipe in the recovery options.
Would not having CWM improve my options to unbrick it? Or is having CWM a good thing?
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
sbdags said:
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
Click to expand...
Click to collapse
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
wushdishmeen said:
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
Click to expand...
Click to collapse
Unfortunately it's not Asus, unlocking or the bootloader that is the problem - it's the older incompatible version of CWM that has caused the issue. It didn't understand what you asked it to do as it is not compatible with Jelly Bean. You need to get this part clear. Many people wipe successfully from Android or the bootloader from ICS and JB regularly. Asus don't write code into their bootloader to deliberately brick your device when wiped. They also don't support custom recoveries that are not compatible with their bootloaders.
It is a documented issue that has caused others like yourself to brick your device when wiping JB when still essentially on an ICS recovery. Unfortunately there is no way you would know this without some research and Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Re: ASUS Infinity won't boot into recovery or startup ($50 to person who helps fix it
sbdags said:
Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Click to expand...
Click to collapse
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
sbdags said:
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
Click to expand...
Click to collapse
They don't support an unlocked device anyway. It would be as easy as returning the SBK from the server together with the unlock token.
As I said I understand the idea of the warranty being voided by using the unlock tool. But ASUS certainly has programmed the device to brick when using custom recoveries which is something you just said yourself. They are being irresponsible by offering this tool and not telling customers that a custom recovery would brick the device for good. You honestly think they don't know this will happen?
My Galaxy S3 has an unlocked bootloader (through a third party method nonetheless), is rooted, has CWM recovery, is on Jellybean, and the recovery options never disappear with a factory wipe. So clearly it's possible. Even if the device won't boot into android it will still be recognized by Odin because it has download mode built in as a start up option. Holding power + vol up will allow me to enter download mode and I can flash the stock ROM again.
Unlike APX mode I don't need some encrypted nvflash backup just to recover my device. I can simply use the stock ROM to recover my device back to stock no matter what ROM or recovery I'm running. I maybe gave you the impression that I didn't know what I was doing. This issue is something that anyone could fall into and frankly ASUS should be telling people not to use factory wipe if they install a custom recovery. Why would they offer a bootloader unlock for any other reason than to cater to people who want to install custom recoveries and flash ROMs? There's no other use for it to a typical consumer.
The ASUS Infinity loses it's ability to communicate with your computer when this happens. That's the problem here. They need to either need to make it impossible to flash a custom recovery altogether or put a warning on their website near the download that says "Custom recoveries could brick your device when doing a factory wipe". Seeing as it's a well documented issue like you claim.
We are all entitled to our opinion. I'm not buying ASUS products anymore. It's not like I did something wrong and screwed it up. I did something that's possible on every other modern android device and was kicked in the nuts for it.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners? So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware, whether directly or indirectly related to it. Whether we as consumers have the tools available to recover from the software issue is not the point. Nor am I saying that ASUS should fix it for free, since they clearly state that using the tool will void your warranty. My point is that ASUS should certainly have the ability to simply reprogram our motherboards for a reasonable fee, rather than forcing a motherboard replacement and charging 50% of the tablet's price to fix it.
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted. It just doesn't happen and Windows certainly also has it's share of bootloader errors. There is always a way to recover from software issues and salvage the hardware, unless it's some incredibly rare series of failures that lead to an electrical problem that fries the hardware. Which is certainly not the case here or anything remotely close to it.
MOD EDIT: DELETED
What I said was they should not be charging $200 for a replacement motherboard for a software related issue. They should be charging a reasonable fee to reprogram the existing component. From what I hear they also permanently lock the boot loader on the replacement motherboard. This is not helpful at all considering you lose the ability to customize your device now that you've learned what not to do.
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device. Not to mention the only purpose of unlocking the boot loader is so you can flash custom recoveries. So it's not like they have to run through a long list of possible problems like your over exaggeration implies.
Anyway... I managed to disassemble the tablet without breaking anything.
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer? Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
I'm assuming not obviously but I might as well ask. I guess my choices are to either spend $160 on a new motherboard and swap it out and sell it, or further disassemble and sell the parts. If anyone needs a flawless brand new digitizer and LCD panel let me know.
Thought I'd share some photos so others in the same situation feel more comfortable taking it apart. It was actually really easy. The motherboard is the long dark green component running along the top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wushdishmeen said:
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners?
Click to expand...
Click to collapse
From my understanding of the situation, after all that I read about the Tegra 3, APX mode, NVFlash etc.: yes, it would be possible if you knew the unique 128 bit AES "secure boot key" that is burnt into the fuses of your Tegra 3 chip. This key together with NVFlash enables you to write arbitrary partitions or blocks to the eMMC.
wushdishmeen said:
So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
Click to expand...
Click to collapse
I can only guess that their service centers do not have access to the database that stores the mapping from serial numbers to SBKs, and that they are generally unorganized - which shows because so many people have problems unlocking their tablets.
wushdishmeen said:
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware
Click to expand...
Click to collapse
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
wushdishmeen said:
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted.
Click to expand...
Click to collapse
I agree - it's ridiculous and only the consequence of trying to lock users out of their own devices. I think the whole crap is due to DRM, to make media companies happy.
wushdishmeen said:
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device.
Click to expand...
Click to collapse
For Asus, there are no "well documented issues". They don't even document the issues they fix with firmware updates. Their customer service is a joke. And they don't need it - they are a big company. Big companies do not succeed by providing good customer service, they succeed by sucking slightly less than other big companies.
wushdishmeen said:
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer?
Click to expand...
Click to collapse
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+Transformer+Infinity+TF+700+Teardown/10306/1
wushdishmeen said:
Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
Click to expand...
Click to collapse
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Thanks for actually reading my post and providing all that useful info. I appreciate that you took the time and also understood where I was coming from. My first few posts were a reaction to the realization that it was bricked and I might have to pay $200 to fix it. But everything after that was a legitimate concern for the way ASUS is choosing to handle this issue. Hopefully anyone else who ends up in this situation will see this thread and it'll help them. I went through the motions for them and will hopefully end up with a good result either by swapping the motherboard myself or selling the parts for a good profit. I'll let everyone know the outcome either way.
_that said:
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
Click to expand...
Click to collapse
I didn't read what the entire issue was. But I can make a guess that this is an issue that can be resolved and the problem is just that the common consumer doesn't have the tools to fix it themselves. My actual point was not that we should be able to fix the ASUS tablet ourselves, but that ASUS should be able to fix it without needing to replace the motherboard.
_that said:
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+...ardown/10306/1
Click to expand...
Click to collapse
When you said JTAG I was thinking of the tools I have for my XBOX to JTAG and flash the NAND. That's unfortunate that it's not possible.
I'm aware of the iFixit article. I looked at it before taking the tablet apart and it helped me avoid breaking the side clips like he did. The reason I took the pictures wasn't because I thought there were none. It was basically just visual proof to instill confidence and encourage people to take theirs apart as well. I figure if they see a regular person like me take it apart with no hesitation they might opt to replace their own motherboard rather than pay ASUS $200.
_that said:
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Click to expand...
Click to collapse
Is the eMMC part of the motherboard or separate? I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
wushdishmeen said:
I'm aware of the iFixit article.
...
Is the eMMC part of the motherboard or separate?
Click to expand...
Click to collapse
Read the whole article, there are pictures of the motherboard with the chips explained - one of them is the eMMC.
wushdishmeen said:
I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
Click to expand...
Click to collapse
I don't think you have any warranty on a "naked" motherboard at all except if it was installed by an authorized service center.
Hey guys I've had my N5 for almost a year now but it seems to have gone kaput on me recently...
On Monday I was on a skype call, (just audio) when my phone suddenly restarted, I didn't pay much mind to it as that happened before and it would usually just cut back on, but this time, it restarted, and restarted and just didn't stop. That lead me to think its the power button being stuck so i checked it out and made sure its not being depressed and well yeah it wasn't. And soon after that the phones screen was sometimes on during the reboots and sometimes off. I knew it was rebooting because the N5 vibrates a bit when Google pops up on the loading screen in a certain way, but yeah now the screen doesn't light up at all, there's still vibrations and sounds like when I call or when I say Okay Google a few times, the LED will even light up during a call. I know the phone is "on and working" in the background but the screen doesn't light up and as such I can't touch it, any ideas and or advice friends?
bump de bump?
Possibly your backlight burnt out? Water damage?
if you are running cyanogenmod, you could be experiencing sod "sleep of death". thats when you know the phone is on and working, but the screen doesnt turn on. ive been reading lots of complaints about cm and the sod.
TheROMGuy said:
Possibly your backlight burnt out? Water damage?
Click to expand...
Click to collapse
As the phone kept rebooting it went from seeing everything, to seeing nothing but the back light to dark, so maybe? It was just by me on my desk too so I was doubtful about the water damage but I put it in the sealed rice bag for about 24 hours just in case but still no luck.
I actually am running cyanogenmod and whenever I do have a problem I always feel that its related to CM as the phone doesn't have any physical damage...maybe I should look into that, any other ideas friends?
P.S I am using the ElementalX Kernel and UNFORTUNATELY I turned on the FAST CHARGE USB option and that makes the phone play funny with the computer, if you guys have any advice as to how I could turn off that option please do let me know
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
dynamo147 said:
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
Click to expand...
Click to collapse
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
simms22 said:
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
Click to expand...
Click to collapse
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
dynamo147 said:
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
Click to expand...
Click to collapse
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
simms22 said:
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
Click to expand...
Click to collapse
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
dynamo147 said:
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
Click to expand...
Click to collapse
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
simms22 said:
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
Click to expand...
Click to collapse
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
dynamo147 said:
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
Click to expand...
Click to collapse
send back the rma? honestly, i dont know. i dont know anyone thats ever had to pay. unless its obvious that you did something, youll be fine.
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
I will chat it up with one of the customer service peeps and see what they think then, and maybe even hopefully one will know about the replace anything deal
anactoraaron said:
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
Click to expand...
Click to collapse
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
dynamo147 said:
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
Click to expand...
Click to collapse
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
anactoraaron said:
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
Click to expand...
Click to collapse
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
dynamo147 said:
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=2513701.
Hi,
My nexus 5 constantly reboots at the google logo. I think it is a power button problem.
I bought my nexus 5 from the google play store but I do not live in the US, so RMAing it would be difficult.
So is there any way I can fix it? I tried tapping on the power button on the mother board but it didn't help.
Thanks!
liamkosh said:
Hi,
My nexus 5 constantly reboots at the google logo. I think it is a power button problem.
I bought my nexus 5 from the google play store but I do not live in the US, so RMAing it would be difficult.
So is there any way I can fix it? I tried tapping on the power button on the mother board but it didn't help.
Thanks!
Click to expand...
Click to collapse
I think your phone is soft-bricked... Try to boot into custom recovery, factory reset, and reflash a custom rom.
Sent from my Hammerhead running Android L !
AndreIrawan97 said:
I think your phone is soft-bricked... Try to boot into custom recovery, factory reset, and reflash a custom rom.
Sent from my Hammerhead running Android L !
Click to expand...
Click to collapse
I have the same issue but I cannot get into recovery or anything else. There is not enough time before the phone reboots again. I have read of people having success but it seems rather rare. The strange thing is that I can press or tap (with luck) on the back of the phone, near the power button, and the phone will turn on. I am sure this is a hardware issue but I got mine from T-Mobile and my bootloader is unlocked and on Android 5.0. The bad thing is that I am now able to JUMP! and was looking at the Nexus 6... oh the humanity!
On an side note: When pressing on the back of the phone (see above) repeatedly I was able to get the phone to fully boot but once I quit it rebooted again. I have not been able to repeat this as of yet. I am leaving it on the charger and hoping that it will somehow right itself like other have reported... that is unless anyone has any suggestions.
rantrav said:
I have the same issue but I cannot get into recovery or anything else. There is not enough time before the phone reboots again. I have read of people having success but it seems rather rare. The strange thing is that I can press or tap (with luck) on the back of the phone, near the power button, and the phone will turn on. I am sure this is a hardware issue but I got mine from T-Mobile and my bootloader is unlocked and on Android 5.0. The bad thing is that I am now able to JUMP! and was looking at the Nexus 6... oh the humanity!
On an side note: When pressing on the back of the phone (see above) repeatedly I was able to get the phone to fully boot but once I quit it rebooted again. I have not been able to repeat this as of yet. I am leaving it on the charger and hoping that it will somehow right itself like other have reported... that is unless anyone has any suggestions.
Click to expand...
Click to collapse
sounds like a "stuck" power button
simms22 said:
sounds like a "stuck" power button
Click to expand...
Click to collapse
I agree. I took the phone apart and messed with the components but nothing has changed. When I was able to get the phone to book all the way up "Power off" appeared as if I were pressing the button. I am not sure how to fix this.... I am sure that T-Mobile will not cover the warranty since it is unlocked.
rantrav said:
I agree. I took the phone apart and messed with the components but nothing has changed. When I was able to get the phone to book all the way up "Power off" appeared as if I were pressing the button. I am not sure how to fix this.... I am sure that T-Mobile will not cover the warranty since it is unlocked.
Click to expand...
Click to collapse
it should be a relatively inexpensive fix at any local repair shop. or you can try repairing it yourself, can probably find a youtube vid about it.
simms22 said:
it should be a relatively inexpensive fix at any local repair shop. or you can try repairing it yourself, can probably find a youtube vid about it.
Click to expand...
Click to collapse
I have not found a video, yet. I tore it down as far as I could but I will keep searching. I am 99% sure that it is hardware related but I don't think that T-Mobile will swap it out or let me use my JUMP! because of the unlocked bootloader. I knew I should have relocked it when I put 5.0 on it!!!!
rantrav said:
I have not found a video, yet. I tore it down as far as I could but I will keep searching. I am 99% sure that it is hardware related but I don't think that T-Mobile will swap it out or let me use my JUMP! because of the unlocked bootloader. I knew I should have relocked it when I put 5.0 on it!!!!
Click to expand...
Click to collapse
you still can, its very simple. in fastboot.. fastboot oem lock. or if you have root, the boot unlocker for nexus devices app. you can lock or unlock the bootloader with the app, if you have root. personally, i dont think they would even know about the bootloader being unlock.
simms22 said:
you still can, its very simple. in fastboot.. fastboot oem lock. or if you have root, the boot unlocker for nexus devices app. you can lock or unlock the bootloader with the app, if you have root. personally, i dont think they would even know about the bootloader being unlock.
Click to expand...
Click to collapse
The issue is that the phone reboots about every 2 seconds making it impossible to make a connection through ADB, recovery, or anything else. I did, however, find a solution/idea on a post by "nadrojcote":
"For the last week or so my power button/lock button has been intermittent, sometimes having to hit it 5 times or so to get the screen to unlock. Yesterday it all of a sudden stopped working and I couldn't unlock.
I am making this post to share my fix I found for the problem. Seeing how my phone is not under warranty because I have already replaced the screen, I took to tearing it apart and seeing what's going on. Hoping I could order a new power button, unfortunately the button is soldered onto the main board. Upon taking it apart I realized I had put a little shim in between the power button and the plastic button in the housing as a "rattle fix". This is what I am thinking caused the problem, this caused me to be putting too much pressure on the power button and caused it to over time break apart the back of the actual buttons metal housing on the main board. I removed the shim and it still did not work. I was going to take the main board and heat it at a low heat in the oven in hopes to reseat solder points, but before I did that I tried using a fine pair of needle nose pliers to crimp the back housing of the button back together. Luckily this worked. Unfortunately I do not have pictures, but if someone else has the same issue you should be able to see what I'm referring to by comparing the power button to the volume buttons on the mainboard, there is a metal housing around the actual button that is soldered to the main board, it has a slit down the back side of it that allows it to spread apart. The volume keys should be tight.
THE PROBLEM: Power/Lock button stops working
THE CAUSE(assumed): Nexus 5 power/lock button rattle fix
THE FIX: Using needle nose pliers to crimp the metal backing of the power button housing good and tight.
I hope this helps others out in the future as I'm sure I wont be the only one with this problem."
Now, I did not have a loose power button and so did not mod it. I did however take the phone apart and pull the board out. On the back of the board, opposite of the power switch, if an aluminum(?) case which can be removed. Under this there is another aluminum housing with a circle in the middle of it. The circle was somewhat bent touching the board parts below so I carefully bent the circle up. Next I gave the power switch a few "gentle" taps and pressed the casing around the switch to hopefully make it tighter as was recommended by "nadrojcote."
As you can tell from my word use, I am no where near an expert on anything electric BUT my phone is now working. I have not put it back together yet but I am in the process of restoring it to factory and locking the bootloader in case I need to send it in. I have sent some major prayers to God today! (If you do not believe in God you don't have to say anything negative about my post... just carry on)
This happens to me always to restart device
There is a solution to this?
What this fire button solution problem?
Who tried to replace power-on button to know is% 200 percent of the problem?