I have a Sprint Galaxy Note 3 that I've apparently managed to softbrick. This happened after I attempted to flash it back to a rooted stock ROM so that I could update the PRL (as I was having no luck trying to do it manually). Unfortunately, as this was not originally my phone, I don't know what exactly was installed. The last ROM I remember seeing on the phone was a nightly build of PAC-ROM from March. I'm not sure what kernel it's running.
(I didn't realize that downgrading would softbrick the phone... I've only ever upgraded my ROM before. If it matters, I /think/ it's a 16 gigabyte phone, but I'm not sure.)
It comes up into a screen that says "Firmware update encountered an issue. Please select recovery mode in Kies & try again."
Above that, it says
ODIN MODE
PRODUCT NAME: SM:N900P
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, 1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
I have tried:
using kies (couldn't find the device)
following the directions @ galaxynote3update.com/fix-bricked-samsung-galaxy-note-3-unbrick-recovery-guide but I don't understand how to create a PIT file and I'm hesitant to use the one I found on XDA because it's for the 32 gigabyte version of the phone.
downloading Odin 3.09 and attempting to flash back to stock*
These are the messages I got when I tried to flash back to stock with Odin.
<OSM> N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
)
If anyone has any ideas, please help. Tyvm in advance.
http://forum.xda-developers.com/note-3-sprint/general/how-to-restore-nk4-update-to-lollipop-t3086965
saveyoursanity said:
I have a Sprint Galaxy Note 3 that I've apparently managed to softbrick. This happened after I attempted to flash it back to a rooted stock ROM so that I could update the PRL (as I was having no luck trying to do it manually). Unfortunately, as this was not originally my phone, I don't know what exactly was installed. The last ROM I remember seeing on the phone was a nightly build of PAC-ROM from March. I'm not sure what kernel it's running.
(I didn't realize that downgrading would softbrick the phone... I've only ever upgraded my ROM before. If it matters, I /think/ it's a 16 gigabyte phone, but I'm not sure.)
It comes up into a screen that says "Firmware update encountered an issue. Please select recovery mode in Kies & try again."
Above that, it says
ODIN MODE
PRODUCT NAME: SM:N900P
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, 1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
I have tried:
using kies (couldn't find the device)
following the directions @ galaxynote3update.com/fix-bricked-samsung-galaxy-note-3-unbrick-recovery-guide but I don't understand how to create a PIT file and I'm hesitant to use the one I found on XDA because it's for the 32 gigabyte version of the phone.
downloading Odin 3.09 and attempting to flash back to stock*
These are the messages I got when I tried to flash back to stock with Odin.
<OSM> N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
)
If anyone has any ideas, please help. Tyvm in advance.
Click to expand...
Click to collapse
op follow the guide posted below your post. i wrote it and will get you up and running. follow the links all programs are there you need.you should be flashing nk4 as its the latest tar
Yay! FOllowing those instructions worked. I appreciate it
Related
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_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> 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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
Hi guys,
I rooted my GS4 (SGH-I337 running 4.4.4) but wanted to update it but was receiving an error that said "install interrupted". I then used flashify to flash back to stock firmware that i downloaded from SamMobile. However, after I rebooted the phone, it became stuck on the ATT logo screen. I have tried to use Odin but I get a fail message. Here are the logs:
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried Odin v3.10.6, 3.09, 1.85, 3.07, and 3.04 with the same result. I read in some forums that using a pit file would help, but I receive a fail message using it saying, "Re-partition operation failed".
I have also tried wiping cache partition and factory reset through recovery mode with no success.
Any help would be appreciated, thanks in advance!
-Daniel
Odin Mode
Here is what the phone says on 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
emMMC Burst MODE enabled
START [224,1440]
SW REV. CHECK FAIL : FUSED : 5 Binary : 1
I had/have a virus that persists through all types of recoveries that I could find and try. The virus would install multiple apps and the phone would restart constantly.
I then tried Odin, put the device into download mode (pwr btn, vol dwn, home) and it started saying "downloading... do not turn off target" with a bar that would not move. This was different from what I was expecting from the guides.
I connected the device to my PC and tried to use Odin, loaded up the package? and device was showing connected in odin. The file analysis seemed to work, so I hit start and nothing changed on the device. Odin fails after a few seconds. I then try turn off the device and now comes back with "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" with the same not moving bar.
Top left of this screen is:
Code:
ODIN MODE
PRODUCT NAME: SM-T330
CURRENT BIRNARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE(CSB)
AP SWERV: S1, T1, R1, A1, P1
UDC START
Kies tells me the device is not compatable with Kies.
I'm stuck, please help.
Some Odin output:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T330XXU1ANE8_T330XSA1ANE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
the rom you try to odin is kitkat, if you are coming from lollipop you need to activate the repartition option or you can try to flash android 5. if it still fails msg me.
sub77 said:
the rom you try to odin is kitkat, if you are coming from lollipop you need to activate the repartition option or you can try to flash android 5. if it still fails msg me.
Click to expand...
Click to collapse
I cant turn off the device or do anything. Its stuck on the screen which I described last.
I dont know which version of android was on the device.
I let the tablet die and it came back to the same thing
try different usb cable & ports and if possible try kies recovery from another pc, too.
So I was gifted a Verizon Samsung Galaxy S4. I decided to factory reset it and wipe all data/cache. That was successful and I booted into the phone. I got stuck on the Samsung reactivation lock page. I had trouble logging, and there was an SSL error (caused by the unset date/time). I decided just to flash the stock rom, but this only caused more trouble.
I went into download mode, connected the USB, started Odin (tested with version 3.04, 3.09, 3.10, and 3.12), and tested 3 roms from these two pages:
http://forum.xda-developers.com/showthread.php?t=2289325
http://forum.xda-developers.com/showthread.php?t=2735172
This is the output log:
<ID:0/003> 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/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've used different USB cables, USB ports, versions of Odin, roms, I tried using a pit file, disabling my antivirus, but nothing is working. If I try to boot the phone normally or go to the volume up menu it redirects me to this page: http://androidcentral.us/wp-content/uploads/2013/09/Firmware-upgrade-error.png
Verizon and Kies (they were both off during the Odin flash attempts) are unable to see the phone in download mode and the error page above.
Some additional information. In the top left of the device it displays this:
DOIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: ON
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
and after a failed Odin attempt:
START [224, 1440]
SW REV. CHECK FAIL : fused : 8, Binary: 1
I had a friend give me his cracked S4 and I just swapped out the parts. Everything is working fine now, can a mod close this?
After I rooted my device running Android 7.0, it got stock in a bootloop once rebooted. I have tried to flash different stock ROMs on this device from Samsung so I can recover my phone. Each firmware is an official firmware from Samsung, but all gives the same error when flashing through ODIN.
I have spent over 8 hours on different forums and I haven't found a fix for this. At this time I believe my device is hard bricked, because I have found other issues with the boot.img fail, but this one is for sboot.bin for the Galaxy S6 Edge SM-925i.
I need help please, has anyone found a way to flash and find a workaround for that sboot.bin fail in ODIN?
I already tried to flash other firmwares for the model SM-G925F and for SM-G925A, and they aren't compatibles at all.
Below are the logs from ODIN, regardless of what version of ODIN I use when flashing.
-------------------------------------------------------------
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3727 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
----------------------------------------------------------------
Here is the logs from my phone after a failed flash:
----------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SM-G925I
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
RP SWAEV: B: 4 K :2 S:2
SW REV. CHECK FAIL. DEVICE: 4. BINARY: 3
By the way: Here is a video with the exact error that I posted here. https://youtu.be/N2XoFN4UTns
:crying: Here is a video with the exact error that I keep getting, I am only posting this for help. Thanks a lot for your help. :crying:
https://www.youtube.com/watch?v=N2XoFN4UTns
Your bootloader version on device is newer than that you are trying to flash....find latest firmware for your device and flash with odin and there will be no problem...
Happened to me and solved with this simple method
krokanic said:
Your bootloader version on device is newer than that you are trying to flash....find latest firmware for your device and flash with Odin and there will be no problem...
Happened to me and solved with this simple method
Click to expand...
Click to collapse
i have the same problem Odin stuck at sboot.bin
i flashed the last version and now is stucking at hidden.img`
thats happened when you flash bootloader