Database Users

i9505 Softbrick Odin flash is failing [Resolved]

Hi All, I'm in desperate need of some help. For the past few days I've been going down the road of getting the latest Phoenix ROM working properly and I've been taking a step backwards with everything I've attempted, now I'm stuck at a soft-brick stage on my i9505
My current issue:
I can get into download mode. Not recovery, definitely not boot, only download mode.
Odin correctly identifies the phone but attempts to flash to the phone fail. It spits out the following:
Code:
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone then shows the progress bar completely stalled either at what looks like 99% for small writes (Like my attempt to flash TWRP), or at what looks like 1% (when I flash a full firmware). When I get home tonight I'll list the codes on the screen when it does it but I see a "START", and a "BBA" (I think), but I never get to the "END" command.
Has anyone experienced something similar?
What got me to this stage:
1. Flashed new Phoenix rom v10 upgrading from v9.4.
2. On sleep the cell dropped out constantly and so did WiFi so someone suggested I install a WiFi fix.
3. Installed the modem for XXUGNJ8 (I think). Combined package for LTE and GSM.
4. Every time the modem activated the phone had problems. Locked up when I open the phone app, reboot if someone called me, no sound when calls did "work", and the phone never sleeps and chews the battery after a simple text message.
5. Attempted to revert modem to XXUEMK4 (the other Galaxy S4 still on stock Android 4.3 had this modem). FAILED!
At this point my phone said the last firmware update failed and I was effectively in a softbrick scenario. I can still get into download mode.
6. Attempted to flash Optus carrier firmware 4.4.2 XXUGNH6. This failed, but the download screen changed now and says Samsung Official Firmware on it.
All other attempts to write to the phone have failed.
I've tried a different USB cable.
I've tried a different version of Odin.
I've tried flashing TWRP.
I tried installing Heimidall but have yet to get it working. (Visual studio runtime issues).
I installed Keis just to waste a bit of time.
I tried reinstalling drivers.
I just can't seem to write to the phone. Has anyone experienced anything similar and figured out a fix? When I get home tonight I'll post some pictures / screenshots of the errors I'm getting.
Cheers.

Are you trying to flash an older version of 4.4.2 that you had downloaded earlier?
Flash the LATEST 4.4.2 version for your phone.
"If someone helps, never forget to hit thanks ?"

Latest for my carrier? Or the latest version of stock there is?
By the way for the record here's some more info. Attached is a screenshot of my Odin after it fails. This was after attempting to install Philz recovery.
My phone has the following on the screen:
Code:
Odin MODE
Product Name: GT-i9505
Current Binary: Custom *note this said Samsung Official yesterday
System Status: Custom
Knox Kernel Lock: 0xfffffffc
Knox Warranty Void: 0xfffffffc
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: Enable
and then the bits from the actual download attempt:
Code:
START [224, 1448]
BAR [240,1440]
That's it. The progress bar is sitting at what looks like the 99% mark.

No sure if this will help but I solved my issues by running odin as admin and make sure usb debugging is ticked.

