hey there,
i currently have a galaxy S5 SM-G900F which is stuck in safe mode,i have searched and searched this forum for a solution and have exhausted all possible fixes for this issue
the only one i have not yet done is to use odin to flash a new firmware...yet
this device was dropped into a toilet and after drying it out was scrambled,(the rom kept jumping into all sorts of different parts of itself,so i updated from kitkat via kies to lollipop...the update went fine and the device has re-booted without the previously explained problem above but now it will not exit out of SAFE MODE
if anybody has any suggestions as to a fix that would be very appreciated....also the menu and back hardware buttons light up but do not work only the home button seems to work and am not sure if this is an effect of safe mode or not...also VOL- seems not to work either
could all of these problems be related to that fatal toilet dunk and will it be worth my while getting these parts fixed or replaced...???
The button problem should appear because of the toilet drop.
Send from my G900F @ Ressurection Remix using Tapatalk.
sp3d00 said:
The button problem should appear because of the toilet drop.
Send from my G900F @ Ressurection Remix using Tapatalk.
Click to expand...
Click to collapse
this much info i did gather from XDA...now the device is back to going all funky again...will only boot if vol+/home button/power button are held together then as soon as it boots the system goes haywire...flickering between all sorts of crap and so fast that i cannot identify anything...only a battery pulls seems to solve that issue...is weird as it was working fine this afternoon straight after i updated to lollipop..for hours it was fine...then funky rom raised it's ugly head and has not gone away...also it is still in safe mode as well....
If you have done this already then boot your phone into Recovery Mode, wipe cache and do a factory reset, I can't remember but I think in stock recovery (I use TWRP so I can't check) but I think there is an option to shut down the phone so if it stays in recovery after the wiping and factory reset select that option, then remove the battery for a few minutes, then replace the battery and reboot the phone.
Hopefully the water hasn't caused any permanent damage, they are only waterproof to a limit and it can get in, the non working buttons could be related to a conflict with 4.4 rom residue software and the new 5.0 software, the wipes will clear this, then if its still not behaving try to re-flash the rom again, if that fails then the water may well have got to it.
Bear in mind the factory reset will wipe all phone data, contact data, etc, basically it will restore it to an out of the box condition.
Related
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
I'm having the same issue. It sounds like a fastboot -w is required to wipe out userdata and cache.
Unfortunately I can't seem to get my PC to recognize my tablet in fastboot mode. I might have to send my tablet back to Samsung to get reflashed.
kolor9 said:
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
Click to expand...
Click to collapse
That has happened to me when I was having battery issues. I was able to keep connecting and disconnecting the charger cable until I got my tab to work again.
yeah might be that as well, i noticed strange behavior for last weeks, suddenly it started draining battery very fast or shutting down in the middle of the battery. running very slow and freezing.
when connected to pc it always goes: connect/disconnect/connect/... (hearing windows sounds for that)
i fully charged that yesterday, will try to boot today.
HOWEVER i was able to get into recovery menu, wipe/delete cache, sdcard, factory reset, etc.
might be that firmware/rom/bootstrap has been fuked up when battery died suddenly?
sharing experience
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
You may need to open up your tab and do the battery disconnect procedure. I finally had enough with my tab and opened it up. So far I am happy again.
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Thanks for the suggestion but it did not work for me...I experienced same problem you mentioned below except I had gone on vacation and my tab battery died and when I was able to recharge it, it just recycles through the Samsung logo!
Tried all the suggestions on this site and no luck so far...I'm guessing it might be time to take it in to Tmobile and see what they have to say, probably not much!
I'm not ever going to get a Samsung tablet again...Asus from here on out!!!
cx5 said:
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
Click to expand...
Click to collapse
ceperz said:
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Click to expand...
Click to collapse
if its gsm go to overcome restocking method
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
It's been few days since ur post. But I'll give it a shot for trying to suggest.
Try holding power button for 8 seconds to properly power off. Then charge it for a good hour before starting the unit.
Else just keep charging it. Standard times are 4 hours to get zero to 100%.
Once my power used till zero and no response what so ever even after charge 5 mins. Finally let it charge 1 good hour & it came back to life.
Good luck.
Regards cx5, on the move via xda tapatalk.
fabricatedhero said:
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Dont see a thanks buttom i appreciate it MAN !!!
If it really happened after installing bad apps it will only wipe recovery mode
I was uninstalling some apps to get ready to back up and flash my phone because my microphone volume was stuck at minimum and no one could hear me. After rebooting my back and multitask (menu) button won't light up or respond. This has happened to me before occasionally. I could fix it by powering the screen off and back on. I believe I read somewhere it had something to do with xposed.
I tried flashing using MOP and my buttons didn't come back so I loaded a TWRP, wiped all partitions, rebooted in download mode and flashed with regular ODIN. Still can't get the buttons to function. Home button works just fine, though.
I tried finding a solution to this but I can't seem to find one. I had the same issue intermittently on my Galaxy S4 but I fixed it by wiping the partitions and reflashing. G900R4 USC variant.
So I went into stock recovery and did a factory reset. It was already as wiped as it could possibly get afaik but I thought I'd try just to see. My buttons lit up in stock recovery so I knew they were getting power. I did a factory reset and low and behold upon reboot my buttons came back.
Did I fix it or is there a circuit starting to fail on my phone and it was just luck? I'm curious.
For the past few months I've been running the Galaxy S4 I9506 on Lineage Os 14.1, I occasionally encountered random bootloops during use where the phone would suddenly die then run into a bootloop as it tried to restart. When it did this, I was able to fix it by removing the battery, waiting a while, then re-inserting it, but I've recently encountered a problem where as soon as I put the battery back it starts bootlooping without pressing the power button. I am also unable to access TWRP or Odin mode as the bootloop overrides it. Is this due to a hardware fault within the phone or is there some way I can still save my S4?
*EDIT*
In the end I was able to find a replacement motherboard and swap it out with the faulty one. The phone once again booted normally and after a re-flash Lineage OS has been working flawlessly ever since. I believe this means the previous motherboard may have just died of old age, will still try the oven trick though.
I recommend flashing the latest stock ROM using Odin, use the phone in a stock configuration to confirm that everything works.
https://updato.com/firmware-archive-select-model?exact=1&q=GT-I9506
Without installing and using the stock ROM, it wouldn't be possible to determine if it is a hardware or software problem.
audit13 said:
I recommend flashing the latest stock ROM using Odin, use the phone in a stock configuration to confirm that everything works.
Without installing and using the stock ROM, it wouldn't be possible to determine if it is a hardware or software problem.
Click to expand...
Click to collapse
Whenever I boot the phone into Odin it will sit in the download mode for about 5 seconds before cutting power and bootlooping again, does this mean that it is a hardware fault in the phone?
ShaunCB said:
Whenever I boot the phone into Odin it will sit in the download mode for about 5 seconds before cutting power and bootlooping again, does this mean that it is a hardware fault in the phone?
Click to expand...
Click to collapse
Could be a power button problem too.
ShaunCB said:
For the past few months I've been running the Galaxy S4 I9506 on Lineage Os 14.1, I occasionally encountered random bootloops during use where the phone would suddenly die then run into a bootloop as it tried to restart. When it did this, I was able to fix it by removing the battery, waiting a while, then re-inserting it, but I've recently encountered a problem where as soon as I put the battery back it starts bootlooping without pressing the power button. I am also unable to access TWRP or Odin mode as the bootloop overrides it. Is this due to a hardware fault within the phone or is there some way I can still save my S4?
Click to expand...
Click to collapse
Seems an hardware issue. The only way I know to give you a chance to boot to os and save your data is to use the trick of hoven. Put the motherboard (whiteout the camera) in the hoven at 200°C for almost 10 minutes. It seems strange but working for me. If you decide to try remember that I am not responsible of any damage!
Regards.
Edit: a thing that you can do to check if the problem is hardware related it is to remove the middle frame and try to boot. If you successfully boot the problem is the motherboard.
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Come on guys! Please don't tell me that I've tried everything and exhausted all the possibilities...
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Nevin1901 said:
If there is still warranty on the phone, then send it in for repair. If there isn't, then I would take it to a repair shop and see what they can do about it. It is wierd that you can enter download mode, but can't flash stock firmware. I think it might be a motherboard problem
Click to expand...
Click to collapse
Unfortunately, there's no warranty and I'm pretty sure no one would repair this kind of failure for a price lower than the price of a used and fully functional Galaxy s8.
Yes, I can enter the download mode and I CAN flash stock firmware, but I can flash only the ones which are newer or the same as the one installed on the phone.
Yes, most probably it's a motherboard failure. In some YouTube videos I have seen people fixing similar issues by replacing the CPU (which I am unable to do by myself). Other suggestion I found on iFixit says that I could soak my motherboard in 99% Isopropyl alcohol and leave it overnight in it (I am going to try this if I get my hands on the alcohol).
BTW: One interesting thing I experienced while flashing the phone without its battery connected is that the phone's screen will go black when you press 'Start' button in Odin, but nevertheless the installation will finish normally and you can track its progress in Odin. At the end you'll need to restart your phone manually.
roberta-xda said:
Hi everyone,
When I tried to restart my Galaxy s8 it entered some kind of hardcore bootloop where I couldn't stop it from looping except by entering the download mode, letting it drain the battery or simply disconnecting the battery. When I exit the download mode it will just continue looping. It is also impossible to enter the recovery menu, which makes things much worse.
I have tried opening the phone and disconnecting everything except power supply (either battery or charger) and screen to see whether some detachable component is failing it (camera, speaker, etc.). But nothing.
I have also tried reinstalling the firmware (BL + CP + AP + HOME_CSC), it installs successfully but it doesn't fix the bootloop. I have also tried two most recent firmware, also without success. Somewhere on the Internet I have found a recommendation to install the firmware from June 2017 which I have tried but it doesn't work anymore because it's not possible to install earlier version of firmware on Samsung phones anymore (since November 2019 I believe).
Now I have started to believe that this could be a motherboard failure but it doesn't really make whole lot of sense because the phone can enter the download mode and reinstall firmware just fine. Or maybe there is a component which can make it able to enter the download mode, but nothing else would work?
Has anyone experienced something like this? How could it be fixed? Any recommendations? Is there any hope?
Edit: The phone has never been rooted, means it is in its original software state (currently on Android Pie with build number G950FXXS8DTC1). Is there any way to install anything on it (custom ROM, TWRP, etc.)?
Click to expand...
Click to collapse
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Just wanted to share a video I found. This is exactly how my s8 bootloops: https://youtu.be/gBlIcAJzgVA?t=5
PS: Obviously, the solution explained in the video didn't work for me.
PS2: This issue started by just restarting the phone. Before the restart it was in a perfect state, fully working, never had any hardware issues. Although there were some software issues introduced by an update (October or November 2019 I think) which made my phone need to restart 2 times to fully boot once if I wanted to restart it or turn it on after it was turned off. But those software issues were solved by a latter software update.
kjaved373 said:
I have an S8 with a similar issue. I can get to recovery menu but following similar steps to above by flashing combination firmware and still got stuck in bootloop. Subscribing to this thread in case anyone has a fix.
Click to expand...
Click to collapse
i know it's already an old comment, but was your phone also completely stock?
Leberkuchen said:
i know it's already an old comment, but was your phone also completely stock?
Click to expand...
Click to collapse
Yeah I believe so.
A couple of days ago. I wanted to check my phone in the morning and it started boot looping when I pressed the power button. Then, after a couple of boots it went into the TWRP recovery. I wiped cache/dalvik in hopes of a quick fix but still boots into recovery.
I can also go into the bootloader but the bootloader is completely unresponsive. It just gets stuck on the "barcodes" option, the volume keys do nothing and adb doesn't see my device when it's in the bootloader. I also tried re-flashing the same ROM I'm using(within recovery) to no avail.
I still intended on using this thing for a couple more years (I have a couple of spare OEM batteries and a spare chasis). Really appreciate any help.
Recovery.log from TWRP
Any flash drive can become corrupted.
Boot loops are commonly caused by poorly coded apps like launchers and power management apps.
Rootkits are always suspect with abnormal boot ups and unstable operation when no other cause can be found.
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
*a drop, water exposure or a ESD event when repairing a phone can cause this... sometimes not immediately.
blackhawk said:
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
Click to expand...
Click to collapse
Can I reflash firmware without the download mode working properly?
Sorry, way beyond my skillset...