Database Info

Power Button Not Working + Stuck on Cyanogen Startup Screen

OK first of all, if you can fix this you are a GENIUS!
Basically, my power button stopped working today. The phone DID work fine and the screen turned on via plugging in the charger etc as it 'jumps' it. Also, when I take my battery out and put it back in, the phone automatically turns on, which leads me to believe the power button is somehow stuck or pressed in, even though it clicks like normal when I push it... Backing this theory up in the fact that when I start in bootloader (i.e. just holding the volume UP button when I put my battery in) I can't use the volume up or down buttons to scroll through the options, which I believe is due to the power button being 'stuck'.
So in trying to fix this, I downloaded the new Cyanogenmod 10 to see if it was a software issue. I previously had 9 installed. Long story short, it didn't fix it and I decided to go back to Cyanogenmod 9.. so I went into ROM Manager and loaded the previous version of 9 that I had the zip of on my SD card. NOW when I turn my phone on it just stalls on the Cyanogenmod intro!! And I can't turn my phone on or scroll through the options in Bootloader to install another version..
ANYONE know how to fix this?

If your power button is really stuck I'd suggest taking your phone apart to an extent and taking a look at it.
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Air Kernel (JBN Stable 1 - Voodoo)
Smartassv2 (800/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Undervolted)

309041291a said:
If your power button is really stuck I'd suggest taking your phone apart to an extent and taking a look at it.
Nexus S. (GSM i9020a)
Paranoid Epsilon 1.2 (1.992 - 4.1.1)
Air Kernel (JBN Stable 1 - Voodoo)
Smartassv2 (800/200)
Deep Idle (Off - Deadline)
BLX (98 - Inverted Apps)
Black Exodus (Undervolted)
Click to expand...
Click to collapse
The power button isn't literally stuck, that's why I put 'stuck' in quotation marks. The button still presses as per normal and the phone hasn't been damaged at all. It just seems like the button is stuck, because when I put the battery in the phone automatically switches on, whereas normally I would have to hold the power button in to do that. I did try to take the phone apart but I couldn't get the front off LOL

I have the same exact problem. Thought it was a ROM issue. But no.
I even tried to Odin but when I hold the volume buttons and plug and in USB. It just turns the phones on. Every time I plug in a cord. It will always turn on. Making it impossible to get into download mode.
So then I installed " widget rebooter " which should get me into download mode right from my home screen. But all it does is reboot. Leading me to think I can't get into download mode anymore without a jig.
IM STUMPED!!
Sent from my Nexus S using Tapatalk 2

Use fastboot from a computer. Fastboot boot recovery name of recovery.IMG will boot it up ( the image needs to be in the same directory as fastboot).

Hey, I actually have the same issue with the power button. I just ordered this off of ebay: http://www.ebay.com/itm/230794282928
It's a completely new housing so every button works. In the meantime, you can try fixing the power button by opening the phone up, removing the 6 screws, locating the power button and blowing really really hard on it, or hit it with some compressed air. If it doesn't work....the link above is a $30 fix to permanently fix this issue and you also get a new phone feel afterwards.

If the power button itself is broke that housing won't fix it.
I recently dropped my phone and my power button wouldn't work or sometimes it would work but it would act like it is stuck, so I took my phone apart and used 99% alcohol with a q-tip and cleaned the power button on the motherboard and the plastic button on the case as well as other all the other connections and let it air dry for 30 mins and reassembled and it works now.
Sent from my Nexus S

albundy2010: Can you please explain how to use fastboot? I have tried connecting my phone to Odin but it doesn't work because like BuLLeT_PrOOf_wAlleTz says, as soon as I put my battery in the phone turns on.. so I can't get into download mode even if I am pressing the two volume buttons.. And then when my phone turns on it just sticks on the Cyanogenmod 9 startup screen.
shadowx360: This looks great, but will it definintely fix the issue? I was told that I need a new 'ribbon' for the power button.. it's not the actual outer casing button itself that doesnt work.. it's the internal button that I think is connected to the motherboard..... so I'm guessing that just buying outer casing won't work?

Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.