I don't see you tried a different usb port/different pc.
For using heimdall your don't need the frontend interface. You only need to make sure you use the correct drivers for heimdall and then use the terminal to flash the recovery.
"heimdall flash --recovery recovery.img --no-reboot" (it's case sensitive.)

Ok success.
I used the i9505 pit file and re-parition and with that I can successfully flash twrp or philz recovery. Which brought up an error saying non-official firmware detected.
I tried flashing XXUGNJ8 downloaded straight from Samfirmware but it failed. I tried it both with and without repartitioning.
So I tried twrp again and failed.
Then I tried XXUGNJ8 again and it failed but got all the way to the image stage.
I read about swapping cables, drivers, USB ports, well I did all of that to no avail.
Finally I took the entire mess to work and used a new computer there, fresh drivers, fresh everything, and everything worked just fine. I have no idea what's wrong with my computer, but it was not happy.
Thank god these phones are hard to brick. I'm willing to bet my USB connection dropped out while flashing which caused the issue to begin with.

[Q] G900F dead, help me fix it please!

First: Yes i've tried Odin flashing stock rom, recovery and all the other things!
So from the beginning:
My phone unlocked itself in my pocket and some weird things happend (i don't know what).
When I took it out it said that my sd-card could be safely removed
Then it said it was coruppted (I checked it on my laptop and it wasn't)
Then it started to reboot, and suddenly got stuck in bootloop!
When I pulled out the battery and put that in again. it booted black screen with text in the left uppercorner with some things about not being able to boot because there's no XXXX partition and some other things I cant remember.
So I thought, let's try and flash stock rom on it, and did that. Flash failed with error (size) or something.
Then I thought, let's reboot into recovery (How dumb that I haven't thought of that before) When I tried it it just bootlooped trying to get into recovery everytime.
Flashed new recovery, Still the same problem.
Flashed stock rom of another country, It worked but after odin finished and rebooted my phone it tries to boot itself into recovery (bootloop)
So nothing worked...
Download mode says this:
Current binary: Samsung official
system status: custom
Reactivation lock(kk): off
knox warranty void 0x1 (4)
qualcomm secureboot: ENABLE (CSB)
rp swrev: s1, t1, r1, a1, p1
udc start
I really don't know what to do, can you guys please help me?
Thanks in advance.
Donovan Nice

PMed you my Skype. Contact me if needed

Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.

v3rtex said:
Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.
Click to expand...
Click to collapse
Must it be pit only? I tried pit file together with stock ROM but that didn't work

I would try it step by step, so pit only first.
Is there any error message in odin?

Flashed pit file, succesfull. No errors. Phone still stuck in bootloop

Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.

v3rtex said:
Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.
Click to expand...
Click to collapse
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right

donoboy97 said:
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right
Click to expand...
Click to collapse
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...

v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
Recovery + pit works, pulled out the battery, waited a minute or so. Booted in recovery, get's the blue message.. and then bootloops again...

Gonna try nand erase, as you said I have nothing to lose. Wish me luck I guess?

long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work

elliwigy said:
long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work
Click to expand...
Click to collapse
md5's match!

v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard

donoboy97 said:
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard
Click to expand...
Click to collapse
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope

elliwigy said:
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope
Click to expand...
Click to collapse
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!

donoboy97 said:
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!
Click to expand...
Click to collapse
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version

it's taking a while, please hold

elliwigy said:
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version
Click to expand...
Click to collapse
Nope v3.09 did not work, tried redownloaded stock rom, stock rom from another country, and all of them with pit file..

did u dl tar from sammobile or elsewhere?

S5 G900F stuck in a bootloop

somebody can tell me step by step what to do? I'm stuck in a bootloop and i tried to install the stock firmware with odin but it keeps failing Odin says that after i started it, everything is ok and i get a "pass" in Odin but it just keeps rebooting i only can get into download mode, not into recovery mode And when the phone starts to boot, i just get this black screen with the samsung galaxy S5 on it and in the top corner in blue letters "recovery booting ..." and then it goes black and restart ...
Can anybody help me i'm kinda desperate

Hi, try with pit file check your pm´s

israelicky said:
Hi, try with pit file check your pm´s
Click to expand...
Click to collapse
Whatdo i do with the file? Flash it with odin and then? Do i flash a new rom after it?

i tried to flash it again and used that PIT file but still the same result any other suggestions? Or is my phone ready for the recycle bin? :crying:

Flash it whit the rom

Does it say G900F in download mode?

Odin mode
Product Name : SM-G900F
Current binary : Samsung official
System status : Custom
Reactivation lock (KK) : Off
Knox waranty void : 0x1 (2)
Qualcomm secureboot : Enable (CSB)
Ap survey : S1, T1, A1, A1, P1
Secure download : Enable
UDC start
Thats what it says ...

Sounds like something in DATA is corrupted, which ODIN does not wipe
So flashing ROMs with ODIN won't fix it, you need to wipe the phone
Almost the same thing was happening with another member the other day, using ODIN option "Nand erase all" while flashing the ROM to wipe the phone, and then using KIES3 to recover the firmware was their fix
After Nand erase all, the phone would only enter download mode, KIES3 fixed that with the firmware recovery process
http://www.samsung.com/uk/support/usefulsoftware/KIES/
--
Or you could try flashing TWRP with ODIN, and see if you can get into TWRP recovery first, factory reset from there

I tried to put TWRP on my S5 with odin but that didn't work ...
Now i just flashed the phone with a new rom and with "Nand erase all" ticked and then do a firmware upgrade with "Kies" but unfortunately that didn't worked either :crying:

any other suggestions?

In ODIN, uncheck "Auto reboot"
Flash TWRP
When it completes disconnect USB and remove battery to power off
Replace battery and immediately boot into recovery
Volume Up & Home & Power
ANd you need to add more details other than "It didn't work" or we can't help

Ok i did what you suggested and at first it starts up with this on the screen :
Recovery booting .... (in blue letters)
Set warranty bit: recovery (in yellow letters)
then it just reboots without this text on it but it just keeps rebooting ... i dont get to see any thing else but the samsung galaxy s5 powered by android screen ...

And what does KIES firmware recovery say?

With the kies program i get thesame result ... it just stucks in the bootloop ...

No, what does KIES say when you run the firmware recovery?
I'm going to leave you to it, can't help you when you just keep repeating the same thing "Doesn't work"

Im not home at the moment,i will give it another go when im at home and tell you what it sayw

Ok, i opened Kies and searched for that emergency recovery firmware that you talked about but i don't see a option to select my phone??
Here is a printscreen from kies and my phone connected i download mode ...
http://i1360.photobucket.com/albums/r643/Tom_Mutsaerts/Naamloos2_zpskzwqrxly.jpg

Ok, you may close this topic, i brought the s5 to a repairshop and they are gonna check what the could do ... possible even necessary to replace the touchscreen and lcd according to the salesmen :s

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

S7 edge bootloop

Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do

nonechap said:
Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
Click to expand...
Click to collapse
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.

Or you can continue to use Odin which when you plug the USB in will show that a connection is made even though the phone says it's not in download mode.

Cosmic Blue said:
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Click to expand...
Click to collapse
I did an emergency recovery with my phone model and serial, same with kies.

nonechap said:
I did an emergency recovery with my phone model and serial, same with kies.
Click to expand...
Click to collapse
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.

Cosmic Blue said:
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Click to expand...
Click to collapse
it is not under warranty anymore, should i replace the motherboard ?

@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you

rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
In this case, when i flash the rom, should i use the 4 files or only the AP file ?

nonechap said:
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
Click to expand...
Click to collapse
use old odin

rony raj said:
use old odin
Click to expand...
Click to collapse
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)

nonechap said:
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
Click to expand...
Click to collapse
odin v3.09 or 3.12
update bootloader and modem from given first post by me

rony raj said:
odin v3.09 or 3.12
update bootloader and modem from given first post by me
Click to expand...
Click to collapse
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?

nonechap said:
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
Click to expand...
Click to collapse
tell me rom on your device before bootloop
6.0 or 7.0

rony raj said:
tell me rom on your device before bootloop
6.0 or 7.0
Click to expand...
Click to collapse
6.0.1

nonechap said:
6.0.1
Click to expand...
Click to collapse
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/

rony raj said:
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
Click to expand...
Click to collapse
I tried but still nothing, i think i have to replace the motherboard ?

nonechap said:
I tried but still nothing, i think i have to replace the motherboard ?
Click to expand...
Click to collapse
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs

rony raj said:
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
Click to expand...
Click to collapse
After flashing boot.tar, when i run the .bat, it says error: closed
EDIT: i have to enter into the recovery mod and select "adb update" in order to make my phone detected by my computer

Those files are for the S7. Do they work for the S7 Edge also?
Edit - I tried it and it fails in odin. My phone is bricked.
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse

Works !!!
Sorry to revive an old thread but I think it might help people recover from a bootloop with a bit of addtional explanation than initially provided.
So I have an S7 Edge as a backup phone and hadn't used it for a while. Google FRP was activated. I tried to update to a newer firmware through Odin (can't OTA since it's from Tmo and i'm in Canada). Anyways for whatever reason it failed in the middle and I was stuck in a bootloop that wouldn't stop. I tried downgrading, I tried factory, I tried new versions, nothing would do, I'm assuming because of FRP.
So I followed Rony Raj's post https://forum.xda-developers.com/showpost.php?p=71906126&postcount=17 but kept getting stuck. The thing is once you flash the proper Boot.tar file, the phone will appear to still be in a bootloop. You will have to go with the screen (the phone) and the sound of the connection and disconnection from your computer. So basically just sync with the sounds and time it so you open the ''S7 & S7 Edge QUALCOMM.bat'' file at the exact time your phone reconnects and it'll work. I had to do it about 6-7 times before i got it right.
When that is done your phone will restart in download mode. When you do just flash the latest version of the firmware you get from AndroidFileHos*.com or Sammobil*.com. Make sure you select all 4 files in Odin (BL, AP, CP and SELECT CSC HOME for CSC - NOT CSC).
Once all that is done your phone will restart and everything should be fine, well that worked for me
Thanks a lot to @rony raj for putting together the files and the steps to save my G935