Strange Behaviour with Home button and Power Button. Software or hardware? - Galaxy S6 Q&A, Help & Troubleshooting

Hey guys,
Let me start by saying I'm really enjoying the forums, I've been lurking here for a while and decided it's finally time to make an account.
Let's get into it, picked up a Rogers Samsung Galaxy S6 (Canadian) Home button works occasionally, power button didn't work, but after a quick boot into recovery it started working. Now, I thought the home button problem is software related due to the fact that it only works sometimes, and then when it works amazing for a couple of times, the power button and the home button both stop responding (even after a firmware re-install)
Here's where things get fun.
So I attempt to root the phone and flash the kernel, except I flash the wrong build (noobish, i know) I flashed a g920f xspace kernel found on here, not paying attention to the model number. After getting the "Seandroid error on boot" i figured I did something wrong, but the device boots normally into the lock screen and the phone functions fine, aside from the that buttons repeat their usually sequence of working and not working. I can also install and root with supersu.
I found the right kernel for my device, g920w8 and i attempted to flash again. Which was successful according to Odin, however once I check the kernel build, it still has the old build. I would like to flash a new rom on it and hope that the rom fixes the problem with the home button and power button (I don't really care for the messages coming during boot, just want the darn buttons to work!)
Has anyone experienced this problem before? Warranty is out so I don't really care, as long as I don't brick it.
Should I "dirty flash"? (not sure how)
I'm going to try another firmware install to see if it removes wrong kernel
Update: Firmware reinstalled removed old kernel
Here are the specs for the phone (now stock after the firmware update):
Android Version 6.0.1
Baseband: G920W8VLU5CPI4
Kernel: 3.10.61-9232017 [email protected]#1 Sept 12th 2016
Build Number: MMB29K.G920W8VLU5CPI4

Related

[Resolved] Galaxy Tab 2 Screen of death issue! Please help me!

I posted this in another thread and no one was able to help me. So I am posting it in it's own thread hoping that someone can. I know a lot of people having this same issue.
Guys, I have a brand new Galaxy Tab 2 that I bought yesterday and after following the first rooting guide, the one that uses Heimdall to flash a .pit file and a "boot-bjr.img" file, I'm having a really serious issue.
So I went through the process (not the first time I rooted an Android device) using the original heimdall method and it was easy and simple. After the root I made sure by downloading root checker basic from the Play store. I was indeed rooted. But then something weird started happening. The screen goes into standby by itself after a few seconds like normal, but I can't get it to wake up from standby. I have to shut off the device by holding the power button and then turning it back on again. When I do that it works normally again until the screen shuts off either by me pressing the power button to do it manually, or until the screen dims out into standby. I've tried wiping the cache, I've tried a factory reset, and I've even ran the process again all over using heimdall. I'm guessing it's probably the kernel that gets flashed using heimdall? Please help me out here because I only got this device yesterday and It really sucks that it's not working. Someone suggested that It's the kernel's problem and I need to be running the original kernel which is (Kernel version: 3.0.8-292098-user [email protected] #1 Build number: IML74K.P3113UEALCB). I checked and I'm running kernel version (3.0.8-275757-user se,[email protected] #1) Build Number: (IML74K.P3113UEALD3). He also suggested that I do a factory reset to reset the kernel. I did using the stock recovery and the kernel remained the same modified version. Is there anyway that I can revert back to the stock kernel? Someone please help.
I was able to fix it easily. I found someone online who had an identical Galaxy Tab 2 and had them make a nandroid backup and send me the files over dropbox. I got an md5 mismatch error which was simple to fix after some googling and then the restore went fine. Now I have no problems with the tab and the kernel is @SEP-66 #1 instead of @SEP-103 #1 which was causing the problem.

Messed up SGS2LTE GT-I9210 (Another Home/Back issue)

SGS2 LTE GT-I9210
The reason why im writing this is because i was to ignorant and hasty.
By starting of i followed a thread on a swedish forum on how to get my phone rooted, first of it worked as expected.
After a while i updated my android to a newer version, and yesturday i found out that my root had stop working, so i gave it a second shot, i followed the same tutorial.
After that my home & back buttons stopped working, and then i saw in the same thread that alot of people have encountered the same problem.
I have looked around and it seems like a way to get the keys to work is to install a older version of SlickMod, when i do my keys work, but this system does not support a swedish keyboard layout.
I was stupid and did not backup my phone before i tried rooting it.
I want to ask is there a way to restore my phone without having its standard backup, or atleast getting it to work propperly (without any fancy mod)?
For now i can only enter odinmode.
Wrong forum buddy you should search xda for your phone model and see if you can find what you're looking for
-sent from my POS i897
no camera, no power button but at least I got miui lol
erikmm said:
Wrong forum buddy you should search xda for your phone model and see if you can find what you're looking for
-sent from my POS i897
no camera, no power button but at least I got miui lol
Click to expand...
Click to collapse
I can't seem to find a forumpart for my phone on xda, can you point me in the right direction?
@ogelami
There is a search feature for something still there is not a match for your exact model but if it was me I would start here:
http://forum.xda-developers.com/forumdisplay.php?f=1055
I would steer clear of any forum not specifically for your phone. It appears that is a very new model. I think its the one Sprint is getting.
Procedure to successfull solve softkeys issues with GT-i9210 !
ogelami said:
SGS2 LTE GT-I9210
The reason why im writing this is because i was to ignorant and hasty.
By starting of i followed a thread on a swedish forum on how to get my phone rooted, first of it worked as expected.
After a while i updated my android to a newer version, and yesturday i found out that my root had stop working, so i gave it a second shot, i followed the same tutorial.
After that my home & back buttons stopped working, and then i saw in the same thread that alot of people have encountered the same problem.
I have looked around and it seems like a way to get the keys to work is to install a older version of SlickMod, when i do my keys work, but this system does not support a swedish keyboard layout.
I was stupid and did not backup my phone before i tried rooting it.
I want to ask is there a way to restore my phone without having its standard backup, or atleast getting it to work propperly (without any fancy mod)?
For now i can only enter odinmode.
Click to expand...
Click to collapse
Hello,
Based on GT-i9210T procedure that does not work properly on GT-i9210, I tryed some alternative procedure and I successfull retrieve all of my soft keys fonctionnalities.
We have to note that today, there are no CWM recovery for GT-i9210. CWM 5.0.2.6 or 5.8.1.3 (touch) are dedicated to hercules (i9210T) and not to Celox (i9210). Flash Celox with hercules CWM recovery causes soft keys issues !
So this is my procedure based on sc0ttf procedure, which was dedicated to GT-i9210T (and not GT-i9210) (http://forum.xda-developers.com/archive/index.php/t-1593061.html)
1st of August 2012
WARNING: do this at your own risk!
Assuming you've got CW5.8.1.3 (CWM v5.0.2.6 do not work on GT-i9210) on your I9210 and a most recent backup zip on your SD (doesn't have to be pre-superuser i.e. your first ever back-up)
1. Copy your back-up file from SD to your computer (just in case)
2. Install ICS Megamix EXACTLY THE WAY IT TELLS YOU TO (MAKE SURE YOU INSTALL DARKSIDE SUPERWIPE)
Install ICSMegamixS3v2.zip - http://forum.xda-developers.com/show....php?t=1576924
DARKSIDE SUPERWIPE - http://forum.xda-developers.com/show....php?t=1477955
NOTE : After installation :
* Wipe Data
* Wipe Cache
(Only !)
As you reboot, you will notice it (ICS) being unstable and unable to make calls.
NOTE : for me (i9210 Celox), no problem to dial following code
3. Now press *#*#2663#*#* and confirm Phone's Touch is 0x9 and Part's Touch is 0x0. If this is so, now press Touch Key FW Update which will upgrade your Part's to 0x9
3 bis (added by me) : do the same with *#*#86824#*#*
NOTE : for me, the version was v0x11
4. Reboot
5. Now laugh as you see your phone having a psychotic episode. Your soft buttons should be lit up and your screen should be wacky (like you're repeatedly and continuously pressing the soft menu button). NOTE: although your buttons are lit up now (brought tears to my eyes), they are not working yet but are close to working
6. Now, reboot into CWM v5.8.1.3 => this was impossible for me !!!
=> NOTE : For me, CWM v5.8 was so unstable that it was impssible to performe remaining wipes. I decided to flash stock rom, hoping that i9210 will be back and more stable...
7. Stock Rom flash. Reboot : i9210 were so unstable that I forced it to stop.
8. Reboot on recovery mode, wipe data wipe several times...
H/W Key release is OK (v07) using *#*#2663#*#* et *#*#86824#*#*
9. Stop the GT-i9210 and remove battery 1 min
10. Reinsert battery and test
11 dial *2767*3855# => deep factory reset and reboot
12 : Every thing is OK
=> All is OK for me...
Hoping that tomorrow, everything will be OK* !
NOTE : yesterday I tryed the same procedure and I flashed CWM 5.1.8.3, I think it was the reason why this morning, soft keys were gone out...
i have the touch recovery installed on my i9210 (portuguese) and it's working nicely.
So you lost your soft keys, flashing ICS on i9210 right?
therethere said:
i have the touch recovery installed on my i9210 (portuguese) and it's working nicely.
So you lost your soft keys, flashing ICS on i9210 right?
Click to expand...
Click to collapse
Yes, following the tutorial I post will cause your soft keys to reborn. Flashing ICS, following the procedure above and flashing back a firmware for GT-i9210 is the way to do it.
well it's weird cause i only have the recovery 5.8.1.3 and my touch keys are just fine.

[Completed] Stock ROM - Is this supposed to happen?

It's been a while since I've tinkered with my Note 3, usually because I fancied seeing what the Note 7 OS looked like etc.
The last time was to unroot my phone and put the official KitKat back.
Now after sometime I've had issues with services like Bluetooth so I reinstalled the stock ROM although it's BTU Lollipop this time because for some reason Odin wasn't accepting my H3G 4.4.2 stock ROM.
Nevertheless, it has installed but to my surprise, all my apps, settings and messages are still there. The Bluetooth service is now back in business too. I guess I should be pleased but I'm wondering if this should happen?
As mentioned, it's been a while since I played about with ROMs but that was when I rooted and used apps like CWM but how do I completely wipe my phone first without rooting, before installing the stock ROM?
To install a stock ROM I press Vol. down, Home & power buttons and use Odin but before this, do I use the Vol. Up option first to wipe everyting?
One little extra question please, because my KtKat ROM seems corrupted now, where can I go to get another one? I can see samMobile.com has them but you have to pay. If that's the norm now then so be it.
Thanks very much and hope you can help.
Actually, nevermind, I bit the pillow and tried the Vol. Up option first to wipe the data & partition cache.
Just didn't know if I was going to find myself unable to install a new ROM with the Vol. Down option afterwards.
Needless to say, it worked a treat!
Very happy bunny.

Need help with my S6!

Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match

Desperately need help w/issue After 8.0 Update...

S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!

Categories

Resources