Samsung Galaxy S6 Edge is bricked - Galaxy S6 Edge Q&A, Help & Troubleshooting

Dear Members help is needed!
The device was running 5.1.1 version and upgraded to 7.0 with FOTA.
Then the device start to stuck and restart until I got "SAMSUNG GALAXY S6 edge powered by android"
And stuck at this screen forever (NO BOOTLOOPS).
Things i tried:
1. Flash with ODIN same ROM version and downgrade versions (Didn't helped)
2. Smart Switch restore, it finished successfully but Didn't helped (Same screen)
3. TWRP ODIN and install custom ROM (Didn't helped)
4. no-verity-opt-encrypt-5.1 install (Didn't helped)
More Details:
1. Cannot turn off the device, just when i'm in TWRP and pressing POWER OFF
(WHEN USB CABLE IS CONNECTED TO DEVICE IT START AUTOMATICALLY!)
2. Device Manager recognize device as "SAMSUNG Mobile USB Modem" under Download Mode
3. TWRP is the only thing that working as recovery
(After installing Original ROM Recovery doesn't works)
4. When switching to ADB Sideload device manager recognize as SAMSUNG Android ADB interface.
5. When i'm in TWRP PC shows just Internal Storage.
Any other ideas to make this phone to work?

Related

[Q] Can't Get Into Download Mode

Hi guys, I'm in the process of installing CM 10.0.0 on my at&t galaxy note as per Quincyatt Info on Cyanogenmod wiki. I'm having trouble pushing the cm.zip onto my sdcard via adb. When I try to get into download mode in order to put zip with cyanogenmod on my sdcard I get a screen that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The play by play is:
1) boot phone by holding Volume Down while plugging in microUSB.
2) Receive "Warning!! A custom OS can cause critical problems in phone and installed applications..."
3) press Volume Up to continue to download mode
4) screen goes to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The steps I followed on the wiki:
1) Get and setup Heimdall Suite 1.4RC2
2) Flash ClockworkMod Recovery 6.0.3.1-quincyatt onto my phone
3) I powered off
PS when I try to "adb push cm-10.0.0-quincyatt.zip /sdcard/" I get "error: device not found," which I assume is because my phone, while plugged in, is not in download mode.
PPS When I try to go directly into CWM with volume up + volume down + lock/power it takes me to the "Firmware upgrade encountered an issue.."
i had this same issue about a month ago...
-
I booted my phone to this message: Warning!! A custom OS can cause critical problems in phone and installed applications...
Then plugged the usb cable to my phone and ran Odin.and flashed with pda.tar file
Then rebooted the phone and my phone was able to get to download mode.
dubsteps said:
i had this same issue about a month ago...
-
I booted my phone to this message: Warning!! A custom OS can cause critical problems in phone and installed applications...
Then plugged the usb cable to my phone and ran Odin.and flashed with pda.tar file
Then rebooted the phone and my phone was able to get to download mode.
Click to expand...
Click to collapse
Yep. Thanks!
For the record:
I used Odin to flash a stock I717 kernel (provided by da___g) and then proceeded with the cyanogenmod wiki's instructions. In order for my computer to see my phone so it could push files via adb I had to be in ClockWorkMod. My phone was non-functional (could only go into download/recovery mode and CWM) until I flashed CM10 with CWM.
Why push a zip file with adb? Just put it on your sd card by data cable or by mailing it to yourself or by download.
But then you have to be able to get into recovery. . .

[Q] Can not get rid of stock recovery despite ODIN successfully flashing device

