[Q] bootloop on htc one x running stock settings...HELP - AT&T, Rogers HTC One X, Telstra One XL

hey guys. I was trying to connect to public WiFi today and my phone just shut off. It goes through the boot process. I get the first HTC guietly brilliant, then i get the att, then the last htc ONE, it vibrates, goes black like my home screen is about to pop up and nope, no home screen. It goes right back to being quietly brilliant. My phone is not rooted or flashed or any of that junk (my nook however is lol) Its been stuck on repeat for a good 5 hours now. Ive read online a couple of different things to go about doing, but they are all having to do with rooted phones. I am under warranty, so i can get a new phone, however i do have some precious pictures of my new baby cousin and my father that just recently passed that i REALLY DONT want to give up...can someone pleeassseee help?!?!?!??!?!

"fastboot erase cache" will work on a stock phone
also find a way to get into safe mode which i'm not sure how to do

well if u dont know how to do it, then i sure as heck dont know how to do it. and "fastboot, erase, cache"??? lol i know u know that was probably coming lmao

in that case hold volume down + power for until lights flash and stop, then keeping holding volume down and tap power until you get into bootloader, then go recovery. once you get there press volume up to see dialog and selections, select wipe cache, once finished reboot.

ok so I go to recovery and shows the 2 green arrows in circle with a green arrow pointing at an image of a cell phone then it almost immediately switches to an image of a phone with a red triangle with an exclamation mark in the middle and it stays like that for a minute and then reboots and starts the evil cycle of being quietly brilliant all over again

i can't help you anymore more than google could easier, as a stock phone is worthless to me so i know little about a stock phone.

got it all figured out...thanks for your help and for um being so nice, i say sarcastically.

DvineLord said:
also find a way to get into safe mode which i'm not sure how to do
Click to expand...
Click to collapse
Similar to bootloader, except you start pressing vol down while the boot screen is showing (but before the phone fully boots), instead of before.
---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------
jnassi421 said:
ok so I go to recovery and shows the 2 green arrows in circle with a green arrow pointing at an image of a cell phone then it almost immediately switches to an image of a phone with a red triangle with an exclamation mark in the middle
Click to expand...
Click to collapse
That's the stock recovery. What DvineLord was suggesting won't work in stock recovery.

too bad there is no safe mode once you flash custom rom or that is what i've been led to believe

DvineLord said:
too bad there is no safe mode once you flash custom rom or that is what i've been led to believe
Click to expand...
Click to collapse
Works fine on CleanROM JL Beta. Pretty sure I've used it on other Sense based customs as well. Maybe its a Sense feature, and doesn't work on AOSP ROMs?

Related

[Q] recovering from a softbrick

So I have an lg g2x originally running gingerbread 2.3.3 and I went through this procedure -> http://forum.xda-developers.com/showthread.php?t=1259852&highlight=linux+g2x+root
Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down and tries to boot again.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
I am running linux and do *not* have access to windows at all.
Which LG screen are you getting? The static one or the one with a moving green bar underneath it? Can you still boot into Clockworkmod Recovery or was that a no go? You need to give more detailed information so people can figure out at what point in the boot process your phone is rebooting.
I get that initial booting LG screen with the face and the letters LG, there is no green bar. It sits in that screen for 15 or 20 seconds then attempts to reboot. Well, thats what I assume happens. The screen goes black, the buttons along the bottom flash and then after a few seconds that white LG screen comes back and it does it all again. It never gets past that and never into CWM. I can still put it in the flash mode that allows nvflash to connect and do its thing, but thats about it.
If you have successfully nvflashed cwm. Then you should be able to get into cwm by holding volume down+power until it goes to a blueish LG screen. Then flash a rooted rom from there.
That is the easiest/safest way of rooting a g2x. If you haven't done this you can Google "nvflash g2x Linux" and find guides on how to do it.
Sent from my LG-P999 using xda premium
Right, thats exactly what should happen. Unfortunately, its not what actually happens. During bootup I a can hold power + volume down all day long and get the exact same behavior. Its a bit disconcerting.
[solved]
Guys, I found the problem and figured I would post it here for future folks.
I was unable to start my phone plugged into the charge (both to the computer and to the wall). I had to have the battery in for this to get to a good place. I guess initial startup just took too much power.
So if you do this, after using the restore script. Press the power button and volume down hold both, then *put in the battery*. Thats what worked for me.
thanks!

Strange incident with CWM

hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
the same thing happened to me once on my ns4g. I had to pull the battery.
try flash recovery img at fastboot and then see if you can get in recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
As long as it is working OK now then all is good.
Happens every now and again.
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
bigmem said:
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
Click to expand...
Click to collapse
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
allenxx said:
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
Click to expand...
Click to collapse
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
bigmem said:
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
Click to expand...
Click to collapse
try twrp recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
It's caused by scrolling through the menu options 3 times. It's actually a feature. I forget where I read it but apparently back in the day there was a dude with a broken power button who couldn't select things in CWM so Koush put in that feature just for him. I believe one of the other buttons works to select items when that's enabled. To get out of it just keep scrolling up or down through the menu options 3 more times.
You ended up in the stock recovery. Hold power then press volume down OR volume up (cant remember which) and you'll be in stock recovery.
Also, the physical buttons are disabled when you press vol up and vol down at the same time. Do it again to return to normal.
happened to my yesterday again, after six months of problems free.
anyway nothing to be scared about.
thank u for answers, i kinda forgot about that thread... LOL

Stuck on BOOT!!!

So i unlocked the bootloader and rooted the phone, and after that im stuck on boot and nothing seems to get it back to work.
When i use the restore function on the tool i get "fastboot" is not recognized as an internal or external or external command...
Help Please? got the phone like 20 mins ago and have not even use it (((
Will anyone be kind enough to help me? its not even funny :'(
first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.
elementaldragon said:
first off... it generally might take a little bit to get a response to a thread, especially with almost no information provided. Expecting a reply within 17 minutes under such circumstances is expecting quite a lot.
Now... when you say "Stuck at boot"......... what? do you see anything on the screen? If so, what? Android on its back with a red triangle? Android standing with a thing spinning by its chest and a bar below it? Does it at least turn on at all? Need details.
And fastboot is only recognized if you actually have the phone in fastboot mode... i.e. holding power and "volume down" down when powering the device on.
Click to expand...
Click to collapse
The phone turns on, and it gets stuck on the boot where the circles are spinning, if I go to fastboot the android is laying down with the chest open and blue inside.
Where im stuck is at the spinning nexus logo.... :'(
I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?
elementaldragon said:
I'm starting to get the feeling that you may have jumped the gun on modding your phone... ESPECIALLY unlocking the bootloader. Probably why a lot of people suggest going the manual route for things rather than relying on a tool to make it just a series of keystrokes. Less likely to potentially miss a step if you're constantly reading what has to be done next, rather than just typing number and/or hitting the Enter key.
After unlocking the bootloader, did the phone reboot, and did you see the one thing i mentioned on the screen, the android standing with his chest open and the thing spinning in front of it, with the tiny progress bar of sorts below him?
Click to expand...
Click to collapse
I dont believe i saw that :/
Im trying to flash factory image now.
:/
http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...
elementaldragon said:
http://www.xda-developers.com/android/how-to-root-and-unlock-the-google-nexus-5-xda-developer-tv/
May want to watch the video there. The thing i speak of is at the 4:20 mark. When the bootloader is unlocked, a factory reset is automatically performed by the phone. If you're seeing the android on his back, with the blue lights inside, and text above and below him, chances are that's fastboot mode... but it could be something different that you're talking about.
It's getting quite late, and i have to get some sleep. Hopefully someone else might be able to pick this up from here...
Click to expand...
Click to collapse
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command
I had the same problem. Jumped the gun from unlocking the bootloader to immediately installing TWRP without a reboot. I was stuck in a boot loop for hours. Power down the phone by holding in the power button. Boot into the bootloader by holding down volume and the power button. From here you can use fastboot. I wiped the data and cache. "fastboot erase userdata" and "fastboot erase cache".
The error you mention above with fastboot is your computer not finding the path to fastboot. On linux, browse to the directory fastboot is in and use ./fastboot erase userdata
Once the data and cache were cleared I could boot just fine.
http://forum.xda-developers.com/showthread.php?t=2512534
Sent from my Nexus 5 using Tapatalk
orphan22 said:
Yes y did saw that, my problem is that when i try to do anything i get this "fastboot" is not recognized as an internal or external or external command
Click to expand...
Click to collapse
It seems you didn't install Fastboot on your computer... Check the requirements.

Dead photon?

Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance
Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger
Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.
http://i.imgur.com/3XYLngJ.png
kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?
Yes
Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.
I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now

[Q] HTC One S bricked-ish

Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
why not change the volume button, at gsm service.
It's a good phone.
compul said:
Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
Click to expand...
Click to collapse
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
null0seven said:
why not change the volume button, at gsm service.
It's a good phone.
Click to expand...
Click to collapse
While that is my last resort, I'd like to avoid it. I do have a working Nexus 5 after all.
TiTAN-O-One said:
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
Click to expand...
Click to collapse
It's the volume rocker, not the power button; and it's been broken for a long time. I'm a little afraid I might rip things apart, but this makes it look outright easy: youtube.com/watch?v=6j25jajIq3g. I'll give it a try.

Categories

Resources