Bootloader for SM-N910K 5.1.1 - Galaxy Note 4 Q&A, Help & Troubleshooting

I am downgrading my Korea set of Note 4 SM-N910K where I met the error of SECURE CHECK FAIL : (BOOTLOADER)
I tried searching on the web for SM-N910K Bootloader but to no avail.
Are there any other Bootloader versions that I can use?
Below are the details of my phone information and the error I am facing:
My Phone Information: Screenshot attached
Firmware version that I am trying to downgrade to: N910SKSU2DPF4_N910SSKC2DPF4_N910SKSU0DPF2_HOME.tar
Odin version used: Odin3-v3.10.6
Odin Error:
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note4 Error:
ODIN MODE
PRODUCT NAME: SM-N910K
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRENTY VOID: 1
AP SWAEV: 2
SECURE CHECK FAIL : (BOOTLOADER)

lruihao said:
I am downgrading my Korea set of Note 4 SM-N910K where I met the error of SECURE CHECK FAIL : (BOOTLOADER)
I tried searching on the web for SM-N910K Bootloader but to no avail.
Are there any other Bootloader versions that I can use?
Below are the details of my phone information and the error I am facing:
My Phone Information: Screenshot attached
Firmware version that I am trying to downgrade to: N910SKSU2DPF4_N910SSKC2DPF4_N910SKSU0DPF2_HOME.tar
Odin version used: Odin3-v3.10.6
Odin Error:
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note4 Error:
ODIN MODE
PRODUCT NAME: SM-N910K
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRENTY VOID: 1
AP SWAEV: 2
SECURE CHECK FAIL : (BOOTLOADER)
Click to expand...
Click to collapse
Hi!
This Bootloader collection should work.
Although I'm sure it should work, please read the instructions and the info on the page I linked carefully.
Regards,
Vygravlil

Related

[Q] Unsupport dev_mode in bootloader

Hi
I have I9505XXUAMDM firmware installed and tried to install I9505XXUAME2_I9505OXXAMDB_NEE.
When device is in download mode and I'll start installing new firmware with odin, it stops immediately and shows this in odin (both 1.85 and 3.07):
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed (succeed 0 / failed 1)
and this in device:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
START [224, 1440]
Unsupport dev_type
Tried also differen usb port. Using original cable. After that I'm able to boot back to old firmware. Any idea what's going on?
Hi,
I used Odin 3.04 to root my phone.
All went smoothly and without a hitch.
Sent telepathically from my S4
Thanks, got it working with 3.04.
Sent from my GT-I9505 using Tapatalk 2

Samsung Galaxy S4 (I9500): Bricked After Trying To Install Custom Recovery

Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. After several failed attempts I find some software on the Play store that seems promising. Long story short, I no longer have a functioning recovery partition, and my phone will always try to boot into recovery mode unless I boot in Odin mode.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is also factory unlocked.
I did notice however that the text in the top left when in Odin mode says it is a SGH-I337
The full text:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!
Edit: Added phone error

Troubleshooting Downgrade of N910K from 6.0.1 to 5.1.1

I am holding on to Korea version of Note 4, SM-N910K.
I am trying to downgrade it to 5.1.1.
I downloaded my firmware via sammobile, and it is version N910SKSU2DPF4_N910SSKC2DPF4_N910SKSU0DPF2_HOME.tar.
However, Odin gave me this error when I Start:
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my Note 4, I am seeing this error:
ODIN MODE
PRODUCT NAME: SM-N910K
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRENTY VOID: 1
AP SWAEV: 2
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
May I know what have I gone wrong?
Thank you
lruihao said:
I am holding on to Korea version of Note 4, SM-N910K.
I am trying to downgrade it to 5.1.1.
I downloaded my firmware via sammobile, and it is version N910KKTU1COI2_N910KKTC1COI2_N910KKTU0COI1_HOME.tar.
However, Odin gave me this error when I Start:
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my Note 4, I am seeing this error:
ODIN MODE
PRODUCT NAME: SM-N910K
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRENTY VOID: 1
AP SWAEV: 2
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
May I know what have I gone wrong?
Thank you
Click to expand...
Click to collapse
Restart pc and Try different usb cable.
Trex888 said:
Restart pc and Try different usb cable.
Click to expand...
Click to collapse
Hi, I tried restarting my PC and changing cables. But I am still seeing the same error. I have attached my screenshot about my phone information in the next post.
My Phone Information: Screenshot as attached
Odin version: Odin3-v3.10.6
I am now seeing the error SECURE CHECK FAIL :BOOTLOADER
I tried searching for SM-910K 5.1.1 bootloader but to no avail
lruihao said:
My Phone Information: Screenshot as attached
Odin version: Odin3-v3.10.6
I am now seeing the error SECURE CHECK FAIL :BOOTLOADER
I tried searching for SM-910K 5.1.1 bootloader but to no avail
Click to expand...
Click to collapse
I have the the phone note4 n910k. It have unknown error . Phone restart each 30 seconds. I tried many methods. Download 6.0.1 official rom and custom roms. I tray to downgrade to 5.1.1 but I can't. Please any help in this field

galaxy s4 I9505 soft bricked odin fail

Hello.
Today i tried to flash the stock firmware I9505XXUHPK2 BTU again because i was trying out some custom rom found on xda but decided to get back to stock.
After wiping my current os by TWRP i went to download mode and flash the firmware but failed.It says
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Now my custom recovery TWRP is gone and it shows
odin mode
product name: gt-i9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty viod: 0x1
csb-config-lsb: 0x30
write protection: enable
eMMC burst mode enabled
please help.TIA
Flash again without the pit file. A pit file is needed if Odin can't read the memory chip's partition table.
Also try using different usb ports and usb cables.

S7edge stuck in Boot, need help in flashing firmware with Odin

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 "

Categories

Resources