Hello,
I recently got a used Galaxy S3 I9300. I wanted to install temasek's UNOFFICIAL CM12.1. I already installed CWM on my old Galaxy S2.
Now I got a ridiculous problem; I cannot get CWM or TWRP installed via Odin. This is what I did, in every detail:
a) Turn on USB Debugging (not even sure if necessary)
b) Started in DOWNLOAD-MODE by Voldown+Home+Power
b1) Funnily, it already confirms that I tried to install "Custom Binary Download" 4 times but otherwise is unimpressed. Current binary is still "Samsung Official".
b2) I connect via USB and start ODIN 3.10.7 in Admin mode.
b3) It recognizes the telephone, I have "Auto Reboot" and "F. Reset Time" selected, nothing else. Then I select the .tar I want (i tried "twrp-2.8.6.1-i9300.tar" and "CWM_6.0.4.7_Touch_GT-I9300.tar"), AP box is checked.
b4) I press start, Odin says that everything is fine and signals "Pass".
c) Now, when I start into recovery mode by Volup+Home+Power I still land in the default recovery. This is really annoying.
What am I doing wrong?
Thanks a lot in advance
Greetings
untrue

FIX for bricked Phone because of wrong model of recovery

Hello! NYT here and im gonna show you how to fix your bricked phone because of installing wrong model of recovery
Example of this scenario:
I installed Grand Duos model instead of Grand 2 Duos model and my phone is stuck in download mode.
Needs:
-Odin3
-Computer
-USB Cable
-Phone (obviously)
-[IMPORTANT]Phone's
information (model number and model only)
-Correct model any of the custom recovery
Fix for this problem:
The problem wont affect anything on the phone's internal and external storage.
1.install odin on your computer
2.download correct custom recovery model. It can be Philz, CWM or TWRP
3.connect phone via USB cable on the computer
4.open ODIN (ODIN3)
5.select AP or PDA
6.select the downloaded custom recovery
7.start flashing it (change settings when told on the instructions of the recovery)
8.turn into recovery
[If it doesnt work or launch try this]
9.As if the problem above happened, repeat doing recovery combination (For me its 3 times doing the combination)

Bricked Samsung Galaxy Grand Neo (GT-I9060)

I rooted my Samsung Galaxy grand neo using kingroot apk successfully. I wanted to install the twrp custom recovery to flash some custom roms. When I install it through the rashr (or something similar) app it will so successfully flashed and show go in recovery,when i go in recovery mode the screen got stuck at the Samsung logo. I am unable to enter the recovery mode or get into the normal phone features. Only download mode is accessible.And also my phone is not connect with pc in download mode. I have already install SAMSUNG USB DRIVER to pc. I think my phone is soft-bricked. Please help me out!!
THANKS IN ADVANCE...

Galaxy S7 Edge soft-bricked / Odin gets stuck

Hello androids, I have a big problem or a good challenge, depends on your optimism. I've been looking for and trying solutions for hours and hours, but I think I've come across a wall and I need your help:
Originally I wanted to root my s7 Edge / SM - G935F (OS Marshmallow 6.0.1) by following a tutorial using an autoroot ROM for this phone. I remember I had USB debugging and OEM unlock enabled. I also installed the USB / ADB drivers correctly.
I used Odin v3.11, since they recommended using it for this mobile and MM 6.0.1. According to Odin, the rom was installed successfully, but my phone entered a loop with the Samsung logo and "RECOVERY IS NOT SEANDROID ENFORCING". Something failed in the process and I decided to install a S7 Edge stock ROM in 8.0.0 from SAMMobile (this one) with Odin v3.13 using HOME_CSC so that I don't lose certain data
Unfortunately everything was going well until just at the end when "hidden.img" did not process correctly and resulted in FAIL. I've been since then stuck with this error:
"An Error has occurred while updating the device software. Use the Emergency Recovery in the Smart Switch PC Software."
It won't even turn off. From there I can only access the Download Mode and neither the Smart Switch or the ADB & Fastboot console won't detect the device. Odin does recognize the phone, but every time I try to install a rom, the log gets stuck in "SetupConnection ..".
I have tried a bunch of solutions such as removing the "hidden.img" from the package, reinstalling the drivers, changing the USB port, changing Odin's version, installing only the BL, etc., but nothing shows progress...
I'm sorry if during the process I managed to do some stupidity that I am not aware of. Other phones I have never had problems, but now I feel defeated and lost. I need a savior! :crying:
Any way to make Odin work, ADB detect my device or access a working bootload? Thanks in advance!

Categories

Resources