Faulty power button. Fixed myself. - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I take no responsibility for your damaged devices, or any stuff you did in wrong way.
So how it went wrong:
Some days ago i flashed some rom. it was working okay. Than i flashed some more, and random reboots started to occur. Than i tried to boot to recovery from rom, and it just started to bootloop, not booting to rom neither to recovery.
managed to get to download mode after several attempts, odined a recovery (twrp as i always use it).
rom booted after i flashed recovey via odin. than i went back to recovery, checked md5 and its ok. So than did another clean flash, it was running ok. But than i pick my phone out of pocket and it's dead again. Odined once more.
It was booting like this - 3-5 seconds/vibration/blackscreen. and also not displaying battery on charging, even no led, even not letting to get to download mode. After battery reinsert it starts to boot, without pressing a thing.
Try not to panic first, try to boot properly and test how power bottom behave.
Fix:
Disassemble, put 2 little pieces of rubber between button and board, and should work fine so no matter to go for repair. It consumed me 10 minutes. Assembles without any trouble. And saved 5-10 bucks.
Can attach some photos if you ask to.

#000000 said:
I take no responsibility for your damaged devices, or any stuff you did in wrong way.
So how it went wrong:
Some days ago i flashed some rom. it was working okay. Than i flashed some more, and random reboots started to occur. Than i tried to boot to recovery from rom, and it just started to bootloop, not booting to rom neither to recovery.
managed to get to download mode after several attempts, odined a recovery (twrp as i always use it).
rom booted after i flashed recovey via odin. than i went back to recovery, checked md5 and its ok. So than did another clean flash, it was running ok. But than i pick my phone out of pocket and it's dead again. Odined once more.
It was booting like this - 3-5 seconds/vibration/blackscreen. and also not displaying battery on charging, even no led, even not letting to get to download mode. After battery reinsert it starts to boot, without pressing a thing.
Try not to panic first, try to boot properly and test how power bottom behave.
Fix:
Disassemble, put 2 little pieces of rubber between button and board, and should work fine so no matter to go for repair. It consumed me 10 minutes. Assembles without any trouble. And saved 5-10 bucks.
Can attach some photos if you ask to.
Click to expand...
Click to collapse
Can you please attach some photos, I'm having the same issue with my power button

When I had this problem a month ago I took out my handy dandy heat gun after disassembling the back and cleaning with isopropal alcohol. Fixed mine right up and I haven't had any issues since *knocks on wood*. If I have anymore problems though I will try this, thanks.

landroid2000 said:
Can you please attach some photos, I'm having the same issue with my power button
Click to expand...
Click to collapse
Will upload in 1-2 days. Having issues with second device.

#000000 said:
Will upload in 1-2 days. Having issues with second device.
Click to expand...
Click to collapse
Okay thanks

This is a nasty issue with pretty much any Samsung device, these are pretty ingenious work arounds considering the actual solder job can be a nuisance. I obviously recommend replacing the button to anyone if possible but still interesting to see what works!
P.S. I work at a uBreakiFix, my manager hates this solder job :laugh:

Related

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.

[Q] Random Reboot Leads to Bootloop from...

