Wife was running CleanRom 2.1 for a week or so. Yesterday she goes to wake the screen and the phone wouldn't wake by pushing any buttons. She pulled the battery and tried to boot the phone with no success. At this point we are stuck with the attached (IMG_01.jpg) image when plugging the phone into a USB port. Plug it into the wall charger and you get the same image however leaving it on this charge for a while brings IMG_02.jpg. Unplugging the phone from the cable results in no power at all to the device. This means no Download/Recovery Mode from battery only.
On to plugging into the computer. By quickly inserting the cable and pressing the keys to enter Download mode i can successfully enter Odin mode and flash files. From here i have flashed full stock images and still no full boot success.
So, next I can boot into recovery (sometimes, again only plugged in) I was able to wipe following stock odin flash. After rebooting from recovery i can see the samsung and galaxy sIII boot logos then the stock VZW 4GLTE boot animation(with sound). once i get to the language select screen and move to activation the phone shuts off and goes back to the empty battery with a circle in the center (IMG_01.jpg).
So far I have tried:
1. Different USB ports/cables - Incl. OEM (connection appears to be fine to the system either way though)
2. Flashing full stock images in odin with PASS results.
3. Ive tried to unbrick using the methods found here: http://forum.xda-developers.com/showthread.php?t=1840030
Im looking for any help or suggestions on moving forward here. Overall there is no power to the device without plugging in the cable. I have tried another battery still with no power. I have thought about flashing the insecure bootloader however i have not found a way to do this in Odin if it is possible at all.
ODIN MODE (Reads as follows)
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLED
Thanks in advance for any help at all. If you share a similar problem please post as well, may help narrow down the cause and eventual fix.
With my ability to access ODIN MODE and boot to the setup screen, does this mean i have a good chance at recovery?
Looks like you might have a bad battery.
I tried another battery and that's not working.
This morning I had a green LED (charged) light. I woke the screen to the lock screen and it seemed to stay on. I couldnt get past the activation since the sim is no good. ( I had to deactivate it with vzw to activate a temp phone.) I eventually pulled the plug to see if it would hold charge but it just shut off and I wasn't able to boot up again.
The same thing happened to my first s3. You will need to get a replacement.
So my phone (S6, SM-G920F) crashed recently (completly out of the blue, I was opening a YouTube-Link I've sent myself via the PC) and I can only access the Download Mode, but not the Recovery mode.
What I've tried (In order):
-Flash any ROM (DTM, DBT, VIA [Different Carriers for Germany, I dont know if mines branded]), only the DBT (Universal) ROM even flashed, others just failed in Odin3, phone still doesn't work
-Install TWRP
-Use SmartSwitch (After some failed ROM-Installations, it showed the following Message on the screen of my phone:
Spoiler
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
, Smart Switch didn't even work. I've installed Samsung USB-Drivers first, then installed Smart Switch. If I try to use the Emergency Recover Function, Smart Switch just freezes up entirely
Does someone here know how I can fix my device?
Someone? D:
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: XEF
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone in download mode.
After that, press Start. When Odin done the installation, phone will restart. When it is restarted, disconnect the cable.
After 1-2 minutes, phone will boot up as completely refreshed device.
Even this method doesn't fix your device, then you need to replace your motherboard.
Thank you so so much, it worked like a charm,
Your tutorial was my last chance, and by accident i found this thread who gave me the magic solution (sorry for my bad english, it is not my native language)
Cheers !
Thanks for providing the above detailed instructions forumber2. Apologies for chipping in on the thread, but i had almost exactly the same issues at the iamflee but with one key difference - my wife had dropped the phone down the toilet first! She retrieved the phone immediately powered off, sim card out etc. and left it in a bag of rice for a week to dry out. It wouldn't turn back on at all. I tried all combinations of buttons and nothing, until I plugged it into my laptop and found I could get it into Download mode (but not recovery or to boot).
I tried lots of different ROM's/ TWRP/ bootloaders etc. but no joy, and then came across your answer above.
I followed it to the letter and Odin completed successfully, however the phone did not reboot at the end, it simply turned off, and will not turn back on. I can get it into Download mode but that is all.
Please can someone confirm what I think I already know, that the phone is goosed and I need to move on and stop spending hours trying to get it to work again! Or is there one last glimmer of hope with something else that I can try.
Thanks,
Matt
I am aware this does not contribute to the problem, but may give context.
Currently, I am stuck with an Samsung Galaxy S6 SM-G920F, which I am told 'randomly restarted' and since then was stuck on the Samsung boot screen. After the battery finally reached zero, it became stuck on the battery charging screen.
I have been able to force the phone to restart using either (Power + Vol Down + Home OR Power + Vol Down), but I am still greeted being stuck on the Samsung boot screen. Furthermore, I cannot boot into recovery mode (P + Vol Up + Home), but I can boot into download mode. However, Samsung Kies 2.6 is left on 'Connecting' in perpetuity without giving an error of any kind. I have installed the drivers provided and Windows detects the phone as a 'Gadget Serial'.
So, to clarify:
+ can boot into download mode
+Windows can detect the phone
- cannot boot into recovery mode
- stuck in boot loop
- Samsung Kies stuck on 'connecting'; hence emergency recovery is out the question
- Odin cannot detect the phone in download mode
I would conclude this SM-G920F motherboard has failed, or partially at least
same issue
safesploit said:
I am aware this does not contribute to the problem, but may give context.
Currently, I am stuck with an Samsung Galaxy S6 SM-G920F, which I am told 'randomly restarted' and since then was stuck on the Samsung boot screen. After the battery finally reached zero, it became stuck on the battery charging screen.
I have been able to force the phone to restart using either (Power + Vol Down + Home OR Power + Vol Down), but I am still greeted being stuck on the Samsung boot screen. Furthermore, I cannot boot into recovery mode (P + Vol Up + Home), but I can boot into download mode. However, Samsung Kies 2.6 is left on 'Connecting' in perpetuity without giving an error of any kind. I have installed the drivers provided and Windows detects the phone as a 'Gadget Serial'.
So, to clarify:
+ can boot into download mode
+Windows can detect the phone
- cannot boot into recovery mode
- stuck in boot loop
- Samsung Kies stuck on 'connecting'; hence emergency recovery is out the question
- Odin cannot detect the phone in download mode
I would conclude this SM-G920F motherboard has failed, or partially at least
Click to expand...
Click to collapse
I am having the same issue with the same terminal, did you manage to solve it?
safesploit said:
I would conclude this SM-G920F motherboard has failed, or partially at least
Click to expand...
Click to collapse
either that or the charge port
paublouska said:
I am having the same issue with the same terminal, did you manage to solve it?
Click to expand...
Click to collapse
was your phone submerged in water at all?
I have the same issue as the OP. J700F (J7-2015) stuck in boot loop.
+Charges
+Turns on but stucks on boot logo
+Can enter Download mode
+does show up in ODIN
-Cannot access recovery mode
-Cannot turn the phone on obv.
-Has FRP lock but I have the phone passcode and email (no email password duh)
Now I downloaded the correct firmware for my region (KSA; do I need to use XEF?) and connect my phone in download mode, select the files. now when I press start, it fails in ODIN and shows "Custom binary(boot) not allowed due to FRP" (I may have used wrong wordings but it seems it cannot install firmware due to FRP lock)
Now what am I looking at ?
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not
Device: P3110
ROM: cm-13.0-20160517-1900-UNOFFICIAL-espressowifi (Android 6.0.1)
I know this is an old thread but I have seem some recent activity and I need some help!
I have been using TWRP 2.8.7.0 successfully many times. I noticed a newer version on https://dl.twrp.me/p3110/twrp-3.0.2-0-p3110.img.html. I flashed 3.0.2-0 with odin and got a flash error. Now I am stuck at boot with with "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". I tried to re-flash the current recovery while the Download screen was still active but the connection dropped and odin could not see the device. I killed odin, restarted a new odin session and nothing. I also tried reconnecting the USB cable and even tried different ports and different versions of odin. Noting. The device is no longer seen by my PC - obviously including adb, Odin or Kies. I have tried to power off the device and boot to both Download Mode and Recovery. The device continues to reboot every time to the same message as above. I can't get it to power off completely even after holding the power button alone many times and also trying vol-up and vol-down. There are slightly different amounts of time that it take to reset the screen while holding the power button, some shorter and some longer.
- Tried releasing the power button during both the shorter and longer reboot cycles. Same result.
- Held the power button down for over a minute and longer. Same result. It just rebooted to the above message.
If I can get to download mode I think I can re-flash the original recovery with odin and then restore a recent backup with TWRP, if necessary. I can usually figure these things out but I am at a loss. Any suggestions would be greatly appreciated.
-djlman
Systematically unplug the device when pushing buttons to select the boot mode
So I have Galaxy S7 (Flat). It had installed TWRP with Magisk on stock Android. I decided to install LineageOS (https://forum.xda-developers.com/t/rom-q-s-lineageos-with-microg-for-samsung-s7-flat-edge.3921094/) (clean install using TWRP) and it installed successfully, everything was fine, I've turned my phone off and on few times and system was booting without any problems.
But then I decided to boot into TWRP (using key combination) to install magisk and... it's stuck on loading screen forever.
I can't even turn it off ! And my phone is getting hotter and hotter. Please help !
I can't turn it off, because simply holding power button doesn't do anything.
I can restart it by holding power + volume down ,but it just opens TWRP again.
I've read I could boot into Maintenance Boot Mode ,but it requires to turn off a phone, which I'm unable to do.
Only thing I am able to do is to boot into Download Mode, but it doesn't change anything (still cant turn off phone in this mode)
Should I try to disassembly the phone and take out the battery manually? I don't really see any other option.
Did I bricked my phone ?
@edit
I have backup of stock system made by TWRP, but it doesn't change anything as I cant use TWRP.
I didn't install LineageOS custom recovery.
Ok, so I left phone overnight to deplete the battery. And it didn't work ! I thought that battery is dead and phone is off, but the moment I've plugged the power cord it automatically turned on into TWRP screen, like a zombie !
However I've solved the problem. As I was able to get phone into Download Mode (by holding power+volume down+home) I used Odin. I've installed newest Odin on PC, Samsung USB drivers and flashed the newest TWRP tar. Although it was scary, I was almost sure I've bricked my phone. Adb/fastboot were not detecting the phone.
And after re-flashing TWRP everything works fine. Also LineageOS booted like a charm, it stay intact.
So, it seems that installing LineageOS somehow corrupted my TWRP, despite that I un-ticked the option to install LineageRecovery ,so technically it shouldn't mess with it at all.
Anyway, problem solved.