I have replaced the cracked display and after the replacement, Samsung logo is stuck on the screen. According to the guy from the repair shop, a firmware update is necessary. So I have downloaded the file from here:
https://www.sammobile.com/samsung/galaxy-note-3/firmware/SM-N9005/TMS/download/N9005XXSGBRI2/244008/ and followed the instructions on the site (install Odin, boot in download mode, start update). The update failed with the following message on the screen:
ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: Official
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, A2, A3, P3
SECURE DOWNLOAD: ENABLE
UDC START
Volume size is too big 122880 < 409600
ODIN: invalid ext4 image
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2288 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have searched XDA forums and found advice to use PIT file. Among others, I've used this one: https://forum.xda-developers.com/showthread.php?t=2503547
After firmware update with PIT file there is the same error in Odin:
Log:
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2288 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now after a reboot following message appears on screen: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
- I have installed "Smart Switch PC" version 4.1.17054_16 (since this is the last one that supports "Emergency software and initialization")
- Opened the tab "Device Initialization"
- search for model name: SM-N9005
- type in serial number
The dialog says: SM-N9005 does not support initializing. Please contact our service center.
Any suggestions on what to do next? I just want a functioning phone, I do not need any custom roms/bootloaders/unlocks. Thank you.
https://www.sammobile.com/forum/threads/35929-SOLVED-firmware-flashing-FAIL-after-hidden-img
https://www.google.com/search?client=firefox-b-d&q=odin+fail+at+hidden.img
Thank you for the tip. This helped me with the error " Firmware upgrade encountered an issue" now I am back at the "Samsung Galaxy Note3" logo. Booting into recovery mode also does not work as the logo stays on the screen with the message "RECOVERY BOOTING...". So I am back at the beginning. When I was troubleshooting the issue I was searching for "Samsung galaxy note3 stuck on logo screen" (and its variations), or searching for error messages from the logs. Maybe I am asking the wrong questions. Is flashing the firmware the right way to fix my problem that was originally caused by replacing the broken display?
just find a stock android 5.0 flash it with odian in download mode. a replacement screen shouldn't do that to your phone unless the screen u paid for is fake or incompatible with your note 3.
Related
Hello guys!
I am on stock 4.4.2
Downloaded stock rom from sm.
Tried to flash - fail at hidden.img.ext
FLASh failed.
Now i can't boot my phone.
Knox is still on 0x0
Kies doesnt recognise my phone to try recovery...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL9_G900FVFG1BNL1_G900FXXU1BNL9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What to do?
The obvious answer is to flash the rom again in Odin.
If no joy with flashing Lollipop try and flash a Kitkat rom and then try flashing Lollipop again.
Try Odin 3.07
I had the same problem with 3.09, spend several hours flashing and downloading the FW again and again. I finally tried with Odin 3.07 and everything is OK.
apmos said:
Try Odin 3.07
I had the same problem with 3.09, spend several hours flashing and downloading the FW again and again. I finally tried with Odin 3.07 and everything is OK.
Click to expand...
Click to collapse
Will try now.
tried with 3.10.0 still nothing
Tried with stock 4.4.2. still the same....and on the other computer too with windows 7
before was doing on windows 8
So...odin 3.07:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL9_G900FVFG1BNL1_G900FXXU1BNL9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
NOT GOOD AT ALL!
I can't flash any rom to G900F with odin, can't boot my phone...constantly getting FAIL (SIZE)!
What to do next?
This is info from the screen:
ODIN MODE
PN: SM-G900F
CB: Samsung Official
SS: Official
RL (KK): OFF
KWV: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV
SECURE DOWLOAD: ENABLE
UDC START
Don't get it.
I have tried SPANISH firmware LOLIPOP 5.0 (unbranded) and it worked!?!
I am on Croatian VIP network, bought it there...tried to flash VIP's 4.4.2 and 5.0
and it failed everytime no matter to ODIN version....
So? What to do next? Why i am not able to flash my branded firmware?
Usually when that message appears in odin it means the the firmware you're trying to flash has not the same partitions as your memory, try to find pit file for your VIP version and then flash again using that file
Well let it fail then remove the cable put it back reset odin check repartition and flash put file.. your phone will work but i have not idea what is tha secure boot and download i am still searching.
Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for your time
Try This
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Uxepro said:
Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for your time
Click to expand...
Click to collapse
Solved. Just flash an unbrand FW on an unbrand phone
billd2439 said:
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Click to expand...
Click to collapse
Will this work on my rooted n90005.
And can you send me a link to step by step rooting guide?
Sent from my SM-N9005 using Tapatalk
Couldn't be certain but I believe if you install an official rom on a rooted phone the root is lost. That would meet it should install no problem and restore the phone to stock.
Hello,
First I was on 4.4.2, then I've switch to 5.0. ( without root priv )
Today I've downgrade from 5.0 to 4.4.2, and my "note 3" bricked!
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNH1_N9005TMNGNL2_N9005XXUGNH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I've download .pit file from here, and my "note 3" got re-partition.
Now I want root my android, but I got this error ( using this tut here )
Code:
NAND Write Start!!
<ID:0/004> FAIL!
I need your help, I want clean (rom, pit, 4.4.2 system) with root for my "note 3- n9005"
Thanks.
your first mistake: updated to loli(s..t)pop.
second: not saved rom creddentials
solution: kies 3 or odin
dancapitan said:
your first mistake: updated to loli(s..t)pop.
second: not saved rom creddentials
solution: kies 3 or odin
Click to expand...
Click to collapse
when my note bricked, I try restore from kies, but I can't
now I need clean .pit and 4.4.2 software with root
a7m3d said:
when my note bricked, I try restore from kies, but I can't
now I need clean .pit and 4.4.2 software with root
Click to expand...
Click to collapse
1. That .pit file is good but you have to flash the correct firmware for it: HERE. Follow the steps of that thread too for flash the firmware correctly.
2. Take out the battery of your device when the process of flashing finish (wait 10 sec.). Put it in again.
3. Boot your device in Stock Recovery and select: Wipe data/Factory reset.
4. Select "Reboot System Now" option then.
5. Root it then with that method you posted b4.
Joku1981 said:
1. That .pit file is good but you have to flash the correct firmware for it: HERE. Follow the steps of that thread too for flash the firmware correctly.
2. Take out the battery of your device when the process of flashing finish (wait 10 sec.). Put it in again.
3. Boot your device in Stock Recovery and select: Wipe data/Factory reset.
4. Select "Reboot System Now" option then.
5. Root it then with that method you posted b4.
Click to expand...
Click to collapse
1- I've download PIT from here, and download firmware from here, and flash the firmware.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
2- when flash finish, I've take out my battery from device. ( I didn't put "auto-reboot" in Odin3)
3- I've Wipe data/Factory reset with Stock Recovery.
4- I've Reboot System.
5- I try to root it with http://androidxda.com/root-samsung-galaxy-note-3-sm-n9005
but the problem:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
a7m3d said:
1- I've download PIT from ...
Click to expand...
Click to collapse
1. Try flashing this custom recovery first: HERE.
2. Flash this FILE via TWRP. Reboot then.
Joku1981 said:
Try flashing this custom recovery first: ONE.
Click to expand...
Click to collapse
I've going to setting, and enable developer mode then I've root my phone again and it's rooted!
but my phone still reboot and reboot (dosen't stop??)
edit; I've done ‘wipe cache partition.’ and it's work now
Please close the topic
The phone would start and all of a sudden shut off and either stay off or it would turn back on but go into the download mode, and very rarely it would turn back on properly, so being the hard headed 20 year old i am i tried to flash it without consulting help first
i have no idea what i did but now the device only loads into download mode (if it even turns on) ive tried to flash it properly now and it comes up with an error
ODIN log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 3431 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Write)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what it says on the phone:
ODIN MODE (HIGH SPEED) {in red}
PRODUCT NAME: SM-N910F {in white}
CURRENT BINARY : Samsung Official {in white}
SYSTEM STATUS: Official {in white}
REACTIVATION LOCK: Off {in white}
KNOX WARRANTY VOID: 0x0 {in white}
QUALCOMM SECUREBOOT: Enabe (csb) {in grey}
RP SWREV: S1,T1,R1,A1,P1 {in grey}
SECURE DOWNLOAD: Enable {in blue}
UDC START {in red}
ODIN: flash write failure {in red}
Downloading...
Do not turn off target!!
{a progress bar that is frozen}(ive left it over night and it hasn't moved an inch)
I know this was me being hard headed and being stupid thinking it is simple but any help would be much appreciated, thank you in advance
PS
the model of the note 4 is :SM-N910F
PPS if i try to flash it again the odin log says:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 3431 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Hope it doesn't have an emmc problem.
Which files did you try to flash or was it just one?
If they latter use samfirmtool to download multiple part stock ROM by checking "binary nature" in its options.
As you are flashing one older ROM an older Odin might hekp as well not to mention other cables/USB ports.
it looks VERY emmc issue
and since you did not seek to get educated first, before doing anything... well you end up here
we try to help
so
read here, maybe it will work for you
Hi there,
The Samsung S7 Edge of a friend got stuck @boot. I have tried to reset and wipe. But that does not solve the problem.
So now i am trying to put on the latest official firmware from Samfw, Smammobile and/or Frija but Odin 3.14 fails.
I think the phone got stuck in an OTA update.
Please help
Here are more details.
S7 Edge SM-G935FD in the Netherlands (PHN), the G935F version should be working as well, its an exynos chipset with dual sim.
In download mode it says on top left:
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock is ON (i cannot go to devevlopper mode to change that)
Secure Donwload: Enabled
Warranty Void: 0
AP: SWREV: B:8 K:6 S:7
I followed all kind of guides on XDA
Get the right Odin 3.14
Get the right Firmware. Samfw.com_SM-G935F_PHN_G935FXXU8ETI2
Using Default Odin Settings
I have a connection to the phone.
This is the ODIN log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4045 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Dekay99 said:
Hi there,
The Samsung S7 Edge of a friend got stuck @boot. I have tried to reset and wipe. But that does not solve the problem.
So now i am trying to put on the latest official firmware from Samfw, Smammobile and/or Frija but Odin 3.14 fails.
I think the phone got stuck in an OTA update.
Please help
Here are more details.
S7 Edge SM-G935FD in the Netherlands (PHN), the G935F version should be working as well, its an exynos chipset with dual sim.
In download mode it says on top left:
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock is ON (i cannot go to devevlopper mode to change that)
Secure Donwload: Enabled
Warranty Void: 0
AP: SWREV: B:8 K:6 S:7
I followed all kind of guides on XDA
Get the right Odin 3.14
Get the right Firmware. Samfw.com_SM-G935F_PHN_G935FXXU8ETI2
Using Default Odin Settings
I have a connection to the phone.
This is the ODIN log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4045 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OH just found this great article
[GUIDE] AN ESSENTIAL GUIDE FOR G935F/FD
AN ESSENTIAL GUIDE FOR G935F/FD DISCLAIMER ☆THIS WILL BE A HUGE WORD WALL, SO DON'T BOTHER WITH THIS IN ADVANCE IF YOU MIND READING LARGE AMOUNTS OF WORDS ON SCREEN :D ☆THIS ISN'T A ROOT GUIDE EXACTLY BUT WHEN YOU READ THIS TILL THE END...
forum.xda-developers.com
Did i read it well, and understand that FRP Lock is ON.. that prevents me to install anyting?
"But if you haven't rooted/enabled OEM Unlock before, this won't work either and you may had to take your phone to a repair shop "