OK all I am sincerely reaching out as I am out of ideas. Here is the situation...
Issue : Last evening, running most recent Liquid Smooth 4.4 (Superb ROM, I don't feel this is really at fault just relevant and thorough), I had been doing some heavy tethering when I picked up my beast and stepped out for a smoke. As I am reading up on moto360's 2 1/2 hour sellout I get a random reboot. Eh, no biggy ... it does happen. (Not often, or at all to speak of in my case just stating.) Right after reboot I hit the power button to make a forced boot cycle and it rebooted again before I pressed anything on screen!
Now SOMETIMES I will boot past the initial "NOTE II" splash (NOT often at all ... usually get reboots, splash hangs, or the phone simply turns off on its own from here) If it does make it past Note II splash it will reboot, hang, or simply turn off from here as well.
Steps Taken: I firstly, attempted a restore... no dice. I attempted a fresh install (TW, SlimRom, and DU) ... no dice dos. OK hmmmm
Now to all mighty ODIN (L900VPUCNE2_L900SPTCNE2_1561791_REV04) .... NO FREAKING DICE!!! WTF?!?!? I additionally attempted MC2_STOCK_with_COUNT_RESET-20130511 ... no bueno!
I still have access to Recovery and Download soooooooo ... I lay down at the mercy of you the community!!!
Thanks in advance and if you need more info PLEASE don't be shy!
Same issue here!!!
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Exact same thing
I've been running the latest nightlies of OmniRom. And yesterday, out of the blue, random reset then bootloop. No luck with anything, recovery, odin, etc.
Did Sprint deliberately brick our phones?
I'll try the odin to stock to see if I get any luck there. But if anyone else figures it out, it'd be nice to know the fix. Thanks!
No luck going back to stock. It's dead Jim.
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
If my case, my phone would boot loop around the splash screen. on the battery power only. I could go into recovery and download mode with no issues and stay on for hours. If I connected it to, say a PC, it would boot, but would random shut off within five minutes. But if I plugged into the wall charger, it would boot with no problems. Stay on for hours. If I plugged it from the charger, it would immediately shut off and try rebooting which it would just boot loop.
Luckily, the batteries are pretty cheap at $10 to $20 on Amazon. I went with the Anker for $15 to get me by till I get my next phone, which will probably be October; I'm heavily learning towards the Note 4
Replace the battery
I had the exact same issues. I ended up buying a $10 battery on amazon and it solved the problem. I did go through all the flashing, odin to stock, etc. All was pretty good when plugged in to a good power source. It took me about 4 hours of trial, error, reflashing, etc before I realized it was probably a battery issue. The new battery has solved the problem.
lovekeiiy said:
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
Click to expand...
Click to collapse
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
crackrock360 said:
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Click to expand...
Click to collapse
I couldn't flash any of counter reset rom through anything but TWP so i have to boot into download and update away from Philz. AFTER the recovery update I started making headway. but couldn't ever seem to make it past boot no matter how much batter is charged. I was beginning to think it was something that died on the inside (heh...heh)
After reading through some of these greatly appreciated replies I am going to plug her up to the wall and try the ne2 counter reset again(12:58 am). ... AND I may go throw some cash at a battery juuuuuust in case. (I do tether 100gigs daily sooooooo it does make sense that it could have burnted up lmao!)
UPDATE 1:25AM : I did as advised and it does seem battery has taken a dive! hmmm so weird! It still shows having power and charging. But after being plugged into wall I made it booted into a fresh ODIN install!!! (keep in mind that AS SOON AS odin gave me a pass I switched to Wall outlet!) I have even performed a power cycle to confirm it wasn't a fluke! I will indeed be out first thing in the morn to get a new battery!
AGAIN I can not thank you all enough ... I would have never thought of that. (you would think it would be one of the first things but eh you live and learn.)
I will update with any new progress!
cheers!
crackrock360 said:
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
Click to expand...
Click to collapse
'When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.' EXACT CIRCUMSTANCES AS I SIR!!!
Mine does the same and hangs .... right? HIt the power button and as soon as it lights up to start to boot then plug in the power cable. (the freezing while off and charging is a known bug in at least two roms i believe)
Congrats Rubledub!
As for me, I'm still screwed. Invested $40 in a battery (had to have it today, couldn't wait on shipping)
With the new battery fully charged I still have the same result!
crackrock360 said:
,,, Do the batteries go bad instantly?
Click to expand...
Click to collapse
There were probably signs of the battery going bad, but misread. But in my experience, it went to total crap instantly.
The signs of going bad were shorter battery life, getting stuck/freezing when trying to charge the phone when off (there's that battery graphic that shows up). Unfortunately, I did all kids of other stuff before I really figured it out, and looks like a messed up my modem and now cannot connect to 3G. Kind of irritating, but luckily, I spend 75% of my time in LTE areas. Just got to ride this out till the Note 4 is released.
Here is thread of when I was having trouble: linky/URL]. It's a lot of me trying slightly different things with no changes in results. Plus, I was a buddy's house who was in a 3G only area. The worse part, my phone did this the day before I left to spend the weekend five hundred miles away from home at a friend's house to visit.
sloanmeister said:
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Click to expand...
Click to collapse
Just chiming in to say this worked for me! Thanks!
Joelski144 said:
Just chiming in to say this worked for me! Thanks!
Click to expand...
Click to collapse
Oh i agree! Thats is what had me so baffled ... Not even the odin installs were breathing life, and Odin ALWAYS works for me. If Odin isnt getting it done and neither is a battery then your problem may be far more serious???
Weird Recovery Lag and bootlooping after CM12 update
Hey guys,
I came across this thread and the issues I'm having sound so what similar, so I thought you might be able to help.
I have two Samsung Note 2(l900) and running on cm12 as of yesterday morning. I installed the new nightly manually on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
I'm back on stock rom and the device is working great but takes forever to get into manual recovery which I believe is why it is having issues booting Cm 12