albundy2010 said:
Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.
Click to expand...
Click to collapse
With mine I believe it's beyond the power button. I believe it's Not able to get into download mode at all. I have used commands and it just reboots.
Doesn't necessarily mean we're idiots.
Sent from my iPad using Tapatalk HD

I did not mention download mode.

albundy2010 said:
Start the phone into the bootloader as you described in your original post. That is fastboot .
If you don't know how to issue the commands on the computer and set it up read a guide.
In a perfect world everyone with a unlocked nexus should know how to do it. But morons ( sorry its true, well not really sorry ) use one click , scripts etc.
Even of you used one of those open a command prompt in the folder ( directory) of the tool that has fastboot.exe in it and put the recovery. img ( should already be one in there) in there and issue the command.
Click to expand...
Click to collapse
I have downloaded fastboot.exe and have connected my phone to the usb and have it in bootloader... how can I then use the PC to install another version of cyanogenmod so I can at least start up my phone?
FYI when i type 'fastboot devices', nothing comes up... and if, for example, i typoe 'fastboot reboot', it sais <waiting for device>, but no action or prompt appears on my phone.. it just stays in bootloader..

You don't have the drivers installed. Read a guide on how to set up fastboot / install the SDK

albundy2010 said:
You don't have the drivers installed. Read a guide on how to set up fastboot / install the SDK
Click to expand...
Click to collapse
It gets tiring repeating the same stuff over and over, doesn't it? There's at least 1 thread regarding a broken screen or power button each freaking week and yet nobody but the people helping seem to be able to use the search function.

polobunny said:
It gets tiring repeating the same stuff over and over, doesn't it? There's at least 1 thread regarding a broken screen or power button each freaking week and yet nobody but the people helping seem to be able to use the search function.
Click to expand...
Click to collapse
Thanks for the help polobunny, really appreciate it.

PS I have installed the drivers, as far as I can see. I have "Android Composite ADB Interface" in device manager, BUT it only shows up when I start my phone and connect, NOT when I start in fastboot mode. Anyone know a way around this.
FYI I am searcing for other threads on this one, but have had no luck so far.
I have reinstalled the driver from http://dottech.org/android/26188/us...rs-for-windows-for-all-android-phones/#google

bump. If anyone could help it would be much appreciated.

Notice how nobody replied after your stupid comment quoting polobunny?
There is a reason for that..... bump all you want. Good luck getting anybody to help

albundy2010 said:
Notice how nobody replied after your stupid comment quoting polobunny?
There is a reason for that..... bump all you want. Good luck getting anybody to help
Click to expand...
Click to collapse
Why was my comment stupid? Polobunny was the one mocking the person in need of help, assuming he hadn't tried searching google/forums first. There is no need for a reply like that.

you should be able to manually boot into recovery, bootloader and download modes. If your phone is powering on when the battery is inserted, it means there is a positive signal going through the power button to complete the circuit, in some way. With that said, let's assume you inserting the battery is the moment you would hypothetically be pressing the button if it worked. So in this individual case of the battery insertion acting as a power button depressing, it should be possible to get into any one of the modes desired by keeping any additional buttons depressed while inserting the battery.
In other words, to get into download mode press the vol up+down buttons at the exact same time the battery is inserted. it should work. My sister's evo4g had the exact same symptoms your phone does, and it worked for hers. I was easily able to boot into the bootloader, as well as recovery by following the steps I mentioned, and since it was a touch-based recovery, I was still able to flash/backup/restore, etc...I had full control over recovery, and everything worked just fine.
on second thought, download mode probably won't work with our device since you have to release the power button or it will fully boot....but fastboot and recovery should definitely work!!

[Q] Nexus S i9020A Bricked due to failing power button - Odin seems the last hope?

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.

[Completed] Htc One M8 hardware buttons working weirdly

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.

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.

Samsung J7 Prime (2017) SM-G610Y Boot Looping Problem

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.