My Wife's Galaxy S8 randomly cut off this morning.
Nothing happens unless its plugged into a power source.
When I got hold off it and plugged it into the wall I managed to get it to turn on using the force reboot keys (Volume Down+Power).
It would boot up and then after about 30 secs shut off.
I then booted into Recovery Mode.
Cleared Cache.
And it kept booting back into recovery mode.
Formatted to factory settings.
And it kept booting back into recovery mode.
Tried flashing a firmware update via SD card
And it kept booting back into recovery mode.
THEN I downloaded the firmware from Sammobile.com
Used odin to flash and it read as a success, but NOW
It boots into the "An error has occurred while update the device software. Use the Emergency recovery function in the Smart Switch PC software."
That software says it cannot communicate with the phone though.
So I tried to flash via odin 1 more time (booting into DL mode, getting the error message, and trying anyway).
Now it fails.
Doe anyone have ANY suggestions? I have googled and searched this forum high and low, but am really lost now.
Is the device a complete gonner or is there a chance that I can still recover?
Any and all suggestions are GREATLY appreciated.
jduplooy said:
My Wife's Galaxy S8 randomly cut off this morning...........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Related
Greetings everyone, I am a new member and hope to become more involved in the community.
I have installed many custom ROMs on my Galaxy Note 3 SM-N9005 in the past. On my latest attempt to install a custom ROM the recovery software went all funny. The phone would turn on and boot directly into recovery mode (displaying the text "RECOVERY BOOTING... RECOVERY IS NOT SEANDROID ENFORCING. Set Warranty Bit: Recovery"). It wouldn't go any further, meaning that I never get to see the actual menu where I would be able to clear cache, factory reset or install firmware. It then immediately dies and starts up again into the same screen. I tried using all the hardware buttons (i.e. booting into safe mode and recovery mode), the phone doesn't react at all. When plugging it into a PC there is also no reaction on the PC. The phone simply continues to boot into the recovery screen and then die before reaching the options menu.
PLEASE HELP, I have been trying to fix the issue for two days now. Any advice would be highly appreciated!
Hi, thank you for using XDA Assist. Can you boot into download mode? It sounds like you'll have to flash the stock firmware in Odin. If you run into problems you can ask for help herehttp://forum.xda-developers.com/galaxy-note-3/help
jd1639 said:
Hi, thank you for using XDA Assist. Can you boot into download mode? It sounds like you'll have to flash the stock firmware in Odin. If you run into problems you can ask for help herehttp://forum.xda-developers.com/galaxy-note-3/help
Click to expand...
Click to collapse
Originally the phone would not boot into download mode at all. It was essentially hard bricked. After a couple hours of messing with it, trying to get some kind of reaction out of the device, I managed to get it to boot into download mode. I actually managed this by pulling out the battery and pushing Power + Volume Down + Home whilst almost jump starting using the battery (connecting the battery connectors without fully putting the battery in to the phone). This managed to wake the phone into download mode similar to what a USB Jig would have.
Solution was found purely by luck.
Thread closed.
So this morning I was trying to unroot my phone and return it to stock. I found a ROM and was going to use TWRP to flash it on and then replace the recovery with stock... except the ROM I found soft bricked my phone. OK not ideal but found a work around in the Sideload function.
I downloaded ViperROM and it was copying across but got stuck on 7% for ages. The screen was black but vibrating to the power button. After ages I assumed it has crashed so I yanked out the cable and tried to turn my phone off and on again... it doesn't turn off. It just vibrates away when I press the top button. So not only do I have a phone with no OS, I can't get it to turn off and on again.
When I reconnect it to my computer and enter adb devives I can see it's still in Sideboot mode. When I try to "adb reboot bootloader" I get "error: closed".
Any ideas on how I can at least get my phone to load the recovery again?
Please help!
Boxy89 said:
So this morning I was trying to unroot my phone and return it to stock. I found a ROM and was going to use TWRP to flash it on and then replace the recovery with stock... except the ROM I found soft bricked my phone. OK not ideal but found a work around in the Sideload function.
I downloaded ViperROM and it was copying across but got stuck on 7% for ages. The screen was black but vibrating to the power button. After ages I assumed it has crashed so I yanked out the cable and tried to turn my phone off and on again... it doesn't turn off. It just vibrates away when I press the top button. So not only do I have a phone with no OS, I can't get it to turn off and on again.
When I reconnect it to my computer and enter adb devives I can see it's still in Sideboot mode. When I try to "adb reboot bootloader" I get "error: closed".
Any ideas on how I can at least get my phone to load the recovery again?
Please help!
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
You did not mention the device name. However,
There is a general forum for android here https://forum.xda-developers.com/android/help where you can get better help and support if you try to ask over there.
Good luck.
Vivek_Neel said:
Hi, thank you for using XDA assist.
You did not mention the device name. However,
There is a general forum for android here https://forum.xda-developers.com/android/help where you can get better help and support if you try to ask over there.
Good luck.
Click to expand...
Click to collapse
Ahh sorry. My fault, I thought this was the Android one. And completely dumb move on forgetting the phone! I'l try my luck over there.
Thanks,
Hey guys I really need some help here. I bricked my brand new phone after downloading and running the samsung debloat app (https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en) I chose the the one click option to debloat the phone and thought everything was cool. I did not disable and other apps at all. Later that night the phone was around 25 percent so went to put it in extreme power saving mode and boom the phone goes into a endless bootloop. I reset the phone and and the phone wont boot up past the verizon logo. I tried putting the phone in safe mode and still nothing... I'm assuming that the app disabled a system setting that is linked to the extreme power saving mode.
If you can get into download mode just re-flash the firmware with Odin. There is a thread in the Development forum that has the firmware files. Good luck. I'm sure it'll be fine, you'll just have to setup the phone again. Here is the thread: http://forum.xda-developers.com/showthread.php?t=3214560
You probably need to flash the full firmware file.
Press volume up, home, and power at the same time to go into recovery and do a factory reset. If you can't, or that doesn't work, try Odin as described in the previous post.
Sent from my SM-N920V using Tapatalk
I tried to root my sgs6 with an CF auto root. This didn't work because after the first reboot of my Phone I got the message:
"Recovery is not seandroid enforcing"
I've been looking on the internet and have seen several options which didn't work, including:
- Getting into recovery mode (home + on/of button + volume UP). This doesn't work somehow.
- Try to install stock firmware.
- Retry the same root
- Try a different root.
Also; connecting via Kies/Smart Switch gives me the reply that the S/N isn't valid. This however, is not true.
The biggest problem that I seem to have is connecting my phone to my computer properly. And I can't turn on 'USB debugging' anymore (I turned it on when I started with my root).
So maybe my first question is: How can I get my phone to connect with my computer properly?
And after that; How can I fix the failed root.
Additional info:
Model name: SM-G920F
Android 5.1.1. before I tried to root my phone.
If additional information is required, please let me know.
Thanks in advance.
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s6/help
The experts there may be able to help. Good luck.
Not an expert, but I've got the same message in the top left corner on the bootscreen after installed TWRP trough Odin and flashing adam-kernel.
Does not interfere with my phone working though. Even SmartSwitch still recognises it. Maybe wrong version of autoroot?
We found the solution:
We downloaded the original stock firmware and installed it through odin. Some things we encountered during the solving:
- It failed on the hidden.img
- We had to extract that file and load it seperatly through odin.
At that point the phone kept resetting, but after removing the cable from the computer and charging it with the normal charger it booted like normal again. The android sign (which we saw before but the phone went rebooted all the time) stayed in the screen and after a couple of minutes it started installing.
After 10-15 minutes the phone worked again!
Tnxs for your efforts!
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
lexlex121 said:
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
Click to expand...
Click to collapse
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I don't understand how to get into recovery mode. The phone, when the charger plugs in, attempts to boot all the time.
I know the Recovery mode key combo but I have no idea to power off this phone. I've let the battery run.