VM Soft-Bricked...I know...

Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
FoxyDrew said:
Haha I had this same problem before, was ready to send my phone back. I was so scared and it wasn't working for like 3 days.
Click to expand...
Click to collapse
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
kenmoini said:
Yeah, note to self, never get a phone without a removable battery. The sticky pads under the back cover while I was popping it off were annoying. Thankfully my phone was only down for a few hours.
Click to expand...
Click to collapse
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
LiquidPlacidity said:
This phone has a non-removable battery. You don't need to take out anything, all you do is hold volume up + the power button for 10 seconds or more. It will ALWAYS hard power off no matter what state the phone is in.
Also, what file did you flash over to improve the speaker clarity which broke your phone? I spoke to you about this earlier in my CarbonROM thread. I actually was able to fix the boomsound issue and there is no more crackling in my speakers. I'm going to post how to do it when I get home.
Edit: SORRY! Volume UP, not DOWN. Got mixed up
Click to expand...
Click to collapse
I tried Vol Up/Down + Power for at least 30 seconds, was just stuck at HTC logo screen and I could feel the phone getting hotter so instead of having it run down the battery I decided to pop off the top. The back is meant to be non-removable but starting at the SD/SIM slot...slot, a guitar pick works great to undo the clips. Used a credit card to separate the sticky pads from the back. Pulled out the battery cable from the mainboard and reseated it, started it back up in HBOOT.
I flashed some sorta ZIP that's used with the HTC One M8 phones, figured if they have BoomSound it'd help too but noooope, haha. Can't remember what it was called. Did a lot of searching, tried Viper4Android, that sucked, tried tweaking the DSP, nothing came close to the original.
Sharing my own bricking experience
I'm a newbie, but I wanted to share my own experience from a few days ago. I bricked my VM/USA 816 when I was restoring a ROM backup of CM12 over a stock ROM. I was stuck on the CM12 blue "alien head" boot screen. I tried to get into the recovery screen by holding down power & volume, but it would only reboot and load CM12 again and not TWRP.
After a couple of hours of trying to get into recovery and deciding not to wait for the battery to drain because I thought the blue CM12 logo might burn into the screen. I decided to try to remove the cover and unplug the battery. I started at the SIM/SD Card slot trying to pop the cover off a little with a small screw driver to get a credit card(CC) between the cover and phone. Once I got it started I moved clockwise(cover side up) around with either a bent CC or a smaller cut up piece of CC to pop the tabs. I wasn't very gentle since I knew I wasn't going to return the phone and I bought the phone from VM with account balance so I didn't feel like I was really going to waste $300. Thank HTC the plastic cover is very forgiving. Once you get past the HTC logo you have to worry about the sticky tape around the bottom half of the phone where the battery is located. The bent CC was the best tool here and as I said earlier I wasn't very gentle while pulling off the cover once the tabs were loose.
Once I had the cover off I didn't know how to unplug the battery connector so I decided to pry the battery out. Once I did that I could see that the connecter pops up. I plugged the battery back in but the phone tried to load CM12 again. I don't remember if I had to press power button to turn on phone or it started when I connected the battery. I got back into the same state as before with a boot loop with no way getting back into recovery. So I unplugged battery again and connected the phone to my PC. I could see the screen the flashing between the charging screen and TWRP, but I couldn't get into recovery with buttons or screen touches. I then went into a command window on my PC to try the adb command. First I did a "adb devices" then I did a "adb reboot recovery" to get into TWRP. Once in TWRP I did an advanced wipe and installed CM12, gapps and supersu again from my ext SD Card. I'm not sure but I may have done a format of the internal storage just to be safe. Once I was up and running again I replaced the cover starting again clockwise from the SIM/SD Card corner and all the way around the phone till you get near the SIM/SD Card slot and have to replace the flap which is held in place by the cover/phone.
I hope this helps anyone who runs into the same problem.
kenmoini said:
Well, guys was doing pretty well there for a second, I had just installed CarbonROM, was tweaking to my heart's content. Flashed a bad file in an attempt to improve speaker clairity, and boom stuck on the HTC boot logo.
Popped open the back, unplugged the battery, rebooted into HBOOT, rebooted into recovery and attempted to restore one of my backups I took right before flashing the bad zip. Failed. Can't load the data partition.
Ok, got the RUU file from this thread: http://forum.xda-developers.com/desire-816/general/ruu-htc-desire-816-a5chl-ruu-file-t2920254
Downloaded, put on root of SD card, renamed, rebooted to HBOOT, it picked it up, seemed to flash it, but it also seemed to go faster than it should. I'm suspecting it failed as well.
So now I've just got my phone sitting in recovery. Unable to mount the data partition.
Any clue on what I can do now? Hoping I haven't bricked this sucker...
Click to expand...
Click to collapse
You have to flash and use CWM 6.0.5.1 and wipe the same partitions that were backed up in your STOCK nandroid backup.
Once you do this, reboot to hboot. Enter fastboot. Flash the stock recovery. Wipe the data/cache/dalvik. Reboot and go to hboot again. (Your device won't be able to boot yet.) Enter fastboot again.
Flash CWM (ONLY CWM) and make sure it flashes by flashing it twice back to back without leaving fastboot at any point.
Boot into recovery and once loaded reboot into hboot once more then go once again to fastboot and flash Philz Recovery with the same double flash process.
Now boot into it, mount as a USB and create a clockworkmod/backup folder on the device root directory since Philz Recovery doesn't use the buried part of the system like CWM.
Drag and drop your stock root nandroid backup. Use Philsz recovery to restore it. Boot up and your phone will boot after 3-5 minutes.
Flash back CM11/12 if you'd like.
Sent from my 710C using XDA Free mobile app
kenmoini said:
Ok, my persistence paid off....Mods feel free to close this thread, I came up with a fix.
For anyone else in the same rut, this is how I fixed it...
Downloaded stock recovery from this link: https://drive.google.com/file/d/0B4NAwrQOaS7QVkxFYnhFZmhjOGc/view
Flashed stock recovery from Fastboot.
Loaded into stock recovery, key combo'd Volume UP + Power, got to the menu. Did a factory reset. Guess it reset partition mount points or something.
Rebooted to Fastboot, flashed TWRP, rebooted to recovery, restored a backup, and bam I'm back!
Click to expand...
Click to collapse
Hello
Thank you for sharing your solution.
I have a problem which is described in this thread: http://forum.xda-developers.com/des...im-boots-fastboot-t3316255/page3#post65409302.
My questions to you:
1. My bootloader is locked. Is it possible to flash stock recovery on it?
2. I tried to flash official rom but I received the message "Partition update fail!". Can what you did, resolve this problem?

[Q] Phone turns off automatically

I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.

Useful advice for scenario: Blank TWRP + Bootloop After Rom Flash.

I had almost given up on my phone and was coming here to get some help.
As I was writing up this thread I had left my phone on the blank screen I'm about to describe.
then i noticed out of the corner of my eye the screen light up.
So my advice is, if you ever have this scenario happen it may take over 20 minutes for TWRP to even load.
This may not be something that can be duplicated, but hopefully it can be useful for someone who would panic about this like myself and keep trying things.
(I have a sneaky suspicion about my SD card now, I believe it may have become corrupted during the install.. breaking the rom.. and then making the phone hang while loading twrp.)
Mate - mt1-u06
(Ab)using TWRP v2.8.1.0
Thanks
So today I wanted to try out this:
http://forum.xda-developers.com/ascend-p6/ascend-mate/rom-omnirom-t3092487
and when I flashed it through twrp I did the install it was all successful but I forgot to wipe before rebooting (woops) So i thought hmm maybe it didn't need it,
so left it for a few minutes, realized this is a bootloop and needed to be done again.
So I was like okay I'll just shut it off and go back into recovery.
Did it like I normally would (power and the volume) and my heart kinda sank when I got a black screen (back-lit so you could tell it was still on).
weird usually it loads...
powered it off and let it load normally again to see if it was just taking a while to setup maybe to just get into the OS.
Nope 1 hour later nothing.
Have tried getting into recovery a million times but its still blank.
and to get the nooby stuff out of the way:
Fully charged before I did it and It wouldn't even turn on if it wasn't so that's kind obvious.
Mate - mt1-u06
using TWRP v2.8.1.0
Click to expand...
Click to collapse

Categories

Resources