I had a shower half a year ago with my Razr, and had it's power button damaged by it, however, it effected my access to ap fastboot.
luckily, I might not be able to use the power button, but I can still restart my phone by holding volume down, but the volume down doesnt fuction both as power button and volume down, it only provides the volume down command.
My os has become really slow, I have no idea why, I think my phone could still function rapidly after the water damage, positive it didnt corrupt any hardware like the cpu because then I wouldnt be even able to turn my phone up,
I am having cm 11 and the nights updates didnt make it any better, im positive it was one of the updates I installed made my os function slower.
So my only solution is to write down a new stock rom on my phone, but as soon as I go to ap fastboot, it only leads to a black screen.
I could probably install a new stock from the os loaded it self through the usb debugger feature, but I tried to research my issue on google and around the forum and I couldnt find non that have my problem, so I am really not sure if its a good idea flashing a stock through the os, when the fastboot it self doesnt exist in my phone.
What should I do?
Thanks!
Related
Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N
Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app
Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.
Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.
I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app
XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.
In case anybody comes back here, I'm just gonna drop this in.
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
Hey Guys,
I´m no English native so please be patient. I`m although no noob with Android and hardware but can`t figure out some strange defects on my M8. Hope for help!
So here is the story: A week ago I woke up late. My Phone was stuck in Bootloader and I couldn’t select any option. Only my Volume Up Button did change the marking
of options. Strangely it did so in the wrong way. Means Volume Up changed up to down. Pushing the Power Button shortly to select an option didn`t do a thing at all.
But pushing it for long did what it should: It shut the Phone down. As I restarted it I again got stuck in bootloader. By trying out different ways I managed to somehow
boot in safe mode. It took me some time to figure out that my Volume Down Button was stuck and was therefore the reason for the strange booting procedure.
It´ll get more strange from here on so please remember: Bootloader, only Volume Up Button working but in the wrong way, Power Button only reacts to long periods
of pushing, probably Volume Down Button stuck.
In safe mode the Power Button worked fine again and did respond to all kinds of pushes as it should. Volume down did not do a thing (As expected). Theory seems
confirmed. To rule out software issues I did a full reset in TWRP which I had to start from cmd on my desktop as my phone still did not take any selections in bootloader.
And additionally flashed a new rom (Skydragon GPE 5). Didn´t change my problem at all so I went to bed. My phone was nearly powered out and I forgot to plug it.
In the morning I found it dead so I plugged it in and booted it up. Strange thing: It booted completely normal. All Buttons were working. Yes, even the Power Down
Button. Now I realized that Wi-Fi isn`t working which could be because of my old firmware and the new rom. So I started to learn how to update the firmware - which
took me 15 minutes. As I got back to my Phone to get it started the Volume Button was stuck again. Now it finally has to be some hardware defect right? I found the
spare parts on Ebay and wanted to give it one last shot before I placed the order. So risked to get stuck in safe mode or bootloder (again) and pushed the Power
Button down hard. But surprise my phone decided to open a new chapter of strangeness: Nothing happened at all. Now the Power Button wasn`t working any more.
No reaction to short pushes and what’s completely new, no reaction to long pushes too. So I avoided restarts form that point on and used my phone for the last days
in that condition. Decided I could life without two of the three hardware buttons But as I could not flash the firmware without restarting the phone no Wi-Fi starts
to bother.
To be honest: I don`t know what to do! I don`t want to waste money on spear parts if there’s the option of some really strange software failure. A defect over night
without any physical forces aside from really high room temperatures seems unlikely to me. Even more if you count in the strange healing over night and the factor
that it not only broke down again but although spread it´s desesse to the power button. I`m really out! Any Ideas?
FabianX2 said:
Hey Guys,
I´m no English native so please be patient. I`m although no noob with Android and hardware but can`t figure out some strange defects on my M8. Hope for help!
So here is the story: A week ago I woke up late. My Phone was stuck in Bootloader and I couldn’t select any option. Only my Volume Up Button did change the marking
of options. Strangely it did so in the wrong way. Means Volume Up changed up to down. Pushing the Power Button shortly to select an option didn`t do a thing at all.
But pushing it for long did what it should: It shut the Phone down. As I restarted it I again got stuck in bootloader. By trying out different ways I managed to somehow
boot in safe mode. It took me some time to figure out that my Volume Down Button was stuck and was therefore the reason for the strange booting procedure.
It´ll get more strange from here on so please remember: Bootloader, only Volume Up Button working but in the wrong way, Power Button only reacts to long periods
of pushing, probably Volume Down Button stuck.
In safe mode the Power Button worked fine again and did respond to all kinds of pushes as it should. Volume down did not do a thing (As expected). Theory seems
confirmed. To rule out software issues I did a full reset in TWRP which I had to start from cmd on my desktop as my phone still did not take any selections in bootloader.
And additionally flashed a new rom (Skydragon GPE 5). Didn´t change my problem at all so I went to bed. My phone was nearly powered out and I forgot to plug it.
In the morning I found it dead so I plugged it in and booted it up. Strange thing: It booted completely normal. All Buttons were working. Yes, even the Power Down
Button. Now I realized that Wi-Fi isn`t working which could be because of my old firmware and the new rom. So I started to learn how to update the firmware - which
took me 15 minutes. As I got back to my Phone to get it started the Volume Button was stuck again. Now it finally has to be some hardware defect right? I found the
spare parts on Ebay and wanted to give it one last shot before I placed the order. So risked to get stuck in safe mode or bootloder (again) and pushed the Power
Button down hard. But surprise my phone decided to open a new chapter of strangeness: Nothing happened at all. Now the Power Button wasn`t working any more.
No reaction to short pushes and what’s completely new, no reaction to long pushes too. So I avoided restarts form that point on and used my phone for the last days
in that condition. Decided I could life without two of the three hardware buttons But as I could not flash the firmware without restarting the phone no Wi-Fi starts
to bother.
To be honest: I don`t know what to do! I don`t want to waste money on spear parts if there’s the option of some really strange software failure. A defect over night
without any physical forces aside from really high room temperatures seems unlikely to me. Even more if you count in the strange healing over night and the factor
that it not only broke down again but although spread it´s desesse to the power button. I`m really out! Any Ideas?
Click to expand...
Click to collapse
You might have better results by asking those that own your device.
http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
The_Merovingian said:
You might have better results by asking those that own your device.
http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
Click to expand...
Click to collapse
I did see it more as a general Problem not only related to the divice. But thanks will try!
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.
Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.
You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.
Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!
A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.
Try restarting by pressing home, power and volume up all at once.
Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.